OpenRouter

OpenRouter defaults are protective, but the selected upstream model provider and optional logging or data-sharing controls determine end-to-end handling.

Plan Scope

OpenRouter API and chat; downstream handling varies by selected model endpoint and account privacy controls.

Prompt Retention

OpenRouter does not retain prompts or responses by default. Optional private logging retains content for at least three months and possibly longer until deletion is requested; some processing and cache features have separate retention.

Response Retention

Same policy as prompts.

Ordinary Logging

Request metadata such as model, token counts, timestamps, cost, and latency is retained without prompt or response content.

Model Training

OpenRouter does not train on inputs or outputs by default. A separate opt-in permits product improvement; downstream model providers may retain or train unless endpoint policy controls exclude them.

Product Improvement

Optional input/output sharing is off by default and provides a usage discount when enabled. Anonymous prompt categorization may occur under a zero-data-retention arrangement.

Human Or Operator Access

Privately logged content is visible to the account owner or organization admins; OpenRouter says it does not access that content except where feature terms, operations, security, troubleshooting, or law require.

Subprocessors And Routing

Requests are sent to the selected or automatically routed model provider, whose own endpoint-specific policy applies. Zero-data-retention routing can be enforced.

Deletion Controls

Account owners may request deletion of privately logged prompt and response content; retention for optional features is documented separately.

Caveat

Privacy depends on both OpenRouter settings and the final model endpoint. OpenRouter conservatively treats an unknown provider policy as retaining and training on data.