Account
Privacy
What the API keeps, and what it never does. The same for the three formats.
| Data | Kept? |
|---|---|
| Prompts and responses | No. Processed in memory, then discarded. |
| IP addresses | No. Our servers never receive them. |
| Email, name, password | No. There are none. |
| Per-request records | No. |
| Daily token totals per model | Yes, for billing. |
| Balance and invoices | Yes. |
| Saved chat conversations | Only encrypted, with a key that never leaves your browser. Titles and dates are encrypted too: the one thing kept in clear is the month of the last save, so that a conversation inactive for 12 months can be deleted. |
The API is stateless
API requests are not saved anywhere: if you want a history, keep it on your side. Only conversations from the browser chat are stored, and only as ciphertext.
In transit
Traffic reaches us through Cloudflare, which shields the service from attacks. Like any such network, it decrypts requests while passing them on: it is set not to forward visitors' IP addresses to us, and we keep none.
Your account ID
The account ID never reaches our servers either: the browser derives a separate login secret from it, and we store a hash of that. This is why a lost ID cannot be recovered.