What we store about an API request
We keep one line per request with the model, tokens and cost. We don’t store your prompts or the answers.
Il centro assistenza è scritto in inglese e in olandese. Stai leggendo la versione inglese.
What we store per request
- The time, the request ID and the workspace.
- The key that sent it (or the playground), the endpoint, the model and the lane.
- The number of input, output and cached tokens, and the cost.
- The status code, how long it took, whether it was streamed and, if it failed, an error code.
- Internal details about how we routed the request, for our own administration. They never contain your prompt or the answer.
Except for the internal details, that’s what you see in your usage log and the CSV export, and what we need for your balance and invoices.
What we don’t store
- The content of your prompts: messages, system prompts, files or images.
- The content of the answers.
- Your playground chats. They live only in your browser tab and are gone when you leave or reload the page. Each answer is charged and listed in your usage, like any other request.
- Your API keys themselves. We keep a fingerprint and the first and last characters, so we can recognize a key but never show it again.
To answer a request, we route it to the model provider. How long we keep data and how it’s handled is in our Privacy policy.
What else we keep
- Your account: name and email address, and for each session the browser and IP address, which you see under Settings › Where you’re signed in.
- Billing details, payments and invoices. We keep invoices and payments for 7 years, as the law requires.
- Help conversations: what you write to Miles or a colleague in Help is saved, so a colleague can read it and reply.