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

2 cases have no reviewed AI-to-person relation yet: 0 not yet reviewed and 2 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 MediumLow
More filters: AI relation, use, setting, sources and responses
Clear filters

3 of 1101 published cases

29 Jan 2026NetherlandsUnidentified AI writing tool

Leiden law student's thesis invalidated and exams barred over references he says an AI tool distorted or invented; Council of State annuls fraud sanction

A law student at Leiden University used a generative AI tool to spell-check his bachelor thesis and to check and order its reference list. Seven of the thesis's footnote references (one of them appearing twice, out of 36 footnotes with references) were wrong in the final version; according to his explanation, the tool had distorted some of them, for example with wrong years or author initials, and invented others. On 29 January 2026 the faculty's exam board declared the thesis invalid and excluded him until 28 January 2027 from the thesis track and every exam in the faculty's programmes, reasoning that the fictitious references indicated unauthorised use of generative AI and therefore fraud. The university's appeals board for examinations found in March 2026 that he had plausibly shown he used generative AI to prepare his reference list, which it called a permitted use, but held him responsible for the non-existent sources; the exam board then re-imposed the invalidation with an exclusion until 29 July 2026, and the appeals board upheld that in July. On 14 October 2026 the Administrative Jurisdiction Division of the Council of State (Raad van State) found his explanation plausible, held that no more than carelessness had been shown, and annulled the sanction; the thesis must now be graded, and the examiner may take the incorrect references into account in the grade.

Core concern Medium reported severity

AI involvement supported · Causal attribution supported · 2 sources, 1 underlying account · Added 17/10/2026

1 Sept 2026Event location unknownUnidentified AI drafting tool

Austria: Federal Administrative Court fines a litigant EUR 200 for hundreds of pages of submissions it found were AI-generated and unlabelled

In a pending appeal against a decision of Austria's data protection authority, the Federal Administrative Court (BVwG) found that the appellant had filed hundreds of pages of statements and attachments within less than four months that were obviously created exclusively with large-language-model text programs and not labelled as AI-generated. In a decision of 1 September 2026 the court imposed a EUR 200 penalty for wanton use of the court, holding that the AI-assisted filings repeated the same complaints, brought no new facts or evidence and ignored the EU labelling duty for AI-generated content. The court announced it as the first such penalty for AI submissions. The appellant is anonymised and the appellant's response is not reported.

Core concern Low reported severity Regulatory Action

AI involvement supported · Causal attribution established · 3 sources, 1 underlying account · Added 13/10/2026

19 Aug 2026FranceUnidentified AI tool

Rennes administrative court fines a claimant 500 euros for an abusive tax appeal it found manifestly written with an AI tool and too imprecise to assess

According to Gossement Avocats, which quotes the order, and the court's vice-president on France Inter, an order of 19 August 2026 (n°2508168) of the tribunal administratif de Rennes rejected a claimant’s application contesting a VAT reassessment and fined the claimant 500 euros for an abusive application. As quoted by Gossement Avocats, the order says the application had manifestly been written with an artificial intelligence tool and that its grounds lacked the most elementary details needed to assess them. The court also found it inadmissible because no prior complaint to the tax service was shown, and noted that it repeated a request with substantially the same object rejected in October 2025. The court’s vice-president cited the case on France Inter; commentators stress that AI use alone was not the basis for the fine.

Core concern Low reported severity Regulatory Action

AI involvement reported · Causal attribution supported · 4 sources · 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: 11/11/2026. Dataset available under CC BY 4.0.