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 is wider: it also records consequential decisions and claims about people. 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
2
Located 3 of 3 cases · 0 unknown
Languages in checked sources
1
Recorded for 3 of 3 cases
3Core 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.

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.

3 2026
Reported severity Medium
More filters: AI relation, use, setting, sources and responses
Clear filters

3 of 452 published cases

Export JSONExport CSV
9 Jan 2026United StatesUnidentified facial recognition system

Brooklyn Center, Minnesota: immigration agents in Border Patrol vests handcuffed a U.S. citizen who was working at a house in January 2026 and an agent told him after a facial recognition scan that he was born in Mexico City; a federal judge found he was detained solely because of his race or ethnicity, and a second scan confirmed his citizenship before release

In findings of fact filed on 9 March 2026 in Hussen v. Noem, a proposed class action over immigration stops during Operation Metro Surge, Judge Eric C. Tostrud of the U.S. District Court in Minnesota found that a U.S. citizen working at a house in Brooklyn Center on 9 January 2026 was stopped and detained based solely on his race or ethnicity. Two agents with 'border patrol' on their vests asked where he was born, said his REAL ID papers were fake and his driver's licence proved nothing, and handcuffed him. According to the findings, one agent conducted a facial recognition scan and told him he was born in Mexico City; in his sworn declaration the man says the agent also told him he was not a U.S. citizen and was under arrest. After about thirty minutes of driving, a different agent used a facial recognition scan that determined he was a citizen, and he was released. The government's declarations did not dispute his account. The judge denied a preliminary injunction for lack of a certainly impending future injury, and the plaintiffs later dismissed the suit. No source read names the facial recognition application. A complaint filed on 1 October 2026 over the killing of Renee Good restates the episode.

Contextual tracker case Medium reported severity Lawsuit Dismissed

AI involvement reported · Causal attribution unclear · 4 sources, 2 underlying accounts · Added 02/10/2026

20 May 2026United StatesMeta internal AI systems (reported)

US: 26 Meta employees sue alleging an AI-assisted May 2026 layoff selection penalized workers on protected leave, Meta says people made the decisions

On 20 May 2026 Meta began notifying about 8,000 employees (roughly 10 percent of its workforce) that they had been selected for layoff. On 13 July 2026 twenty-six anonymous employees who had taken or requested medical, pregnancy, parental or family leave, or a disability accommodation, sued Meta in the US District Court for the Northern District of California. The complaint alleges, on information and belief, that Meta used internal AI-assisted systems (including the Metamate assistant, keystroke and activity monitoring, AI-token-usage dashboards and algorithmic performance ranking) to score, rank and select employees, and that these inputs could not accumulate during protected leave, so plaintiffs on leave were disproportionately selected. Meta says workforce decisions were made by people, not AI, and that no selection decision was made by AI. On 17 July 2026 the court denied a temporary restraining order, recording that the parties dispute whether Meta used AI in the terminations and finding serious questions on the merits but no shown likelihood of success. One plaintiff was voluntarily dismissed on 3 August 2026. The preliminary injunction motion was argued on 24 August 2026 and taken under submission. The plaintiffs are pursuing their merits claims in arbitration and the allegations are unproven.

Contextual tracker case Medium reported severity

AI involvement disputed · Causal attribution disputed · 10 sources, 5 underlying accounts · Added 29/09/2026

1 Mar 2026IndiaAI roommate kitchen monitor (reported)

India: Bengaluru-based employer says he fired his cook after a home AI kitchen monitor flagged fruit taken

On 1 March 2026 a Bengaluru-based technology professional posted on X that he had deployed a home "AI roommate" (a kitchen camera with an AI vision model, which he said was Claude Haiku 4.5) that monitored his cook while she cooked, alerted him when she took anything and sent weekly reports. The post said the system "caught her red handed", that he "caught her twice this week" and that he had "just fired" her. Screenshots quoted by Hindustan Times show the bot listing apples and a banana as gone, reporting the cook eating blueberries, and giving hand-washing and cleaning observations. All coverage derives from the employer's post: the post carries no video, the cook's account is not reported and the alleged taking is unverified.

Contextual tracker case Medium reported severity

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