# Zero Data Retention

**Zero Data Retention (ZDR)** means that a provider will not store your data for any period of time.

**Infron allows you to route to endpoints that have a Zero Data Retention policy.**

Providers that do not retain your data are also unable to train on your data. However we do have some endpoints & providers who do not train on your data but *do* retain it (e.g. to scan for abuse or for legal reasons). Infron gives you controls over both of these policies.

### How Infron Manages Data Policies <a href="#how-openrouter-manages-data-policies" id="how-openrouter-manages-data-policies"></a>

Infron works with providers to understand each of their data policies and structures the policy data in a way that gives you control over which providers you want to route to.

Note that a provider’s general policy may differ from the specific policy for a given endpoint. Infron keeps track of the specific policy for each endpoint, works with providers to keep these policies up to date, and in some cases creates **special agreements** with providers to ensure data retention or training policies that are more privacy-focused than their default policies.

If Infron is not able to establish or ascertain a clear policy for a provider or endpoint, we take a conservative stance and assume that the endpoint both retains and trains on data and mark it as such.

### Per-Request ZDR Enforcement <a href="#per-request-zdr-enforcement" id="per-request-zdr-enforcement"></a>

You can enforce Zero Data Retention on a per-request basis using the `zdr` parameter in your API calls.

#### Usage <a href="#usage" id="usage"></a>

Include the [`zdr`](https://infronai.gitbook.io/docs/routing-and-gateway/inference-provider-routing#zero-data-retention-enforcement-zdr) parameter in your provider preferences:

```json
{
  "model": "gpt-4",
  "messages": [...],
  "provider": {
    "zdr": true
  }
}
```

When `zdr` is set to `true`, the request will only be routed to endpoints that have a Zero Data Retention policy.

### Caching <a href="#caching" id="caching"></a>

Some endpoints/models provide implicit caching of prompts. This keeps repeated prompt data in an in-memory cache in the provider’s datacenter, so that the repeated part of the prompt does not need to be re-processed. This can lead to considerable cost savings.

Infron has taken the stance that in-memory caching of prompts is *not* considered “retaining” data, and we therefore allow endpoints/models with implicit caching to be hit when a ZDR routing policy is in effect.

### Infron’s Retention Policy <a href="#openrouters-retention-policy" id="openrouters-retention-policy"></a>

**Infron itself has a ZDR policy**; your prompts are not retained.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://infronai.gitbook.io/docs/features/zero-data-retention.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.