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
1
Located 1 of 3 cases · 2 unknown
Languages in checked sources
2
Recorded for 3 of 3 cases

4 cases have no reviewed AI-to-person relation yet: 0 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.

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

3 of 628 published cases

Aug 2026Event location unknownUnidentified OpenAI generative AI service (reported)

Health-guidance contractor says an employee entered insured members' names and disease information into an unauthorised external generative AI service

A local-government employees' mutual aid association said in a notice dated 4 September 2026 that RIZAP, the company it contracts for specific health guidance, had reported that on 20 August 2026 it emerged that a RIZAP staff member, during data-extraction work, had entered data containing personal information into an external generative AI service that RIZAP did not permit. The association says 726 of its members across 14 branches are covered and lists the data as membership numbers, email addresses, names, dates of birth, sex, some addresses and phone numbers, the type of health guidance and, for members with them, high blood pressure, diabetes or dyslipidaemia. The IHI group health insurance society reported 210 of its members in a 2 September notice that, according to a security news site, names OpenAI as the provider, says the matter came to light through the employee's own report, and says OpenAI answered on 1 September that the data had not been used for model training. RIZAP's own release, as described in an ITmedia column, says the information was uploaded by mistake to a generative AI service the employee used privately, and that the company confirmed no possibility of viewing by third parties other than the service operator or of use in training. Whether the provider's staff could view the data was still being checked when the insurers published.

Contextual tracker case Medium reported severity

AI involvement reported · Causal attribution supported · 3 sources · Added 12/10/2026

29 Apr 2026Event location unknownChatGPT

Texas health plan says an employee uploaded a file of members' personal and prescription data to ChatGPT from a home network, against its policy

Community First Health Plans, a nonprofit health plan in San Antonio, Texas, said in a 29 June 2026 release that on the evening of 29 April 2026 one of its employees uploaded a file containing personal information of some members to ChatGPT from a home computer network, circumventing the plan's firewall safeguards and violating its policy. The plan says it does not use ChatGPT and that its systems detected the violation and alerted its IT department. According to the release, the file may have included members' names, addresses, dates of birth, member identification numbers and prescription drug information. The next morning the plan revoked the employee's access, directed and verified deletion of the data from the employee's ChatGPT account, asked OpenAI to delete any related data, and ended its relationship with the employee. It notified affected members and federal and state agencies, offered 12 months of identity monitoring and says it is not aware of any misuse. The release gives no number of affected members.

Contextual tracker case Medium reported severity

AI involvement reported · Causal attribution supported · 1 source · Added 12/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

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: 12/10/2026. Dataset available under CC BY 4.0.