Docs / More
Request data privacy
Cent AI does not store the content of successful requests by default. Failed requests are kept as encrypted error records for 30 days. You can turn on 24-hour content storage per key.
Last updated
Content of successful requests is not stored by default
For a request that succeeds, the prompts you send and the answers you get back are not stored. Cent AI passes the request to the model, streams the answer back to you and keeps only the data needed to bill the request and show it to you.
This is the default for every key. Nothing needs to be turned off.
Failed requests: error records
When a request does not end successfully, Cent AI keeps a full error record so the cause can be found and fixed. A request also gets a record when it succeeds only after a model provider attempt failed.
| Error record | |
|---|---|
| Which requests | Every failed request to /v1/*, the Usage API (/v1/organization/*) and Playground runs. Dashboard and sign-in pages are not recorded |
| Content | The request as received, including headers, your API key or management key and your IP address; the body; each model provider attempt and its answer; what was sent back to you. Errors created by our edge server: selected headers and the request size, no body |
| Protection | Encrypted. Readable only by Cent AI operators; every opening is logged. Never used for training |
| How long | 30 days, then deleted automatically. Deleting your account does not delete them earlier |
Successful requests that needed no retry are not recorded.
What is kept for every request
Cent AI keeps metadata for each request. It keeps content only for failed requests (above) or when you turn it on (below):
| Kept | Examples | How long |
|---|---|---|
| Request details | Request ID, time, key, project, model, status, duration | 90 days in detail |
| Usage and cost | Tokens per rate, rates used, usage.cost | 90 days in detail; daily totals per model, key and project are kept permanently |
| Charges | The charge to your balance | Permanently, as part of your balance history |
| IP address | A keyed hash of the address, not the address itself | Used for abuse signals and the activity log of a key |
This is what you see on the Requests and Usage pages of the dashboard.
Opt-in: keep content for 24 hours
You can turn on content storage for one key in Keys, in the key's settings: "Keep request and response content for 24 hours".
| Off (default) | On | |
|---|---|---|
| Prompt and answer | Not stored | Stored encrypted for 24 hours, then deleted |
| Requests page | Metadata only | Metadata, and the content of each request while it is less than 24 hours old |
The setting applies per key, so you can keep it on for a test key and off for a production key. It applies to requests made while it is on.
What logs contain
Cent AI's logs never contain the request or response body, the Authorization or x-api-key header, or your key. Error records are stored separately from logs. They contain the request ID, key and account IDs, the public model name, status, duration, tokens and cost.
Playground
Playground chats are not saved. Leaving the page clears the chat. A Playground run that fails gets an error record like an API request. Playground runs are billed like API requests and appear on the Requests page with their metadata. See Playground.
Full policy
How Cent AI handles personal data, including your account data and your rights, is described in the Privacy Policy.