Policies
Privacy and data retention
A summary for developers. The privacy policy is the authoritative text.
What the gateway stores
- Keys: a hash of each key secret, its name and its balance.
- Holds: the amount reserved while a request is in flight.
- Credits: top-ups and their payment references.
- Receipts: ids, time, endpoint, model, token counts, price version, charge, provider, upstream request id and a SHA-256 of the output. Never the text.
What it never keeps
- Prompts and outputs: they pass through memory only and are not written to the database or logs.
- Your IP address on forwarded requests: the provider sees the gateway's address. Your IP is used in memory for rate limits and location checks.
- Your wallet address at login.
In transit
While a request is in transit the gateway sees its content, your IP address and timing, and the provider that serves it sees content and timing. Each provider's own data practices apply; the privacy policy lists them.
For prepaid keys, user, safety_identifier, metadata and the x-abliteration-session-id header are forwarded to the provider.
How long records are kept
| Record | Kept |
|---|---|
| Your IP address | In memory only, in rate-limit windows of up to an hour |
| Passkey challenges | 5 minutes |
| Console sessions | 30 days |
| Refusal and moderation records | 7 days |
| Safety classifier verdicts | 30 days (longer under a legal hold); self-harm flags are not stored |
| Support conversations | 365 days after the last message, or until the key is deleted |
| Keys, balances, receipts, payment references | As records, until deleted or detached when no longer needed |
Cookies
The site sets no cookies of its own and runs no analytics or advertising trackers. The console stores your theme choice and, for the life of a tab, your passkey session in your browser.
Last updated