71 Total
Stay ahead of the changes
Track OpenRouter and hear on the next check after its terms change. We check daily where we can, and show you where we can't.
Summary
Generated by a model from the captured document; not read by a person

OpenRouter's Privacy Policy explains what happens to your data when you use the service: by using it, you consent to data collection, and some AI providers that receive your messages may use them to train their models — something OpenRouter says it cannot control. OpenRouter can change this policy at any time without advance notice, and keeping using the service counts as your agreement to the new terms. If you ask to delete your account, that action cannot be undone once confirmed.

Analysis

OpenRouter's Privacy Policy establishes the terms under which OpenRouter collects, uses, and shares personal data from users of its Site and Service. The policy requires that use of the Site or Service constitutes consent to data collection and use, and that continued use after a revised policy is posted constitutes acceptance of changes, including retroactive application to personal data already held. OpenRouter expressly disclaims responsibility for how third-party Model Providers and LLMs handle user Inputs and Outputs after transmission, including use in model training, and acknowledges it cannot control Model Provider-side training once data is transmitted. Users bear responsibility for obtaining biometric notice and consent from any third parties whose voice or image appears in data submitted to a Model, and account deletion is irreversible once confirmed.

What this means for you

When you use OpenRouter, your inputs and outputs may be used by third-party Model Providers for AI model training, and OpenRouter states it has no control over that use once your data is transmitted. Any image, audio, or video you submit may be treated as biometric information under applicable laws, and if it contains another person's likeness or voice, you are responsible for obtaining that person's consent. OpenRouter may change its privacy terms at any time without notice, applying new terms even to data it already holds, with your continued use treated as acceptance. If you wish to manage how your data is handled by Model Providers, you should review the training-permission status of those providers before submitting data through OpenRouter.

Institutional Analysis
Stay ahead of the changes

Institutional analysis available with Insight

Which mapped governance frameworks each document engages, tied to the specific provisions that engage them.

3 important changes detected

19 versions captured · Latest change detected by ConductAtlas: October 2026

What changed OpenRouter's privacy policy now includes an additional disclosure circumstance for data sharing: routing API requests in-region in Europe through EU in-region routing on Business. This clarifies that customer data may be disclosed to facilitate regional data routing compliance, a practice the policy previously did not explicitly describe in its data disclosure section.
Why this matters The updated policy now explicitly states that OpenRouter may disclose customer data to route API requests in-region in Europe as part of its EU in-region routing service on Business. This clarifies an operational practice rather than introducing a new data-sharing authority. Users relying on OpenRouter's Business tier for EU in-region routing should be aware that data routing to facilitate this service is an authorized disclosure circumstance under the policy.
View full change record →
What changed OpenRouter expanded its privacy policy to document a new Files API feature that allows users to upload and persistently store files (images, PDFs, documents) for use in inference requests. The policy now specifies how these uploaded files are handled: they are encrypted, retained until deletion or account closure, transmitted to selected model providers, and not used for training OpenRouter's own models. Additionally, OpenRouter raised the minimum age requirement from 13 to 18 years old.
Why this matters The updated policy establishes a new Files API feature allowing you to upload and store files for use with inference requests. Files are encrypted at rest and in transit, retained until you delete them or close your account, and transmitted to the model provider you select for processing. OpenRouter states it does not use uploaded file content to train its own models, for unrelated analytics, or for marketing. The policy also raises the minimum age requirement from 13 to 18 years old, meaning users under 18 are no longer eligible to use the service.
View full change record →

July 7, 2026 medium

OpenRouter's privacy policy now explicitly discloses that user inputs are transmitted to third-party model providers, which may use those inputs for model training unless the user selects a provider that …

View change record →
Clauses withheld

We withheld clauses we had published from this document. Each withholding is recorded in our correction log:

Featured provisions
Generated by a model from the captured document; not read by a person

Complete Provision Index

Every distinct legal provision identified in this document. Featured provisions appear above with analysis.

71 provisions
12 featured
14 clause types
Disclosure and Transparency Requirements 1
Acceptable Use Restrictions 1
Stay ahead of the changes

Monitoring

OpenRouter has updated this document before. Monitor includes alerts from a daily check, structured change summaries, and monitoring for up to 20 platforms.

Stay ahead of the changes

Governance Intelligence

Need provision-level monitoring and regulatory mapping? Insight includes governance timelines, drift analysis, and full provision tracking.

Cross-platform context

See how other platforms handle Behavioral Tracking Across Third-Party Sites and similar clauses.

Compare across platforms →
Archival ProvenanceSource & Archival Record
This version captured October 17, 2026 00:55 UTC
Last successful capture October 17, 2026 00:55 UTC
Date stated by the document August 31, 2026 (as printed in this version)
Capture Method Automated scheduled archival capture
Document ID CA-D-000811
Version ID CA-V-007674
SHA-256 (extracted text, extractor v5) 586d37214934b55657c6c14282394069d23ca94baf7ff4308d9b9a03889daa7a
Archived bytes SHA-256 (anchor) 132f6c09ca05c8eef3a06b0602b4d9e34b74c1173514c8caa2d859557dcf6f7f
✓ Snapshot stored ✓ Archived bytes anchored (verified Oct. 17, 2026)

Governance Monitoring

Monitor governance changes across the platforms you rely on.

Structured alerts for policy changes, governance events, and provision updates across 343 platforms.

Start monitoring → Compare plans