# Data and privacy

What the router stores and for how long, content logging, and how to keep data in Russia.

## What the router stores

| Data                                                               | Kept                                            | Who sees it                                     |
| ------------------------------------------------------------------ | ----------------------------------------------- | ----------------------------------------------- |
| Request metadata: time, model, key, tokens, cost, status, attempts | For billing and logs                            | Members of the Router space with access to logs |
| Content of requests and answers                                    | Only with content logging on, 1 to 30 days      | Members with access to logs                     |
| API keys                                                           | A hash and the prefix; the secret is shown once | Nobody                                          |

The router never writes prompts, answers or keys to its own service logs.

## Content logging

Content logging stores the body of every request and answer of a Router space, so you can open them in the call card of the logs.

- It is **off** by default. The owner or an admin turns it on in the space settings and confirms that bodies may contain personal data or secrets.
- It applies to new requests only.
- Retention is 1 to 30 days (7 by default); older content is deleted automatically. Each side of a call is kept up to 1 MiB.
- Content is stored encrypted. Support staff can read it only with access the space owner grants for a limited time.
- **Delete all logs** in the space settings deletes the stored content at once.

## Providers

A request goes to the provider that runs the model. Providers have their own retention policies: some keep requests for a while for abuse checks, some may use them to train models. To choose:

- `"provider": {"zdr": true}` — only providers that keep nothing, see [Zero data retention](/docs/en/zero-data-retention);
- `"provider": {"data_collection": "deny"}` — no providers that store data for training.

The router does not send providers your headers, your API key or the name of your application.

## Keep data in Russia

Models with `ru-1/…` and `ru-2/…` ids are hosted in Russia; a request to them is sent straight to the Russian provider and does not leave the country. To make sure a `models` fallback cannot leave either, add `"provider": {"only": ["ru"]}`. See [Models and routing](/docs/en/models-and-routing#keep-data-in-russia).

Keeping data in Russia and zero data retention are different guarantees: Russian providers' retention policies are not confirmed, so ZDR requests never go to the Russia region.