Skip to main content

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

2022
2023
2024
2025
2026

2 of 90 incidents

Filters:

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.

Last updated: Sep 6, 2026

Subscribe or export (CC BY 4.0)

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).