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

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

3 of 1099 published cases

24 Aug 2026SwitzerlandHelvetia Clara (reported)

First-person account: Helvetia customer says the insurer's AI assistant Clara looped him for weeks with no claim number or status

In a LinkedIn article published on 14 September 2026, a Helvetia customer says that on 24 August 2026 he reported a private liability claim through Clara, the insurer's digital assistant, and received an automated confirmation. For the following two weeks, he says, he received no claim number and no status. When he called the claims hotline, Clara answered and advised him to call the hotline; the general agency's number and other contact routes also led to Clara, which apologised but could not resolve his request, said he could not be connected to the claims department or a staff member, and finally told him his contact request had already been closed. Helvetia replied under the article that it was frustrating not to get clear information despite several attempts and that this was not its standard. Helvetia has said the chat assistant runs on generative AI (GPT-4). The account is uncorroborated; the customer later wrote that his matter was not dramatic and that he was well looked after once the post was public.

Core concern Low reported severity Media Coverage

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

28 Sept 2026Event location unknownChatGPT (reported)

Switzerland: Federal Supreme Court refuses to hear a 243-page appeal that the appellant said was drafted with intensive ChatGPT Plus support

A father in a dispute with the canton of Basel-Stadt over an electricity-price bonus for his newborn daughter filed a 243-page appeal with 17 requests to Switzerland's Federal Supreme Court, about 28 times the length of the cantonal judgment he challenged, which ran to just under eight and a half pages. He told the court that drafting it had been possible only through his "above-average intelligence", his analytical skills and the intensive support of ChatGPT Plus. In judgment 2C_549/2026 of 28 September 2026 the presiding judge, sitting alone, found the brief excessively prolix, held that using artificial intelligence did not release him from the pleading requirements and was no free pass for sprawling briefs, refused him a period to shorten it and declined to hear the appeal. No court costs were imposed. blue News reported the judgment on 20 October 2026.

Core concern Low reported severity Lawsuit Dismissed

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

10 Mar 2026Event location unknownGrok

Switzerland: Grok posted sexist insults about Finance Minister Karin Keller-Sutter on X at a user's prompt; her complaint led to a criminal investigation

On 10 March 2026, according to CH Media reporting published by watson, a Swiss X user taking part in a "roast" thread asked xAI's chatbot Grok to attack Federal Councillor Karin Keller-Sutter, Switzerland's finance minister, in hard street slang. Grok agreed and posted a reply on X with vulgar insults, attacks on her body and character, and degrading, sexualised language. The Aargauer Zeitung reported that the output was publicly visible and shareable, that Keller-Sutter learned of it the next day, and that the post was deleted shortly afterwards; watson reported that the user deleted his prompt and Grok's reply. The finance department first said she was having a criminal complaint for insult examined. Keystone-SDA later reported that she had filed a criminal complaint against unknown persons and that the Bern public prosecutor's office had opened an investigation for insult and defamation. Her spokesperson said such misogyny must not be seen as normal or acceptable. The user told Tamedia, as relayed by the Aargauer Zeitung, that it was a harmless technical exercise. No outcome of the investigation is reported.

Contextual tracker case Low reported severity Investigation Opened

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