What to do after a demand letter
What to do after your business receives an ADA or CIPA website demand letter: steps to take, records to keep, and how to respond.
What to do after your business receives an ADA or CIPA website demand letter: steps to take, records to keep, and how to respond.
If your business received a demand letter about your website, don't panic, don't ignore it, and don't start changing your website straight away. Save the letter, preserve records of how your website currently works, and share the letter with legal counsel. A demand letter is an allegation, not a legal finding. Website demand letters usually involve one of two areas: website accessibility or how your website collects and shares visitor data. The letter may mention laws such as the ADA or California's CIPA. We explain what those mean below.
If your business receives a demand letter, the following steps can help you understand the claim and decide what to do next. Before changing your website, it can help to preserve a record of how it is currently set up.
1. Keep the letter. Save it along with any related emails, envelopes, or follow-up messages.
2. Note the key details. Write down who sent it, the date, what it claims, which parts of your website it mentions, and any deadline.
3. Contact legal counsel. A lawyer can explain what the letter means for your business and may ask you to keep certain records.
4. Preserve evidence of how your website works right now. Before making changes, capture the current state of your website. Depending on the claim, this could include screenshots, a scan of the cookies and trackers your site uses, records of visitor consent, an accessibility scan, or a record of recent website changes.
5. Investigate the claim. Check whether the problem described in the letter actually happened on your website at the time.
6. Fix confirmed issues. Address anything the investigation confirms, plus any other gaps you find along the way.
7. Respond to the claimant, with legal counsel where appropriate.
8. Check your insurance. Some business policies may cover this type of claim, and you may need to notify your insurer.
Our guide to responding to a website demand letter provides more detail on each step of the process.
A website demand letter claims that something on your website violates the law. It usually asks your business to fix the alleged problem, pay a settlement, or both. A plaintiff's attorney typically sends it and includes a deadline to respond.
For US businesses, website demand letters commonly involve:
• Accessibility: the letter claims people with disabilities can't properly use part of your website. These claims often reference the Americans with Disabilities Act (ADA).
• Privacy or tracking: the letter claims a tool on your website collected or shared visitor information improperly. These claims may reference state privacy or wiretapping laws such as the California Invasion of Privacy Act (CIPA).
No. A demand letter is one side's claim and often comes before a lawsuit, but it doesn't prove a violation. What matters is the facts: which tools were running on your website, how they were set up at the time, and which laws apply to your business.
Website demand letters affect businesses of all sizes. Some laws provide fixed damages per violation, which can make settlement demands attractive. For example, CIPA allows $5,000 per violation under California Penal Code section 637.2.
The volume is significant. More than 4,300 digital wiretapping lawsuits have been filed since February 2022, according to Fisher Phillips litigation data cited by the Association of Corporate Counsel. On the accessibility side, 360 ADA website lawsuits were filed in September 2026 alone.
Businesses outside California can receive these letters too. Plaintiffs argue that CIPA can apply when a California resident visits a website, regardless of where the business is based. If your letter mentions CIPA, legal counsel can help you understand how the current law may apply to your business.
Most website demand letters fall into one of these two types. Use this table to understand which type of claim your letter may involve and where to start.
ADA demand letter | CIPA demand letter | |
|---|---|---|
What is the claim about? | People with disabilities can't properly use part of your website | Website tools collected or shared visitor information improperly |
Common laws mentioned | ADA Title III, sometimes state laws such as California's Unruh Act | CIPA section 631 or section 638.51, sometimes other state wiretapping laws |
What may be mentioned | Navigation, forms, images, videos, PDFs, checkout | Pixels, analytics, chat, session replay, embedded video |
What should you preserve? | Accessibility reports, scans and records of fixes | Tracker scans, consent records, tag manager history and vendor settings |
Who should investigate? | Legal counsel plus your accessibility or web team | Legal counsel plus your privacy, web or marketing team |
An ADA website demand letter claims that a person with a disability couldn't use part of your website. Examples include an image without a text description for screen reader users, a form that can't be completed with a keyboard, text with poor color contrast, or a checkout that doesn't work with assistive technology.
These letters usually cite ADA Title III, which covers businesses open to the public, and ask you to fix the barriers and pay a settlement.
Many accessibility claims reference the Web Content Accessibility Guidelines (WCAG). WCAG provides technical guidance for making websites more accessible, although the exact legal requirements can depend on the law and jurisdiction involved.
Our ADA demand letter guide provides additional context on these types of claims.
A CIPA demand letter claims that a tool on your website shared visitor information with a third party without proper consent. Common examples are tracking pixels (small pieces of code that report visitor activity to advertising platforms), analytics, chat tools, session replay (tools that record how visitors move and click on your site), and embedded video. The FTC has also highlighted how pixel tracking can share data visitors don't expect.
If your letter mentions CIPA, check which section it cites. That can help you understand what type of website technology the claim involves:
• Section 631 (wiretapping): usually about chat tools and session replay. The claim is that a third party effectively listened in on a visitor's communications.
• Section 638.51 (pen register or trap and trace): usually about pixels and analytics. The claim is generally that a website tool collected information used to identify or track a visitor or their device without the required authorization.
Note: Under SB 690, signed on September 30, 2026, private plaintiffs can no longer sue under Section 638.51 over website or app tracking from January 1, 2027, and the change also reaches pending claims filed in the two years before that date. Section 631 claims are not affected.
Our CIPA demand letter guide explains what each section usually targets and which records to preserve.
Similar claims are brought under other state laws, including Pennsylvania's Wiretapping and Electronic Surveillance Control Act and the Florida Security of Communications Act. Video tools raise their own issues, covered in our guide to website video tracking lawsuits. For a full explanation of the law, see our CIPA guide.
Once you know what the letter claims, investigate that specific issue. Don't try to audit every law at once. Start with the technology, page, or accessibility barrier named in the letter, and preserve the records that show how your website was set up at the relevant time.
Your records form the basis of your response. Use this checklist as a starting point, and share it with your legal counsel and web team.
Records to preserve for a privacy or CIPA claim
• A dated scan of the cookies and trackers your website loads (a cookie scanner can produce this)
• Consent logs or receipts: records showing whether each visitor agreed to tracking, and whether scripts ran before they did
• Your consent banner settings and screenshots
• Tag manager version history (the record of when tracking tools were added or changed)
• Chat and session replay vendor settings
• Privacy policy and cookie policy versions, with dates
• Vendor contracts and data processing agreements
Records to preserve for an accessibility or ADA claim
• Accessibility audit and scan reports (an accessibility scanner can produce a dated report)
• Your published accessibility statement
• Remediation tickets or a log of fixes
• Accessibility issues reported by visitors, for example through an issue reporting tool
• A VPAT or Accessibility Conformance Report, if you have one
Records useful for either type of claim
• A website change log or release notes
• Archived snapshots of relevant pages
• The demand letter itself, with envelope or email details
Consent logs show whether a tracking tool ran before a visitor agreed, which is often the central question in a CIPA claim. Without them, you're reconstructing the past from memory. The same applies to accessibility: dated scan reports and fix logs show what your website looked like and what you'd already done.
How Clym helps you maintain these records Clym's consent management platform creates consent receipts that record visitor consent decisions. RealtimeCompliance™ can control tracking scripts based on consent, while Clym's wiretapping consent functionality can record consent associated with chat and AI assistant interactions.
An accessibility widget can be part of an accessibility program, but it isn’t enough on its own. Website accessibility requires ongoing testing, fixes to underlying barriers, a way for visitors to report issues, and records of the work you’ve done.
Privacy and accessibility involve different requirements, so addressing one doesn’t necessarily address the other. Our guide to website compliance requirements can help you understand what may apply to your business.
Receiving a website demand letter doesn't automatically mean your business violated the law. Preserve the letter and your website records, involve legal counsel, and investigate the specific claim before making changes.
The more documentation you have about your website's accessibility, tracking tools, consent settings, and past changes, the easier it is to understand what happened and respond based on evidence rather than assumptions.
Disclaimer: This article is for informational purposes only and does not constitute legal advice. Clym is not a law firm and does not provide legal advice. Consult a qualified legal professional for guidance specific to your business.
No. Ignoring a demand letter can lead to a lawsuit, and you may lose the chance to resolve the claim early. Don't reply to the sender straight away either. Preserve the letter and your website records, share it with legal counsel, and investigate what the letter claims before you decide how to respond.
No. A demand letter is not a lawsuit. It is typically sent before a lawsuit is filed and gives the recipient an opportunity to respond to the allegations or discuss a resolution. However, a demand letter can lead to a lawsuit, so you shouldn't ignore it.
Because a demand letter can lead to a lawsuit or settlement talks, consider involving legal counsel early. A lawyer can help you understand the letter's claims, which laws may apply, what evidence to preserve, and how your business should respond, including whether to dispute the demand.
Demand letters set their own deadlines, often measured in weeks, but the law doesn't. Note the date as soon as the letter arrives and involve legal counsel quickly, because investigating your website and gathering records takes time. Your attorney can advise whether to ask for more time.
Yes. Plaintiffs argue that CIPA applies whenever a California resident visits your website, no matter where your business is based. Courts still divide on how CIPA applies to website tracking, but letters reach businesses nationwide. Pennsylvania, Florida, and several other states have similar wiretapping laws.
Not on its own. In September 2026, 91 of the 360 companies sued over website accessibility were using a third-party accessibility widget, according to UsableNet. A widget can support accessibility, but you also need regular testing, fixes to underlying barriers, a way for visitors to report issues, and records of your work.
Not before you've preserved evidence. Scan your website, export your consent records, and save your settings and version history first, then talk to legal counsel about changes. Removing a tool too early can make it harder to show what your website was actually doing when the alleged violation happened.