Data collection
What is recorded per request, and why prompts and responses are not stored unless you turn on capture.
We do not store your prompts or the model's responses. Not encrypted, not for a short window. The request body is forwarded to the provider and never written to our database. The single exception is request capture, which stores bodies only for a key whose owner has explicitly turned it on, and only for the retention window that key chose.
What we do record, per request, is the metadata needed to bill you and show you your own usage:
- Which model and provider handled it
- Response status and latency
- Token counts in and out, and the resulting cost
- Timestamp, and which of your keys was used
Account records hold your email, name and an optional organisation. Sign in events hold IP, the city and country derived from it, and the browser user agent, kept as a security trail. Prompt storage exists only as the opt-in request capture above, off unless a key's owner turns it on. The full detail is in the privacy policy.