Privacy Policy

The short version

We keep what is needed to run an account and bill it: who you are, which keys you hold, and how much each request cost. We do not store the prompts you send or the responses you receive. We do not sell your data, and we run no advertising.

What we collect

• Account. Your email address and name. If you sign in with Google, we receive those from Google along with whether the address is verified; we never see your Google password. If you set a password with us instead, we store only a bcrypt hash of it.
• API keys. A key's name and the limits you set on it, a SHA-256 hash used to authenticate requests, and — so the console can show you a key you have mislaid — a copy encrypted with AES-256-GCM.
• Usage records. For each request: the model and provider it was routed to, input and output token counts, the cost charged, how long it took, whether it succeeded, and a request identifier. These records carry no prompt or response content.
• Billing. Your credit balance, top-ups, adjustments and invoices. Card details, where payment is taken, are handled by the payment provider and never reach our servers.
• Referrals. If you arrived through a reseller's referral code, we record that attribution and the commission it accrues.
• Operational logs. Ordinary web server logs, which include IP addresses and request lines, kept for security and debugging.

What happens to the content you send

RunToken is a gateway. When you call /v1/chat/completions, your messages are forwarded to the upstream provider your request routes to — OpenAI, Anthropic, or a self-hosted deployment — and their response is passed back to you. That provider receives your content and handles it under their own terms and privacy policy. We pass it through and record only the metering fields listed above.

Why we hold it

To authenticate your requests, to route and price them, to charge your balance and produce invoices, to show you your own usage, to pay referral commissions where they are owed, and to keep the service secure and working.

Who else sees it

• Upstream model providers, for the content of requests routed to them.
• Our payment provider, for the payment itself.
• Our hosting provider, which runs the servers the service sits on.

We disclose data otherwise only where the law requires it. We do not sell it or share it for advertising.

How long we keep it

Account, key and billing records are kept while your account exists, and afterwards for as long as accounting and tax obligations require. Usage records are kept so that you and we can reconcile what was billed. Server logs are kept for a short operational period.

Security

Traffic is served over TLS. API keys are stored as hashes for authentication; the recoverable copy is encrypted at rest with a key held outside the database. Passwords, where used, are stored only as bcrypt hashes. No system is perfect, and we do not claim otherwise.

Your choices

You can revoke or delete any API key from the console at any time, which stops it working immediately. Write to us to ask what we hold about you, to correct it, or to close your account and have its personal data deleted, subject to the accounting records we are required to keep.

Changes

If this policy changes materially, we will update the date at the top of this page and, where the change affects you, tell account holders by email.

Contact

Questions about this policy, or about data we hold: support@ontosphere.ai.