Skip to main content

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

In this selection

Published cases
9
Countries with reported events
3
Located 7 of 9 cases · 2 unknown
Languages in checked sources
1
Recorded for 9 of 9 cases

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.

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

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.

Reported severity HighMediumLow
More filters: AI relation, use, setting, sources and responses
Clear filters

9 of 1102 published cases

Jan 2021United StatesHireVue (reported)

Massachusetts job applicant alleges CVS's AI-analysed HireVue video interview was an unlawful lie detector test; court let his claim proceed, then he settled

A man who applied for a supply chain job with CVS in Massachusetts around January 2021 says CVS put him through a HireVue video interview with questions about integrity, and alleges that HireVue sent the recording to a platform called Affectiva, which analysed his facial expressions, eye contact, voice intonation and inflection with artificial intelligence and fed a score to CVS. He sued CVS in a proposed class action under the Massachusetts Lie Detector Statute, alleging the interview was a lie detector test and that the online application lacked the notice of rights the law requires. He says he did not know the interview was a lie detector test and would not have taken part had he known. In February 2024 a federal judge in Massachusetts denied CVS's motion to dismiss the notice claim, finding a concrete informational injury; CVS had not challenged the other claims at that stage. A law firm commentary says he was not hired. In July 2024 he reached an individual settlement with CVS, whose terms were not reported. The allegations about the AI analysis were not tested in court.

Contextual tracker case Low reported severity Lawsuit Settled

AI involvement reported · Causal attribution alleged · 3 sources · Added 02/11/2026

2019Event location unknownSiri

Whistleblower says accidental Siri activations recorded private conversations heard by Apple contract graders; Apple apologised and later settled class suit

On 26 July 2019 the Guardian reported that contractors grading a small share of Siri recordings for Apple regularly heard confidential information. Its anonymous source, a contractor, said Siri was often activated by mistake, for example by the sound of a zip, and that these accidental activations captured private discussions between doctors and patients, business deals, apparently criminal dealings and sexual encounters, with location, contact details and app data attached. Apple told the Guardian that requests were not linked to users' Apple IDs and that less than 1% of daily activations were graded. On 28 August 2019 Apple apologised, said it had suspended human grading, and said audio would no longer be retained by default, grading would become opt-in and recordings found to be inadvertent triggers would be deleted. Device owners' class action, Lopez v. Apple in the federal court in Oakland, alleged that Apple recorded private conversations after unintended Siri activations and disclosed them to third parties. Apple agreed to pay $95 million while denying wrongdoing, and co-class counsel say the judge granted final approval on 16 October 2025.

Contextual tracker case Medium reported severity Lawsuit Settled

AI involvement supported · Causal attribution supported · 4 sources · Added 29/10/2026

23 Feb 2024United KingdomMetropolitan Police live facial recognition

London: Met Police live facial recognition wrongly matched a man to his watchlisted brother; officers stopped him and he later received a settlement

On 23 February 2024 Shaun Thompson, a London community volunteer whom the 2026 judgment describes as 39, walked past a Metropolitan Police live facial recognition deployment near London Bridge station. The High Court records as not in dispute that the system detected a high level of facial similarity between images of him and the watchlist image of his brother, who was the subject of an outstanding arrest warrant, and generated an alert. According to the court's account, officers stopped, detained and questioned him and made him prove his identity, and when he declined to have his fingerprints taken he was threatened with arrest; he says the experience left him angry and distressed. Officers ended the engagement after checking police records about his brother, and he confirmed his identity with a passport photograph on his phone. Big Brother Watch, whose director was his co-claimant, says he was held for almost 30 minutes despite showing several identity documents. His judicial review claim about the stop, issued in May 2024, was withdrawn under a consent order agreed on 18 December 2024 on terms including a settlement sum paid to him. An amended challenge to the Met's revised live facial recognition policy of September 2024, brought with Big Brother Watch's director, was dismissed by the Divisional Court on 21 April 2026; the court said it was not judging the merits of the technology, and the claimants announced plans to appeal.

Contextual tracker case Medium reported severity Lawsuit Dismissed

AI involvement supported · Causal attribution established · 4 sources, 3 underlying accounts · Added 26/10/2026

2 Aug 2020United StatesUnidentified license plate reader

Aurora, Colorado: police held a woman and four children at gunpoint in 2020 after a plate reader matched her SUV to a stolen motorcycle, The Denver Post reports

On 2 August 2020 Aurora police officers stopped an SUV they believed to be stolen, ordered the woman driving it and four children to lie on the ground at gunpoint, and handcuffed two of the children. The Denver Post reported that a license plate reader at an Aurora intersection had alerted police because the SUV had the same plate number as a stolen motorcycle from Montana, and that officers did not check the reading or the vehicle description. Prosecutors declined to charge the officers in January 2021 and called what happened unacceptable and preventable. The department said all officers were repeating training on license plate scanners. Sentinel Colorado reported that the department's system had flagged the SUV, which carried Colorado plates, and that the City of Aurora agreed in February 2024 to a $1.9 million settlement with the woman and the children to resolve a lawsuit over the officers' actions. One officer was suspended for 160 hours. The woman said the stop destroyed her mentally and that one of the children became withdrawn.

Contextual tracker case Medium reported severity Involving minors Lawsuit Settled

AI involvement reported · Causal attribution supported · 2 sources · Added 05/10/2026

16 Apr 2021United StatesFlock Safety license plate readers (reported)

Atherton, California: police stopped a driver at gunpoint in April 2021 and made him lie on his stomach to be handcuffed after a license-plate reader misread the letter H on his dirty plate as M and matched it to a stolen car; the town settled his lawsuit for $45,000 in 2023

At about 5:30 a.m. on 16 April 2021, according to a lawsuit reported by The Almanac, an automated license-plate reader in Atherton, California, misread the dirt-obscured plate of a driver's car, reading its letter H as M, and matched it to a reported stolen vehicle. Atherton police followed the car for several minutes without visually verifying the plate, then made a high-risk felony stop, ordering him at gunpoint to throw his keys out of the window, get out and lie on his stomach to be handcuffed. He sued three officers in 2022 for unreasonable seizure and excessive force; the officers denied the allegations and the injuries he claimed, and the case was settled on 16 March 2023 for $45,000. Business Insider, citing police records, reported in March 2026 that the misread came from a Flock camera and that officers noted the Flock cameras had misread the plate; an Atherton police commander said the plate was obstructed by dirt and that the town denies wrongdoing.

Contextual tracker case Medium reported severity Lawsuit Settled

AI involvement supported · Causal attribution supported · 2 sources · Added 04/10/2026

23 Jul 2023United StatesFlock Safety license plate readers

Police in New Mexico handcuffed two sisters, one a child, after a Flock plate camera misread a digit and flagged their car as stolen, lawsuits say; settled 2025

On 23 July 2023 Española police officers pulled over a car driven by a 21-year-old woman with her 12-year-old sister as a passenger, after a Flock Safety camera at an intersection flagged the car's plate as belonging to a vehicle stolen in Rio Rancho. According to the sisters' lawsuits, reported by the Santa Fe New Mexican in January 2024, the camera had read a 2 on the plate as a 7, and officers handcuffed both sisters and placed them in the backs of separate police vehicles before discovering the error; the older sister had asked an officer to call their mother, who lived nearby, to collect the girl. The suits sought damages for anxiety, fear, worry and restriction of movement. Business Insider, which reviewed the body-camera footage and incident report, reported in March 2026 that officers said the number was obscured by a license plate cover although it is visible in the footage, and that the family settled with the city in 2025.

Contextual tracker case Medium reported severity Involving minors Lawsuit Settled

AI involvement supported · Causal attribution supported · 2 sources · Added 04/10/2026

11 Apr 2024United StatesFlock Safety license plate readers

Toledo, Ohio: police stopped a man's pickup at gunpoint in April 2024 after a Flock license-plate camera misread his plate as stolen, released a police dog that bit him, and charged him; prosecutors dropped the charges and he later settled a lawsuit for $35,000

On 11 April 2024 Toledo police officers stopped a pickup truck after a Flock license-plate camera alerted them to a stolen plate. According to the police report and body-camera footage reported by 13abc and ABC News, the camera had misread the plate, which was not stolen. Officers drew their guns, ordered the driver out and to the ground, and a K-9 handler released a police dog as he began to kneel. The driver told ABC News he was bitten seven times on his forearm and elbow, was traumatized and could not work; he was arrested and charged with obstruction, resisting arrest and, later, failure to comply. Prosecutors dropped all charges in August 2024. The department found the dog deployment within policy and reprimanded the officer who made the stop for failing to visually verify the plate against the reader's information. Business Insider reported in March 2026 that police records show the camera read a 7 on the plate as a 2, that the man lost feeling in his fingers, gave up his lawn-care business and forklift work, sold his truck and was evicted, and that he had sued the officer and the city and settled in October for $35,000.

Contextual tracker case High reported severity Lawsuit Settled

AI involvement supported · Causal attribution supported · 5 sources, 3 underlying accounts · Added 04/10/2026

Dec 2025CanadaGoogle AI Overviews

Google AI Overview reportedly described fiddler Ashley MacIsaac as a convicted sex offender, and a concert was cancelled

In December 2025 Cape Breton fiddler Ashley MacIsaac said a First Nation north of Halifax cancelled his concert planned for 19 December after reading a Google AI-generated search summary that said he had convictions for sexual offences. He says the statements were false and came from online articles about another man in Atlantic Canada with the same last name. The First Nation apologised in writing and Google amended the search results. MacIsaac says he feared for his safety and worries about other lost work. In a statement of claim filed in February 2026 in the Ontario Superior Court of Justice he seeks damages of 1.5 million from Google (US dollars in the Globe and Mail copy of the Canadian Press story, no currency stated in the CBC copy). None of its claims was tested in court. CBC News reported in August 2026 that a notice of discontinuance ending the lawsuit was filed on 29 July 2026; MacIsaac gave no reason, Google did not comment, and no settlement is reported.

Contextual tracker case Medium reported severity Lawsuit Filed

AI involvement reported · Causal attribution alleged · 6 sources, 4 underlying accounts · Added 29/09/2026

Jun 2025Event location unknownChatGPT

Delaware court finds Krafton fired three Unknown Worlds executives without valid cause in a takeover that followed its CEO's ChatGPT strategy

A Delaware Court of Chancery opinion of 16 March 2026 finds that in June 2025 the CEO of Krafton, after being warned that a dismissal with cause would not eliminate a contingent earnout obligation, consulted ChatGPT. The chatbot answered that the earnout would be difficult to cancel, suggested an internal task force (Project X) whose mandate was to negotiate a deal or execute a takeover of the studio, and prepared a "Response Strategy to a No-Deal Scenario" that recommended locking down the studio's Steam and console publishing rights and build-pipeline access. The court found that Krafton followed most of these recommendations over the next month: it locked the studio out of its Steam publishing rights, which severed the studio's practical ability to launch its game and forced the studio's CEO to the negotiating table, posted a message on the studio's websites, and on 1 July 2025 sent termination letters to the studio's two founders and its CEO. The court held that Krafton breached the acquisition agreement by terminating the three executives without valid Cause and by improperly seizing operational control, reinstated the studio's CEO and extended the earnout period by 258 days. The opinion records that the Krafton CEO had begun exploring options including firing the executives before consulting ChatGPT, and does not find that ChatGPT recommended the terminations. Krafton said it disagreed with the ruling. On 1 July 2026 Krafton announced a mutual settlement with the studio and the three executives dismissing all pending proceedings; IGN, citing Bloomberg, reported that the studio's CEO stepped down as part of it.

Contextual tracker case Medium reported severity

AI involvement supported · Causal attribution unclear · 4 sources, 2 underlying accounts · Added 29/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: 18/11/2026. Dataset available under CC BY 4.0.