NOPE · AI and people

AI incidents

Name: NOPE: AI incidents
Creator: NOPE

Reports of AI-related harm and adverse experiences affecting people’s safety, wellbeing, rights and livelihoods. Explore what happened and the evidence available.

NOPE’s core concern is when AI communicates with a person, acts on their behalf, or depicts or impersonates them. The tracker is wider: it also records consequential decisions and claims about people. Each account is reviewed for publication; claims may remain uncorroborated or disputed. How we review and count cases

Explore incidents Our scope and evidence

In this selection

Published cases: 1
Countries with reported events: 1; Located 1 of 1 cases · 0 unknown
Languages in checked sources: 1; Recorded for 1 of 1 cases

0Core concern
AI communicated, acted for, depicted or impersonated 1Contextual cases
AI made a decision or claim about someone 0Unknown or pending relation
0 legacy rows pending · 0 explicitly unknown

These figures describe the cases collected by NOPE. Coverage varies with discovery, reporting and available evidence. They do not estimate how often AI-related harm occurs.

0cases with a recorded lawsuit outcome 0cases with a recorded regulatory response 0cases involving minors

Response counts currently use each case’s principal recorded outcome. Further proceedings may be described in its account.

When events happened

1 cases without a known event year

Cases in this selection, counted once in their first known event year. A series may continue beyond that year. Reporting and collection dates are excluded.

No known event years in this selection.

Search cases Consequence Event country

More filters: AI relation, use, setting, sources and responses

AI-to-person relation Setting Whose AI use Source type inspected AI system Reported severity Response / population Legacy evidence assessment

Event year Sort by Clear filters

1 of 174 published cases

Export JSON Export CSV

Event date unknownUnited StatesFlock Safety automated license plate readers (San Jose Police Department camera network)

San Jose: police officer fired after passing Flock license-plate-reader location data to a relative accused of domestic violence, who used it to find his accuser

San Jose's police chief announced on 11 September 2026 that an officer had been fired after accessing the department's Flock Safety automated license-plate-reader data on his personal phone and giving a vehicle's location to his cousin, a suspect in a domestic-violence case, who used it to locate the woman accusing him. The chief called it 'a betrayal of the public trust', said the officer was placed on leave, criminally investigated and referred to the district attorney, and that the case was submitted to California's peace-officer standards commission for decertification; neither the officer nor the cousin has been charged. The department has since barred access to the system from personal devices and is testing auditing tools. Neither the victim nor the officer is named in the inspected reports.

Contextual tracker case Local tv news AI involvement: supported Causal attribution: supported Medium reported severity Internal Action

Added 16/09/2026

Cases may have several effects and sources. Mixed accounts qualify when they include a reported harm or adverse experience. People are counted within individual cases where sources support a number; we do not publish a collection-wide total of distinct people.

A source’s existence, the experience it reports and AI’s causal role are separate questions. A lawsuit records allegations unless a subsequent finding establishes them.

Methodology and corrections · Subscribe via RSS · Suggest a case or correction · Find support

Last dataset update: 22/09/2026. Dataset available under CC BY 4.0.