Data retention
Router One does not retain prompt or model-response bodies from direct API calls. It records request metadata for billing, usage tracking, and troubleshooting. Playground saves conversation history so users can revisit and continue their chats.
Last updated:
Request content and conversation history
- 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.
Metadata, retention, and cleanup
- Request metadata
- Per-request records include the timestamp, final model and provider, token counts, latency, status, cost, and API key identifiers. Dashboard traces support troubleshooting and usage review; their visibility does not establish a deletion date for all related records.
- Billing reconciliation
- Usage and billing records support charge calculation and reconciliation. Ask support which records apply to your account and what retention or deletion constraints apply to them.
- Retention and cleanup status
- 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
- How to request
- Email support@router.one from the account owner address. Include your account email and relevant request, conversation, or API key IDs, without sending the secret key. Ask support to confirm the eligible records, any retention constraints, and the expected timeline before action.
- Scope
- Identify the data you want reviewed: account details, Playground history, usage, or billing records. These are different record types; deleting a conversation does not by itself confirm deletion of usage or billing records. Support must confirm the applicable scope.
Sub-processors and upstream behavior
- Upstream providers
- Router One forwards requests to the upstream model providers that serve each model family. Each provider has its own retention policy that applies once the request leaves the gateway.
- 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.
Enterprise contracts
- Confirm specific requirements
- Discuss required storage regions, retention periods, deletion, and exports with support before relying on them. Any account-specific commitment must be confirmed in the applicable agreement; this page does not promise that every requested configuration is available.
FAQ
How do I request deletion of my historical data?
Email support@router.one from the account owner address with relevant record IDs and the data types you want reviewed. Support will confirm the eligible scope, any retention constraints, and timing; do not include an API secret key.
Do you publish a sub-processor list?
The model catalog and request traces provide model and route information, but they are not a complete sub-processor inventory. Ask support to confirm the processing parties and applicable data-handling terms for your account.
Where is the metadata stored geographically?
Contact support through /contact to confirm the regions and record types relevant to your account. This page does not guarantee a single storage region for every processing or storage path.