# Router One Data Retention Facts

Last updated: 2026-09-05

- Product: Router One
- Category: LLM API Gateway / AI Model Router
- Direct API calls: Direct API calls do not retain prompt or model-response bodies. Records contain request metadata such as model, token counts, cost, latency, and status for billing, usage tracking, and troubleshooting.
- Playground history: Playground saves conversation history, including user messages, model replies, and tool calls, so users can revisit and continue conversations. This saved chat history is separate from direct API usage records.
- API and Playground boundaries: The direct-API body-retention policy applies to Router One. Requests are forwarded to the upstream model provider to generate a response; upstream providers have their own data-handling policies. Playground conversation history is saved separately.
- Request metadata: timestamp, final model and provider, token counts, latency, status, cost, and account/API key identifiers support troubleshooting and usage review
- Billing records: usage and charge records support billing and reconciliation; support can confirm the applicable records and retention constraints
- Retention and cleanup: This page does not guarantee one retention or automatic-deletion window for every record type. Contact support@router.one to confirm the applicable retention, cleanup status, and scope and timing of a data request for your account.
- Customer-initiated deletion: email support@router.one from the account owner address with relevant request, conversation, or API key IDs and the data types to review; do not send the secret key. Support confirms scope, constraints, and timing before action
- Deletion scope: conversation history, usage, and billing records are different record types; deleting a conversation does not by itself establish that related usage or billing records were deleted
- Upstream handling: upstream providers have their own data policies; model listings and request traces are not a complete sub-processor inventory. Ask support to confirm the applicable processing parties and terms
- Enterprise requirements: confirm storage regions, retention, deletion, and export requirements in the applicable agreement before relying on them; this page does not guarantee every requested configuration is available
- Trust boundary: request-level observability and spend control for developers and small teams — not an enterprise audit, compliance, or RBAC system

## Canonical pages

- Data retention: https://router.one/data-retention
- Security: https://router.one/security
- Privacy policy: https://router.one/privacy
- Observability facts: https://router.one/facts/observability.md
- Company facts: https://router.one/facts/company.md