TCPA Call Record Retention and the Spoliation Risk of Losing It
The records that usually decide a TCPA case are ones the business creates every day: the consent for each number, the dialer logs, and the opt-out requests that came in later. Those records help the defense. But they sit on systems built to purge old data, and once a claim is on the horizon the company has to stop the purge. Lose the data after the duty attaches and the fight shifts from the calls to a sanctions problem the company can lose before the merits.
What call records actually matter in a TCPA case?
Start with the records that prove or defeat each theory. A consent claim under 47 U.S.C. § 227(b) depends on whether the business had prior express consent, or prior express written consent for marketing, before it called or texted a cell number. The record that answers that is the opt-in itself: the web form, the checkbox language, the keyword text, the date and the IP or phone number tied to it. A Do Not Call claim under § 227(c)(5) comes down to the company’s internal do-not-call list and its registry scrub history. A revocation claim rests on the opt-out log and the timestamp showing how fast the company honored a “stop” reply.
Then there’s the dialer. Whether equipment qualifies as an autodialer, meaning an automatic telephone dialing system that uses “a random or sequential number generator,” is often the whole case after Facebook, Inc. v. Duguid, 592 U.S. 395 (2021). The platform configuration, the dialing records, and the vendor’s technical documentation are what show how the calls were actually placed. Lose them and the company is arguing about its own equipment from memory.
Here is the list of what a TCPA defendant should treat as evidence the moment a claim is realistic:
- Call and text logs and the dialer or messaging-platform data for the challenged campaign, plus the consent records for every number involved, all frozen under a litigation hold.
- The internal do-not-call list and the opt-out records, with the dates each request came in and the date it was honored.
- The National Do Not Call Registry scrub records and the version dates of the registry used for each call.
- Vendor and lead-source contracts, the calling or texting scripts, and any recorded voice or AI-voice message files.
- Advice of counsel before responding to a demand letter, contacting the claimant, or offering anything to settle, so the response does not waive privilege or create new evidence.
When does the duty to preserve TCPA call data start?
The duty starts when litigation is reasonably anticipated, not when the complaint is served. Federal Rule of Civil Procedure 37(e) frames the obligation around information that “should have been preserved in the anticipation or conduct of litigation.” In a TCPA matter, a demand letter from a plaintiff’s firm, a pre-suit settlement overture, or a pattern of “stop” complaints about a specific campaign can each cross that line. The company does not get to wait for a case number.
What triggers the duty is a judgment call, and it is one worth making early instead of defensively. A business that treats the first serious demand letter as the preservation trigger almost never regrets it. A business that waits, hoping the claim goes away, is the one explaining to a magistrate judge why ninety days of text logs disappeared on a rolling retention schedule after the letter arrived. The rule does not care that the deletion was automated. It cares whether the company took reasonable steps once it should have known.
What happens if we lose the records? Rule 37(e) in two tiers
Rule 37(e) applies only to electronically stored information, which is nearly everything that matters here, and it sorts the consequences into two very different tiers. The distinction is the single most important thing a calling business should understand about spoliation, because it controls how bad the day gets.
Under the first tier of Rule 37(e), if a party “failed to take reasonable steps to preserve” the data and it “cannot be restored or replaced through additional discovery,” a court that finds prejudice may order “measures no greater than necessary to cure the prejudice.” That can mean letting the other side introduce evidence about what was lost, barring the company from using related evidence, or giving a limited instruction. It is a real setback, but it is proportional.
The second tier is the one that ends cases. A court may presume the lost information was unfavorable, instruct the jury to presume it, or dismiss the case or enter a default judgment, but Rule 37(e)(2) allows those measures “only upon finding that the party acted with the intent to deprive another party of the information’s use in the litigation.” That intent requirement is a meaningful shield. Negligent loss, even careless loss, does not get a plaintiff an adverse-inference instruction under the rule. A plaintiff who wants the case-ending sanction has to prove the company meant to bury the evidence, and that is a high bar. The practical lesson cuts against panic: losing data is a problem, but the catastrophic version requires intent, and a company with any documented preservation effort is usually nowhere near it.
| Claim theory | Statute or rule | Per-violation exposure | The record that proves or defeats it |
|---|---|---|---|
| Autodialed or prerecorded call or text without consent | 47 U.S.C. § 227(b)(3) | $500, up to $1,500 if willful or knowing | Opt-in and consent records, plus dialer configuration and logs |
| More than one Do Not Call violation in 12 months | 47 U.S.C. § 227(c)(5) | Up to $500, discretionary trebling | Internal DNC list, registry scrub records, and reasonable-procedures proof |
| Failure to honor revocation | 47 U.S.C. § 227(b) | $500, up to $1,500 if willful or knowing | Opt-out log with timestamps |
| Loss of the above after the duty attached | Fed. R. Civ. P. 37(e) | Curative measures, or adverse inference or default on a finding of intent | The preservation effort itself |
Do the FCC’s own recordkeeping rules help or hurt?
They help, if the company actually follows them, and they hurt badly if it lets them lapse. The FCC’s telemarketing rules already require callers to keep certain records. A caller relying on the registry safe harbor has to use a version of the national registry “obtained from the administrator of the registry no more than 31 days prior to the date any call is made, and maintains records documenting this process,” under 47 C.F.R. § 64.1200(c)(2). And an internal do-not-call request “must be honored for 5 years from the time the request is made,” under the same regulation’s subsection (d)(6).
So the compliance program that was built to satisfy the FCC produces exactly the evidence that defeats a DNC claim: dated scrub records and a maintained suppression list. A business running a tight program walks into litigation with its best defense already documented. The risk is subtler. Those retention schedules are built for compliance, not litigation, and a routine purge that is perfectly lawful on an ordinary Tuesday becomes spoliation the moment it runs on data the company already had a duty to hold. The compliance calendar and the litigation hold are not the same instrument, and treating them as one is how good records get destroyed by a system doing exactly what it was configured to do.
How do automatic deletion settings create spoliation risk?
Most of the loss in these cases is not a shredding-party cover-up. It is a default setting. Messaging platforms and dialer vendors often retain detailed logs for a fixed window, then roll them off. Carriers keep SMS content for a short period. Call-recording systems overwrite on a cycle. None of that is sinister, and none of it stops once a demand letter arrives unless a human being intervenes. The intervention is the whole ballgame. Within days of anticipating a claim, the company should suspend auto-deletion on the relevant systems, tell the vendor in writing to preserve the campaign data, and document that it did both. That paper trail is what keeps a loss in Rule 37(e)’s first tier if something slips through anyway. The firm’s TCPA litigation defense work often starts with exactly this step, because the preservation posture set in the first week shapes how the rest of the case plays out.
Questions businesses ask about TCPA record retention
Does a demand letter really start the preservation duty?
Often, yes. The duty attaches when litigation is reasonably anticipated, and a serious demand letter from a plaintiff’s firm is a classic trigger. A letter that names a campaign, a claimant, and a TCPA theory is usually enough on its own. The safer course is to open a hold when the letter arrives instead of litigating later about whether the company should have known.
How long should a company keep call and consent records?
Longer than the minimum. The FCC requires internal do-not-call requests to be kept for five years, and registry scrub documentation on a 31-day cycle. For litigation exposure, consent records and campaign logs are worth keeping through the full period a claim could still be brought, which runs years. A short retention window is a compliance choice that becomes an evidence gap.
Can we be sanctioned for data a vendor deleted?
Possibly. If the company controlled the data or could have directed the vendor to preserve it, a court can treat the loss as the company’s. That is why a written preservation notice to the dialer or messaging vendor belongs in the first days of a hold. Control, not physical custody, is what decides it.
Is negligent loss of records enough for an adverse-inference instruction?
No. Under Rule 37(e)(2), the serious sanctions, including an adverse-inference instruction and default, require a finding that the party acted with intent to deprive the other side of the information. Negligence can still bring curative measures under the first tier, but it does not get a plaintiff the case-ending remedies.
If your company is facing a TCPA claim
If your company received a TCPA demand letter or was named in a class action, the first move is preserving the call logs, consent records, and opt-out data before a retention schedule erases them, because those records usually carry the defense. Rosenberger + Kawabata represents businesses defending TCPA lawsuits and class actions through its business litigation practice, including claims involving lost or purged call records. Contact Rosenberger + Kawabata online for a confidential consultation, or call (310) 894-6921.
Sources
The statute is the Telephone Consumer Protection Act at 47 U.S.C. § 227, and the preservation rule is Federal Rule of Civil Procedure 37(e), which governs the failure to preserve electronically stored information.
The FCC’s recordkeeping and delivery rules are at 47 C.F.R. § 64.1200. The autodialer definition comes from Facebook, Inc. v. Duguid, 592 U.S. 395 (2021).
This post is general information about the Telephone Consumer Protection Act and related laws as of August 10, 2026. It is not legal advice, and reading it does not create an attorney-client relationship. Courts and the FCC change the rules in this area often, and the outcome of any claim depends on its facts. Past results do not guarantee future outcomes.