Skip to main content
NOPE

NOPE · AI and people

AI incidents

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 also records consequential decisions, claims and privacy harms involving AI. Each case needs a described connection between AI use and the harm, including private information recorded into or disclosed to an AI service. 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
3
Countries with reported events
1
Located 3 of 3 cases · 0 unknown
Languages in checked sources
1
Recorded for 3 of 3 cases
0Core concern
AI communicated, acted for, depicted or impersonated 3Contextual cases
AI made a decision or claim about someone

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.

3cases 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

0 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. NOPE has searched recent events more thoroughly than earlier years, so bar heights also reflect collection effort.

1 20211 20231 2024
Reported severity HighMedium
More filters: AI relation, use, setting, sources and responses
Clear filters

3 of 1099 published cases

Export JSONExport CSV
17 Sept 2023United StatesUnidentified facial recognition system

Reno casino's facial recognition wrongly matched a patron to a barred man and police jailed him for about eleven hours, his federal lawsuit alleges

Jason Killinger, a UPS truck driver, alleges in a federal civil-rights complaint filed in July 2025 that on 17 September 2023 the Peppermill Casino in Reno reported to police that its AI facial recognition software had identified him as a man barred from the casino months earlier. According to the complaint, casino security handcuffed him, and the responding Reno police officer, told the system had found a 100 percent match, did not examine his other identification and took him to jail as an unidentified person, where fingerprints confirmed who he was. The complaint says he was handcuffed for about four hours, starting in the casino security office, spent about eleven hours in police and jail custody, and was treated the next day for bruised wrists. According to the complaint, he was then charged with trespassing, and a prosecutor dismissed the charge without prejudice at the bench trial. Casino.org reports that he settled a suit against the casino. In March 2026 the court let him add the City of Reno and a municipal liability claim over facial recognition policies, but refused a new wrongful arrest claim against the officer on qualified immunity grounds. In September 2026 the ACLU, the ACLU of Nevada and the Innocence Project filed a proposed amicus brief supporting him. His September 2026 motion for partial summary judgment says a Reno police detective later concluded that the match was wrong and that he and the barred man were different people, and it cites a declaration by a former casino security officer, who worked there from about October 2024, that the system often alerted at 100 percent on the wrong people; in a declaration reported by Casino.org, the officer said he had never known the system to misidentify anyone. The case is ongoing.

Contextual tracker case Medium reported severity Lawsuit Ongoing

AI involvement reported · Causal attribution alleged · 9 sources, 3 underlying accounts · Added 04/10/2026

14 Aug 2021 to 14 Mar 2024United StatesSt. Louis mugshot recognition (SMRT)

St. Louis County, Missouri: Christopher Gatlin was arrested in August 2021 after officers ran a grainy bus surveillance photo through a regional facial-recognition system and was held roughly 17 months (Post-Dispatch and Bloomberg Law: about two years) on a first-degree assault charge dismissed in March 2024; his federal civil-rights suit (filed January 2025) was amended in August 2026 to add Amazon Web Services, whose Rekognition technology the complaint says underpinned the match

Christopher Gatlin was arrested on 14 August 2021 for an assault at the St. Charles Rock Road MetroLink station after a joint St. Louis County and city team uploaded a grainy, blurry surveillance photograph from a bus into the St. Louis Mugshot Recognition Technology System, a facial-recognition tool that searches stored mug shots (more than 500,000 uploaded, the suit says per the Post-Dispatch; more than 250,000 per Biometric Update via Hoodline), and built the investigation around the resulting match together with a witness identification; he was charged with first-degree assault and held roughly 17 months (the Post-Dispatch says almost two years), a county judge suppressed the witness identification as unconstitutionally suggestive, and prosecutors dismissed the charges on 14 March 2024 (Post-Dispatch; Hoodline citing Biometric Update; Bloomberg Law). Gatlin sued St. Louis County, the City of St. Louis and named officers in the US District Court for the Eastern District of Missouri on 13 January 2025; on 15 October 2025 the court denied the city's motion to dismiss and granted a detective's motion only as to one count; on 13 August 2026 the court allowed a second amended complaint adding Amazon Web Services, which the complaint says supplied the Rekognition program the system used; the county, city and officers answered on 27 August 2026, AWS's response was extended to 21 September 2026 and on 17 September it moved for a further extension to 28 September (no ruling on the docket when read), and a jury trial is set for 1 November 2027 (CourtListener docket). Amazon told the Post-Dispatch that its terms of service prohibit the use of its facial recognition technology in criminal investigations and that it would fully investigate any information that emerges in the litigation. The ACLU lists Gatlin among fourteen people known to have been wrongfully arrested in the US because police relied on erroneous facial-recognition results.

Contextual tracker case High reported severity Lawsuit Ongoing

AI involvement reported · Causal attribution alleged · 5 sources · Added 26/09/2026

1 Aug 2024 to 1 Oct 2024United StatesFACES facial recognition

Florida: 93% facial-recognition hit led to Robert Dillon's arrest as an attempted child abductor; charges dropped, ACLU suit filed

In August 2024, Robert Dillon, a 52-year-old self-employed commercial crabber from the Fort Myers area, was arrested at his San Carlos Park home on a third-degree felony warrant for the attempted luring of a child at a Jacksonville Beach McDonald's in November 2023 — a crime he had no part in. The warrant rested on a 93%-confidence result from FACES, the Face Analysis Comparison and Examination System maintained by the Pinellas County Sheriff's Office, run against low-resolution cell-phone photos of a surveillance screen, plus a restaurant employee's photo-lineup identification. Dillon spent a night in jail and bonded out against his truck's title; prosecutors dropped the charges in October 2024 after work-alibi evidence, but it took about a year to expunge the arrest and remove his mugshot. In June 2026 the ACLU filed a federal lawsuit (M.D. Fla.) against Jacksonville Beach, the Jacksonville sheriff and the Pinellas County Sheriff's Office, calling Dillon one of at least 14 known wrongful arrests from police reliance on facial recognition since 2019.

Contextual tracker case Medium reported severity Lawsuit Filed

AI involvement supported · Causal attribution supported · 3 sources · Added 15/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: 04/11/2026. Dataset available under CC BY 4.0.