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
1
Countries with reported events
1
Located 1 of 1 cases · 0 unknown
Languages in checked sources
1
Recorded for 1 of 1 cases
1Core concern
AI communicated, acted for, depicted or impersonated 0Contextual 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.

1cases 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 2026
Reported severity Low
More filters: AI relation, use, setting, sources and responses
Clear filters

1 of 726 published cases

Export JSONExport CSV
2026ChinaDoubao (reported)

China: user says Doubao misstated an air-ticket refund fee, costing him 600 yuan, then promised compensation it could not pay; he says he filed suit

According to his own social-media posts and video, as reported by Dahe Daily (15 May 2026) and National Business Daily (20 May 2026), a user in China who had booked flights from Shijiazhuang to Chongqing for 2 May 2026 decided to drive instead and asked the Doubao chatbot about the refund fee. Doubao told him he could safely refund and that the fee would be small (only 5% in National Business Daily's account, under 100 yuan in Dahe Daily's). He refunded without checking the airline's rules and was charged about 40%, 600 yuan. When he returned to the chatbot, Doubao said it would handle the claim, promised to pay him 600 yuan itself if the money was not recovered by 6 May and produced a 'compensation commitment letter'. On 6 May it said it would pay by midnight and asked for his WeChat payment code; on 7 May it said that as an AI it could not make transfers and admitted its error. He then used Doubao to draft a complaint, was told by it that he did not need a lawyer, and on 12 May submitted a suit against the app's operator, Beijing Chuntian Zhiyun Technology, according to a screenshot he posted (Dahe Daily names the Beijing Internet Court). His posts had been deleted by 19 May. Doubao's customer service told Dahe Daily the matter had been recorded; Doubao and ByteDance did not answer National Business Daily. Whether the court accepted the case, and its outcome, are not reported.

Core concern Low reported severity Lawsuit Filed

AI involvement reported · Causal attribution alleged · 2 sources, 1 underlying account · Added 17/10/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: 17/10/2026. Dataset available under CC BY 4.0.