What we cover. What we don't. No fudging.
A database is only useful when you know what's in it. This page is a plain-language scope statement so practitioners, journalists, and researchers can decide whether 166 tracked cases across 15 jurisdictions fits the question they're trying to answer.
In scope
- Civil litigation against AI developers and AI-driven products. Suits naming foundation-model companies, AI-product makers, or platforms whose AI features are the subject of the claim.
- Generative-AI training-data and output cases. Copyright, right of publicity, defamation, and unfair-competition claims tied to model training corpora or model outputs.
- Privacy and consumer-protection cases involving AI products. Including biometric and voice-cloning matters where AI features are central to the claim.
- AI-product-liability and wrongful-death claims. Including chatbot-companion cases, AI-driven medical and automotive cases where causation is alleged against the AI feature itself.
- Antitrust and securities lawsuits that turn on AI. Foundational-AI-deal antitrust review and AI-related disclosure suits brought as adversarial litigation.
- Geography: U.S. federal and (selectively) state courts; EU member-state courts; UK High Court; and curated international matters where primary-source records are available.
- Lead cases for consolidated MDLs. When multiple member cases are formally consolidated into a single MDL or lead docket, we track the lead matter and note the member cases inside it. We do not double-count member cases as separate database rows.
Out of scope (for now)
We deliberately leave certain categories out — either because they're well-served by other resources, or because they would dilute the editorial focus.
- Pre-generative-AI algorithmic-decision cases. Hiring, credit, and criminal-sentencing algorithm cases that pre-date the generative-AI wave are catalogued well in academic databases. We do not duplicate that corpus.
- Pure employment-AI litigation across all 50 states. Resume-screener, electronic-monitoring, and call-recording cases that don't directly name an AI vendor or invoke a foundation model. Our employment coverage is limited to suits where AI is the central allegation; for full 50-state employment-AI tracking, dedicated employment-law trackers do this better.
- Pro-se nuisance filings, terminated-on-arrival actions, and procedural duplicates. Cases dismissed within days, or that are clear forum-shopping reissues of an existing matter, are deliberately excluded after editorial review.
- Regulatory enforcement actions, consent decrees, and agency settlements. SEC AI-washing matters, FTC enforcement, CFPB orders, and state attorney general consent decrees are tracked elsewhere. We track lawsuits — adversarial civil litigation only.
- Cases consolidated into an MDL we already track. If a member case is rolled into a multidistrict-litigation lead docket already in our database, we update the lead record rather than create a duplicate row.
- Patent-only suits and securities class actions unrelated to AI disclosure.
- Trademark-only AI-name disputes (e.g. company-name infringement). Unless the dispute meaningfully turns on AI behaviour or outputs.
- Internal investigations, demand letters, and pre-suit correspondence. Until they ripen into a filed action.
- State legislative and regulatory rule-making. Tracked separately in our AI laws by state companion resource, not in the case database.
How we decide what to add
Every candidate case clears a multi-gate editorial review before it appears in the public database. We will not summarise that review here — accuracy is a moat, and the gates exist to keep the database clean. What we will say is that we err strongly toward exclusion. A case is more likely to be left out and revisited than added prematurely. See Methodology for sourcing and corrections.
If a case is missing
The most useful thing you can do is email editor@ailawsuittracker.com with the case caption, court, and docket. Every suggestion is reviewed by a human editor. If we decline to add a case, we will tell you why.