The first rule of thumb is: do not ignore the letter, but do not panic and assume that the alleged violation has been established. A CIPA demand letter is an allegation, not a judicial determination of liability. Many current website-tracking demands involve legal theories that remain contested, and the viability of a claim may depend heavily on the particular technology involved, the information actually transmitted, the timing of the transmission, consent, standing, and the specific CIPA provision being invoked.
At the same time, the company should take the letter seriously because receipt of a sufficiently concrete demand letter may trigger a duty to preserve relevant evidence. Under California law, the preservation obligation can arise before a lawsuit is filed when the party is objectively on notice that litigation is reasonably foreseeable. The California Court of Appeal has explained that this means litigation is “probable and likely to arise” from the dispute, rather than merely a possibility. (See Victor Valley Union High Sch. Dist. v. Superior Court, 91 Cal. App. 5th 1121, 1138–39 (2023).)
A demand letter expressly asserting a CIPA violation and threatening litigation can therefore be highly significant to the preservation analysis. Once litigation is reasonably foreseeable, relevant electronically stored information should not simply be deleted or allowed to disappear through routine retention practices. California Code of Civil Procedure §2023.030(f)’s safe harbor for Electronically Stored Information (“ESI”) lost through routine, good-faith operation of an electronic information system does not protect destruction of ESI occurring when the party was already under a duty to preserve the evidence.
That does not mean the company should leave the allegedly defective website configuration running. Preservation and remediation are two different things. If a Meta Pixel, session-replay tool, analytics script, chat application, or other tracker appears to present a legitimate concern, there is ordinarily no reason to continue the potentially problematic conduct merely to preserve evidence.
Instead, the preferred sequence is:
Preserve → document → remediate promptly → test → document the remediation.
Before making material changes, the company and its counsel should preserve enough evidence to reconstruct how the website operated at the relevant time. Depending upon the claim, that may include the privacy policy and cookie notice in effect on the date of the alleged visit; consent-management-platform settings and logs; Google Tag Manager containers and version history; Meta Pixel and Google Analytics configurations; source code and relevant scripts; server logs; screenshots of the consent flow; vendor agreements; and, where feasible, a network-level capture showing which HTTP requests leave the browser, which domains receive them, and what information is transmitted before and after the visitor makes a privacy choice.
Once that evidence has been adequately preserved, the company should promptly correct any genuine deficiency it identifies. Preservation does not ordinarily require a business to continue conduct that may create additional exposure. Indeed, continuing a questionable tracking configuration after receiving actual notice of the alleged problem could create unnecessary additional risk.
Counsel should also consider sending a preservation notice to the claimant and claimant’s attorney. A prospective plaintiff’s preservation obligations can likewise arise before filing suit when litigation is reasonably anticipated. Depending upon the allegations, potentially important claimant-side evidence could include the device and browser used for the visit, cookies and local storage, browser history, screenshots, HAR or other network captures, the precise URLs visited, date and time of the alleged visit, consent selections, Global Privacy Control settings, browser extensions, privacy settings, IP information, and the scanning or testing methodology used to identify the alleged violation. California’s preservation standard focuses on whether litigation is reasonably foreseeable rather than simply whether a complaint has already been filed.
The company should then have counsel and appropriate technical personnel reproduce the alleged conduct. The central questions are factual: What happened when the claimant visited the site? Which tracker fired? When did it fire? What information was transmitted? To whom? Did the behavior differ before and after consent? Did the claimant reject tracking or transmit an opt-out preference signal? And does the technical evidence actually support the allegations in the demand letter?
There are also several things the company should generally not do. It should not contact the claimant directly to apologize, explain the website’s operation, admit that tracking was unlawful, or negotiate a payment before the claim has been evaluated. It should not indiscriminately delete trackers, logs, tag-manager histories, consent records, or prior versions of its privacy policy without first preserving relevant evidence. And it should not assume that because a tracker was present, a CIPA violation necessarily occurred. Courts continue to disagree about important aspects of these claims, including whether particular tracking technologies satisfy CIPA’s statutory definitions and whether plaintiffs have suffered an injury sufficient to establish standing.
Finally, the company should promptly check its cyber, privacy, technology E&O, or other potentially applicable insurance policies. Notice provisions can be important, and coverage questions should be evaluated before the company incurs substantial defense expenses or negotiates a settlement.
The practical advice is therefore:
Preserve quickly, remediate quickly, and investigate before responding. Receipt of a demand letter can place a business on notice of reasonably foreseeable litigation and therefore create preservation obligations under California law, but that obligation does not require the company to leave potentially problematic tracking technology running. Preserve sufficient evidence to reconstruct the historical website configuration, correct any legitimate deficiency, test the corrected configuration, and have counsel evaluate the claim based upon what the website actually transmitted—not simply what the demand letter alleges.
This formulation also avoids suggesting that a business should freeze its website in a potentially noncompliant state, while recognizing the preservation rule established in the Victor Valley Union High Sch. Dist. case.