AI vendors and your data

Vendors146Answers427

146 vendors · 427 answers

Zero Data Retention changed OpenRouter, Nov 9, 2026

OpenRouter · Nov 9, 2026 · 13 added, 4 removed · seen by the weekly check

The pageAll OpenRouter terms
  1. Added: Zero Data Retention (ZDR) means no routine storage of prompts or responses after processing, apart from the CSAM exception described on this page.
  2. Added: OpenRouter describes every endpoint's data policy with three tiers:
  3. Added: No routine storage after processing, as described on this page.
  4. Added: OpenRouter or a provider may retain prompts and responses from any request, whether flagged or not, only to detect, investigate, and prevent abuse.
  5. Added: Data may be stored and used for training under the applicable provider policy.
  6. Added: Safety Retention limits why data can be kept. It does not require a request to be flagged before it can be stored.
  7. Added: When ZDR is enforced in your privacy settings or a guardrail, you choose whether Safety Retention endpoints are also allowed. The choice is separate for Google models and All other models , the two groups where Safety Retention endpoints exist today.
  8. Added: Allow Safety Retention: ZDR-enforced requests can use ZDR endpoints and Safety Retention endpoints.
  9. Added: ZDR only: ZDR-enforced requests use ZDR endpoints only. Safety Retention endpoints are excluded, so some models may be unavailable.
  10. Added: Set this in your privacy settings or in a guardrail's settings. A guardrail can only be stricter than your account setting: if your account is set to ZDR only, a guardrail can't allow Safety Retention. If you haven't chosen, self-serve accounts allow Safety Retention and enterprise accounts use ZDR only. In the API, zdr: true on a request follows the same account and guardrail choice. The guardrail fields are allow_safety_retention_google and allow_safety_retention_other in the Guardrails API . When ZDR isn't enforced, Safety Retention endpoints are available like any other endpoint that doesn't train on your data. OpenRouter has privacy settings that, when enabled, only allow you to route to endpoints that have a Zero Data Retention policy. You can enforce ZDR globally, per model group, per guardrail, or per request. Providers that do not retain your data are also unable to train on your data. However we do have some endpoints & providers who do not train on your data but do retain it (e.g. to scan for abuse or for legal reasons). OpenRouter gives you controls over both of these policies.
  11. Removed: Zero Data Retention (ZDR) means that a provider will not store your data for any period of time. OpenRouter has privacy settings that, when enabled, only allow you to route to endpoints that have a Zero Data Retention policy. You can enforce ZDR globally, per model group, per guardrail, or per request. Providers that do not retain your data are also unable to train on your data. However we do have some endpoints & providers who do not train on your data but do retain it (e.g. to scan for abuse or for legal reasons). OpenRouter gives you controls over both of these policies.
  12. Added: If you don't choose, enterprise accounts default to ZDR only and all other accounts default to Allow Safety Retention . On guardrails, use allow_safety_retention_google for Google models and allow_safety_retention_other for other models that use Safety Retention, such as open-weight models on Vertex. A guardrail can't allow Safety Retention when your account setting is ZDR only . On a model page, the provider details for an endpoint that uses Safety Retention show ZDR compatible: Only with Safety Retention allowed . If your own Google Cloud agreement includes zero data retention, you can use Vertex through your own key with ZDR only . Declare ZDR on your BYOK key. Requests through that key are treated as ZDR. See Declaring ZDR on a Key .
  13. Removed: If you don't choose, enterprise accounts default to Zero retention only and all other accounts default to Safety retention allowed . On guardrails, use allow_safety_retention_google for Google models and allow_safety_retention_other for other models that use Safety Retention, such as open-weight models on Vertex. A guardrail can't allow Safety Retention when your account setting is Zero retention only . On a model page, the provider details for an endpoint that uses Safety Retention show ZDR compatible: Only with Safety Retention allowed .
  14. Added: When zdr is set to true , the request will only be routed to ZDR endpoints, plus Safety Retention endpoints if your settings allow them (see Allowing or excluding Safety Retention ). When zdr is false or not provided, ZDR enforcement still applies if enabled in your account or guardrail settings.
  15. Removed: When zdr is set to true , the request is routed only to endpoints that have a Zero Data Retention policy. Endpoints that use Safety Retention are included only if Safety Retention is allowed for your account or guardrail (see Google Safety Retention ). When zdr is false or not provided, ZDR enforcement still applies if enabled in your account or guardrail settings.
  16. Added: The following endpoints are eligible when ZDR is enforced. Note that this list is also available programmatically via https://openrouter.ai/api/v1/endpoints/zdr . It is automatically updated when there are changes to a provider's data policy. It also includes Safety Retention endpoints, which are used only if you allow Safety Retention . The provider logging table shows which providers use Safety Retention.
  17. Removed: The following endpoints have a ZDR policy. Note that this list is also available progammatically via https://openrouter.ai/api/v1/endpoints/zdr . It is automatically updated when there are changes to a provider's data policy.:
About this change
Page
openrouter.ai/docs/features/zdr
Kind
Documentation
Text hash
fc635da50d98 to ed88579a9807
Dated by
the weekly check that first read the new text