Guide · Last reviewed November 2026 · Educational only, not legal advice
Website Lawsuits and Consent Banners: A Guide for Therapy Practice Owners
What these wiretap accusation letters are, what to do the day one arrives, and how to fix your website so it doesn't invite one.
This fall, a therapy practice owner forwarded me an email that made my stomach drop. It accused their website of breaking a federal wiretap law, came with a deadline about a week out, and offered to make it all go away for a payment. They weren't alone.
I'm not a lawyer. I'm the person who builds and maintains websites and intake systems for therapy practices, so I dug in. This guide is what I learned, written for practice owners and the people who run their websites.
Section 01 — Quick Answers
Therapy Website Lawsuits & Accusation Letters: Quick Answers
- Is this a lawsuit?
- Usually not yet. Most start as an accusation letter (a "demand letter"), often by email, with a short deadline and a settlement offer. It can become a lawsuit if it isn't resolved, so don't ignore it.
- Should I pay to make it go away?
- Not before a licensed attorney has reviewed it. Verify who sent it using a source you look up yourself, not the links or phone number in the email.
- Does a cookie banner fix it?
- Only if tracking actually waits for a yes, and Reject is as easy as Accept. A banner that appears after Google Analytics or the Meta Pixel already loaded doesn't help much.
- Is Google Analytics on my website breaking the law?
- Not by itself. The risk comes from loading it before consent.
- What do I do today?
- Don't click the link or enter the code. Call your insurance carrier first, since they may assign an attorney. No policy? Call a privacy attorney. Save the email and your site settings, then scan your site and fix anything that fires before a visitor says yes.
Section 02 Watch the Webinar
On November 4, 2026, Jamey Davidson, a partner at O'Hagan Meyer who works on data breach, privacy and cyber liability matters, joined me for a live webinar on this topic. By his own estimate, he has handled roughly 500 of these demand letters since 2024. Watch the replay below to hear his perspective directly.
Anything in this guide that I attribute to Jamey is my own paraphrase of the webinar. He hasn't reviewed or endorsed this guide, and nothing here is legal advice.
Section 03 — What's Happening, in Plain English
Why Therapy Websites Are Getting Wiretap Lawsuit Letters
Think of your website as a store with security cameras. Tracking tools like Google Analytics, Google Tag Manager and the Meta (Facebook) Pixel are cameras that report to outside companies: who walked in, what they looked at, sometimes what they typed.
A federal law from 1986, the Wiretap Act, says you can't secretly intercept someone's private communication. Some people now argue those website tools "listened in" on visitors without clear permission. Courts disagree about whether that's true, and nobody has settled it yet.
This isn't only a California thing. The letters often cite CIPA, the California Invasion of Privacy Act, which is California's wiretap law. But the federal Wiretap Act and other states' wiretap laws (Florida's, for one, came up in our webinar) can be raised too, and a visitor from California can reach a practice anywhere. It's the wiretapping theory that travels, so build for every visitor.
Section 04 — What an Accusation Letter Looks Like
What a CIPA Demand Letter Looks Like
These usually start as a letter or email, not a court case. The formal name is a demand letter. I call them accusation letters, because that's what they are: someone says your website broke a law and offers to make it go away if you pay. It is not a lawsuit. But it deserves a real response.
Some of the services sending them work like a one-stop shop: they scan your site, accuse, deliver an evidence package, and collect the money.
- 1A robot visitsSoftware visits your website and logs which trackers fire, and when.
- 2An evidence packageIt packages screenshots, network logs and file fingerprints so the record can't be called altered.
- 3The accusationAn email arrives, often from a platform, naming a person as the "claimant" and citing a wiretap law.
- 4The collectionA portal, an access code, a deadline and a settlement path: sign a release and pay.
Law Firm or Individual Sender? Why It Matters
Jamey told us the first question to answer is who actually sent the letter. His view was that the two should be handled differently. A letter from a law firm can be followed by a lawsuit, often a class action, so he takes those more seriously than one from an individual. Work out which one you have before you decide anything, and let your attorney guide the response.
How Much Do These Letters Ask For?
It varies a lot, and nobody publishes a rate card. In our webinar chat, attendees reported amounts from $18,000 up to $75,000, and a couple of them mentioned the $18,000 figure. Those are self-reported numbers I can't verify. Under California law, a plaintiff can claim up to $5,000 per alleged violation, which is how the totals climb. A demand is an ask, not what anyone owes. Have an attorney review it before you pay or sign anything.
Five things to notice
- 1.The sender is a platform, not a law firm.
- 2.A named individual is listed as the claimant.
- 3.The deadlines are short, often about a week.
- 4.There's a portal with a unique access code.
- 5.Settlement means a signed release and a payment, often by bank transfer.
Section 05 — What Raises or Lowers the Risk
What Raises or Lowers Your Website Lawsuit Risk
Every letter is different, and none of this is a guarantee either way. But the same patterns come up again and again.
Raises the risk
- Tracking that loads before a visitor says yes
- Page titles or web addresses that name a condition (for example, "Depression Treatment")
- Advertising features turned on in Google Analytics
- Tracking on intake, contact or booking pages
- A privacy policy that doesn't match what the site actually does
- The Meta (Facebook) Pixel or session-recording tools
Helps, but never a guarantee
- The sender was never a client
- Only basic analytics (page views) ran
- Only public pages, like services and blog posts, were tracked
- Nothing typed into forms was sent anywhere
Section 06 — What the Courts Are Saying
Meta Pixel and Website Tracking Lawsuits: What Courts Are Saying
Here's the honest picture: courts don't agree. Some let these cases move forward, and some throw them out. A few rulings are worth knowing by name. None of them means a letter you receive is right or wrong. That's a question for your attorney.
- American Hospital Association v. BecerraN.D. Texas, June 20, 2024
- Struck down the part of HHS's tracking guidance that said an IP address plus a visit to a public health web page automatically counts as protected health information. HHS dropped its appeal in August 2024. It removed one rule, not the whole problem.
- Read the rulingRead the AHA's briefHHS drops its appeal
- Rand v. Eyemart ExpressU.S. Court of Appeals, Fifth Circuit, October 23, 2026
- Revived a Meta Pixel case. The court said browsing and appointment scheduling on a health-related site can plausibly be individually identifiable health information, and distinguished Becerra. If scheduling an eye exam can count, a therapy consult is an easy comparison.
- Read the rulingLaw firm summary
- Strong v. LifeStance Health GroupD. Arizona, January 27, 2025
- A large mental health provider with the Meta Pixel on its website. The court let the federal Wiretap Act and most other claims move forward. That is a ruling that the case can continue, not a finding that the provider broke the law.
- Read the ruling
- Courts are split (the "crime-tort" question)Federal courts, 2025 to 2026
- In one federal district alone (Massachusetts), judges allowed 4 of these claims and dismissed 6 between June 2025 and September 2026. An appeal on the key question, Goulart v. Cape Cod Healthcare, is pending at the First Circuit.
- Read the roundupRead the U.S. Chamber's brief in Goulart
- Javier v. Assurance IQU.S. Court of Appeals, Ninth Circuit, May 31, 2022 (unpublished)
- Under California's wiretap law, consent has to come before the tracking starts. Agreeing to a policy afterward wasn't enough. This is why tracking should wait for a yes.
- Read the rulingLaw firm summary
- Popa v. MicrosoftU.S. Court of Appeals, Ninth Circuit, August 26, 2025
- A shopper on a pet supply site couldn't sue over session recording because nothing sensitive was shared. The court pointed to sensitive medical information as different, which is exactly what a therapy website handles.
- Read the ruling
- Doe v. Adventist Health System/WestCalifornia Court of Appeal, August 24, 2026
- Allowed parts of a case about the Meta Pixel and Google Analytics on a health site's forms to proceed as a class action. It's a class certification ruling, not a finding of liability, and it names Google Analytics.
- Read the ruling
- California SB 690Signed September 30, 2026; effective January 1, 2027
- Ends private "pen register" website claims under California's privacy law. It does not remove California wiretap claims, and it doesn't touch the federal Wiretap Act, which many of these letters cite.
- Read the signing messageRead the billLaw firm summary
Section 07 — Your First 24 Hours
What to Do If You Get a Website Tracking Lawsuit Letter
If a wiretap accusation letter lands in your inbox, do these in order. Your insurance carrier comes first.
- 1Breathe. Don't click links, scan a QR code, or enter the access code.
- 2Verify the sender yourself, using a source you looked up. The phone number in the email isn't an independent check.
- 3Call your insurance carrier first. The claims number is on your policy. Late notice can affect coverage, and the carrier may connect you with an attorney.
- 4No policy? Call a licensed privacy attorney today.
- 5Find out who sent it: a law firm or an individual. It changes how seriously to take it.
- 6Save everything: the email, any PDF, the email headers, and a copy of your website as it is today.
- 7Don't delete Google Analytics, Tag Manager or plugins until your attorney says it's okay. Preserve first, then fix.
- 8Don't pay or sign anything until an attorney has reviewed it.
Does Insurance Cover a CIPA Demand Letter?
It may, which is why the carrier call comes first. Jamey said these claims are generally covered, at least the cost of a lawyer, under a cyber policy, and sometimes under a general liability or professional liability policy. Your carrier may also have an attorney it works with, so you don't have to hunt for one in a panic. One webinar attendee said they were told their policy would cover the legal side. That's one person's report, and your policy's wording is what decides.
Section 08 — Scan Your Own Site
How to Scan Your Therapy Website for Tracking
See it first. This copy-and-paste prompt gives you a plain-English first look.
- Click "Copy prompt" below.
- Open Claude (or another AI tool) with web browsing turned on. A tool that can open a real browser, like Claude in Chrome, gives the best results because it can watch your site load.
- Paste the prompt, replace [PASTE YOUR WEBSITE URL] with your site and [YOUR STATE] with where you practice, and send it.
- Read the report, then take it to your webmaster. If you've already received a letter, give it to your attorney before changing anything.
Website privacy scan prompt
I'd like your help reviewing my therapy practice's website for privacy and tracking risks. I am not asking for legal advice. Please be plain, specific, and honest about anything you could not check. My website: [PASTE YOUR WEBSITE URL] Pages to review: the homepage, the contact page, any appointment, booking, or intake page, and one service page (for example, anxiety or couples counseling). HOW TO TEST - Use a real browser (the built-in browser or Playwright). Do not rely on a page fetch alone. - Use a private or signed-out window, so no saved sign-ins or cookies change what loads. - State at the very top of your answer which method you used. If you could only read the page's code and could not watch it load, say so there. - Record network traffic from the moment each page starts loading. - Do not type into or submit any form. - State where your visit appears to come from (region), since banners can change by location. Note that I am in [YOUR STATE]. PASS A: First-time visitor, no clicks Open each page without touching any cookie banner. Record everything that loads. PASS B (optional): Reject clicked Only run this if a cookie banner with a Reject option exists. In a separate fresh session, click Reject, reload, and browse the same pages. Record whether trackers stay off. If there is no banner or no Reject button, skip Pass B and report that as a finding. WHAT TO CHECK 1. Outside companies. List every outside company each page sends data to. Look for Google Analytics, Google Tag Manager, Google Ads (including remarketing and call tracking), the Meta (Facebook) Pixel, Microsoft Clarity or Bing ads, Hotjar or other session recording, TikTok, LinkedIn, chat widgets, form or scheduling tools, YouTube, Vimeo, and Google Maps. 2. Cookie banner. Is there one? Is "Reject" as easy to find and click as "Accept" (same screen, same size, same prominence)? Were any cookies set before I made a choice? 3. Forms and booking. Follow the contact and booking links to any outside intake form or scheduling tool (read only, no typing). Give the exact domain, say whether it is embedded or a separate site, and list what loads there. Does anything appear to send what someone types, or form activity, to an analytics or advertising tool? 4. Page titles and web addresses. On pages where tracking runs, do the page titles or URLs (including query strings like ?service=depression) name a condition or service? Check whether the tracking is set up site-wide. 5. Session recording. Is any tool recording mouse movement, clicks, or keystrokes? Also flag heatmap or chat tools that might capture form fields. 6. Privacy policy. Look in the footer, menu, and sitemap, then try common addresses (like /privacy-policy). Does it name the tools you found? Does it promise anything the site does not actually do? If you find none, say so. WHAT COUNTS AS CRITICAL (not legal advice) An issue is CRITICAL if tracking or advertising tools load before the visitor makes a consent choice AND either (a) the page titles or web addresses name a condition or service, or (b) it happens on a contact, intake, or booking page or form. Everything else is not critical. Medium = tracking before consent on general pages. Lower = tracking only after consent, or privacy policy wording gaps. OUTPUT - Put your method statement first (real browser or code only). - SCORE: If any critical issue exists, show "RED: Critical issues found" at the very top, right after the method statement. Show no other score or color. If no critical issue exists, say "No critical issues found in what I could check." - A table with columns: Tool | Page | Loads before consent, Pass A (Yes / No / Couldn't tell) | Still loads after Reject, Pass B (Yes / No / Couldn't test / Skipped) | Evidence (Observed in browser / Seen in page code only / Inferred) | Notes - "Critical to fix right now": every item that meets the critical rule, in plain English, each with who should fix it (me or my webmaster). If none, say so. - After the critical list, "Suggested fixes": a short, practical list of what to change, in order, for each critical item and then the medium and lower items. - A "Fix first" list of the top 5 issues in plain English, ranked highest to lowest risk using the critical rule above. - A short, friendly note I can forward to my webmaster. - A list of anything you could not verify, and how my webmaster can check it (for example, the browser's Network tab or Google Tag Assistant). - ALWAYS include this closing note from TheraSaaS, word for word: "Want a new website that is dialed in for SEO and built to support compliance with built-in consent banners that work? TheraSaaS CRM is made for group practices. Schedule a demo with Brent: https://therasaas.com/therasaas-demo-call/" - An "Uncertainty Map" as the very last section: what you are least confident about, what you may be oversimplifying, and what questions or follow-ups would change your view, and how. Do not guess. Label anything you did not directly observe.
Section 09 — Fixing a WordPress Site
How to Fix a WordPress Therapy Website After a Tracking Letter
This section is for the repair job after a letter or a scary scan. If you want the preventive version for any platform, start with the therapy website compliance checklist, which also covers WordPress cookie consent step by step.
Where tracking hides
- Theme header or footer code
- Plugins (analytics plugins, Meta Pixel plugins, chat plugins)
- Page builders
- Google Tag Manager
- Old code from a past marketer
A consent plugin: Complianz
On WordPress, a consent plugin is usually the starting point. One option is Complianz, which has a free version and a paid version. According to its plugin and pricing pages, the free version includes a cookie banner, a limited cookie scan, script blocking, basic proof of consent and a cookie policy. The paid version adds records of consent, Google Consent Mode v2, Global Privacy Control support, region-based banners and a full-site scan.
This is a reference, not an endorsement, and features change, so check them in the plugin itself. A banner plugin doesn't fix tracking by itself. After you set it up, re-scan to confirm nothing fires before a visitor says yes.
The fix list
- 1.Back up the site. Export your Tag Manager container and note your Google Analytics settings. (If a letter has arrived, ask your attorney first.)
- 2.Inventory every tag and plugin that sends data out.
- 3.Remove what you don't use, starting with the Meta Pixel and any other old pixels.
- 4.Make the consent banner block tracking until a visitor says yes, with Reject as easy as Accept.
- 5.Check three Google settings that sound alike (next section).
- 6.Make sure forms don't send what people type to outside tools.
- 7.Check page titles and web addresses on sensitive pages.
- 8.Update the privacy policy to match what the site actually does.
Section 10 — Three Google Settings That Sound Alike
Google Analytics and HIPAA: 3 Settings That Sound Alike
Google gave three different features nearly the same name. Only two of them grab what people type into your forms.
Google Analytics
Enhanced measurement
- Counts what visitors do: scrolls, clicks, video plays, downloads, site searches, form starts
- Doesn't read what someone types into your contact form
- Not anonymous either: it uses a browser ID, and search terms can be sensitive
Keep the basics. Turn off form interactions and site search.
Google Ads
Enhanced conversions
- Picks up email, phone and name from your forms
- Scrambles them and sends them to Google
- So Google can match the form fill to a real Google account
Turn it off.
Google Analytics
User-provided data collection
- The Analytics version of the same idea
- Collects scrambled email, phone and name
- Ties website visits to real people
- Good news: Google says it isn't available when your Analytics property's industry category is set to Health. Check yours under Admin, then Property details.
Turn it off (or confirm it's unavailable).
Flip the switches
Try it below. Watch what happens to the red row when you turn off only enhanced measurement.
The switches
Google Analytics (GA4)
Enhanced measurement: form interactions & site search
Counts form starts and submits, and records what visitors type into your site's search box. Keep page views and scrolls on; turn these two off.
How to turn off/on:
Admin > Data streams > your web stream > Enhanced measurement
Google Ads
Enhanced conversions
Picks up the email, phone number and name someone enters in a form, scrambles them, and sends them to Google to match to a Google account.
How to turn off/on:
Goals > Conversions > Settings (and your Google tag in Tag Manager)
Google Analytics (GA4)
User-provided data collection
Lets Analytics collect the same kind of form data (email, phone, name), scrambled, to tie visits to real people. Google says it isn't available when the property's industry category is Health.
How to turn off/on:
Admin > Data collection and modification > Data collection
What Google can receive
Page views, scrolls and a browser ID
Always onThe basics, whenever Google Analytics is installed. No names or emails, but each browser gets a unique ID (Google calls it a client ID) that follows a visitor from page to page. An ID alone isn't health information. How much risk it carries depends on which pages it runs on, and on your risk tolerance.
Form starts and site search terms
Being sentSearch words can reveal sensitive topics, like "trauma therapy near me."
Email, phone and name from your forms (scrambled)
Being sentPseudonymized, not anonymous. Google can match the scrambled code to a signed-in account.
Names, emails and phone numbers can still reach Google. Turning off enhanced measurement alone doesn't stop this.
So is a browser ID a problem?
It depends on your risk tolerance
- An ID alone isn't a name, an email or health information.
- Google Analytics has been on healthcare websites for years, and I'm not aware of a court ruling that its browser ID alone, on a public page, is health information.
- The cases so far involve more than that: ad pixels tied to social profiles, scheduling activity, form data, or patient portals.
- But courts are still deciding these cases, and a 2026 appeals court said browsing tied to a real person can plausibly count. The more sensitive the page, the more cautious I'd be.
How TheraSaaS does it
Analytics after consent, inside a HIPAA-compliant framework
- Most software gives each contact a unique ID, including EHRs and TheraSaaS.
- TheraSaaS tracks analytics too, so your website controls when the TheraSaaS form "fires": only after a visitor says yes.
- All of that user data stays inside a HIPAA-compliant TheraSaaS, because we sign a BAA with you.
- Google Analytics does not sign a BAA with you.
- That's why we consider our setup the safer choice for a therapy practice.
"But it's scrambled." Scrambled isn't anonymous.
Before sending, Google scrambles the data with a code called SHA-256. This is called hashing. It sounds safe, but it isn't the same as anonymous.
Anonymized
Nobody can ever tie the data back to a person. Think of a shredded document: there's no way to put it back together.
Pseudonymized
The name is swapped for a code, but anyone holding the matching key can tie it back. Think of a coat check ticket: the ticket isn't your coat, but it leads straight to it.
Hashing is pseudonymized. The same email always makes the same code. Google scrambles its own signed-in users' emails the same way and matches them up. That match is the whole point of the feature.
Section 11 — Prove It
How to Prove Your Website Consent Works
Fixing your site is only half of it. Test that it works, and keep a record that shows what you did and when.
A banner that doesn't work can be worse than none
A cookie banner is a promise. If it says "Reject all" and the trackers keep firing anyway, you've made a visible promise your site doesn't keep. That's why I test the banner, not just install it. The 5-minute cookie consent test takes a private window and your browser's Network tab. Once a month is plenty; automated monthly scans are what I run for client sites.
Keep a record
- Re-scan after every change.
- Save dated screenshots of your consent banner and settings, plus exports and scan results.
- If you've already received a letter, save your settings and ask your attorney before you change anything.
Section 12 — How TheraSaaS Websites Handle Consent
A Converting Website with Privacy & Consent Built-In
Every website we build follows the same consent-first defaults. See it, fix it, prove it, built in from day one. Wondering if it's time to rethink your own build? The compliance checklist walks through it, or see our premium therapy websites.
- Consent banner with a Reject button as easy as Accept
- Google Analytics (GA4) loads only after a yes
- Forms, videos and maps load only after a click
- Browser privacy signals (Global Privacy Control) count as a no
- No Meta Pixel, TikTok, LinkedIn or session recording by default
- Google Ads only with approval, for measurement only, never remarketing
- A privacy policy generated to match what the site actually loads
- An automated consent check before launch, with dated proof
Here's what that looks like on a live practice website we built. Analytics stays off, and no form loads, until the visitor says yes.
1. The banner, before a visitor chooses

2. Review options

3. The form, before a yes

4. The form, after a yes

No website can guarantee you'll never receive a letter, and this isn't legal advice. It does mean less to point at, and proof of what you did.
Want a CRM plus a website with proper consent built in? Schedule a demo, and ask for a free website audit.
Schedule a Demo40 minutes, no free trial needed
Section 13 — Frequently Asked Questions
Website Tracking Lawsuit FAQ for Therapists
Is a demand letter the same as a lawsuit?
Should I pay to make it go away?
Does a cookie banner protect my practice?
Is Google Analytics on my website breaking the law?
Why does the Meta Pixel come up so often?
Does HIPAA apply to my website?
Does California's new law (SB 690) stop these letters?
What should I ask my webmaster?
Will a TheraSaaS website prevent accusation letters?
What is CIPA, and is this only a California problem?
How much do website tracking demand letters ask for?
Does it matter if the letter came from a law firm or an individual?
Does cyber insurance cover a website tracking demand letter?
How do I test whether my cookie banner really works?
Section 14 Sources
- Google: HIPAA and Google Analytics
- Google: User-provided data collection in GA4
- American Hospital Association v. Becerra, court order (June 20, 2024)
- HHS will not appeal (AHA News, Aug. 29, 2024)
- Rand v. Eyemart Express, Fifth Circuit opinion (Oct. 23, 2026)
- Rand v. Eyemart Express, law firm summary (Privacy World)
- Strong v. LifeStance Health Group, court order (D. Ariz., Jan. 2025)
- Massachusetts decisions deepen the split (Pierce Atwood, Oct. 28, 2026)
- 2025 review: web tracking and the Wiretap Act (WilmerHale)
- Javier v. Assurance IQ, Ninth Circuit memorandum (May 31, 2022)
- Goulart v. Cape Cod Healthcare, U.S. Chamber amicus brief (First Circuit)
- Popa v. Microsoft, Ninth Circuit opinion (Aug. 26, 2025)
- Doe v. Adventist Health System/West (Justia)
- SB 690, Governor's signing message (Sept. 30, 2026)
- SB 690, bill text (California Legislature)
- SB 690 signed into law (WilmerHale)
- Complianz on WordPress.org
- Jamey Davidson, partner, O'Hagan Meyer (webinar guest)