AI vendors and your data

Vendors146Answers427

146 vendors · 427 answers

Zero Data Retention changed OpenRouter, Nov 2, 2026

OpenRouter · Nov 2, 2026 · 11 added, 5 removed · seen by the weekly check

The pageAll OpenRouter terms
  1. Added: Planned update (October 27, 2026): OpenRouter will screen all inference requests, including ZDR traffic, for child sexual abuse material (CSAM) in flight. Content flagged as potential CSAM may be retained for human review, reporting, and preservation where required by law. This does not permit general retention or use for model training. Read the announcement . We're updating this page and our related terms.
  2. Added: Removes AI Studio endpoints. Vertex endpoints that use Safety Retention remain available only if Safety Retention is allowed (see Google Safety Retention )
  3. Added: Starting October 18, 2026, Google requires Safety Retention for Google models served through Vertex. With Safety Retention, Google doesn't retain prompts by default, but it may retain prompts that its safety classifiers flag, for up to 90 days, for abuse monitoring. Google doesn't use retained prompts for training. These endpoints don't meet a strict Zero Data Retention requirement. When you enforce ZDR for Google models, you choose how OpenRouter treats these endpoints in your privacy settings or on a guardrail:
  4. Added: Excludes endpoints that use Safety Retention. Most Google models become unavailable.
  5. Added: Lets ZDR-enforced requests use endpoints that use Safety Retention.
  6. Added: 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 .
  7. Added: 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.
  8. Removed: When zdr is set to true , the request will only be routed to endpoints that have a Zero Data Retention policy. When zdr is false or not provided, ZDR enforcement still applies if enabled in your account or guardrail settings.
  9. Added: Declaring non-ZDR records an explicit attestation that the upstream retains data. Under a ZDR requirement it routes the same way as Not declared . The difference is what your audit trail records: Declared non-ZDR is known and attested, Not declared is unknown.
  10. Added: A private endpoint created before this setting existed keeps its current classification and behaves as it did. Editing its declaration applies the rules above, subject to the override precedence below.
  11. Added: Overrides and attestations An explicit OpenRouter data-policy override set by our team remains authoritative over your declaration. If OpenRouter has assigned a specific data policy to your private endpoint, that policy decides eligibility regardless of what you declared. A declaration is your attestation about your agreement with the upstream. OpenRouter records it and routes on it, and does not independently verify the upstream's contractual behavior.
  12. Added: For inference content covered by OpenRouter's ZDR policy, we do not retain prompts or responses after processing, except when you explicitly choose to have us store them or when retention is needed for CSAM review, reporting, and related legal preservation. CSAM screening will also apply to requests covered by OpenRouter's ZDR policy. See CSAM Screening Across OpenRouter .
  13. Removed: Declaring non-ZDR records an explicit attestation that the upstream retains data. Under a ZDR requirement it routes the same way as Not declared today. The difference is the fact preserved for your audit trail: Declared non-ZDR is known and attested, Not declared is unknown.
  14. Removed: Existing private endpoints keep their current classification. Introducing this setting did not bulk-migrate them, so a private endpoint created before the setting existed behaves exactly as it did. Editing its declaration applies the rules above, subject to the override precedence below.
  15. Removed: Overrides and attestations An explicit OpenRouter data-policy override set by our team remains authoritative over your declaration. If OpenRouter has assigned a specific data policy to your private endpoint, that policy decides eligibility regardless of what you declared. A declaration is your attestation about your agreement with the upstream. OpenRouter records it and routes on it. It is not independent verification by OpenRouter of the upstream's contractual behavior.
  16. Removed: OpenRouter itself has a ZDR policy; your prompts are not retained unless you specifically opt in to prompt logging.
About this change
Page
openrouter.ai/docs/features/zdr
Kind
Documentation
Text hash
1047f7d4c7fa to fc635da50d98
Dated by
the weekly check that first read the new text