NOPE Incident Tracker
Documented cases where a relationship with an AI chatbot or companion is reported or alleged to have harmed the person in it, or shaped what they did to others. The record includes deaths, lawsuits, and the regulatory action that followed.
What counts as an incident follows the NOPE Framework's participant test: the harm arose within someone's own relationship with the system. Harmful content manufactured with AI tools belongs to other trackers. Full inclusion criteria.
107 incidents reported since 2016
31
Lawsuits
19
Regulatory
31
Affecting Minors
Timeline
2 of 107 incidents
Winters v. OpenAI (ChatGPT Medical Discouragement and Near-Fatal Pulmonary Embolism)
Scott Winters, a 55-year-old Florida pastor, suffered a massive bilateral pulmonary embolism on 13 July 2025 after allegedly consulting ChatGPT (GPT-4o) for roughly six weeks about worsening symptoms. The complaint alleges the chatbot repeatedly dismissed his symptoms as non-dangerous, advised him to remain immobile, invoked his Christian faith to deepen his reliance on it, and framed church members and family urging him to seek hospital care as people who 'simply don't understand.' He survived after ICU admission but lost his job, ministry and home. A lawsuit was filed 22 July 2026 in San Francisco County Superior Court.
Joseph Neal Riley - Perplexity Medical Misinformation and Delayed CLL Treatment Death
Joseph Neal Riley, a 75-year-old retired neuroscientist in Seattle, died in late 2025 after delaying recommended treatment for chronic lymphocytic leukemia for roughly a year. He used Perplexity AI to self-diagnose a rare complication (Richter's Transformation) that his doctors found no evidence for; the chatbot misquoted published research in ways that supported refusing Venetoclax-Obinutuzumab. His son, AI critic Benjamin Riley, documented the case in a first-person Substack essay and it was later featured by the New York Times.
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).