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
2
Countries with reported events
2
Located 2 of 2 cases · 0 unknown
Languages in checked sources
2
Recorded for 2 of 2 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 Low
More filters: AI relation, use, setting, sources and responses
Clear filters

2 of 1099 published cases

5 Sept 2026United StatesGoogle AI Overviews (reported)

Kodiak, Alaska: a hunter reported to have relied on a Google AI answer that snipe season opened on 1 September hunted three snipe before the 8 October opening, reported the violation to wildlife troopers and was fined $150

Alaska Beacon reported on 28 September 2026 that a Kodiak woman hunted snipe illegally on 5 September after a Google search for snipe season told her the season began on 1 September, according to a wildlife trooper's affidavit attached to a citation filed at the Kodiak district court. The outlet describes the answer as a Google AI overview. She hunted three snipe, grew suspicious on learning that duck season did not open until 8 October, checked the regulations and called troopers to report herself. The outlet reports the trooper said he ran an identical Google search and received identical incorrect information. She pleaded no contest and was fined $150, and told the outlet she felt shame and embarrassment. A Department of Public Safety spokesman said it was the first time he thought the agency had seen AI cited, and that she had acted correctly once she learned of the mistake. Google did not respond to the outlet's request for comment.

Core concern Low reported severity

AI involvement reported · Causal attribution alleged · 2 sources, 1 underlying account · Added 05/10/2026

17 Apr 2026 to 19 Apr 2026ChinaDoubao

Jiashan, Zhejiang: a man chose his mother's burial date on Doubao's recommendation, the chatbot then contradicted itself, and after a relative's road accident his family blamed the date; he sued the app's operator for an apology and damages

A man living in Jiashan county, Zhejiang, whose mother died suddenly on 17 April 2026, asked the ByteDance chatbot Doubao which day was auspicious for her burial after disagreeing with a feng-shui master's choice of 20 April; Doubao recommended 19 April and he persuaded his family to follow it. When he asked again what time to bury her, Doubao said 19 April was not an auspicious day and repeated that answer when pressed; relatives had already been notified, so the funeral went ahead on the 19th. Not long afterwards a relative was seriously injured in a traffic accident and family members blamed the burial date, saying it had broken the feng shui; he says family relations became tense and relatives blamed him. His complaint to the operator went unanswered, and, with a complaint drafted with Doubao's help, he sued Beijing Chuntian Zhiyun Technology for an apology and damages. Jiashan County People's Court heard the case on 3 September 2026 as a network-tort dispute; the company denied any tort or fault, the plaintiff's side attacked the user agreement as a standard-form contract, and no judgment had been reported by 21 September. The story was reported by Jiaxing's municipal broadcaster on 15 September and relayed nationally; the relative's injury is the family's attribution, not an established consequence.

Core concern Low reported severity Lawsuit Ongoing

AI involvement reported · Causal attribution alleged · 6 sources, 2 underlying accounts · Added 21/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.