> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ouraicalling.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Data retention

> Control how long each workspace data channel is kept.

Data Retention is available under **Settings → Data Retention** when the
workspace plan includes the **Data Retention** feature. If the feature is not
included, the page links to **Settings → Plan** for an upgrade.

## Default and channel overrides

The plan default is **24 months (720 days)** unless the governing plan defines
a different period. Leaving a channel without a custom value keeps that plan
default; the workspace is not silently populated with an override.

Workspace owners and admins can set a retention period for:

* calls, including voice, AI avatar, live chat and WhatsApp voice history;
* call recordings, transcripts, summaries and caller-memory data;
* campaign leads;
* email threads and the outbound SMS log;
* Telegram, Slack, Messenger, Microsoft Teams, Discord, Google Chat, X and
  WhatsApp conversations, messages and stored media.

Active campaign leads are protected. Email retention evaluates the last
activity of the entire thread, so an old root message with a recent reply is
not deleted.

## Which plan applies?

A workspace on the main platform follows its platform plan. A customer
workspace created through a white-label reseller follows the plan in that
reseller's catalog. The same rule applies to free-account defaults and
retention limits.

## Cleanup and audit trail

The retention job runs every day at **03:30 UTC**. It removes matching data and
records every deleted object in the retention audit log (`deletion_log`) for
storage-limitation accountability under Article 5(1)(e) GDPR. If the plan
feature is disabled, the job does not apply configurable retention cleanup to
that workspace.

## API and MCP

* `GET /api/v1/settings/retention` reads overrides, limits, entitlement state
  and the exact `plan_default_days`.
* `PATCH /api/v1/settings/retention` updates one or more channel values. Send
  `null` to clear an override and restore the plan default.
* MCP tools: `get_retention_settings` and `update_retention_settings`.

REST uses `settings:read` / `settings:write`; MCP also accepts the matching
assistant read/write scopes.