Zero data retention

Retention depends on the model used for each answer

Retention status and the credentials gateEach answer is routed to a model and ends up in one of three retention states. Zero data retention means the request asks for it and the recipient enforces it, and it fails with an error if no provider can meet it. A provider statement means Featherless says it does not store prompts, which ZeroLog does not enforce. No statement recorded covers every other route. The status is shown with the answer. A chat that holds credentials runs on an enforced route or on a provider with a recorded written commitment, and is otherwise refused unless you allow it for that chat.none availableenforced, or providerstatement on fileno statementAnswer is routedto a modelZero data retentionrequest asks, recipientenforces (OpenRouter pool)Provider statementFeatherless says it doesnot store; not enforcedNo statement recordedall other routesStatus shownwith the answerChat holds credentials?RunsRefused, nothing sentunless you allow itfor this chatNo provider can meet it:error, no fallback
Three retention states are shown per answer, and a chat with credentials is refused on a route with no confirmed commitment.
Diagram as text
  1. Each answer is routed to a model.
  2. Zero data retention: the request asks for it explicitly and the recipient enforces it (models served through the OpenRouter pool). If no provider can meet it, the answer fails with an error and is not sent elsewhere.
  3. Provider statement: Featherless states generally that it does not store prompts or replies. This is the provider's statement and is not enforced by ZeroLog.
  4. No statement recorded: every other route.
  5. The status appears with the answer.
  6. A chat that holds credentials runs on an enforced route, or on a provider statement backed by a written commitment on file (Featherless, 28 September 2026). On any other route it is refused and nothing is sent, unless you allow it manually for that chat.

ZeroLog shows whether zero data retention was enforced for an answer, stated generally by the provider, or not guaranteed.

Where it stands today

Check what applies to each answer
Your conversation Status shown

The conversation shows the retention status for the model that answered.

After the answer Review

The retention status appears with the answer. Review it before sharing sensitive information.

Provider statements

A provider’s general statement does not confirm how a particular request was handled. Check the status in the chat transcript.

The three statuses

Zero data retention: the request asks for it explicitly and the recipient enforces it. This applies to models served through the OpenRouter pool. If no provider can meet the request, the answer fails with “No zero-data-retention provider available for this model” instead of going elsewhere.

Provider statement: Featherless states generally that it does not store prompts or replies. No retention control is sent with each request, so this is the provider’s statement and not something ZeroLog enforces.

No statement recorded: for every other route, ZeroLog has no non-retention statement on file. The chat says so.

With an automatic model choice, the status is the one for the model that answered. Anonymous chats and chats with credentials both ask for zero-data-retention routing.

The chat transcript identifies the provider and its retention status for the route that answered.

A chat that holds credentials is stricter: it is refused, without any network call, on a route whose zero-data-retention commitment is not confirmed, and it never falls back to another provider. Featherless counts as confirmed through its written commitment of 28 September 2026, which is the provider’s statement and not enforced by ZeroLog. You can allow such a chat manually for one chat; the chat then shows that the override is active.