# The consent record you cannot produce is the one you needed

Source: https://complymynt.com/blog/defensible-consent-records
Published: 2026-04-22 · Topic: TCPA · 7 min read
Author: ComplyMynt (https://complymynt.com)
Note: ComplyMynt is not a law firm and this article is not legal advice.

> A defensible record has the language shown, the timestamp, the source, and the version. Most stacks store one of the four.

In a TCPA dispute, the question is never whether you had a checkbox. It is whether you can produce, for one specific person on one specific date, the exact language they agreed to.

A defensible record contains four elements: the verbatim disclosure text shown, a trustworthy timestamp, the capture source including page and campaign, and a version identifier for the consent language itself.

Most stacks store a boolean. When the language changes — and it always changes — the record becomes unfalsifiable and therefore worthless.

Retention matters just as much. Keep records for the full limitations period plus a margin, and make sure revocation is recorded with the same fidelity as the original consent.

Test the process, not the schema: pick a real record at random and try to produce the packet in under an hour. If you cannot, neither can your counsel.

## Authoritative references

- [eCFR — 47 CFR 64.1200 (TCPA delivery restrictions)](https://www.ecfr.gov/current/title-47/chapter-I/subchapter-B/part-64/subpart-L/section-64.1200)
- [FCC — Telephone Consumer Protection Act rules](https://www.fcc.gov/general/telemarketing-and-robocalls)
- [GDPR Article 7 — conditions for consent](https://eur-lex.europa.eu/eli/reg/2016/679/art_7/oj)
- [FTC — CAN-SPAM Act: A Compliance Guide for Business](https://www.ftc.gov/business-guidance/resources/can-spam-act-compliance-guide-business)