# Data controls

> Eevo docs. Every page as Markdown is listed at https://eevo.io/llms.txt; the API is described at https://eevo.io/api/openapi.json.

Set how long Eevo keeps each key's requests, and choose for your organization whether Eevo can learn from them and where they run.

## Configuring data retention

Retention can be configured separately for each API key. Additionally, there is an organization-level setting for configuring data retention for MCP connectors and the API playground. Both default to 30 days.

Retention covers the request, the answer, the metadata, chosen decision notes and revision notes. When the retention period ends, the content is deleted. The time, model, tokens and cost are retained for usage stats and billing.

> [!NOTE]
> **Exception**
>
> **Not stored** has one exception. When a Consequence-based Decision API decision is still running when the first response ends (202), the answer is retained until it is fetched, or 1 hour passes.

## Allowing using data for improving Eevo

The training setting in **Data controls** specifies whether Upright can use the requests and answers your organization stores in anonymized form to train future Eevo models. It is on by default. Data from keys set to "Not stored" is never used, even with the setting on. Enabling data usage really helps us improve Eevo for your use case. If you choose to turn it off, we recommend providing us feedback separately on any potential issues you encounter.

Turning the setting off applies to every decision from then on.

## Configuring data region

Eevo runs requests in two regions: a global region and the EU region. EU region requests are fully processed in the EU, including inference. There are two mechanisms for specifying data region:

1. **Data controls in the Eevo console:** In [Eevo console](https://eevo.io/data-controls) data controls, an organization admin can choose where the organization's requests run. The setting covers requests from all sources, including the API, the API playground and connectors (Claude, ChatGPT and other MCP clients).
2. **Request base URL:** Requests sent using the API base URL `https://eu.eevo.io` always run in the EU region.

Pricing and request limits are the same for all regions.

## Read next

- [Authentication](https://eevo.io/api/docs/reference/authentication.md): Create an API key and send it with each request.
- [Models, pricing and limits](https://eevo.io/api/docs/reference/models-pricing.md): Reference on Eevo models, pricing and request limits.
