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 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

In this selection

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

7 cases have no reviewed AI-to-person relation yet: 3 not yet reviewed and 4 reviewed as unknown. Show these 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 404 published cases

Event date unknownEvent location unknownFacebook video face-scan check

First-person forum account: a Facebook user says a video face-scan security check failed to recognise them after their appearance changed, an automated ID check then rejected their government ID over a nickname, and they were locked out of a five-year-old account

In a public post to r/facebook on 28 September 2026, a user writes that their five-year-old Facebook account was hit with a security check that asked for a video face scan, which 'failed completely'. They say their face had changed a lot through recent life circumstances and 'The AI simply didn't recognize me.' Facebook then asked for ID, and 'the automated system instantly rejected' their government ID because their profile uses a shortened nickname. The poster says they are locked out of years of memories, friends and active Marketplace listings and are looking for a way to reach a human or download their data. Meta has said that video selfies used to regain access to compromised accounts are compared with the account's profile pictures using facial recognition; whether this check worked that way is not known. The account is uncorroborated.

Contextual tracker case Low reported severity

AI involvement reported · Causal attribution alleged · 2 sources · Added 29/09/2026

Event date unknownEvent location unknownGemini note-taking in Google Meet

First-person forum account: an agency employee in England says Gemini note-taking in Google Meet kept transcribing two prospective clients after the agency's boss left the call, and that the boss passed their private post-meeting discussion to staff to shape a follow-up pitch

In a public post to r/LegalAdviceUK on 28 September 2026, an employee of a marketing agency in England writes that their boss pitched a prospective client and the client's business partner on a Google Meet call with Gemini note-taking switched on. After the boss said goodbye and left, the two business partners stayed on the call to discuss the proposal and the other agencies they were considering, and Gemini kept taking notes. The boss then sent the employee the notes and transcript, which named a competing agency and included 'personal details of who they spoke to specifically on the call', and asked for a follow-up deck built on what the partners liked and disliked. The poster believes the partners did not know they were still being transcribed. Google's help page says Meet tells all participants when notes are being taken; whether the partners noticed is not known. The account is uncorroborated.

Contextual tracker case Low reported severity

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

Event date unknownUnited StatesFlock Safety license plate readers

San Jose: police officer fired after passing Flock license-plate-reader location data to a relative accused of domestic violence, who used it to find his accuser

San Jose's police chief announced on 11 September 2026 that an officer had been fired after accessing the department's Flock Safety automated license-plate-reader data on his personal phone and giving a vehicle's location to his cousin, a suspect in a domestic-violence case, who used it to locate the woman accusing him. The chief called it 'a betrayal of the public trust', said the officer was placed on leave, criminally investigated and referred to the district attorney, and that the case was submitted to California's peace-officer standards commission for decertification; neither the officer nor the cousin has been charged. The department has since barred access to the system from personal devices and is testing auditing tools. Neither the victim nor the officer is named in the inspected reports.

Contextual tracker case Medium reported severity Internal Action

AI involvement supported · Causal attribution supported · 2 sources · Added 16/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: 30/09/2026. Dataset available under CC BY 4.0.