Security
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 conversations
- 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.
What we DO log
- Per-request metadata
- Internal operational records can include timestamps, account and API key identifiers, model, provider routing metadata, token counts, latency, status, and cost. Upstream provider identities and routes are not disclosed in Customer Logs.
- Why
- These records support billing reconciliation and internal operations. Customer Logs provides the model, request ID, tokens, settled cost, recorded latency, status, and any sanitized error.
Transport & key handling
- TLS
- All inbound and outbound traffic is over TLS 1.2+. Plain HTTP is never served: the edge answers it with a redirect to HTTPS. Call the https:// endpoint directly — anything sent over plain HTTP has already left your machine in cleartext before the redirect arrives.
- API keys
- Customer keys are stored hashed at rest. They are never returned by any API endpoint after the create-key call.
- Upstream credentials
- Per-provider keys are platform-owned and rotated regularly. Customers never see upstream credentials.
Upstream behavior
- We pass through
- Once a request leaves Router One, the upstream provider's data policies apply on their end. We do not control their retention.
- Provider selection
- A specified model can use another healthy provider route for that model; model:auto can use server-configured candidates. Customer Logs records the model and request ID; provider identities and service routes remain internal.
FAQ
Does API non-retention include Playground or upstream providers?
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.
Can I export the metadata Router One has on my account?
Yes — the dashboard exposes per-request trace and aggregated metrics. Enterprise contracts can include programmatic export.
How long is metadata kept?
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.