# OPS-240 — Recordings must outlive the consent records they evidence

> Call recordings must be retained at least as long as the consent records they are the evidence for.

- **Rule ID:** OPS-240
- **Layer:** Operational (`OPERATIONAL`)
- **Checks:** `campaign.message_flow + privacy policy`
- **Severity:** HIGH — Rejected by at least one carrier or provider, and a common cause of failure at the rest.
- **When it bites:** Gates approval — get this wrong and registration is refused
- **How it is detected:** AI judgement over the submitted form
- **Fix type:** Fix the field — a better value in the form clears it
- **Required by:** FTC, CTIA, practice
- **Applies:** Applies when consent was collected by live verbal and IVR.
- **Canonical URL:** https://ekas.io/rules/10dlc/operational/ops-240/

## Why this rule exists

Recording retention is usually set by the telephony platform for quality-monitoring reasons — thirty or ninety days is a common default — while consent records are kept for years. The result is a consent record that points at a recording which was deleted long before anyone asked for it, and nobody notices because both systems are behaving exactly as configured.

## How to fix it

Raise the recording retention on the telephony platform to match the consent retention window, or export the consent calls into the consent store. Done when the recording retention setting is at least as long as the period stated for consent records.

## Example of a compliant value

```text
Consent-call recordings are retained for four years, matching the consent-record retention period.
```

## Common mistakes

- A blanket increase across every call is expensive and usually unnecessary — tag the consent calls and retain those, rather than the whole queue.