The short answer
Don't reply in a hurry, and don't rip things off your site before you've recorded what was there. Forward the letter to a lawyer, capture what your site sends today, then fix what's wrong, starting with trackers that fire before anyone agrees, since most letters rest on exactly that. California's SB 690, signed on 30 September 2026, ends private "pen register" claims over websites from 1 January 2027, but the wiretap claims stay.
Why so many of these letters exist
In the US, a large share of these letters cite California's Invasion of Privacy Act (CIPA). The argument is that a pixel or session recorder sending visitor data to a third party is a kind of wiretap unless the visitor agreed first.
CIPA lets a private plaintiff ask for $5,000 per violation, or three times actual damages if that's more, with no need to show any real loss. Some letters count a separate violation for every visit, data transfer or tool that fired, which is how the totals get large.
In Europe the pressure comes from regulators instead. In September 2025, France's regulator fined SHEIN €150 million for setting advertising cookies before anyone chose and for still setting them after people pressed refuse. The same week it fined Google €325 million, partly because refusing ad cookies when creating an account was harder than accepting them.
In US letters the evidence is usually a recording of your site's network requests on a first visit, often a HAR file, showing trackers firing before any choice.
Which part of CIPA your letter cites
Look for the section number in the letter. It tells you what they say happened and what you should capture. SB 690 was signed on 30 September 2026 and takes effect on 1 January 2027.
| The letter cites | What it alleges | What to capture | After SB 690 |
|---|---|---|---|
| Section 631 (wiretapping) | A third party read what visitors typed or did while it was in transit: chat windows, search boxes, forms, session recordings | Which scripts load on pages with chat, search or forms, and whether they load before a choice | Unchanged. Private claims go on |
| Section 632 (eavesdropping on confidential communications) | Recording a communication the visitor expected to stay confidential | The chat widget, its vendor and when it starts recording | Unchanged. Private claims go on |
| Sections 638.50 and 638.51 ("pen register" or "trap and trace") | A tracker collected addressing data such as IP addresses, cookies or device IDs | Every third-party domain that receives a request before a choice | Private claims over websites and apps end. Only California's Attorney General can bring them |
| The damages clause | $5,000 per violation, or three times actual damages | Nothing extra | Still applies to the claims that remain |
SB 690 also reaches pending claims in suits filed since 1 January 2025, so some live cases are affected.
The Governor's signing message called other parts of CIPA "susceptible to abuse" and asked lawmakers to look at them again next year. For now, SB 690 leaves Sections 631 and 632 as they were.
Week one: what to do, in order
1. Don't reply or pay before a lawyer has seen it
Letters often set short deadlines to push you. Write the deadline down and give it to your lawyer, who can tell you what it means. Don't click any links in the letter either.
2. Preserve what your site looks like today
Capture the current state before anyone changes anything. Your lawyer may need it, and "we changed it the next day and said nothing" doesn't look good.
- Save the page source of your homepage and checkout.
- Record a first visit in a private window with the browser's network panel open, and export it (a HAR file).
- Export your Tag Manager container: Admin, Export Container.
- Note which consent tool you use, if any, and its settings.
3. See what your site sends before anyone agrees
Most claims turn on this, so find out for yourself. Open your site in a private window, don't click the banner, and list every third-party domain that receives a request. Look especially for:
facebook.comorconnect.facebook.net(Meta Pixel)analytics.tiktok.comstatic.hotjar.comor other session recordersgoogleads.g.doubleclick.netwith consent granted- Chat widgets that load before consent
If Google's requests are on the list, our guide to checking Consent Mode v2 shows how to read the consent state each one carries.
4. Forward everything to a lawyer
Send the letter, your captures and a short plain description of your setup (platform, consent tool, who manages Tag Manager). That's usually enough for a first conversation.
What to fix, once a lawyer has seen it
These are the usual gaps, and they're worth fixing whatever happens with the letter.
| Gap | Fix |
|---|---|
| Pixels fire on page load before any choice | Hold them until consent where the law asks first, and stop them as soon as a visitor opts out elsewhere |
| No way for US visitors to opt out | A visible "Your privacy choices" link that stops the tags |
| The browser privacy signal (GPC) is ignored | Treat it as an opt-out, before anything fires |
| Reject is hidden or harder than Accept | Same size, same colour, on the first screen |
| No record of what visitors chose | Keep a record per visitor, with the wording they saw |
| Trackers pasted into your theme, not Tag Manager | Find them and hold them too. They're the easiest ones to miss |
What a consent record helps with
A good record won't make a claim go away, but it answers the questions that come next. What did this visitor see, what did they choose and when, and which version of the banner was live?
If the record holds the wording, the choice, the time and the region, without the visitor's IP address, you and your lawyer have facts to work from instead of guesses.
After it's fixed: keep checking
In the Todd Snyder case, California's privacy regulator said a misconfigured privacy portal meant opt-out requests went unprocessed for 40 days. The company agreed to pay $345,178.
A banner that worked on launch day can break when a developer adds a new script or a plugin updates, and tags can change without anyone being told.
How TagSentry helps
TagSentry finds your trackers. Once you've approved them, and while our banner is in charge, it holds them until each visitor's rules allow them, pixels pasted outside Tag Manager included.
It treats GPC as an opt-out of advertising and keeps a consent record for 24 months with no IP address or browser details. Our free scan shows what your site sends before anyone agrees, from one page load in the US, and you don't need an account.
Sources
- Shumaker: Your website may be a lawsuit waiting to happen
- Revision Legal: CIPA website tracking demand letters
- Loeb & Loeb: The millisecond problem, pre-consent tracking and CIPA
- DLA Piper: Governor Newsom signs SB 690 (October 2026)
- Covington Inside Privacy: Governor signs SB 690 and calls for broader CIPA reform
- CNIL: SHEIN fined 150 million euros over cookies
- CNIL: Google fined 325 million euros over cookies and inbox ads
- CPPA: Todd Snyder enforcement announcement