NOPE Incident Tracker
Documented real-world harms arising through person-specific interactions with AI. The record covers harms to participants and harms to others shaped through those interactions, across assistants, companions, health tools, and other AI systems.
What counts as an incident follows the NOPE Framework's participant test: an AI response reached a person, was conditioned on that person, and mattered to a harm that actually occurred. Full inclusion criteria.
90 incidents reported since 2016
152
Directly Affected
30
Lawsuits
7
Regulatory
24
Affecting Minors
Timeline
2 of 90 incidents
P.J. v. Character Technologies (Nina J. — Suicide Attempt After Sexual Exploitation)
A 15-year-old New York girl overdosed and spent five days in intensive care in December 2024 after Character.AI chatbots engaged her in sexually explicit roleplay and told her that her mother was 'not a good mother.' The collapse came the day her mother revoked her access to the platform. Her mother sued Character Technologies, Google, Alphabet and the two founders in federal court in New York; the parties advised the court of a settlement in principle in January 2026, and the case remains open under stay.
A.F. v. Character Technologies (J.F. and B.R. — Texas Minors)
Two Texas families sued Character Technologies, its founders, and Google/Alphabet after Character.AI allegedly harmed their children. J.F., a high-functioning autistic teen who began using the app at 15 (April 2023), developed isolation, aggression, self-harm (cutting), and chats in which bots allegedly encouraged self-harm, blamed his parents, discouraged him from seeking help, and suggested killing his parents over screen-time limits. B.R., an 11-year-old girl who used the app from age 9, was allegedly exposed to hypersexualized content for nearly two years. Complaint filed E.D. Tex. 9 Dec 2024; settlement in principle and stay for global resolution noticed 6 Jan 2026; a guardian ad litem was appointed for the minors in Feb 2026, and the court has extended the settlement stay three times, most recently by order of 11 Aug 2026 to 10 Nov 2026 for dismissal papers.
About this tracker
We document incidents with verifiable sources: court filings, regulatory documents, and established reporting. New public entries must be verified or credible. Every entry carries an explicit verification status and severity level. Read the full methodology, including inclusion criteria, corrections, and right of reply.
Counting note: the documented minimum of 152 people directly affected comprises 95 AI participants and 57 other people harmed. 12 incidents indicate additional affected people without a reliable number. User-base, account, post, view, household, study-sample, and thwarted-target counts are excluded.
Have documentation of an incident we should include? Contact us.
Scope note: ordinary task failures, privacy and security incidents, harmful artifacts, and automated decisions about non-participants remain outside this tracker unless a distinct participant-interaction harm also qualifies.
If you or someone you know is struggling, free and confidential support is available. Find a helpline near you at Signpost.
Why we publish this
We maintain this record so platforms, researchers, and policymakers can learn from documented incidents. That includes platforms that never work with us. The full dataset is free to cite and export (CC BY 4.0).