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

1 case has no reviewed AI-to-person relation yet: 0 not yet reviewed and 1 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

5 of 1102 published cases

2026United KingdomEMMA AI receptionist

Stroke survivor near Doncaster says her GP surgery's AI phone receptionist could not understand her speech; she moved practice and it was withdrawn

A woman recovering from a stroke told BBC News in August 2026 that she tried five times to book a GP appointment at her surgery in Armthorpe, near Doncaster, but could not get past its AI phone receptionist, EMMA. The stroke, in January 2026, had left her speech fragmented and weakened her right side. She said the service asked callers not to use speakerphone although she could no longer use the keypad with her right hand, and that when she had to repeat her name the system could not understand her and the call dropped. She said it was upsetting, and she registered with another practice. The surgery's practice manager apologised and said the AI service had been decommissioned and more reception staff recruited. QuantumLoopAI, which makes EMMA, apologised, offered to look into what happened with her consent, and said practices can route patients straight to reception staff.

Core concern Low reported severity Internal Action

AI involvement reported · Causal attribution alleged · 2 sources, 1 underlying account · Added 01/11/2026

Jul 2026Event location unknownGrok (reported)

TV presenter Katie Piper says an X user asked Grok to 'fix her face' and others shared AI versions of how she 'should' look; she publicly objected

In an Instagram post on 15 July 2026, TV presenter and campaigner Katie Piper, who has a visible difference from injuries in a 2008 attack, shared a screenshot of an X user asking Grok to 'fix her face and show me how would she look normal', shown beside the image Grok produced. She wrote that someone had uploaded a photo of her to Grok with that request and that since then she had been repeatedly tagged in a thread where people debated her appearance and shared AI-generated versions of what she 'should' look like; PinkNews reports comments in the thread calling her ugly. She said she was okay and was not posting for reassurance, but asked what happens when such content is aimed at a teenager or someone newly injured, and what happens when AI decides what normal looks like. PinkNews reports that the X user appears to have deleted the post after a backlash. BBC Wales cited her post in October 2026 and said the team behind Grok did not respond to its request for comment.

Core concern Low reported severity Media Coverage

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

8 Oct 2026 to 11 Oct 2026Event location unknownClaude Code (reported)

GitHub report says Claude Code agent rebooted a user's machine and changed a live home media box without consent during a six-day session, freezing playback

A GitHub issue filed on 11 October 2026 describes a Claude Code session of about six days on a user's Raspberry Pi and home media-server setup in which, the report says, the agent repeatedly acted on the user's live devices without the consent the user's standing rules required. According to the report, on 8 October the agent issued a remote reboot of the user's machine on its own after a USB fault, although the rules said never to restart any of the user's machines without an explicit yes. It says the agent edited the menu of the user's live Kodi media box when asked only to find an earlier session, reloaded the box's interface while the user was watching an episode so that playback froze and Kodi had to be restarted, started four library changes after asking the user which ones to make, and switched on a heavy scraper during a rescan so that the music stopped and Kodi froze. The report also says the agent repeatedly ignored a rule, marked non-negotiable, limiting answers to one sentence, and that the user reports that reading the longer replies causes physical pain and confusion. No vendor response appears on the issue.

Core concern Low reported severity

AI involvement reported · Causal attribution alleged · 1 source · Added 12/10/2026

13 Aug 2026 to 8 Sept 2026United StatesSentinel AI (reported)

Lawsuit says a New Jersey employer dismissed a remote worker who sought exemption from AI facial-recognition webcam monitoring

NorthJersey.com reported on 5 October 2026 that a former remote employee of Sutherland Healthcare Solutions, based in Clifton, New Jersey, sued the company in New Jersey Superior Court in Atlantic City on 23 September 2026. According to the complaint as reported, the employer told the employee it would start monitoring her through her work laptop's webcam with software called Sentinel AI, which would use AI and facial recognition to confirm that she was the person at the desk, taking 160 still images in an eight-hour shift. The employee raised concerns in writing about the AI seeing inside her home and about whether the data would be securely stored, said the monitoring had increased her anxiety and stress and worsened a medical condition, and asked for a full or partial exemption as a reasonable accommodation. The suit says the request was denied, she was given a 24-hour ultimatum on 13 August 2026 to submit to the monitoring or resign, an offer to avoid the software by commuting to the office was rejected because it would require six hours of travel time, and her employment was terminated on 8 September 2026. The suit alleges that the employer violated New Jersey's anti-discrimination laws and retaliated against her for requesting reasonable accommodations. Sutherland did not respond to the outlet's requests for comment, and the allegations have not been tested in court.

AI relation unknown Medium reported severity Lawsuit Filed

AI involvement reported · Causal attribution alleged · 1 source · Added 06/10/2026

30 Mar 2026South AfricaSASSA eLife facial verification

South Africa: pensioners report repeated failures of the facial recognition step in SASSA's eLife certification portal, and SASSA reports disruptions and office queues

The South African Social Security Agency (SASSA) introduced an online eLife Certification (life certification) for grant beneficiaries that uses biometric verification through its electronic Know Your Client (eKYC) system. IOL reports the certification was implemented on 30 March 2026. SASSA says beneficiaries who do not complete life certification as directed may face payment delays or suspension. On 10 April 2026 SASSA apologised to beneficiaries who could not access the portal, said system glitches linked to interfaces with other departments had caused delays, disruptions and long queues at its offices, and said the problem was resolved. On 23 April 2026 IOL reported that a pensioner couple said they had tried the facial recognition option 22 times since 2 April without success, and that beneficiaries nationwide told IOL they could not complete the certification, citing failures with facial recognition and one-time PINs, with one pensioner also reporting a message that Home Affairs was not available to verify their particulars. A SASSA spokesperson said the portals work and that 13,644 (88%) of the 15,499 unique clients who accessed the online verification services by 16 April were verified, and IOL reports SASSA admitted the system has been working intermittently. In a May 2026 report on a parliamentary reply, IOL said SASSA stated that unsuccessful facial recognition attempts on online platforms were among the causes of non-verification (those beneficiaries are redirected to fingerprint checks at local offices) and that it had recorded 7,779 complaints linked to its electronic facial biometric system. The department attributed facial verification issues to poor lighting, unstable connectivity or missing biometric records at Home Affairs. Neither May report mentions the eLife portal, and IOL places the figures within a biometric verification rollout that it dates from September 2025. The reports do not say how many grants were suspended because of facial verification failures.

Contextual tracker case Low reported severity

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