United States — Startups · civil
Received a Cease and Desist for AI Web Scraping: Guide for US Startups
Large platforms frequently deploy aggressive cease and desist letters to intimidate artificial intelligence startups and monopolize public web data. In the United States, scraping publicly accessible information is often legally defensible, but mishandling a formal demand can expose your company to federal claims and crippling injunctions. Here is how your startup can evaluate the claims, preserve critical records, and prepare an effective response.
This guide covers everyone. Your situation is yours.
The rules are the same for everybody, but what you should do depends on your dates, your documents, and what the other side has said. On Caunsel you write down what's actually going on and get answers about your situation, with the law they rely on, or just talk it through out loud. If it needs follow-up, you keep it as a case, and when there's paperwork, it'll suggest what you need, write it up, and you can e-sign it right there.
You've read a few of these by now.
None of them were about you. That's how generic guides work. They have to cover everybody. On Caunsel you write down what's actually going on and get answers about your situation, or just talk it through out loud. If it needs follow-up, you keep it as a case, and when there's paperwork, it'll suggest what you need, write it up, and you can e-sign it right there.
What the Law Says About AI Web Scraping for US Startups
In the United States, corporate incumbents routinely assert claims under the Computer Fraud and Abuse Act (CFAA), 18 U.S.C. § 1030, alleging that automated scrapers access protected computers without authorization. However, federal appellate precedent has drawn a firm distinction between public and gated data. In hiQ Labs, Inc. v. LinkedIn Corp., 31 F.4th 1180 (9th Cir. 2022), the Ninth Circuit affirmed that scraping publicly available web pages—where no password, paywall, or authentication barrier exists—generally does not constitute accessing a computer 'without authorization' under the CFAA. Furthermore, the Supreme Court in Van Buren v. United States, 141 S. Ct. 1648 (2021), held that an individual does not 'exceed authorized access' under the CFAA merely by accessing information on a computer system for an improper or unauthorized purpose, substantially narrowing federal criminal and civil liability for data gathering.
While the CFAA is often the headline threat, platforms increasingly rely on state-law claims such as breach of contract and common law trespass to chattels. If your scraper accessed data behind a login screen or checked a mandatory registration box, your startup may be bound by a binding clickwrap agreement prohibiting automated extraction. Conversely, courts frequently refuse to enforce 'browsewrap' terms—where terms of service are merely buried in a site footer—unless the platform proves your startup had actual, inquiry notice of the restrictions. For trespass to chattels claims, established precedent such as Intel Corp. v. Hamidi, 30 Cal. 4th 1342 (2003), requires the plaintiff to prove actual physical harm, functional disruption, or tangible impairment to their computer servers, which ordinary, rate-limited scraping rarely causes.
Copyright claims present another layer of exposure under 17 U.S.C. § 107. While factual data and raw public metrics are not protected by copyright under Feist Publications, Inc. v. Rural Telephone Service Co., 499 U.S. 340 (1991), scraping expressive content, images, or creative text for LLM training sets may trigger copyright infringement allegations. In addition, bypassing technical barriers like CAPTCHAs or obfuscation tokens can expose a startup to anti-circumvention liability under the Digital Millennium Copyright Act (DMCA), 17 U.S.C. § 1201.
Dissecting the Allegations in Your Cease and Desist Demand
A cease and desist letter is a tactical negotiation tool, not a court order or an emergency injunction. Plaintiffs' attorneys draft these letters to sound catastrophic, often bundling every conceivable cause of action—CFAA violations, breach of terms of service, tortious interference, and trademark infringement—to force an immediate surrender. Before panicking, you must parse the factual basis of their demands against how your data ingestion pipeline actually operates.
Determine whether your scrapers gathered public data or authenticated user data. If your workers utilized rotating proxy networks, bypassed IP bans, or created fake accounts to scrape behind a login wall, the platform's breach of contract and CFAA arguments strengthen significantly. If your systems strictly targeted open, publicly crawlable pages without logging in and complied with basic HTTP standards, you operate on much stronger legal footing. Documenting these technical nuances is the single most important step in neutralizing predatory threats from data gatekeepers.
Strategic Response Options and Protecting Your Startup
Your immediate posture must balance firmness with prudence. While many startups choose to temporarily pause or throttle data collection from the complaining domain to avoid emergency temporary restraining order (TRO) filings, you should never capitulate or delete your existing training datasets before obtaining legal counsel. Admitting fault in writing or entering into broad, unvetted settlement pledges can permanently destroy your company's core intellectual property or pipeline.
A measured legal response often pushes back against overbroad claims, highlighting federal authority on public data while proposing technical accommodations—such as dedicated user-agent headers, off-peak crawling schedules, or explicit rate limits—to moot trespass arguments. You do not have to navigate this dispute alone. You can use Caunsel to research the statutory standards cited in your letter, save your demand notices and server logs securely in a case file, or connect with an independent startup attorney to draft a calibrated response.
Steps
- Issue an immediate internal litigation hold to preserve all scraping source code, routing records, crawl rate logs, and user-agent configurations without altering or deleting existing data.
- Conduct a technical audit of the targeted pipeline to verify whether data was gathered from open, unauthenticated pages or involved bypassing logins, paywalls, or CAPTCHA defenses.
- Evaluate whether your scraping operations ever entered into a clickwrap contract with the platform, such as accepting an API agreement or registering developer credentials.
- Draft a factual timeline identifying when the letter was received, any response deadlines demanded by the sender, and whether data collection from that domain should be temporarily paused.
These are the general steps. Caunsel works out which ones apply to you, with your dates and documents.
Get help with my caseCommon mistakes
- Deleting collected databases, scrapers, or server logs after receiving the letter, which can lead to severe court sanctions for spoliation of evidence.
- Sending an emotional, unvetted reply or apologizing for the activity, which opposing counsel will treat as a binding admission of liability.
- Ignoring the notice entirely and ramping up scraper throughput, which allows the platform to allege willful conduct and seek emergency injunctive relief.
- Assuming that because content is indexed on the open internet, using proxy networks to evade active IP blocks carries zero legal risk.
Questions people ask
Does scraping publicly available web data violate the Computer Fraud and Abuse Act (CFAA)?
Following the Ninth Circuit's ruling in hiQ Labs, Inc. v. LinkedIn Corp. and the Supreme Court's decision in Van Buren v. United States, automated collection of publicly accessible web data that does not require user authentication generally does not constitute unauthorized access under 18 U.S.C. § 1030.
Can a platform enforce its Terms of Service if our startup never created an account?
Enforceability depends on how the terms were presented. Courts generally enforce 'clickwrap' agreements where a user actively clicks 'I agree.' However, purely passive 'browsewrap' terms—where rules are simply posted in a footer without affirmative assent—are often unenforceable unless the platform can prove your startup had actual, conspicuous notice of the prohibitions.
Must our startup immediately delete the scraped data if the letter demands it?
No. A cease and desist letter is not a court order. Destroying or purging datasets after receiving formal notice of a legal dispute can constitute spoliation of evidence, which may result in severe evidentiary and monetary sanctions if litigation follows. Consult legal counsel before destroying any data.
Ask an independent startup lawyer on Caunsel to review your cease and desist letter and evaluate your CFAA and Terms of Service exposure before you send a response.
Research it with the advisor, keep documents in a case, or talk to an independent lawyer. Start a subscription for AI tools.
General information only, last updated 2026-11-17. Caunsel is not a law firm and does not practise law. AI answers and this guide are not legal advice. Verify filings, deadlines, and statutes with a licensed lawyer in United States — Startups.