Privacy Policy
This Policy explains how Flotera Inc. handles personal information through its website, GPU server management panel, installed server agent, APIs, support, and optional integrations. For privacy requests, email privacy@flotera.com.
Scope and privacy roles
Flotera Inc., a Delaware corporation ("Flotera," "we," "us," or "our"), provides software for operators managing their GPU servers: the website, management panel, installed server agent, APIs, documentation, support, and optional marketplace and AI integrations (the "Service"). Marketplaces handle renter payments, payouts, and marketplace fees under their own terms. Flotera billing is separate.
This Policy applies to personal information for which Flotera determines the purposes and means of processing, including website, account administration, business communications, and security purposes. Where we process personal information solely on a customer's instructions, our role depends on that processing and the applicable contract and law; the customer's notice also applies. This Policy does not itself create a data processing agreement.
Operating a server that runs AI workloads is not the same as submitting those workloads to Flotera. Information you send for support, including diagnostic attachments, may contain customer or renter content. Do not include unnecessary personal information or secrets. Independent marketplaces and AI providers have their own privacy notices.
Information we collect
The information depends on the features you use. Server and marketplace records can be personal information when linked to an identifiable person, even when they primarily describe hardware or a business. Product account fields are separate from optional website contact-form fields.
| Category | Information and purpose |
|---|---|
| Account and access | Product account email address, password stored as an Argon2id hash, account name, language, time zone and last sign-in time. The product account does not ask for a personal name, phone, company or address and does not use two-factor sign-in. We also process API access tokens, permissions and integration credentials you provide to enable access and connections. |
| Server agent and fleet | Hostname used as the server name, hardware and system details, GPU readings, host readings, availability, rental state, readiness checks and permitted command activity used to monitor and manage your fleet. The agent reports only whether the server is rented and the marketplace name; it determines that state from container names on the server without sending the names. Hardware and system details can include CPU model and cores, RAM, disk models and sizes, mount paths, OS, kernel, NVIDIA driver and CUDA versions, motherboard vendor, model and BIOS version, network interface name and link speed. GPU readings can include model, memory, utilization, temperatures, fan, power and limits, clocks, throttling and PCIe link. Host readings can include CPU load, RAM, volume usage, network traffic totals, uptime and power draw. |
| Network checks | A network check records public IP address, local IP address, NAT type, latency and reachable ports against a Flotera endpoint. Flotera starts this check about every 6 hours for servers linked to a marketplace, and you can start it from the panel. |
| Marketplace software and readiness | Whether each marketplace's own agent is installed and running, marketplace agent versions, the Vast.ai port range, a short hash of the machine ID file rather than the full machine ID, Docker setup, automatic OS updates, SSH, CPU flags and similar readiness facts. |
| Driver errors, logs, meters and commands | NVIDIA driver Xid data, including the error number, GPU address and the full driver line, which can include a process ID. On your request, the agent can return up to 1,000 lines from the system journal. If you set up a supported smart plug, Flotera processes its readings; on request, the agent can search the local network and report the smart plug local IP address and name. Command records include what was asked, by whom and the outcome. |
| Marketplace connections | Marketplace API keys you supply and marketplace records used for management, pricing and earnings views. Vast.ai account ID, username, email, balance and host flag. Clore.ai wallets and holding balance. QuickPod account ID, user type and commission. Machine records can include machine hostname, public IP address, reliability and earnings. Listing and rental fields can include prices, listing state, rental type, price, GPU count, start and end. Flotera reads earnings per server per day, but not payout or bank details. Flotera's own structured records are not designed to hold renter identity. The raw Vast.ai machine record is stored as received and may include identifier fields supplied by Vast.ai, including any renter identifier included in that record. |
| Market price data | Clore.ai prices come from public data and are shared across customers. Vast.ai and QuickPod market data is read with each customer's own key, kept for that customer for 90 days and not shared with other customers. |
| Flotera billing | Your plan, managed-server usage, wallet balance, top-ups, charge history, payment provider IDs and status history used to calculate and administer Flotera fees. Card, email and billing details are entered directly at Stripe; Flotera does not receive card numbers. Flotera stores top-up amount, status and time, Stripe session and payment IDs, and payment status history. Incoming Stripe notifications are reduced to those fields before storage; payer email, name, address, phone and card details are dropped. These records are distinct from marketplace renter payments and payouts. |
| MCP access and actions | Enabled tools, server scope, connected-client access and action records. Authorized tool results can include server health, rentals, market prices, and pricing rules. |
| Security and access records | Security audit records include keyed hashes of IP addresses and browser information. Web server access logs include raw IP addresses and browser information. Sign-in session records contain a hash of the browser string rather than an IP address. Rate limits use part of the IP address and a hash of the email. See the retention and browser-storage disclosures below. |
| Website activity | Browser and network information, such as IP address, browser details and page requests, processed when delivering website resources, measuring use, and checking for abuse. Cookies and third-party requests are described below. |
| Messages, support and notifications | Information you send, including work email, optional website-contact name, company, phone, fleet size, region, questions and diagnostic material. Recruitment inquiries may include professional details or a resume you choose to provide. If you opt in to Telegram notifications, Flotera processes the Telegram chat ID and message content, which can include server names, prices, balances and alerts. Product email is sent from no-reply@flotera.com with replies to support@flotera.com. |
| Referrals | Referral records can include the inviter, invitee sign-up date, status and progress toward the qualifying activity. The inviting host sees a masked email using the first character, three asterisks and the full domain. The invited host does not see inviter information. The referral code is kept in session storage until sign-up. Referral records can remain after account deletion, but the masked email is removed. |
Credentials are not merely key metadata: connecting a marketplace involves providing its API key. Flotera's servers decrypt and use the key for marketplace calls. For some Vast.ai and Clore.ai read requests, Flotera sends the key sealed so only your own server can open it, and the agent keeps it in memory only. Keep permissions limited to what is needed. Removing access in Flotera and revoking a credential with its issuer are separate actions.
The agent's automatic telemetry is not designed to collect MAC addresses, full machine IDs, hardware serial numbers, disk SMART attributes, full process lists, container names or images, renter identities or workload contents. This statement is about automatic agent telemetry, not support material you choose to send, raw marketplace records, logs requested by you or information handled by marketplaces and AI clients.
Where information comes from
- From you: account setup, server and integration configuration, payments for Flotera, messages, and support material.
- From your systems: the installed server agent, authorized API and MCP activity, and your browser.
- From connected services: marketplaces you connect, the payment provider (payment IDs and status), Telegram when connected (chat ID), and the network provider (anti-bot signals), as well as the website providers described below.
- From your organization: administrators and colleagues who manage your access or provide information in a business relationship.
How we use information
- Provide fleet monitoring, earnings views, permitted server and listing actions, and configured notifications.
- Administer accounts, permissions, integrations, and Flotera billing.
- Diagnose problems, respond to support and privacy requests, and improve service reliability and usability.
- Protect the Service against abuse and unauthorized access.
- Respond to business and recruitment inquiries and send marketing where permitted, subject to your choices.
- Maintain required business records, comply with applicable law, resolve disputes, and enforce our Terms of Use.
Possible future AI model development and training is described in Section 7, separately from operating the Service.
AI assistants and automation
The installed server agent collects readings and executes permitted server commands. An AI assistant connected through MCP is a separate client that you choose and authorize. Information returned by enabled tools for permitted servers may be received by that client and its provider, including fleet health, rental information, prices, and pricing rules.
Review the client's privacy terms, retention and training settings, and the permissions you grant. Enabling Write mode and individual write tools permits changes without a separate confirmation for every call. Review your server scope and action log, and disable access you no longer need. See the MCP documentation for supported actions and access controls.
The Flotera panel, API and installed agent do not use an AI provider to process customer data as part of their own product functions. The AI-client route is the MCP connection you choose and authorize, through which your client receives enabled tool results. Price suggestions come from fixed rules, not from an AI model. We may develop or improve AI models using information where permitted by applicable law and our agreements. Before using Customer Data to train general-purpose models or train or fine-tune a service-specific model, we will describe the proposed use and obtain your separate express agreement. Data collected under an express-agreement requirement will not be used for that purpose without that agreement. Connecting an external AI client does not by itself authorize Flotera to use its inputs or results for training.
These conditions govern Flotera's use, including training undertaken on its behalf. An independently chosen client's or AI provider's use of information you allow it to receive is governed by its own terms and privacy practices.
Automated operational actions, such as permitted listing-price or power-limit changes, are distinct from decisions about individuals with legal or similarly significant effects. Where applicable law provides rights concerning such decisions, including human review or contesting a decision, you may exercise them through the privacy contact below.
Data retention
Retention depends on the information and why it is needed. Product history limits control what the panel shows; for example, Pro's 180-day history is a display limit, not a storage-retention period. Where no fixed period is specified below, the relevant purposes and legal obligations are described in the retention criteria following the table. An absence of automatic deletion is identified separately from those criteria.
| Data | Retention |
|---|---|
| Detailed server and GPU readings | 7 days |
| 5-minute averages | 90 days |
| Hourly averages, online/offline history and alert history | 400 days |
| Agent events, including driver errors | 365 days |
| History of command status changes | 6 months |
| Command output logs | 7 days |
| Per-customer marketplace price data | 90 days, or earlier when the marketplace is disconnected |
| Sign-up and password-reset codes | 24 hours after they expire |
| Server records, command records and network check results | Until the account is erased |
| Marketplace key and account data | Until the marketplace is disconnected or the account is erased; stored marketplace keys are deleted immediately when account deletion is requested |
| Earnings history | Until the account is erased |
| Sign-in sessions | 30 days at most in use; records stay until the account is erased |
| Billing, payment and referral records | No automatic deletion period is implemented |
| Security audit log | No automatic deletion period is implemented. IP address and browser are stored as keyed hashes. |
| Web server access log | The log contains raw IP addresses and browser information; it is size-limited and rotates as it fills |
| First backup copy | 3 days |
| Second encrypted off-site backup | Up to about 3 months |
For records without a fixed deletion period, relevant retention criteria include:
- Billing, payment and referral records: accounting, tax and other legal requirements and applicable claim periods; administering credits and resolving disputes.
- Telegram connection identifiers and raw marketplace records: providing the connected notification or marketplace service, handling disconnection and account-deletion requests, and applicable legal obligations. The retention of independently held provider copies follows that provider's practices.
- Messages and diagnostic material: resolving the inquiry and any related follow-up or dispute, including support and business emails.
- Website and security records: service delivery, measurement, abuse investigation and operational need. Contact-form responses are kept for handling the inquiry and related follow-up or dispute.
A privacy deletion request is different from removing a server or disconnecting an integration. Legal obligations, disputes, fraud investigations, or legal holds may require some records to be retained. Deletion from active systems does not necessarily immediately remove backup copies.
The account owner can delete the account in the panel after removing all servers. At once, sign-ins, API tokens and AI-client access are revoked, and stored marketplace keys are deleted. For 30 days after deletion, you can ask support to restore the account. After 30 days, fleet data, activity, earnings history and telemetry are erased, and email addresses are replaced with a placeholder. Billing, payment and referral records and the audit log are excluded from that account-erasure job. Backups are not edited for individual account deletion; they age out on the backup schedule above.
Copies held independently by marketplaces or AI providers are governed by those providers' practices. A request to Flotera does not itself delete those copies. We assess deletion requests and any exceptions within the requirements of applicable law.
Security
Protecting personal information involves administrative and technical safeguards appropriate to the information and processing. No internet service or storage system is completely secure, so we cannot guarantee absolute security.
Protect your credentials and systems, limit integration permissions, and avoid including secrets or unnecessary renter content in support material. Report suspected security issues to security@flotera.com. Incident notification duties depend on applicable law and contractual commitments. Service and security communications are separate from optional marketing.
International data transfers
Production servers and the first backup copy are in France. A second encrypted backup copy is in Bulgaria. Flotera is a U.S. company, and our staff work in the United States and Bulgaria. Authorized staff may access personal information from those countries to operate and support the Service. Email delivery, payment, network and security, and business email providers may process information in the United States or other countries. Information may also be processed in or accessed from other countries involved in providing the Service or the third-party services you use. Those countries may have different data protection laws.
Where EEA, UK, Swiss, or other applicable law restricts an international transfer, that transfer requires an applicable legal basis and, where necessary, safeguards. The relevant requirements depend on the countries, parties and processing involved. This Policy is not consent to an international transfer or a substitute for required safeguards. Contact privacy@flotera.com to ask about destinations and arrangements relevant to your information.
Your privacy rights and choices
Depending on where you live and subject to exceptions, you may have rights to:
- know whether and how we process your personal information;
- access or receive a portable copy of personal information;
- correct inaccurate information;
- delete information;
- restrict or object to processing;
- withdraw consent without affecting prior lawful processing;
- opt out of targeted advertising, sale, sharing, or certain profiling;
- appeal our denial of a request; and
- complain to a data protection authority.
To exercise a right, email privacy@flotera.com and describe your request and jurisdiction. We may verify your identity and authority using information appropriate to the request. Authorized agents may submit requests where permitted, but we may require proof of authorization and direct verification with you.
Account owners can also delete their account in the panel after removing all servers, as described in Section 8. That account-deletion process is separate from a privacy rights request.
We will not discriminate against you for exercising a privacy right. You can ask us to stop marketing emails, or use an unsubscribe link where provided. You may still receive transactional and service communications.
U.S. state privacy notice
State privacy rights apply to the extent the relevant law covers Flotera and the processing involved. See Sections 2 through 7 for information about categories, sources, purposes, and recipients.
Current website disclosures include browser and network information sent when optional Google Tag Manager, Google Analytics, Meta Pixel, reCAPTCHA, or Fonts resources load, and contact responses submitted to Google Forms. Whether optional measurement or advertising tag disclosure is legally a sale, sharing, or targeted advertising depends on actual use, provider terms, settings, and applicable law; the presence of a tag manager or analytics script alone does not establish that classification.
Where applicable, you may request access, correction, deletion, portability, information about collection and disclosure, and opt out of sale, sharing, targeted advertising, or certain profiling. California law may also provide rights to limit certain uses of sensitive personal information and rights concerning third-party direct marketing disclosures. We do not knowingly sell or share personal information of people under 16.
Send an opt-out request to privacy@flotera.com. See the website controls and remaining GPC limitations. To appeal a denied request where an appeal right applies, reply to the decision and state that you wish to appeal.
European Economic Area, Switzerland, and United Kingdom
Where the EU or UK GDPR applies to processing for which Flotera is controller, the purpose and relationship determine the applicable legal basis. Swiss law has its own requirements; this table does not treat all three legal systems as identical.
| Purpose | Basis where applicable |
|---|---|
| Provide an individual's contracted service, account, support, or Flotera billing | Contract necessity or steps the individual requests before entering a contract. A contract with an employer is not automatically a contract with its employee. |
| Administer organizational accounts and business relationships; secure, maintain, and improve the Service | Legitimate interests in administering the relationship and providing a reliable and secure service, where not overridden by the individual's rights and interests. |
| Keep legally required records and respond to binding legal requirements | Compliance with an applicable legal obligation. |
| Optional tracking or marketing requiring permission | Consent where required, with a right to withdraw. Section 6 describes the website's optional Analytics and Marketing consent controls and their limits; this row does not assert consent for other processing. |
| Handle disputes and legal claims | Legitimate interests in establishing, exercising, or defending claims, or an applicable legal obligation. |
You may object to processing based on legitimate interests and withdraw consent without affecting prior lawful processing. You may complain to an authority where applicable, including the EEA supervisory authorities or the UK Information Commissioner's Office. Contact us about processing roles, applicable data-processing terms, or representative details relevant to your request.
Additional regional information
Canada
Where Canadian privacy law applies, you may request access to or correction of personal information and withdraw consent, subject to legal limits. You may complain to the Office of the Privacy Commissioner of Canada or an applicable provincial authority.
Brazil
Individuals covered by Brazil's LGPD may have rights to confirmation, access, correction, anonymization, restriction, portability, deletion, information about sharing, consent withdrawal, review of certain automated decisions, and complaint to the ANPD, subject to law.
Australia and New Zealand
Where the respective privacy law applies, you may request access to or correction of personal information and complain to us. If unresolved, you may contact the Office of the Australian Information Commissioner or New Zealand Office of the Privacy Commissioner, as applicable.
Other jurisdictions
We honor rights available under applicable privacy law, including in jurisdictions across Asia-Pacific, Latin America, the Middle East, and Africa. Contact us so we can assess and respond under the law that applies to you.
Children
The Service is designed for businesses and adults and is not directed to children under 18. We do not knowingly collect personal information from children in violation of law. If you believe a child has provided personal information, contact us and we will take appropriate steps.
Changes to this Policy
We may update this Policy to reflect changes in the Service, law, or our practices. We will post the updated version and revise the effective date. If changes are material, we will provide additional notice when required, such as by email or through the Service.
Contact us
Flotera Inc.
Delaware, United States
privacy@flotera.com
For security reports, contact security@flotera.com. For other legal questions, contact legal@flotera.com.