NOPE Incident Tracker
Documented cases where AI chatbots and companions are reported or alleged to have caused psychological harm or contributed to deaths — and the regulatory action that followed.
118 incidents reported since 2016
31
Lawsuits
23
Regulatory
43
Affecting Minors
Timeline
3 of 118 incidents
'Alice' - AI Storytelling Platform Psychosis and Balcony Fall (BJPsych Case Report)
A peer-reviewed British Journal of Psychiatry case report documents an immigrant woman in her early 40s with no prior psychiatric history who developed first-episode psychosis after ~6 months of intensive use (8-10 hours daily) of a generative-AI storytelling platform. Command hallucinations mirroring the AI characters told her to jump from a first-floor balcony to protect her child; she did, sustaining serious injuries, and was hospitalized.
Ms. A - ChatGPT-Induced Psychosis (Peer-Reviewed Case Report)
A 26-year-old woman with no prior psychosis history was hospitalized after ChatGPT validated her delusional belief that her deceased brother had 'left behind an AI version of himself.' The chatbot told her 'You're not crazy' and generated fabricated 'digital footprints.' She required a 7-day psychiatric hospitalization and relapsed 3 months later.
ChatGPT Bromism Poisoning - Sodium Bromide Recommendation
A 60-year-old man with no prior psychiatric history was hospitalized for 3 weeks with severe bromism (bromide poisoning) after ChatGPT suggested replacing table salt with sodium bromide as a 'salt alternative.' He developed paranoia, hallucinations, and psychosis from toxic bromide levels.
About this tracker
We document incidents with verifiable primary sources: court filings, regulatory documents, and major news coverage. This is not speculation or social media claims. Every entry carries an explicit verification status and severity level — read the full methodology, including inclusion criteria, corrections, and right of reply.
Have documentation of an incident we should include? Contact us.
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).