Legal
Privacy Policy
What personal data Numes collects, why, who receives it, how long it is kept, and the rights you have over it.
Last updated
This Privacy Policy explains how Floating Point Systems, Inc. ("we", "us") handles personal data when you use Numes: the website, dashboard, chat, documentation, API and provider software (the "Service"). It applies to customers, providers, organization members and visitors.
The short version: we keep the account, payment and request metadata needed to run a marketplace, bill exactly and keep it safe. In production we do not store the content of your prompts or responses, and providers never receive your name, email, account, API key or IP address.
Who is responsible
Floating Point Systems, Inc. is the controller of the personal data described in this policy. Contact us about privacy through [email protected].
When an organization uses the Service, the organization decides who joins and which keys its members use. Questions about how an organization uses its own data should go to that organization.
What we collect
Account and sign-in data
Identity. When you sign in, our identity service records a stable identifier for your login. You can sign in with email and password, passkeys, or a social login (Google, GitHub or Apple, where enabled). For a social login we receive the identifier and email address that provider shares with us.
Profile. Your email address, and optionally your first and last name and a profile picture. Uploaded pictures are resized and stripped of embedded metadata before they are stored.
Security. The sign-in factors you set up, such as passkeys (we keep only their public keys), an authenticator app and recovery codes, and for each active session the browser and operating-system label, sign-in time and last activity.
Email history. The email addresses your account has used, kept encrypted so we can prevent account takeover and resolve disputes about ownership.
Preferences. Whether you agreed to product email (off unless you opt in), and settings you save in the dashboard such as saved views.
Organization and key data
Organization names and handles, memberships and roles, invitations (including the invited email address), API keys and management keys (stored only as keyed digests with display metadata; we cannot recover a key's secret), spending limits and the request policy your organization configures.
Payment data
Card payments are processed by Stripe. We receive and store Stripe's customer and payment identifiers, the amount and status of each payment, and refund or dispute outcomes. We do not receive or store your card number, and we do not keep its last four digits or brand.
Bitcoin payments, where enabled, are recorded with the invoice or address, amount, confirmations and transaction identifiers needed to credit you. Bitcoin transactions are public on their network by design.
Ledger records of every top-up, charge, refund, earning and withdrawal, kept as financial records.
Request metadata
For each API or chat request we record metadata, not content: the model, the provider, endpoint and offer of each attempt, outcome and timing, measured usage and cost, the API key used (by reference), request and generation identifiers, the origin from an HTTP-Referer header (origin only, never the full URL), and the regions you requested and where the request ran. The full list is in Data retention.
Content
In production the Service runs in a metadata-only or zero-retention mode, and we do not store prompts, messages, files, tool arguments or responses. Content passes through our systems only while a request is in flight, including when your organization's request policy inspects or rewrites it. Fields such as user, session and cache identifiers are used for routing only and are not kept.
Dashboard chat conversations and attachments are stored in your own browser, not on our servers.
Support conversations
When you contact support we keep the conversation, encrypted, so we can help you. It is deleted 90 days after the last message.
Provider data
If you become a provider we also process your provider and endpoint names, the data policies and locations you declare, measurements of your endpoints, earnings, and withdrawal records. Where USD payouts are enabled, Stripe collects your identity, tax and bank details for payouts under its own privacy policy; we keep only a reference to your payout account, its status and your country. Credentials for upstream sources you connect are stored encrypted and used only to serve your offers.
Technical and security data
Our servers process your IP address and request headers to deliver the Service and to protect it from abuse, for example for rate limiting and bot protection on sign-in. We do not store client IP addresses with request history. Operational logs and traces are content-free and kept for a short period, about seven days by default. We use Cloudflare Turnstile on password sign-in and registration to tell people from bots.
Cookies and browser storage
We use cookies and browser storage that are necessary to sign you in and run the Service, and we do not use advertising or analytics cookies. See the Cookie Policy.
How we use personal data
| Purpose | Data | Legal basis (where GDPR applies) |
|---|---|---|
| Create and secure your account, sign you in | Account, sign-in, security data | Performance of our contract with you |
| Route, serve and meter requests | Request metadata, content in transit | Performance of contract |
| Take payments, bill exactly, pay providers | Payment data, ledger, request metadata | Performance of contract; legal obligation (accounting and tax) |
| Prevent fraud, abuse and attacks; enforce our terms | Technical, security, payment and request metadata | Legitimate interests in a safe, trustworthy marketplace |
| Verify providers and measure endpoints | Provider data, request metadata | Legitimate interests |
| Provide support | Support conversations, account data | Performance of contract; legitimate interests |
| Send service and security email | Email address | Performance of contract |
| Send product news | Email address | Your consent, which you can withdraw in Profile |
| Comply with law, respond to lawful requests | As required | Legal obligation |
We do not sell your personal data, and we do not use your prompts or responses to train models.
Who receives personal data
Providers
The provider that serves a request receives the content needed to serve it: messages and media, tool definitions and sampling settings, plus an opaque routing hint. Providers do not receive your name, email address, account or organization, API key, the user field, your referrer or your IP address. Media you reference by URL is fetched by us, so providers never contact your URL.
Each provider handles content according to the data policy it declared for its endpoint: whether it collects data, how long it retains it, and where it runs. You can restrict routing to endpoints that do not collect data, that retain nothing, or that run in particular regions. See Provider data policies. Providers are independent; where a provider processes content beyond serving your request, it does so as its own controller under its declared policy.
For encrypted models, where enabled, your request is encrypted on your device to an attested secure enclave. We and the provider relay only ciphertext and see the model, timing, sizes and usage counts, not the content. See Encrypted inference.
Service providers (processors)
We use the following categories of service providers, each under contract to process data only on our instructions:
| Service provider | Purpose |
|---|---|
| Stripe | Card payments, refunds and disputes; provider payouts and payout identity checks where enabled |
| Resend | Sending transactional email |
| Cloudflare | Object storage for profile pictures and encrypted backups; bot protection on sign-in |
| Breez (Spark) | Bitcoin and Lightning payment infrastructure, where enabled |
| Tinfoil | Secure-enclave inference for encrypted models, where enabled |
| Hosting and infrastructure providers | Running our servers, databases and backups |
Identity providers you choose for social login (Google, GitHub, Apple) receive the sign-in request you start with them. Upstream model services used by a provider's hosted source receive request content as described above, as processors or independent controllers under their own terms.
Others
Organization administrators can see the members, keys, usage and activity of their organization.
Authorities, when we are legally required to disclose data, or when disclosure is necessary to protect the rights, safety or property of users, providers, us or the public.
A successor, if we are involved in a merger, acquisition or sale of assets, subject to this policy.
International transfers
We and our service providers may process personal data in countries other than yours, including the United States. Where the law requires it, we protect transfers with appropriate safeguards such as the European Commission's standard contractual clauses. Provider endpoints run in the locations they declare; use region routing if location matters to you.
How long we keep data
| Data | Retention |
|---|---|
| Account and profile | Until you delete your account |
| Email address history | Kept encrypted after account deletion, to prevent takeover and resolve ownership disputes |
| Request metadata and ledger records | Kept as financial and integrity records for as long as needed for accounting, tax, dispute and fraud purposes |
| Activity charts | Five-minute detail for 7 days, hourly for 90 days, daily for one year |
| Support conversations | Deleted 90 days after the last message |
| Operational logs and traces | About 7 days |
| Prompt and response content | Not stored in production |
Account deletion
You can delete your account in Profile after confirming it is you. Deletion erases your name, email address, profile picture, consent, saved views and support conversations, and revokes your keys. Ledger, request metadata and audit records are kept as described above, without your profile details, and your encrypted email history is retained. Deletion is blocked while you are the sole owner of an organization, hold a balance or earnings, or have operations in progress.
Security
We protect data with encryption in transit, encryption of sensitive fields at rest, keyed digests for keys and credentials, strict access controls, audited administrative actions and content-free logging. No system is perfectly secure; if a breach affects your personal data, we will notify you and the authorities as the law requires.
Your rights
Depending on where you live, you may have the right to access, correct, delete, restrict or object to processing of your personal data, to receive a copy of it in a portable format, and to withdraw consent at any time. Residents of some US states have similar rights, including the right to know what we collect and the right not to be discriminated against for exercising privacy rights. We do not sell or share personal data for cross-context behavioral advertising.
You can update your profile and delete your account in the dashboard. For any other request, contact us through [email protected]. We will verify your identity and respond within the time the law requires. If you are in the EU, the UK or Switzerland, you can also complain to your local data protection authority.
Children
The Service is not directed to children and is not available to anyone under 18. We do not knowingly collect personal data from children. If you believe a child has given us personal data, contact us and we will delete it.
Changes to this policy
We will post changes on this page with a new "Last updated" date, and we will notify you by email or in the dashboard before material changes take effect.
Contact
Privacy questions and requests: [email protected].