# Data retention

> Markdown mirror of https://router.one/data-retention for AI assistants and crawlers. Router One is an OpenAI-compatible LLM API gateway.
> Last updated: 2026-07-13

Router One keeps the minimum metadata needed to power per-request traces and billing reconciliation — and nothing more. This page describes the windows, how to request earlier deletion, and what enterprise contracts can adjust.

## Request and response bodies

### Not stored

Prompt content and model completions pass through in real time. They are never persisted to disk and never copied to any analytics store.

### Streaming

Streaming responses are forwarded byte-for-byte. No completion buffer is retained after the connection closes.

## Metadata windows

### Observability — 90 days

Per-request trace (timestamp, final model and provider, token counts, latency, status code, cost, and API key metadata) is queryable in the dashboard for 90 days from the request time.

### Billing reconciliation — 13 months

Aggregated billing rows are retained for 13 months so customers can audit invoices against the underlying usage during the standard accounting period.

### After the window

Data is purged. The dashboard's per-request trace will return 'not available' for requests older than the window.

## Customer-initiated deletion

### How to request

Email support@router.one from the account owner address. Include the account email and any API key or request IDs needed to locate the records; support will confirm the eligible scope, legal retention requirements, and expected timeline before action.

### Scope

Eligible account metadata can be reviewed for earlier deletion. Billing reconciliation rows may still be retained where required by Chinese / international accounting law; support will state which rows are retained and why.

## Sub-processors and upstream behavior

### Upstream providers

Router One forwards requests to upstream LLM providers (OpenAI, Anthropic, Google, etc.). Each provider has its own retention policy that applies once the request leaves the gateway.

### What Router One does not hold

Router One does not hold a copy of the prompt or completion that the upstream provider receives. We hold only the metadata listed above.

## Enterprise contracts

### Adjustable windows

Enterprise contracts can lengthen the observability window, shorten the billing reconciliation window where law permits, or add programmatic export of trace data to a customer-owned destination.

## FAQ

### Can Router One delete my historical metadata earlier than 90 days?

Email support@router.one from the account owner address with the account email and any relevant API key or request IDs. Support will confirm the eligible scope and timeline; accounting-law retention may still apply to billing rows.

### Do you publish a sub-processor list?

The active set of upstream LLM providers is shown on /models. The provider used for a given request is recorded in that request's trace. Router One itself does not hold customer prompts or completions.

### Where is the metadata stored geographically?

Storage region details are documented in enterprise contracts under NDA. Contact sales via /contact for specifics.

## See also

- Methodology: https://router.one/methodology
- Security: https://router.one/security
- Privacy policy: https://router.one/privacy
- Trust hub: https://router.one/trust
- Canonical page: https://router.one/data-retention
- Models and per-model token rates: https://router.one/models (markdown: https://router.one/models.md)
- Pricing: https://router.one/pricing
- API docs (markdown): https://router.one/docs.md
- Company facts: https://router.one/facts/company.md