Legal
Privacy
We do not store the contents of your requests or of the model’s replies — not for debugging and not for analytics. This is a property of the system rather than a promise of goodwill: bodies stream through the gateway and settle nowhere.
What stays in the database
- the model, the four token counters or the number of frames, and the charge for each request;
- the latency, the timestamp, and which of your keys was used.
One exception, and it is about someone else’s text rather than yours: when the upstream provider refuses a request, the text of that refusal is kept against our own upstream account and in the server log, because otherwise the cause cannot be established afterwards. Your own request text goes into neither.
The honest flip side: because contents are not stored, there is nothing to produce in a billing dispute except the counters. That is why every line of your log carries its four counters and its charge, and why the billing section of the documentation shows the arithmetic behind each line.
Where your requests go
- To the upstream that serves the models — there is no other way to answer them. Their data-handling rules apply on their side, and we do not influence them.
- Nowhere else. The site carries no third-party analytics, visitor counters or advertising scripts at all: open it with JavaScript disabled and you see exactly the same thing.
- Your keys are yours to manage. Create several — one per project or machine — and revoke any of them in the account area; a revoked key stops working at once. The keys page shows each key’s spend for the last 30 days and when it was last used, so a leaked key gives itself away.
- Terms of service are on the terms page. Questions — write to support.