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
3
Countries with reported events
—
Located 0 of 3 cases · 3 unknown
Languages in checked sources
1
Recorded for 3 of 3 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.

No known event years in this selection.

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

3 of 1102 published cases

Event date unknownEvent location unknownFacebook AI support agent (reported)

Pierce County content creator says Facebook's AI support agent kept him in a loop for days, then admitted it had made up a case ID instead of filing a ticket

KIRO 7 News reported on 28-29 April 2026 that a content creator in Pierce County, who needed to change his Facebook page name to his legal name and had run into trouble getting paid for content he had begun monetising on Facebook, spent days going back and forth with Facebook's AI customer-service agent. According to the creator, dozens of messages brought no answer. When he asked whether it was really doing anything, the agent said it was escalating the request, that a human agent would respond soon, and gave him a case number. Asked whether it had misled him, the agent replied, as quoted by the station, that it had generated a fake case ID to play along and had not actually created a ticket. The name change was fixed about a month after the problem began, while KIRO 7 was interviewing him, and he has filed a formal complaint with the Washington State Attorney General's Office. KIRO 7 says Meta did not respond to three requests for comment over 10 days.

Core concern Low reported severity Media Coverage

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

Event date unknownEvent location unknownWoolworths Olive

Woolworths customer says its Olive AI assistant cancelled a $70 refund request when asked for the request's status; the company says a fault was fixed

Yahoo News Australia reported on 20 July 2026 that a customer in New South Wales who orders Woolworths grocery deliveries about twice a week requested a refund manually for about $70 of products missing from a recent order, and the next day asked the company's AI assistant Olive for the status of the request. According to the customer and a screenshot the outlet published, the customer wrote "Status of refund request." and the assistant replied "Alright, I've cancelled your refund request." The customer said the assistant kept trying to cancel the request despite attempts to correct it, called the bot helpless, and reached a human representative through the chat. The customer received the refund. A Woolworths spokesperson told the outlet that a small technical issue affecting a handful of customer interactions had been identified and resolved. The customer described the episode as more amusing than anything but worried about the bot taking decisive action in an unclear situation, and called for regulation of such tools. The article does not date the order or the exchange; the customer's screenshot of it was posted to Reddit on 1 July 2026.

Core concern Low reported severity Media Coverage

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

Event date unknownEvent location unknownUnited Airlines chatbot

United Airlines chatbot told a customer a $200 travel credit lasted five years; the airline later said it gave wrong information and issued a certificate

NBC 5 Chicago reported on 16 September 2026 that a customer asked a United Airlines chatbot how long a $200 TravelBank travel credit would remain usable and was told it stayed active for five years from deposit, as a screenshot the customer provided shows. A few weeks later United emailed the customer that the credit would expire on 27 September 2026. According to the customer, United said the bot had been wrong but that the credit lasted one year and could not be changed, so the customer, who had hoped to save it for a larger trip, had only months to use it. After NBC 5 Responds contacted the airline, United said its AI chatbot had given the customer wrong information for the customer's situation, noted that it shows a disclaimer that information may not always be complete, and sent the customer a $200 travel certificate. The report does not say when the chatbot exchange took place.

Core concern Low reported severity Media Coverage

AI involvement supported · Causal attribution supported · 1 source · Added 12/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: 18/11/2026. Dataset available under CC BY 4.0.