Zero retention
Every model served by zdr.sh runs under a zero-retention agreement. That agreement is a condition of the service, not a setting: the same promise holds on every model and every key.
One rule, every route#
There is nothing to choose, so there is no retention switch to find. There is no region selector, no per-key or per-request retention setting, no zero-retention model variant and no header that asks for one. A model id is just the model id: glm-5.3 is glm-5.3 on every key.
A model is offered only while its serving meets the agreement. Models lists what is served today.
What is not stored#
- The request and the answer. No prompt, file, image or generated text is written to a store of ours. There is no trace system, no traffic sample kept for quality and no dataset built from requests, so there is no opt-out to look for.
- The logs. A request leaves a line with its id, the account, the key, the model, the token counts, the latency, the cost, the status and the time. The body of the request and the body of the answer are not in it.
- The serving side. The agreement obliges the provider not to retain the request or the answer once it has been served.
Two things a request can carry are kept on its usage row because they are yours to analyse and not content: the end-user id and the metadata entries the client sent. Neither is forwarded to a model. Chat completions has the fields.
The three places text can rest#
Three features hold text on purpose, and each is a choice rather than a default:
| Where | What it holds | For how long |
|---|---|---|
| Memory vault | The notes you write to it yourself | Until you delete them |
| Response cache | An answer to an exact repeat, when a key turns the cache on | Ten minutes |
| Idempotency replay | The answer to a request sent with an Idempotency-Key, so a retry is answered once | 24 hours from settlement |
None of the three is a record of traffic: nothing enters them unless a key asks for it, and none is read to train, score or review a model. Optimizations describes the cache, and Chat completions the idempotency key.
The web tools are not model routes#
A search sends the query to the search service, and a browse is read by the platform's own reader. Neither keeps the text on this platform. The web search and web browse pages say what each one sends and keeps.
If that ever changes#
Retention is not a setting a customer can turn on or off, so a change to it would be a change to the product, and a model that could not meet the agreement would leave the list rather than serve under a weaker promise. The privacy policy states what is processed, why and for how long.