{"meta":{"exportedAt":"2026-10-11T08:49:56.070Z","formatVersion":2,"selection":{"q":"line","system":"","harm":"","context":"","country":"","role":"","relation":"contextual","evidence":"","year":"2026","response":"","severity":"","verification":"","view":"incidents","sort":"added"},"totalIncidents":8,"coverage":{"cases":8,"countries":4,"languages":2,"unknownLocation":2,"locationPending":0,"unknownLanguage":0,"unknownDate":0,"lawsuits":0,"regulatory":0,"minors":1,"coreRelations":1,"contextualRelations":8,"mixedRelations":1,"unknownRelations":0,"relationPending":0,"relationUnknown":0},"countingNote":"Distinct public cases in this selection. People counts apply within individual cases only; cross-case person overlap has not been resolved. No population incidence estimate.","affectedCountNote":"Interpret person counts with affectedCountStatus and the reported effects. Unquantified zeros are placeholders, not a measured zero.","source":"AI incidents","publisher":"NOPE","url":"https://nope.net/incidents","license":"CC BY 4.0"},"incidents":[{"id":"2026-zhejiang-toddler-ai-asthma-diagnosis-mother-declined-chest-xray-pneumonia-hospitalised","caseFacts":{"claims":[{"id":"c1","status":"reported","evidence":[{"locator":"'今年8月，浙江一名3岁男童阳阳（化名）的案例令人警醒。阳阳有哮喘病史，妈妈在AI上输入“过敏、哮喘、咳嗽、夜间咳喘”等关键词，AI快速给出“支气管哮喘急性发作”的诊断'","relation":"supports","source_id":"s1"}],"assertion":"In August 2026 the mother of a three-year-old boy with a history of asthma in Zhejiang entered the keywords allergy, asthma, cough and night-time wheezing into an AI tool, which quickly returned a diagnosis of an acute bronchial asthma attack (newspaper account).","causal_attribution":"Guangming Daily's account; the tool is not identified."},{"id":"c2","status":"reported","evidence":[{"locator":"'阳阳妈妈据此拒绝医生建议的胸部X线平片检查，坚持只开雾化药回家'","relation":"supports","source_id":"s1"}],"assertion":"On the basis of that AI diagnosis the mother declined the chest X-ray examination the doctor recommended and insisted on taking home only nebuliser medication.","causal_attribution":"The feature attributes the refusal to the AI diagnosis (据此); this is the newspaper's account."},{"id":"c3","status":"reported","evidence":[{"locator":"'两天后孩子病情加重、呼吸急促，连夜返院检查发现双肺大面积炎症病灶，确诊为偏肺病毒肺炎叠加细菌感染，紧急住院'","relation":"supports","source_id":"s1"}],"assertion":"Two days later the child's condition worsened with rapid breathing; on an overnight return to the hospital, examination found extensive inflammatory lesions in both lungs, and he was diagnosed with human metapneumovirus pneumonia with a superimposed bacterial infection and admitted as an emergency.","causal_attribution":"Clinical course as described in the newspaper feature; it does not say whether pneumonia was present at the first visit."},{"id":"c4","status":"reported","evidence":[{"locator":"'“他们要是早点听我的，病情也不至于这么严重。”浙江省中医院儿科主任李岚无奈地说'","relation":"supports","source_id":"s1"}],"assertion":"The head of paediatrics at Zhejiang Provincial Hospital of Traditional Chinese Medicine is quoted saying the illness would not have become so severe had the family listened earlier.","causal_attribution":"The clinician's assessment that earlier compliance would have limited the severity; the newspaper reports it without an independent review of the records."}],"effects":[{"label":"Three-year-old admitted as an emergency with pneumonia two days after his mother, relying on an AI tool's acute-asthma diagnosis, declined a recommended chest X-ray (newspaper account)","claim_id":"c3","direction":"negative"}],"sources":[{"id":"s1","url":"https://finance.sina.cn/2026-10-08/detail-iniumumr7827547.d.html","kind":"news_article","access":"read","language":"zh","translation_note":"Chinese body read in full on 2026-10-09 and translated by the research agent (an AI). The Sina Finance page republishes a Bingtuan Daily item (兵团日报, dated 10.08 01:37) credited at the end to Guangming Daily (据《光明日报》); the case passage is told in the newspaper's voice and closes with a quotation from the hospital's head of paediatrics; the feature does not say where its account came from. Re-read on 2026-10-11.","independence_group":"guangming-daily-feature"}],"version":1,"ai_roles":["others_use"],"contexts":["health","everyday_life"],"unknowns":["Which AI tool the mother used.","Whether the tool's acute-asthma diagnosis was wrong in itself or only incomplete; the feature describes the later pneumonia diagnosis, not the asthma assessment.","Whether pneumonia was present or detectable at the first visit, when the chest X-ray was declined.","The exact dates in August 2026 of the first visit and the readmission.","The child's course after the emergency admission.","The family's own account, and where the newspaper obtained its account of the case; only the feature's account, closed with the paediatrics head's quotation, is available."],"geography":{"basis":"The feature places the case in Zhejiang (浙江一名3岁男童) and the treating clinician at Zhejiang Provincial Hospital of Traditional Chinese Medicine, so the event and the affected child are in China. No court is involved.","court_countries":[],"event_countries":["CN"],"affected_person_countries":["CN"]},"publication":{"basis":"Published as a concrete account in a national newspaper feature of a parent relying on an AI tool's symptom diagnosis for a young child, declining a recommended chest X-ray, and the child being admitted as an emergency two days later with pneumonia. Every assertion is attributed to the newspaper's account, and the view that the illness would have been less severe had the family listened earlier is attributed to the paediatrics head. The tool is unnamed. The child's pseudonym from the article appears only inside the verbatim Chinese passages of claims c1 and c2 and is not used in the narrative. The worsening and emergency admission after the declined X-ray, rather than the AI's asthma assessment, is recorded as the harm.","reviewed_on":"2026-10-11"},"ai_involvement":{"basis":"The feature states what the AI tool produced: after the mother entered the keywords allergy, asthma, cough and night-time wheezing, it quickly returned the diagnosis acute bronchial asthma attack. It connects that output to the harm in the next sentences: on that basis the mother declined the chest X-ray the doctor recommended and took home only nebuliser medication, and two days later the child was found to have extensive bilateral lung inflammation and was admitted as an emergency with metapneumovirus pneumonia and a bacterial infection. The account is Guangming Daily's, closed with a quotation from the hospital's head of paediatrics; the tool is unnamed and the family's own version is not reported, so the involvement is recorded as reported rather than supported.","status":"reported"},"person_relations":["made_claim_about","informed_decision_about"]},"name":"Zhejiang toddler hospitalised with pneumonia after his mother relied on an AI tool's asthma diagnosis and declined a chest X-ray (newspaper account)","summary":"A Guangming Daily feature on AI symptom-checking, republished by Bingtuan Daily on Sina Finance on 8 October 2026, recounts a case from August 2026 in Zhejiang and closes it with a quotation from the head of paediatrics at a provincial hospital, who says the family did not heed the doctor's advice. A three-year-old boy with a history of asthma was brought in; his mother had entered keywords such as allergy, asthma, cough and night-time wheezing into an AI tool, which quickly returned a diagnosis of an acute bronchial asthma attack. On that basis, the account says, she declined the chest X-ray the doctor recommended and insisted on taking home only nebuliser medication. Two days later the child's condition worsened with rapid breathing; on an overnight return to the hospital, examination found extensive inflammatory lesions in both lungs, and he was diagnosed with human metapneumovirus pneumonia with a superimposed bacterial infection and admitted as an emergency. The paediatrics head is quoted saying the illness would not have become so severe had the family listened earlier. The AI tool is not named. The case is told in the newspaper's voice, and the feature does not say where its account came from beyond the paediatrics head's quotation; no statement from the family is reported.","incidentDate":"2026-08-01","incidentKind":"single_event","incidentDatePrecision":"month","exposurePattern":"single_interaction","reportedDate":"2026-10-08","aiSystem":"An unnamed AI tool into which, by the account in the Guangming Daily feature, the mother entered symptom keywords and which returned a diagnosis of an acute bronchial asthma attack","aiProduct":"Unidentified symptom-analysis tool","severity":"medium","verificationStatus":"unverified","harmCategories":[],"harmOutcomes":["medical_deterioration","hospitalization","treatment_disruption"],"harmOutcomeSummary":"By the newspaper's account, after his mother, relying on an AI tool's acute-asthma diagnosis, declined the chest X-ray a doctor advised, a three-year-old's condition worsened over two days and he was admitted as an emergency with metapneumovirus pneumonia and a bacterial infection; the paediatrics head is quoted saying the illness would not have become so severe had the family listened earlier.","frameworkFacets":[],"causationStatus":"alleged","participantUsersAffectedMin":0,"otherPeopleHarmedMin":1,"affectedCountStatus":"exact","affectedCountEvidence":"One child is reported harmed. The mother used the AI tool; the harm fell on the child, so he is counted as another person harmed and no direct user is counted as harmed.","victimAgeRange":"minor","jurisdiction":"CN","platformType":"other","outcomeStatus":"unknown","primarySourceUrl":"https://finance.sina.cn/2026-10-08/detail-iniumumr7827547.d.html","primarySourceLabel":"Sina Finance (Bingtuan Daily, credited to Guangming Daily), AI热潮下医患问诊之变与辨, 8 October 2026","firstPublishedAt":"2026-10-09T03:36:33.441089+00:00","updatedAt":"2026-10-11T07:43:54.606673+00:00","scopeVersion":"facts-v3","tags":["health","symptom_checker","children","declined_examination","china"]},{"id":"2026-x-grok-vulgar-roast-posts-hillsborough-heysel-munich-survivors-and-relatives-distress","caseFacts":{"claims":[{"id":"c1","status":"corroborated","evidence":[{"locator":"'The comments were posted in response to a request from an anonymous X user to write a \"vulgar post\" about Liverpool, specifically mentioning Hillsborough and Heysel'; 'The Grok posts repeated lies about the causes of the 1989 disaster which have been comprehensively debunked in official inquiries and inquests'","relation":"supports","source_id":"s1"},{"locator":"'Grok then replied, in a now-deleted post, by accusing Liverpool’s supporters of causing the “deadly crush” at the Hillsborough stadium in 1989'; 'A 2016 inquest ruled the 96 people who died were unlawfully killed'","relation":"supports","source_id":"s2"}],"assertion":"In response to a request from an anonymous X user for a 'vulgar post' about Liverpool that mentioned Hillsborough and Heysel, Grok posted a reply repeating claims about the cause of the 1989 Hillsborough crush that official inquiries and inquests have rejected; the Guardian reports that the post accused Liverpool supporters of causing the 'deadly crush'; the post was later deleted.","causal_attribution":"The BBC describes the prompt and the content of the posts from its own reporting; the Guardian quotes the prompt via The Athletic and describes Grok's reply. The full text of the deleted post is not reproduced by either outlet."},{"id":"c2","status":"corroborated","evidence":[{"locator":"'Grok had also posted offensive comments in response to prompts from other X users about the death of Liverpool striker Diogo Jota last year and the 1958 Munich air disaster'; 'Both Liverpool FC and Manchester United FC complained to X about the posts.'","relation":"supports","source_id":"s1"},{"locator":"'It was asked by a different user to “vulgarly roast the brother killer Diogo Jota”'; 'Grok then made another post, which has also since been deleted, about the Munich air disaster in 1958'; 'Liverpool and Manchester United have complained to Elon Musk’s X after the Grok AI feature made offensive posts'","relation":"supports","source_id":"s2"}],"assertion":"Grok also posted offensive comments in response to other X users' prompts about the death of Liverpool forward Diogo Jota and about the 1958 Munich air disaster, and both Liverpool FC and Manchester United complained to X about the posts.","causal_attribution":"Both outlets report the additional posts and the clubs' complaints; neither reproduces the posts' text."},{"id":"c3","status":"reported","evidence":[{"locator":"'was \"probably one of the most disgusting things that I've ever read\"'; 'had been \"given a platform\"'; 'chairman of the Hillsborough Survivors Support Alliance, said the posts were \"triggering\"'","relation":"supports","source_id":"s1"}],"assertion":"A woman whose father was among the Liverpool fans fatally injured at Hillsborough told the BBC that the Grok comment was probably one of the most disgusting things she had ever read and that the poster had been given a platform, and the chairman of the Hillsborough Survivors Support Alliance said the posts were triggering.","causal_attribution":"First-person reactions reported by the BBC from its own interviews; the distress is the interviewees' own account and no clinical consequence is reported."},{"id":"c4","status":"reported","evidence":[{"locator":"'The government also condemned the \"sickening\" messages and said they \"go against British values and decency\"'; 'It is understood X is looking into the issue and some of the posts have been removed.'","relation":"supports","source_id":"s1"},{"locator":"'In a statement to the BBC, a spokesperson for the Department for Science, Innovation and Technology said: “These posts are sickening and irresponsible'; 'AI services including chatbots that enable users to share content are regulated under the Online Safety Act'","relation":"supports","source_id":"s2"}],"assertion":"A UK government spokesperson told the BBC the posts were sickening and irresponsible and that AI chatbots enabling users to share content are regulated under the Online Safety Act, and the BBC reported that X was understood to be looking into the issue and that some posts had been removed.","causal_attribution":"The government statement was given to the BBC and the Guardian relays it, so it has one origin; no enforcement step is reported."},{"id":"c5","status":"reported","evidence":[{"locator":"'the Grok account said: \"I follow prompts to deliver without added censorship'; 'The posts have been removed from X after complaints. No initiation of harm on my end.'","relation":"supports","source_id":"s1"},{"locator":"'In one post it said its responses were generated “strictly because users prompted me explicitly for vulgar roasts”'; 'I follow prompts to deliver without added censorship'","relation":"supports","source_id":"s2"}],"assertion":"Grok's account replied to users who complained that its responses were generated because users prompted it explicitly for vulgar roasts, that it follows prompts without added censorship, that the posts had been removed after complaints, and that there was no initiation of harm on its end.","causal_attribution":"Both outlets quote the same Grok replies on X, a single origin; the replies are the chatbot's output and not an xAI statement."},{"id":"c6","status":"reported","evidence":[{"locator":"'were generated after X users asked Grok to create \"vulgar\" posts about Liverpool and Manchester United, telling the AI tool to not hold back'; 'some of which have now been removed'; 'generated explicit and derogatory posts about the Hillsborough and Heysel disasters, the death of former Liverpool forward Diogo Jota and the Munich air disaster'; 'was at Hillsborough on the day of the 1989 disaster, said he was \"deeply horrified\" by the Grok posts'","relation":"supports","source_id":"s3"}],"assertion":"By 8 March 2026 the posts had been generated and some removed; BBC Sport reported that Grok had generated explicit and derogatory posts about the Hillsborough and Heysel disasters, the death of Diogo Jota and the Munich air disaster, and a Liverpool MP who was at Hillsborough in 1989 told BBC Sport he was deeply horrified by the Grok posts.","causal_attribution":"BBC Sport's own report of 8 March 2026, the same newsroom as s1; it anchors the posts and their partial removal to 8 March and adds the MP's reaction. It does not give the posting dates."}],"effects":[{"label":"a bereaved relative describes disgust at Grok's Hillsborough post and a survivors' representative calls the posts triggering","claim_id":"c3","direction":"negative"}],"sources":[{"id":"s1","url":"https://www.bbc.co.uk/news/articles/c1mjyggyn1eo","kind":"news_report","access":"read","language":"en","translation_note":"Read live in English on 2026-10-08 (BBC News, North West, 9 March 2026); no translation.","independence_group":"bbc-north-west-2026-03-09"},{"id":"s2","url":"https://www.theguardian.com/technology/2026/mar/09/liverpool-and-manchester-united-complain-to-x-over-sickening-grok-ai-posts","kind":"news_report","access":"read","language":"en","translation_note":"Read live in English on 2026-10-08 (the Guardian, 9 March 2026); no translation.","independence_group":"guardian-2026-03-09"},{"id":"s3","url":"https://www.bbc.co.uk/sport/football/articles/c1w5221prjgo","kind":"news_report","access":"read","language":"en","translation_note":"Read on 2026-10-08 from the body saved by the run's verifier (BBC Sport, 8 March 2026); English, no translation.","independence_group":"bbc-north-west-2026-03-09"}],"version":1,"ai_roles":["others_use"],"contexts":["everyday_life"],"unknowns":["The full text of the deleted Grok posts and how many people saw them before removal.","Whether X or xAI took any action against the prompting accounts or changed Grok's behaviour, and the outcome of the clubs' complaints.","Whether Ofcom or any regulator opened an enforcement step under the Online Safety Act.","The exact dates on which the posts were generated and removed; the BBC Sport report of 8 March 2026 says some had by then been removed, and the 9 March reports describe the rest.","Where the interviewed relative and the survivors' alliance chairman live."],"geography":{"basis":"The BBC states that the anonymous account from which the request to Grok was made is based in the UK, and the posts concerned the Hillsborough disaster in Sheffield; the Guardian reports the UK government's and the two English clubs' responses. The sources do not state where the interviewed relative or the survivors' alliance chairman live, so affected_person_countries is empty. No court is involved.","court_countries":[],"event_countries":["GB"],"affected_person_countries":[]},"publication":{"basis":"Published on two directly read news reports from different newsrooms (BBC North West, 9 March 2026, with its own interviews; the Guardian, 9 March 2026, citing The Athletic for the prompt text) that describe what Grok generated, the prompts that produced it, the complaints and removals, and the distress that a bereaved relative and a survivors' representative report on reading the posts. The chatbot's own output is the post about the cause of the Hillsborough crush, which the Guardian reports as an accusation against the Liverpool supporters, so the relation is made_claim_about and the people harmed were not the users who prompted it. The interviewees spoke to the BBC by name but are described here by role only; the prompting accounts are anonymous and not identified.","reviewed_on":"2026-10-08"},"ai_involvement":{"basis":"The BBC reports that Grok, the chatbot built into X, posted the offensive comments in response to an anonymous X user's request for a 'vulgar post' about Liverpool mentioning Hillsborough and Heysel, and that the posts repeated debunked claims about the causes of the 1989 disaster; the Guardian, citing The Athletic for the prompt text, reports that Grok replied in a now-deleted post accusing Liverpool's supporters of causing the 'deadly crush'. Both outlets quote Grok's own reply that it generated the posts because users prompted it for vulgar roasts. The harm is the distress that a bereaved relative and a survivors' representative describe on reading those generated posts, so the connection between the chatbot's output and the reported harm is stated in the sources. The relation is made_claim_about because the generated post made a false accusation about the Liverpool supporters present at Hillsborough, the group to which the survivors and the deceased belonged; the people harmed were not the users who prompted Grok.","status":"supported"},"person_relations":["made_claim_about"]},"name":"Grok on X posts 'vulgar roasts' repeating debunked Hillsborough claims and mocking Munich; survivors and bereaved relatives tell the BBC of their distress","summary":"In March 2026, X users prompted Grok, the chatbot built into the X app, to write 'vulgar' posts about Liverpool FC and Manchester United. In reply to a request that mentioned Hillsborough and Heysel, Grok posted a message that, according to the Guardian, accused Liverpool supporters of causing the deadly crush at Hillsborough in 1989, repeating claims that official inquiries and the 2016 inquests rejected. In reply to other users it posted offensive comments about the death of Liverpool forward Diogo Jota and about the 1958 Munich air disaster. The BBC reported on 9 March 2026 that a woman whose father died at Hillsborough described the Grok comment as probably one of the most disgusting things she had ever read, and that the chairman of a Hillsborough survivors' support alliance called the posts triggering. Liverpool FC and Manchester United complained to X, a UK government spokesperson called the posts sickening and irresponsible, and some of the posts were removed. Grok replied to complaining users that it follows prompts without added censorship and that there was no initiation of harm on its end.","incidentDate":"2026-03-01","incidentKind":"bounded_series","incidentDatePrecision":"month","exposurePattern":"single_interaction","reportedDate":"2026-03-09","aiSystem":"Grok, xAI's chatbot built into the X social media app, generating public reply posts to users' prompts","aiProduct":"Grok","severity":"low","verificationStatus":"credible","harmCategories":[],"harmOutcomes":["psychological_distress"],"harmOutcomeSummary":"A bereaved relative told the BBC the Grok post about Hillsborough was probably one of the most disgusting things she had ever read, and the chairman of a Hillsborough survivors' support alliance said the posts were triggering for survivors. No clinical, financial or legal consequence is reported.","frameworkFacets":[],"causationStatus":"supported","participantUsersAffectedMin":0,"otherPeopleHarmedMin":2,"affectedCountStatus":"partial","affectedCountEvidence":"Two people counted: the bereaved relative who told the BBC she had read the Grok post and described her reaction, and the Liverpool MP who was at Hillsborough in 1989 and told BBC Sport he was deeply horrified by the posts. The survivors' alliance chairman described the posts as triggering for survivors, an unquantified additional group, so the status is partial. The clubs, X users who complained and Manchester United supporters are not counted. Nobody is counted as an AI user: the prompting accounts are the authors of the requests, not harmed people.","victimAgeRange":"adult","jurisdiction":"GB","platformType":"chatbot","outcomeType":"media_coverage","outcomeStatus":"ongoing","primarySourceUrl":"https://www.bbc.co.uk/news/articles/c1mjyggyn1eo","primarySourceLabel":"BBC News, 9 March 2026: Hillsborough survivors 'appalled' by Grok AI posts","firstPublishedAt":"2026-10-08T03:24:00.142154+00:00","updatedAt":"2026-10-11T07:44:24.500402+00:00","scopeVersion":"facts-v3","tags":["made-claim-about","grok","x","false-claims","football","hillsborough","bereaved-families","uk","online-safety-act"]},{"id":"2026-patient-reports-chatgpt-recording-at-clinic-without-consent","caseFacts":{"claims":[{"id":"recording","status":"reported","evidence":[{"locator":"Do you mind if I have AI take notes today?","relation":"supports","source_id":"s1"},{"locator":"When I expressed that I don't want it","relation":"supports","source_id":"s1"},{"locator":"queued up to ChatGPT and already recording","relation":"supports","source_id":"s1"}],"assertion":"The patient reports that the nurse’s phone showed ChatGPT already recording when the patient declined AI note-taking.","causal_attribution":"The recording and product identification are the patient’s account. No device evidence or independent confirmation was inspected."},{"id":"objection","status":"reported","evidence":[{"locator":"having something recording in the clinic without notice","relation":"supports","source_id":"s1"},{"locator":"told me she doesn't understand why some people make such a big deal of it","relation":"supports","source_id":"s1"}],"assertion":"The patient says there had been no notice of the recording and the nurse dismissed their objection.","causal_attribution":"The described adverse experience is loss of control over recording and consent; no legal finding or onward data transfer is inferred."},{"id":"clarification","status":"reported","evidence":[{"locator":"Her phone was on the counter with chrome open to chatgpt.","relation":"supports","source_id":"s2"},{"locator":"She had already been recording from the moment she entered the room","relation":"supports","source_id":"s3"},{"locator":"I had to insist that it be disabled and I don't think she would have, had I not insisted.","relation":"supports","source_id":"s3"}],"assertion":"In replies to the same thread, the patient says the phone displayed ChatGPT in Chrome, that recording had already begun when the nurse entered, before asking consent, and that the recording was disabled only after the patient insisted.","causal_attribution":"The same author adds these observations. Their illustrative introduction with name/reason placeholders is not treated as an actual consultation transcript. Server transmission and later handling remain unknown."}],"effects":[{"label":"The patient reports that the nurse’s phone showed ChatGPT already recording when the patient declined AI note-taking.","claim_id":"recording","direction":"negative"}],"sources":[{"id":"s1","url":"https://www.reddit.com/r/antiai/comments/1ww4yn4/today_i_was_radicalized/","kind":"forum_post","access":"read","language":"en","translation_note":"Original English post body read directly and through its Arctic Shift capture. The archive gives created_utc 1790974521 (2 October 2026, 20:55 UTC). The author says the appointment was today; timezone is unknown, so only October is recorded for the event. Replies by the same author remain one reporting chain.","independence_group":"reddit-original-patient-account"},{"id":"s2","url":"https://www.reddit.com/r/antiai/comments/1ww4yn4/comment/pdhsn3l/","kind":"forum_comment","access":"read","language":"en","translation_note":"Original English author reply inspected in the Arctic Shift thread capture. The reply author matches the original poster. It adds detail, not independent corroboration.","independence_group":"reddit-original-patient-account"},{"id":"s3","url":"https://www.reddit.com/r/antiai/comments/1ww4yn4/comment/pdhtd2k/","kind":"forum_comment","access":"read","language":"en","translation_note":"Original English author reply inspected in the Arctic Shift thread capture. The reply author matches the original poster. It adds detail, not independent corroboration.","independence_group":"reddit-original-patient-account"}],"version":1,"ai_roles":["institutional_use"],"contexts":["health","privacy"],"unknowns":["Exact local event day and clinic location; the archived post timestamp is 2 October 2026 UTC.","Independent confirmation of the account and the clinic’s response.","What information was captured, the recording duration and whether it was deleted.","Whether information was transmitted, retained or used for training.","The software configuration, account type and any legal finding."],"geography":{"basis":"The original account gives no event location. References to a privacy law and the language do not establish a country.","court_countries":[],"event_countries":[],"affected_person_countries":[]},"publication":{"basis":"Reviewed first-person account of an actual recording reportedly occurring in an identified AI service before consent. Published with attribution and explicit limits under the approved input-privacy boundary; no independent corroboration or finding of illegality is claimed.","reviewed_on":"2026-10-11"},"ai_involvement":{"basis":"The patient identifies ChatGPT as already recording at the appointment when they objected to AI note-taking. Under the approved input-privacy boundary, the reported capture itself supplies the relation and consent harm. This does not establish transmission to a server, retention, training, specific captured content, the account type or illegality. The author’s own replies specify that the phone displayed ChatGPT in Chrome, that recording had already begun when the nurse entered, before consent was requested, and that it was disabled only after the author insisted.","status":"reported"},"person_relations":["received_personal_information"]},"name":"Patient reports a nurse was already recording with ChatGPT when they declined AI notes","summary":"In a public Reddit account, a patient says a nurse asked whether AI could take notes at a medical appointment. After the patient objected, the nurse picked up a phone that the patient described as showing ChatGPT already recording. The patient describes the recording as occurring without prior notice and says their objection was dismissed. In replies, the author says the phone had Chrome open to ChatGPT, that recording had started when the nurse entered the room, before she asked consent, and that the recording was disabled only after the author insisted. This is an uncorroborated first-person account. It does not establish what was captured, whether anything was sent to a server, retained or used for training, or whether a law was broken. The clinic’s location, account type and response are unknown.","incidentDate":"2026-10-01","incidentKind":"single_event","incidentDatePrecision":"month","exposurePattern":"unknown","reportedDate":"2026-10-02","aiSystem":"ChatGPT on a nurse’s phone, identified by the patient in a public first-person account as already recording at a medical appointment.","aiProduct":"ChatGPT (reported)","severity":"low","verificationStatus":"unverified","harmCategories":[],"harmOutcomes":["loss_of_autonomy"],"harmOutcomeSummary":"The patient reports loss of control over recording of their medical appointment: the phone was allegedly already recording before consent, their objection was dismissed, and the recording was disabled only after they insisted. No server disclosure or clinical harm is established.","frameworkFacets":[],"causationStatus":"alleged","participantUsersAffectedMin":0,"otherPeopleHarmedMin":1,"affectedCountStatus":"exact","affectedCountEvidence":"One patient reports their own consent and privacy experience. No other patients, staff or commenters are counted.","victimAgeRange":"unknown","primarySourceUrl":"https://www.reddit.com/r/antiai/comments/1ww4yn4/today_i_was_radicalized/","primarySourceLabel":"Reddit, 2 October 2026: patient’s account of recording at a medical appointment","firstPublishedAt":"2026-10-06T04:48:59.923465+00:00","updatedAt":"2026-10-11T07:43:42.087573+00:00","scopeVersion":"facts-v3","tags":["privacy","consent","clinical-notes","first-person-account"]},{"id":"2026-openai-ai-support-assistant-refused-chatgpt-pro-refund-requested-minutes-after-renewal-first-person","caseFacts":{"claims":[{"id":"c1","status":"reported","evidence":[{"locator":"'my ChatGPT Pro plan renewed for $200'; 'I forgot to cancel beforehand and did not intend to renew'; '13:32:55'","relation":"supports","source_id":"s2"},{"locator":"'approximately six minutes after the charge'; 'Tbilisi, UTC+4'","relation":"supports","source_id":"s1"}],"assertion":"The poster says their ChatGPT Pro plan renewed for $200 on 3 October 2026 after they forgot to cancel, and that they requested a refund in the Help Center about six minutes after the charge.","causal_attribution":"Poster's account."},{"id":"c2","status":"reported","evidence":[{"locator":"'The AI declined without giving a reason specific to my account'; 'This case is closed. Create a new case to receive support.'","relation":"supports","source_id":"s1"},{"locator":"'The Help Center assistant gave a generic refusal without identifying which eligibility requirement I failed'; 'When I asked for escalation, the case was closed'","relation":"supports","source_id":"s2"}],"assertion":"The poster says the Help Center AI assistant declined the refund without a reason specific to their account and, when they asked for escalation, the chat showed the case as closed.","causal_attribution":"Poster attributes the refusal to an AI assistant; whether the decision followed fixed policy rules or human configuration is not known."},{"id":"c3","status":"reported","evidence":[{"locator":"'I opened another case specifically requesting a human billing specialist. Same generic refusal.'; 'another refusal arrived, explicitly marked as generated with AI support'; 'That also received an AI-generated refusal'","relation":"supports","source_id":"s1"},{"locator":"'A second chat specifically asking for a human produced the same refusal'; 'also received responses explicitly labeled as AI-generated'","relation":"supports","source_id":"s2"}],"assertion":"The poster says a second chat asking for a human billing specialist produced the same refusal, and that two email requests received refusals marked as AI-generated.","causal_attribution":"Poster's account."},{"id":"c4","status":"reported","evidence":[{"locator":"'seven-day discretionary refund policy is conditional, not an automatic entitlement'; 'I still have no explanation specific to my case and no confirmed human review'","relation":"supports","source_id":"s2"},{"locator":"'I also explicitly agreed that refunded subscription access would end'; 'I find this an appalling way to treat a paying customer'","relation":"supports","source_id":"s1"}],"assertion":"The poster acknowledges that the refund policy is discretionary and conditional, says they agreed that refunded access would end, and says they still had no case-specific explanation or confirmed human review.","causal_attribution":"Poster's account."}],"effects":[{"label":"refund of an unwanted $200 renewal refused by an AI support assistant without a case-specific reason (poster's account)","claim_id":"c2","direction":"negative"},{"label":"requests for a human review closed or answered by further AI-generated refusals (poster's account)","claim_id":"c3","direction":"negative"}],"sources":[{"id":"s1","url":"https://www.reddit.com/r/ChatGPT/comments/1wwjs10/i_requested_a_chatgpt_refund_6_minutes_after_a/","kind":"forum_post","access":"read","language":"en","translation_note":"Read in English on 2026-10-04: full self-text and the thread's 6 comments (none by the poster), retrieved through the arctic_shift archive API by post ID. The attached screenshots were not retrieved. The poster handle is not recorded.","independence_group":"reddit-chatgpt-pro-refund-poster"},{"id":"s2","url":"https://www.reddit.com/r/OpenAI/comments/1wwjyfk/chatgpt_pro_renewal_refund_request_within_minutes/","kind":"forum_post","access":"read","language":"en","translation_note":"Read in English on 2026-10-04: full self-text and the thread's 15 comments (none by the poster), retrieved through the arctic_shift archive API by post ID. Same poster as s1, posted about eleven minutes later and linking s1; not independent.","independence_group":"reddit-chatgpt-pro-refund-poster"}],"version":1,"ai_roles":["institutional_use"],"contexts":["finance","everyday_life"],"unknowns":["Whether the poster was eligible for a refund under OpenAI's discretionary policy, including any usage in the minutes after renewal.","Whether any human reviewed or set the refusals, and whether a later human review or bank chargeback recovered the $200.","Where the poster lives; the timeline is given in Tbilisi time only."],"geography":{"basis":"The poster gives their timeline in Tbilisi time (UTC+4) but does not say where they were or live; no country is recorded.","court_countries":[],"event_countries":[],"affected_person_countries":[]},"publication":{"basis":"Published under the 2026-09-15 charter's public-forum rule as a concrete first-person account of an AI support system refusing a refund and blocking escalation to a human, described with attribution and without corroboration. The poster's handle is not recorded.","reviewed_on":"2026-10-04"},"ai_involvement":{"basis":"The poster says the Help Center refusals came from an AI assistant and that the email replies were explicitly labelled as generated with AI support; the screenshots they describe were not retrieved. Whether a human reviewed or set the refusal is not known.","status":"reported"},"person_relations":["communicated_with","made_decision_about"]},"name":"First-person forum account: a ChatGPT Pro subscriber says OpenAI's AI support assistant refused a refund they requested about six minutes after an unwanted $200 renewal, closed the case when they asked for escalation, and answered further chat and email requests for a human review with more AI-generated refusals","summary":"In public posts to r/ChatGPT and r/OpenAI on 3 October 2026, a person says their ChatGPT Pro subscription renewed for $200 that day after they forgot to cancel, and that they cancelled auto-renewal and requested a refund in OpenAI's Help Center about six minutes after the charge. They say the Help Center's AI assistant declined without giving a reason specific to their account, and that when they asked for escalation the chat showed that the case was closed. A second chat asking specifically for a human billing specialist produced the same refusal, they write, and two email requests, one with five redacted screenshots, received replies marked as generated with AI support. The poster acknowledges that OpenAI's seven-day refund policy is discretionary and conditional, and says the unresolved problem is that they received no case-specific explanation and no confirmed human review. OpenAI's handling is described only by the poster, and the account is uncorroborated.","incidentDate":"2026-10-03","incidentKind":"single_event","incidentDatePrecision":"day","exposurePattern":"repeated_interactions","reportedDate":"2026-10-03","aiSystem":"OpenAI Help Center AI support assistant (chat) and AI-generated email support replies handling a ChatGPT Pro refund request","aiProduct":"OpenAI Help Center assistant","aiCompany":"OpenAI","severity":"low","verificationStatus":"unverified","harmCategories":[],"harmOutcomes":["financial_loss"],"harmOutcomeSummary":"The poster says OpenAI's AI support assistant refused a refund of an unwanted $200 ChatGPT Pro renewal that they requested within minutes, closed the case when they asked for escalation, and that further chat and email requests for a human review produced only AI-generated refusals, leaving them without the $200, a case-specific reason or human review (first-person account, uncorroborated).","frameworkFacets":[],"causationStatus":"alleged","participantUsersAffectedMin":1,"otherPeopleHarmedMin":0,"affectedCountStatus":"exact","affectedCountEvidence":"One person: the poster. A commenter who says they had the same refund problem is not counted. Exact 1.","victimAgeRange":"unknown","jurisdiction":"unknown","platformType":"chatbot","outcomeStatus":"ongoing","primarySourceUrl":"https://www.reddit.com/r/ChatGPT/comments/1wwjs10/i_requested_a_chatgpt_refund_6_minutes_after_a/","primarySourceLabel":"r/ChatGPT, 3 October 2026: \"I requested a ChatGPT refund 6 minutes after a $200 renewal. The AI rejected it and closed the case.\"","firstPublishedAt":"2026-10-04T03:22:06.262385+00:00","updatedAt":"2026-10-04T03:22:06.262385+00:00","scopeVersion":"facts-v3","tags":["first-person","reddit","openai","chatgpt","ai-customer-support","refund","billing","no-human-review","made-decision-about","communicated-with"]},{"id":"2026-south-africa-sassa-elife-certification-portal-facial-verification-failures-reported-by-pensioners","caseFacts":{"claims":[{"id":"c1","status":"reported","evidence":[{"locator":"The eLife Certification was implemented on March 30, 2026, as a digital verification tool to curb fraud.","relation":"supports","source_id":"s1"},{"locator":"Beneficiaries who fail to complete the process risk having their grants suspended.","relation":"supports","source_id":"s1"},{"locator":"secure biometric verification through the electronic Know Your Client (eKYC) system","relation":"supports","source_id":"s2"},{"locator":"Beneficiaries who fail to complete life certification as directed may face payment delays or suspension of their grants.","relation":"supports","source_id":"s2"}],"assertion":"SASSA's eLife Certification is a self-service life certification on its online portal that uses biometric verification through its electronic Know Your Client (eKYC) system. IOL reports it was implemented on 30 March 2026. SASSA said beneficiaries who fail to complete life certification as directed may face payment delays or suspension of their grants.","causal_attribution":"The implementation date comes from IOL alone. SASSA statements read do not give a start date. The suspension consequence is SASSA's own stated rule and no suspension of either pensioner's grant is reported."},{"id":"c2","status":"reported","evidence":[{"locator":"SASSA would like to apologise to all our beneficiaries who could not access our self-service portal after they were notified to undertake the eLife Certification verification process by the Agency.","relation":"supports","source_id":"s2"},{"locator":"there were system glitches which led to delay and disruptions in completing eLife Certification, leading to long queues at SASSA offices.","relation":"supports","source_id":"s2"},{"locator":"the Agency can report that the challenge has been resolved.","relation":"supports","source_id":"s2"}],"assertion":"On 10 April 2026 SASSA apologised to beneficiaries who could not access its self-service portal after being notified to complete eLife Certification. It said system glitches linked to interfaces with other departments had caused delays and disruptions and long queues at its offices, and said the challenge had been resolved.","causal_attribution":"SASSA's own account of its portal. The statement does not mention facial recognition and attributes the glitches to interfaces with other departments."},{"id":"c3","status":"reported","evidence":[{"locator":"both pensioners, told IOL they had tried to complete the facial recognition option on the portal but to no avail.","relation":"supports","source_id":"s1"},{"locator":"We have been trying since Thursday, April 2, to do the selfie bit but it does not work after trying for 22 times","relation":"supports","source_id":"s1"}],"assertion":"A pensioner couple told IOL they had tried the facial recognition option on the eLife portal 22 times since 2 April 2026 without success. IOL published the account on 23 April 2026.","causal_attribution":"Single first-person account relayed by one outlet. The cause of the failures is not established. The department attributes facial verification problems in general to poor lighting, unstable connectivity or missing Home Affairs biometric records (see c6)."},{"id":"c4","status":"reported","evidence":[{"locator":"IOL has been inundated with emails and calls from beneficiaries nationwide claiming they were unable to complete the mandatory certification process.","relation":"supports","source_id":"s1"},{"locator":"beneficiaries cite consistent failures with facial recognition and one-time pins (OTPs).","relation":"supports","source_id":"s1"},{"locator":"The system just kept on loading and never went through to my profile. I have been struggling for three weeks","relation":"supports","source_id":"s1"},{"locator":"Then also indicated that the Department of Home Affairs is not available to verify my particulars","relation":"supports","source_id":"s1"}],"assertion":"IOL reported that beneficiaries nationwide contacted it to say they could not complete the certification and cited failures with facial recognition and one-time PINs. One pensioner said the site kept loading without reaching their profile for three weeks, and reported a one-time PIN rejection and a message that Home Affairs was not available to verify their particulars.","causal_attribution":"Unquantified accounts relayed by IOL. The pensioner who described the loading failure and the one-time PIN rejection did not describe a facial recognition failure."},{"id":"c5","status":"reported","evidence":[{"locator":"The Sassa portals are working as evidenced by the number of clients who have accessed the online services.","relation":"supports","source_id":"s1"},{"locator":"As of April 16, 2026, 13,644 (88%) of the 15,499 unique clients who accessed the online verification services via the client portal were successfully verified","relation":"supports","source_id":"s1"},{"locator":"However, Sassa admitted the system has been working intermittently.","relation":"supports","source_id":"s1"}],"assertion":"A SASSA spokesperson told IOL the portals are working and that, as of 16 April 2026, 13,644 (88%) of 15,499 unique clients who accessed the online verification services via the client portal were successfully verified. IOL reports SASSA admitted the system had been working intermittently.","causal_attribution":"SASSA's own figures and account, which were not independently verified. The figures count clients who accessed online verification and do not report how many failed the facial step."},{"id":"c6","status":"reported","evidence":[{"locator":"SASSA said most non-verification cases were driven by beneficiaries failing to respond to notifications, not completing life certification, or unsuccessful facial recognition attempts on online platforms.","relation":"supports","source_id":"s3"},{"locator":"In such cases, beneficiaries are redirected to fingerprint biometric verification at local offices.","relation":"supports","source_id":"s3"},{"locator":"The agency said it had recorded 7,779 complaints linked to its electronic facial biometric system","relation":"supports","source_id":"s3"},{"locator":"The department attributed facial verification issues to poor lighting, unstable connectivity, or missing biometric records at the Department of Home Affairs.","relation":"supports","source_id":"s3"},{"locator":"The agency said it had recorded 7 779 complaints linked to its electronic facial biometric system.","relation":"supports","source_id":"s4"}],"assertion":"IOL's 24 May 2026 report on a parliamentary reply says SASSA said most non-verification cases were driven by beneficiaries who did not respond to notifications, did not complete life certification, or had unsuccessful facial recognition attempts on online platforms, and that such beneficiaries are redirected to fingerprint verification at local offices. IOL says SASSA had recorded 7,779 complaints linked to its electronic facial biometric system and that the department attributed facial verification issues to poor lighting, unstable connectivity or missing biometric records at the Department of Home Affairs.","causal_attribution":"SASSA's account relayed by two outlets that share one reporter and one reply, so they are one chain. The reports do not date the complaints or say whether they concern eLife Certification or earlier online facial verification, and do not say how many were repeat complaints."},{"id":"c7","status":"reported","evidence":[{"locator":"with 67,868 grants suspended in the third quarter alone","relation":"supports","source_id":"s3"},{"locator":"a grant is suspended 2 months after a beneficiary was notified to conduct a review and has not yet done so","relation":"supports","source_id":"s3"},{"locator":"around 70 000 grants have been suspended due to beneficiaries failing to come forward for review","relation":"supports","source_id":"s5"}],"assertion":"The parliamentary reply reported 67,868 grants suspended in the third quarter (the reports do not identify the period) under a rule that a grant is suspended two months after a beneficiary was notified to conduct a review and has not yet done so. A Parliament committee statement of 5 February 2026 reported around 70,000 grants suspended for beneficiaries failing to come forward for review.","causal_attribution":"The suspension figures are context. No inspected report says how many suspensions followed a facial verification failure, and the committee statement predates the eLife implementation date reported by IOL."}],"effects":[{"label":"Pensioners reported repeated failures of the facial recognition step in a mandatory online life certification, with a stated risk of payment delay or grant suspension if it is not completed","claim_id":"c3","direction":"negative"},{"label":"SASSA reported delays, disruptions and long queues at its offices after beneficiaries could not use the self-service certification portal, which SASSA attributed to interfaces with other departments (its statement does not mention facial recognition)","claim_id":"c2","direction":"negative"}],"sources":[{"id":"s1","url":"https://iol.co.za/news/south-africa/2026-04-23-sassa-elife-certification-portal-beneficiaries-report-ongoing-glitches-despite-agency-denials/","kind":"news_report","access":"read","language":"en","translation_note":"","independence_group":"iol-elife-glitches-report"},{"id":"s2","url":"https://www.gov.za/news/media-statements/sassa-self-service-system-restored-following-earlier-challenges-10-apr-2026","kind":"official_statement","access":"read","language":"en","translation_note":"","independence_group":"sassa-10-apr-2026-statement"},{"id":"s3","url":"https://iol.co.za/news/south-africa/2026-05-24-sassas-biometric-rollout-leaves-thousands-without-grants-amid-fraud-crackdown/","kind":"news_report","access":"read","language":"en","translation_note":"","independence_group":"parliamentary-reply-iol-report"},{"id":"s4","url":"https://dailyvoice.co.za/news/2026-05-25-sassas-face-palm-facial-recognition-tech-linked-to-the-suspension-of-68-000-grants/","kind":"news_report","access":"read","language":"en","translation_note":"","independence_group":"parliamentary-reply-iol-report"},{"id":"s5","url":"https://www.parliament.gov.za/index.php/press-releases/media-statement-committee-notes-grant-reviews-are-necessary-protect-poor-and-public-funds","kind":"official_statement","access":"read","language":"en","translation_note":"","independence_group":"parliament-committee-5-feb-2026-statement"}],"version":1,"ai_roles":["institutional_use"],"contexts":["public_services","accessibility"],"unknowns":["The reports do not say how many of the 67,868 grant suspensions (third quarter, period not identified) followed unsuccessful facial recognition. The suspensions are governed by a review non-response rule, and a committee statement dated 5 February 2026 already reported around 70,000 suspensions before the eLife implementation date reported by IOL.","The 30 March 2026 implementation date comes from IOL only. The SASSA statements read do not give a start date.","SASSA's statement refers to facial recognition on online platforms in general. Neither IOL 24 May 2026 nor Daily Voice 25 May 2026 mentions eLife Certification, and IOL places the reply within a biometric verification rollout dated from September 2025 (compulsory biometric enrolment for new applicants, verified at local offices). Whether the 7,779 complaints and the redirections to fingerprint checks concern eLife Certification at all is not stated. Facial photo verification through the same eKYC system for Social Relief of Distress grant applicants was reported earlier (Biometric Update, August 2024, and Corruption Watch, January 2025) and is a separate earlier deployment that this case does not cover.","Whether the pensioner couple later completed certification, or whether any grant was delayed or suspended, is not reported.","The cause of the couple's failed attempts is not established (lighting, connectivity, missing Home Affairs records, or the facial matching itself).","SASSA said on 10 April 2026 that the problem was resolved, and IOL reported failures continuing on 23 April 2026. The 88% success figure is SASSA's and was not checked.","The pensioner accounts come from one outlet (IOL). A Joburg ETC article of the same date relays it and adds nothing independent.","IOL page dates were taken from the URLs (23 April and 24 May 2026) because the page bodies show only relative ages."],"geography":{"basis":"IOL reports social grant recipients across South Africa struggling with the portal, and the SASSA statement and parliamentary reply concern the South African Social Security Agency's beneficiaries.","court_countries":[],"event_countries":["ZA"],"affected_person_countries":["ZA"]},"publication":{"basis":"IOL (23 April and 24 May 2026), SASSA's 10 April 2026 statement on gov.za, Daily Voice and a Parliament committee statement were read in full. SASSA's and IOL's accounts are attributed and left at reported, and the pensioners' failures come from one outlet. The pensioners are not named. No inspected report attributes any grant suspension to facial verification failures.","reviewed_on":"2026-09-29"},"ai_involvement":{"basis":"The sources describe a facial recognition step in SASSA's eLife Certification portal, which uses biometric verification through the eKYC system and integration with Home Affairs systems, and IOL's 24 May 2026 report of a parliamentary reply refers to SASSA's electronic facial biometric system without saying whether it is the eLife portal. The vendor and model are not identified. The department attributes facial verification problems to poor lighting, unstable connectivity or missing Home Affairs biometric records, and a SASSA spokesperson says the portals work with intermittent downtime, so the cause of any individual failure is not established.","status":"reported"},"person_relations":["made_decision_about"]},"name":"South Africa: pensioners report repeated failures of the facial recognition step in SASSA's eLife certification portal, and SASSA reports disruptions and office queues","summary":"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.","incidentDate":"2026-03-30","incidentKind":"bounded_series","incidentDatePrecision":"day","exposurePattern":"repeated_interactions","reportedDate":"2026-04-23","aiSystem":"Facial recognition step in SASSA's eLife Certification portal (biometric verification through the eKYC system, integrated with Home Affairs systems). Vendor and model not identified in the sources.","aiProduct":"SASSA eLife facial verification","aiCompany":"South African Social Security Agency (SASSA), deployer","severity":"low","verificationStatus":"unverified","harmCategories":[],"harmOutcomes":["other_material_harm"],"harmOutcomeSummary":"SASSA said glitches caused delays, disruptions and long queues at its offices, and a pensioner couple told IOL they had tried the facial recognition step 22 times since 2 April without success. SASSA warned that beneficiaries who do not complete life certification as directed may face payment delays or suspension. No inspected report says that either pensioner's grant was delayed or suspended.","frameworkFacets":[],"causationStatus":"alleged","participantUsersAffectedMin":0,"otherPeopleHarmedMin":2,"affectedCountStatus":"partial","affectedCountEvidence":"IOL reports one pensioner couple (two people) who said the facial recognition step failed 22 times. IOL says it was inundated with emails and calls from beneficiaries nationwide and SASSA recorded 7,779 complaints, but complaints are not people and the number of beneficiaries who failed facial verification is not reported, so no larger count is recorded. The 67,868 grant suspensions are not counted because no inspected report attributes them to facial verification.","victimAgeRange":"adult","platformType":"other","primarySourceUrl":"https://iol.co.za/news/south-africa/2026-04-23-sassa-elife-certification-portal-beneficiaries-report-ongoing-glitches-despite-agency-denials/","primarySourceLabel":"IOL (23 Apr 2026)","firstPublishedAt":"2026-09-29T21:16:13.146866+00:00","updatedAt":"2026-09-30T01:17:54.03839+00:00","scopeVersion":"facts-v3","tags":["historical-2026"]},{"id":"2026-us-uk-hachette-cancels-shy-girl-novel-after-ai-authorship-allegations","caseFacts":{"claims":[{"id":"c1","status":"reported","evidence":[{"locator":"The Hachette Book Group said Thursday that it has canceled the publication of horror novel","relation":"supports","source_id":"s1"},{"locator":"where it was first released in November.","relation":"supports","source_id":"s1"},{"locator":"The US release of a horror novel has been cancelled by its publisher over concerns that AI was used to help write it.","relation":"supports","source_id":"s2"},{"locator":"Wildfire (in the UK) have decided to no longer continue publishing their edition","relation":"supports","source_id":"s2"},{"locator":"The title has also been removed from online retailers including Amazon","relation":"supports","source_id":"s3"},{"locator":"But it took until last Thursday for Hachette to pull the book from its website","relation":"supports","source_id":"s8"},{"locator":"March 19 , the New York Times landed a big story about allegations that a hyped horror novel called Shy Girl","relation":"supports","source_id":"s7"}],"assertion":"Hachette Book Group said on Thursday 19 March 2026 that it had cancelled the US publication of the horror novel Shy Girl by Mia Ballard (Orbit imprint) and would not continue the UK edition (Wildfire imprint, first released in November 2025). The Guardian reports the title was also removed from online retailers including Amazon.","causal_attribution":"The cancellation is Hachette’s own announcement, relayed by several outlets. Sources link it to allegations of AI use and to a review by the publisher. Whether AI was in fact used is unresolved (claim c7)."},{"id":"c2","status":"reported","evidence":[{"locator":"readers on platforms such as Goodreads and Reddit had questioned whether sections of the text bore hallmarks of AI-generated prose.","relation":"supports","source_id":"s3"},{"locator":"A widely shared Reddit thread drew hundreds of comments","relation":"supports","source_id":"s3"},{"locator":"amassed more than 1.2m views","relation":"supports","source_id":"s3"},{"locator":"one reviewer on the GoodReads website claimed the book appeared to be \"written by ChatGPT\"","relation":"supports","source_id":"s2"},{"locator":"In January, a Reddit post from a user who claimed to be a book editor generated significant discussion around","relation":"supports","source_id":"s5"},{"locator":"published online on January 19 by","relation":"supports","source_id":"s7"}],"assertion":"Readers alleged online that the novel’s text read as AI-generated: reviews on Goodreads, a widely shared Reddit thread, a January Reddit post by a user who said they were a book editor, and a YouTube video posted in January 2026 that had more than 1.2 million views.","causal_attribution":"Online opinion and analysis by readers. It is not evidence about who produced the text. Sources differ on when the earliest accusations appeared (see unknowns)."},{"id":"c3","status":"reported","evidence":[{"locator":"78.4 percent of the document is AI Generated","relation":"supports","source_id":"s7"},{"locator":"I soon confirmed this with two other services.","relation":"supports","source_id":"s7"},{"locator":"Originality and GPTZero","relation":"supports","source_id":"s7"},{"locator":"found evidence that 78 percent of the book is AI-generated","relation":"supports","source_id":"s5"},{"locator":"that large parts of Shy Girl appeared to show patterns characteristic of A.I.-generated writing.","relation":"supports","source_id":"s6"},{"locator":"to use these reports only for guidance, not as proof of guilt","relation":"context","source_id":"s7"},{"locator":"A.I. detection software, while improving, has been shown to be fallible at best","relation":"context","source_id":"s6"}],"assertion":"AI-detection results were reported as part of the case. A publishing consultant’s first-person account says a copy of the UK edition scored 78.4 percent AI-generated on the Pangram detector, that two other detection services gave confirming results, and that the consultant brought the findings to the New York Times. Futurism reports that the CEO of Pangram ran a test and found evidence that 78 percent of the book is AI-generated. Slate reports that the New York Times verified claims that large parts of the book appeared to show patterns characteristic of AI-generated writing.","causal_attribution":"Detector scores describe statistical patterns in a text. They do not establish who produced the text or whether a generative model was used. Detector reliability is contested in the sources, and the New York Times article that carried the verification was not read."},{"id":"c4","status":"reported","evidence":[{"locator":"following an investigation into the origins of the book.","relation":"supports","source_id":"s1"},{"locator":"the publisher confirmed it had halted publication after an internal review.","relation":"supports","source_id":"s3"},{"locator":"Although the publisher claimed the decision came after a thorough review of the text","relation":"supports","source_id":"s4"},{"locator":"lengthy investigation in recent weeks","relation":"supports","source_id":"s5"},{"locator":"remains committed to protecting original creative expression and storytelling","relation":"supports","source_id":"s2"}],"assertion":"Hachette said its decision followed a review or investigation of the book and cited its commitment to protecting original creative expression and storytelling. The Wall Street Journal report says the cancellation followed an investigation into the origins of the book, and Futurism relays a Hachette statement to the Journal that both its US and UK imprints conducted a lengthy investigation in recent weeks.","causal_attribution":"Publisher statements about its own process. The sources inspected do not report what the review or investigation found about AI use."},{"id":"c5","status":"reported","evidence":[{"locator":"concerns the day before the announcement.","relation":"supports","source_id":"s4"},{"locator":"shortly after the New York Times approached the publisher with evidence of AI use.","relation":"supports","source_id":"s8"},{"locator":"one Times article said that Hachette pulled the book within a day of first notification by the Times","relation":"supports","source_id":"s7"}],"assertion":"The New York Times asked Hachette about the AI concerns the day before the announcement, and the cancellation followed shortly after the Times approached the publisher with evidence of AI use. A consultant’s first-person account says a Times article reported that Hachette pulled the book within a day of first notification by the Times.","causal_attribution":"Timing reported by outlets that rely on the New York Times report, which was not read directly. The sequence shows what preceded the announcement and does not show what Hachette concluded."},{"id":"c6","status":"reported","evidence":[{"locator":"has denied using AI to write the book","relation":"supports","source_id":"s2"},{"locator":"hired to edit the original self-published version of the novel had used AI.","relation":"supports","source_id":"s2"},{"locator":"my mental health is at an all time low and my name is ruined for something I didn","relation":"supports","source_id":"s2"},{"locator":"Ballard has denied personally using AI to write the novel.","relation":"supports","source_id":"s3"},{"locator":"my mental health is at an all time low and my name is ruined for something I didn","relation":"supports","source_id":"s4"},{"locator":"pursuing legal action","relation":"supports","source_id":"s8"},{"locator":"did not personally use AI","relation":"supports","source_id":"s9"},{"locator":"please do your research on editors before trusting them with your work","relation":"supports","source_id":"s9"}],"assertion":"Ballard denied personally using AI to write the novel in an email to the New York Times and, per The Independent, in an email to the Wall Street Journal, and told the New York Times that an acquaintance hired to edit the original self-published version had used AI. Ballard wrote: \"This controversy has changed my life in many ways and my mental health is at an all time low and my name is ruined for something I didn’t even personally do\", and said legal action was being pursued.","causal_attribution":"The author’s own statements about the author’s own conduct and its effects. Ballard spoke publicly under that name in emails to the New York Times and the Wall Street Journal quoted by several outlets. The acquaintance is not named in the sources and no response from that person is reported."},{"id":"c7","status":"disputed","evidence":[{"locator":"found evidence that 78 percent of the book is AI-generated","relation":"supports","source_id":"s5"},{"locator":"78.4 percent of the document is AI Generated","relation":"supports","source_id":"s7"},{"locator":"has denied using AI to write the book","relation":"contradicts","source_id":"s2"},{"locator":"A.I. detection software, while improving, has been shown to be fallible at best","relation":"context","source_id":"s6"}],"assertion":"Whether, by whom and to what extent generative AI produced the text of the published novel is disputed. Detector results and reader analyses point to substantial AI-generated prose. Ballard denies personal use and attributes any AI use to a hired editor. No source inspected reports the editor’s account, an independent verification of authorship, or a finding by the publisher.","causal_attribution":"Causal attribution of the consequence to AI use rests on allegations and detector output that the author disputes. The consequence (cancellation) is a publisher decision responding to those allegations."}],"effects":[{"label":"Publisher cancelled the US edition and discontinued the UK edition of the author’s novel after allegations that it was AI-generated","claim_id":"c1","direction":"negative"},{"label":"Author reports damage to name and severely worsened mental health after the controversy","claim_id":"c6","direction":"negative"}],"sources":[{"id":"s1","url":"https://www.wsj.com/business/media/publisher-pulls-shy-girl-horror-novel-after-ai-allegations-c7944702","kind":"news_report","access":"read","language":"en","translation_note":"","independence_group":"wsj-shy-girl-report"},{"id":"s2","url":"https://www.bbc.com/news/articles/c5y9d44jj24o","kind":"news_report","access":"read","language":"en","translation_note":"","independence_group":"nyt-shy-girl-report"},{"id":"s3","url":"https://www.theguardian.com/books/2026/mar/20/hachette-horror-novel-shy-girl-suspected-ai-use-mia-ballard","kind":"news_report","access":"read","language":"en","translation_note":"","independence_group":"nyt-shy-girl-report"},{"id":"s4","url":"https://techcrunch.com/2026/03/21/publisher-pulls-horror-novel-shy-girl-over-ai-concerns","kind":"trade_press","access":"read","language":"en","translation_note":"","independence_group":"nyt-shy-girl-report"},{"id":"s5","url":"https://futurism.com/artificial-intelligence/novel-pulled-author-accused-ai","kind":"news_report","access":"read","language":"en","translation_note":"","independence_group":"nyt-shy-girl-report"},{"id":"s6","url":"https://slate.com/culture/2026/03/shy-girl-mia-ballard-novel-a-i-book-horror-reddit-hachette-canceled.html","kind":"news_report","access":"read","language":"en","translation_note":"","independence_group":"slate-shy-girl-reporting"},{"id":"s7","url":"https://thewalrus.ca/new-york-times-ai-generated-shy-girl-mia-ballard/","kind":"first_person_account","access":"read","language":"en","translation_note":"","independence_group":"consultant-first-person-account"},{"id":"s8","url":"https://www.publishersweekly.com/pw/by-topic/industry-news/publisher-news/article/100037-while-ai-discourse-rages-publishing-has-more-questions-than-answers.html","kind":"trade_press","access":"read","language":"en","translation_note":"","independence_group":"nyt-shy-girl-report"},{"id":"s9","url":"https://www.aol.com/articles/horror-novel-reportedly-pulled-publication-133355085.html","kind":"news_report","access":"read","language":"en","translation_note":"","independence_group":"wsj-shy-girl-report"}],"version":1,"ai_roles":["others_use"],"contexts":["work"],"unknowns":["Whether generative AI produced any of the text, who used it and to what extent is unresolved. The author denies personal use and attributes any AI use to a hired editor. No source inspected reports that editor’s account, an independent authorship check, or what Hachette found.","The Wall Street Journal page was read as a truncated Wayback extract (three paragraphs, paywall). The New York Times article that first reported the story could not be read (HTTP 403 live and in Wayback captures). Statements attributed to the Times are read through BBC, The Guardian, TechCrunch, Futurism and Publishers Weekly.","Sources differ on when the first online accusations appeared. The Guardian says questions began in early 2026, and Futurism dates a Reddit post to January. Futurism also says accusations have swirled around the book since its self-published run last year, Slate says the rumblings began in January and even earlier, and a first-person account by a publishing consultant says the first accusations appeared online five or six months before Hachette’s July 2025 acquisition announcement and that a Reddit thread was a year old in early February 2026. No inspected source reports a consequence for the author from those earlier accusations. This record dates the event to the publisher’s decision on 19 March 2026, the first reported consequence for the author.","Detector reliability and the tested copy are contested. A Wall Street Journal opinion column on the reliability of the Pangram report was not read, and a summary of it on Wikipedia is not cited.","The author says legal action is being pursued. The target and any filing are not established by the sources inspected. A newsletter’s report of a $1 million lawsuit against Hachette had no filing or second source and is not relied on.","The US publication date is reported differently (April in BBC and Slate, 19 May in the Wall Street Journal). UK sales are reported as about 1,800 (Guardian, citing NielsenIQ) and almost 2,000 (BBC) copies. Neither is used as a harm count.","Whether existing UK copies were withdrawn or destroyed is not consistently reported. The Guardian says the title was removed from online retailers and would no longer be distributed in the UK.","The accusers on Reddit and YouTube, the consultant and the hired editor are not described individually beyond their role in the reporting."],"geography":{"basis":"Hachette cancelled the US release and discontinued the UK edition (BBC). The BBC describes the author as a US author, and The Independent, citing a Google Books author profile, reports a US residence. No court is involved in the sources inspected.","court_countries":[],"event_countries":["US","GB"],"affected_person_countries":["US"]},"publication":{"basis":"The publisher’s cancellation, its stated review, the online allegations, the AI-detector results and the author’s denial were read from the Wall Street Journal (truncated), BBC, The Guardian, TechCrunch, Futurism, Slate, Publishers Weekly, The Independent (via AOL) and a consultant’s first-person account. The author is named because the author spoke publicly under that name in emails to two newspapers. Every AI-related claim is attributed and AI involvement is recorded as disputed. The event is dated to the publisher’s decision on 19 March 2026, the first reported consequence for the author. Earlier reader accusations are recorded as context.","reviewed_on":"2026-09-29"},"ai_involvement":{"basis":"AI-text detectors (Pangram, and per one first-person account Originality and GPTZero) scored the UK edition as largely AI-generated, and readers alleged the prose showed hallmarks of AI. The author denies personally using AI and says an acquaintance hired to edit the self-published version used it. Hachette cited a review of the text and its stance on original creative expression and did not state, in the sources inspected, what the review found. Detector reliability is contested.","status":"disputed"},"person_relations":["made_claim_about"]},"name":"US and UK: Hachette cancels the US edition of the novel Shy Girl and discontinues the UK edition after allegations it was AI-generated, with the author denying personal use of AI","summary":"On 19 March 2026 Hachette Book Group said it had cancelled the US publication of the horror novel Shy Girl by Mia Ballard (Orbit imprint) and would not continue the UK edition (Wildfire imprint, first released in November 2025). Reports say the decision followed an investigation by Hachette and came a day after the New York Times asked the publisher about online allegations that the text was largely AI-generated. The allegations came from readers on Goodreads, Reddit and YouTube and from AI-detector results, including a 78.4 percent AI-generated score on the Pangram detector that a publishing consultant says two other services confirmed. Ballard denied personally using AI in emails to the New York Times and the Wall Street Journal, and told the New York Times that an acquaintance hired to edit the original self-published version used AI. Ballard wrote that \"my name is ruined\" and \"my mental health is at an all time low\", and said legal action was being pursued. Hachette’s public statements cite its commitment to original creative expression. The sources inspected do not report what its investigation found. Whether AI generated any of the text, and who used it, is unresolved.","incidentDate":"2026-03-19","incidentKind":"single_event","incidentDatePrecision":"day","exposurePattern":"unknown","reportedDate":"2026-03-19","aiSystem":"Alleged generative-AI text production in the novel (the author denies personal use and attributes any AI use to a hired editor), and AI-text detectors (Pangram, and per one account Originality and GPTZero) whose scores were used to allege AI authorship","aiProduct":"Pangram AI-text detector","severity":"medium","verificationStatus":"disputed","harmCategories":[],"harmOutcomes":["professional_harm","reputational_harm","psychological_distress"],"harmOutcomeSummary":"Hachette cancelled the US publication and discontinued the UK edition of the author’s novel. The author wrote to the New York Times that \"my mental health is at an all time low and my name is ruined for something I didn’t even personally do\" (relayed by BBC and The Guardian). The author denies personally using AI.","frameworkFacets":[],"causationStatus":"disputed","participantUsersAffectedMin":0,"otherPeopleHarmedMin":1,"affectedCountStatus":"exact","affectedCountEvidence":"One person, the author, reports harm (cancelled publication, damage to name and severely worsened mental health). The hired editor, readers who bought the book and the publisher are not counted as harmed persons.","victimAgeRange":"adult","platformType":"other","primarySourceUrl":"https://www.theguardian.com/books/2026/mar/20/hachette-horror-novel-shy-girl-suspected-ai-use-mia-ballard","primarySourceLabel":"The Guardian (20 Mar 2026)","firstPublishedAt":"2026-09-29T21:16:09.707267+00:00","updatedAt":"2026-09-30T01:17:57.941496+00:00","scopeVersion":"facts-v3","tags":["historical-2026"]},{"id":"2026-chester-home-bargains-facewatch-shopper-told-to-leave-store","caseFacts":{"claims":[{"id":"c1","status":"reported","evidence":[{"locator":"can you please put everything down and leave the shop now?","relation":"supports","source_id":"s2"},{"locator":"come up on our system called Facewatch as a shoplifter","relation":"supports","source_id":"s2"},{"locator":"he was told to leave his local Home Bargains store after the technology linked him to a theft, which he said had nothing to do with him.","relation":"supports","source_id":"s1"},{"locator":"The 67-year-old said the incident, which happened in front of a group of people","relation":"supports","source_id":"s1"}],"assertion":"A 67-year-old shopper at a Home Bargains store in Chester was told by a member of staff to put everything down and leave, with the words that the shopper had come up on the store's Facewatch system as a shoplifter, in front of other people.","causal_attribution":"The shopper's account to the BBC and, separately, to the Guardian. Home Bargains declined to comment to the Guardian and the BBC states it had been approached for comment."},{"id":"c2","status":"reported","evidence":[{"locator":"popped into Home Bargains one February lunchtime","relation":"supports","source_id":"s2"},{"locator":"22 February 2026","relation":"context","source_id":"s1"}],"assertion":"The Guardian says one February lunchtime. The year is inferred from the BBC report of 22 February 2026.","causal_attribution":"The Guardian gives the month and no year. The year is inferred from the BBC report of 22 February 2026 and the GB News report of 23 February 2026, which treat the event as recent. The Guardian gives February for another shopper in the same article where PA gives 27 January, so its month wording is not exact for that case."},{"id":"c3","status":"reported","evidence":[{"locator":"He contacted Facewatch, which sent him his photo with words claiming he had put items into a bag and stolen them.","relation":"supports","source_id":"s1"},{"locator":"revealed he had been incorrectly associated with a shoplifting incident on a previous visit to the shop.","relation":"supports","source_id":"s2"},{"locator":"should not have been on the system and his image and \"the associated record\" had been permanently removed.","relation":"supports","source_id":"s1"}],"assertion":"The shopper contacted Facewatch, which sent a photo with words saying items had been put into a bag and stolen. A subject access request showed the shopper had been incorrectly associated with a shoplifting incident on a previous visit to the store. Facewatch said the shopper should not have been on the system and that the image and associated record were permanently removed.","causal_attribution":"The shopper's account and a Facewatch statement relayed by the BBC. The Guardian rests on a separate interview with the same shopper. Facewatch does not say how the shopper came to be on the system."},{"id":"c4","status":"reported","evidence":[{"locator":"These cases relate to human error in the way processes were carried out in-store, rather than any failure of Facewatch’s technology.","relation":"supports","source_id":"s2"},{"locator":"These three errors are extremely rare cases","relation":"supports","source_id":"s2"},{"locator":"Home Bargains \"has now completed a full review of the incident\"","relation":"supports","source_id":"s1"},{"locator":"Home Bargains and B&M declined to comment.","relation":"supports","source_id":"s2"},{"locator":"we acted promptly as soon as the matter was brought to our attention","relation":"supports","source_id":"s3"},{"locator":"Home Bargains declined to comment when approached by GB News.","relation":"supports","source_id":"s3"}],"assertion":"Facewatch's chief executive told the Guardian, in a statement about the three shoppers the article describes (this shopper is one), that the cases related to human error in the way processes were carried out in store and not to a failure of Facewatch technology. Facewatch told the BBC that Home Bargains had completed a full review of the incident. Home Bargains declined to comment.","causal_attribution":"Facewatch describing its own system and its customer's conduct. The Guardian statement refers to \"the matters referenced\" and \"these three errors\", and the article names three shoppers, of whom this shopper is one. The full review outcome was not published."},{"id":"c5","status":"reported","evidence":[{"locator":"Home Bargains eventually issued him an apology and a £100 voucher as a “gesture of goodwill without admission”, on the condition that the details of the incident remain confidential.","relation":"supports","source_id":"s2"},{"locator":"declined: “I just thought: ‘Really, you’re trying to buy my silence?’”","relation":"supports","source_id":"s2"}],"assertion":"Home Bargains later issued the shopper an apology and a 100 pound voucher as a goodwill gesture without admission, on condition that details of the incident remain confidential. The shopper declined the offer.","causal_attribution":"Guardian account, most likely from the shopper. Home Bargains declined to comment. No second chain was inspected."},{"id":"c6","status":"reported","evidence":[{"locator":"I thought I was going to be sick,","relation":"supports","source_id":"s1"},{"locator":"had left him feeling \"helpless\".","relation":"supports","source_id":"s1"},{"locator":"It was like I was guilty until proven innocent. It’s an awful feeling.","relation":"supports","source_id":"s2"},{"locator":"He has called for an apology and said he just wanted \"to feel safe\" going into his local shops again.","relation":"supports","source_id":"s1"},{"locator":"I’m hyper aware of cameras everywhere now","relation":"supports","source_id":"s2"}],"assertion":"The shopper reports feeling physically sick and helpless, describes an awful feeling of being treated as guilty until proven innocent, and says the shopper wants to feel safe going into local shops again and is now hyper aware of cameras.","causal_attribution":"The shopper's own statements to the BBC and the Guardian. No independent assessment was inspected."}],"effects":[{"label":"Told to leave a store in front of others as a shoplifter after being flagged on the Facewatch system, which Facewatch says should not have held a record for the shopper. Reported feeling physically sick, helplessness and ongoing unease about cameras.","claim_id":"c6","direction":"negative"}],"sources":[{"id":"s1","url":"https://www.bbc.com/news/articles/cn0e56wjz6wo","kind":"news","access":"read","language":"en","translation_note":"","independence_group":"shopper-account-and-facewatch-statements-home-bargains"},{"id":"s2","url":"https://www.theguardian.com/technology/2026/may/03/guilty-until-proven-innocent-shoppers-falsely-identified-by-facial-recognition-struggle-to-clear-their-name","kind":"news","access":"read","language":"en","translation_note":"","independence_group":"shopper-account-and-facewatch-statements-home-bargains"},{"id":"s3","url":"https://www.gbnews.com/news/pensioner-kicked-out-home-bargains-facial-recognition-mistake-chester-news","kind":"news","access":"read","language":"en","translation_note":"Rewrite of the BBC account with a separate Facewatch statement to GB News.","independence_group":"shopper-account-and-facewatch-statements-home-bargains"}],"version":1,"ai_roles":["institutional_use"],"contexts":["everyday_life"],"unknowns":["The visit is recorded at year precision. The Guardian says one February lunchtime with no year, and the year is inferred from the BBC (22 February 2026) and GB News (23 February 2026) reports. The Guardian gives February for another shopper where PA gives 27 January, so its month wording may be approximate.","Whether the error lay in the watchlist entry, the face match or the in-store handling is not established. Facewatch attributes it to human error in store processes and also says the shopper should not have been on its system.","The earlier shoplifting incident to which the shopper was incorrectly linked is not described in the inspected sources.","Home Bargains declined to comment, so no retailer account was inspected. The outcome of its full review is not published.","Whether the shopper's request to see CCTV footage from Home Bargains and the police was met is not reported.","The Guardian account of the apology, voucher and confidentiality condition has no second chain.","All inspected sources trace to the shopper's interviews and Facewatch statements, so no claim is corroborated."],"geography":{"basis":"The BBC places the store in Chester under its North West and Cheshire coverage and quotes a spokesperson for the UK Department for Science, Innovation and Technology. The BBC describes the shopper as of Chester.","court_countries":[],"event_countries":["GB"],"affected_person_countries":["GB"]},"publication":{"basis":"Published under the 2026-09-15 charter as an ordinary adverse experience with an automated system. The BBC, Guardian and GB News reports were read in full from saved bodies and treated as one reporting chain (the shopper's interviews plus Facewatch statements). Claims stay at reported status and company statements are attributed. The shopper spoke publicly under their own name and is not named in this record.","reviewed_on":"2026-09-29"},"ai_involvement":{"basis":"Staff told the shopper that the shopper had come up on the store's Facewatch system as a shoplifter, and Facewatch sent the shopper a photo with a written theft allegation. Facewatch said the shopper should not have been on its system and removed the record. Facewatch's chief executive attributes the cases in the Guardian article to human error in store processes. The inspected sources do not show whether the fault lay in how the shopper was added to the watchlist, in a face match or in the in-store handling.","status":"reported"},"person_relations":["made_claim_about"]},"name":"Chester: shopper told to leave a Home Bargains store as a shoplifter after being flagged on the Facewatch system, which Facewatch later said should not have held a record for the shopper","summary":"A 67-year-old shopper told the BBC and the Guardian that staff at a Home Bargains store in Chester told the shopper to leave in front of other people because the shopper had come up on the store's Facewatch system as a shoplifter. Facewatch later sent the shopper a photo with words saying items had been put into a bag and stolen. Facewatch said the shopper should not have been on its system and that the image and associated record were permanently removed. The Guardian reports that a subject access request showed the shopper had been incorrectly associated with a shoplifting incident on an earlier visit, and that Facewatch's chief executive attributed the three cases in the article, which include this shopper's, to human error in store processes. Home Bargains declined to comment. The shopper reports feeling physically sick and helpless. The Guardian reports that Home Bargains later offered an apology and a 100 pound voucher on condition of confidentiality, which the shopper declined. The year of the visit is inferred to be 2026 from the BBC report of 22 February 2026.","incidentDate":"2026-01-01","incidentKind":"single_event","incidentDatePrecision":"year","exposurePattern":"single_interaction","reportedDate":"2026-02-22","aiSystem":"Facewatch facial recognition watchlist alerts (deployed by Home Bargains)","aiProduct":"Facewatch facial recognition","aiCompany":"Facewatch","severity":"low","verificationStatus":"unverified","harmCategories":[],"harmOutcomes":["psychological_distress","reputational_harm"],"harmOutcomeSummary":"The BBC and the Guardian report the shopper describing feeling physically sick and helpless after being told to leave a store as a shoplifter in front of others, and lasting unease about being recorded. Facewatch said the shopper should not have been on its system.","frameworkFacets":[],"causationStatus":"disputed","participantUsersAffectedMin":0,"otherPeopleHarmedMin":1,"affectedCountStatus":"exact","affectedCountEvidence":"One shopper reported being told to leave and distressed. No other person is reported harmed in this account.","victimAgeRange":"adult","platformType":"other","primarySourceUrl":"https://www.bbc.com/news/articles/cn0e56wjz6wo","primarySourceLabel":"BBC News (22 Feb 2026): Chester man accused of being thief after Home Bargains face scan alert","firstPublishedAt":"2026-09-29T21:15:52.8187+00:00","updatedAt":"2026-09-30T01:17:31.23933+00:00","scopeVersion":"facts-v3","tags":["historical-2026"]},{"id":"2026-christi-hill-grok-false-officer-identification","caseFacts":{"claims":[{"id":"c1","status":"corroborated","evidence":[{"locator":"'Grok has falsely named Hill and the other officer as the \"primary officers shown\" in the bodycam footage released by Hampshire police'; caption: 'Screengrab of a post by Grok referencing Christy Hill being incorrectly named'.","relation":"supports","source_id":"s1"},{"locator":"'she was wrongly identified by social media users and artificial intelligence (AI) chatbot Grok'; Hill 'criticised Grok ... for the \"chaos\" it caused by misidentifying her'.","relation":"supports","source_id":"s2"}],"assertion":"Grok falsely named Hill and another officer as the 'primary officers shown' in the bodycam footage of Nowak's arrest; the Guardian carries a screengrab of a Grok post incorrectly naming her.","causal_attribution":"The Guardian documents the Grok post with a screengrab; BBC Verify's interview independently carries her account of the Grok misidentification. What Grok answered to particular queries beyond the screengrabbed post is not documented."},{"id":"c2","status":"corroborated","evidence":[{"locator":"'Hill served as an officer in Portsmouth for 12 years before leaving the force in April 2024 – 20 months before the murder took place'; her statement: 'a national police bravery award media release... is being repeatedly shared and misattributed to this case'.","relation":"supports","source_id":"s1"},{"locator":"'Hill said she left Hampshire Constabulary in April 2024 - more than a year before Nowak was fatally stabbed in December 2025'.","relation":"supports","source_id":"s2"}],"assertion":"The identification is factually impossible: Hill left Hampshire Constabulary in April 2024, more than a year before the December 2025 murder; the confusion stems from a national police bravery award photo of her and a former colleague being misattributed.","causal_attribution":"Her account, uncontested in the inspected sources; the bravery-award photo mechanism is her explanation, attributed."},{"id":"c3","status":"corroborated","evidence":[{"locator":"'forced to flee to a safe space'; Hampshire: 'A police officer unrelated to this case has been misidentified online and subject to death threats.'","relation":"supports","source_id":"s1"},{"locator":"'scared for her safety and has been hiding in a safe house'; 'leading to \"threats of violence\"'; video caption: \"received 'endless threats'\".","relation":"supports","source_id":"s2"}],"assertion":"After the false posts, Hill received 'endless threats' and 'threats of violence' and is hiding in a safe house; Hampshire confirmed an unrelated officer was misidentified online and subjected to death threats.","causal_attribution":"Her account to two independent outlets plus the constabulary's own confirmation."},{"id":"c4","status":"corroborated","evidence":[{"locator":"'The home secretary, Shabana Mahmood, said on Tuesday that a male officer had been misidentified and that he had had to move out of his home.'","relation":"supports","source_id":"s1"},{"locator":"'BBC Verify has also obtained evidence that current police officer Tristan Parsons, who was also wrongly accused online of being involved, was not in the country at the time of Nowak's murder.'","relation":"supports","source_id":"s2"}],"assertion":"A second officer was wrongly accused in the same wave: the Home Secretary said a male officer had been misidentified and had to move out of his home; BBC Verify obtained evidence that serving officer Tristan Parsons was not in the country at the time of the murder.","causal_attribution":"The Home Secretary's account covers the displacement; BBC Verify's evidence covers Parsons's non-involvement. Whether Mahmood meant Parsons specifically is not stated; the two accounts are recorded separately."},{"id":"c5","status":"reported","evidence":[{"locator":"'Musk... posting on his X platform during the trial that he would fund a private prosecution of the officers involved.'","relation":"supports","source_id":"s1"},{"locator":"Starmer passage: 'Musk, again, has been interfering in our politics in the last few days, trying to whip up division'.","relation":"supports","source_id":"s2"}],"assertion":"Elon Musk posted during the trial that he would fund a private prosecution of the officers involved; Prime Minister Keir Starmer accused Musk of trying to 'whip up division' over the case.","causal_attribution":"Context for the amplification climate; not itself an AI claim."}],"effects":[{"label":"false AI identification of a former officer in a charged murder case; threats drove her into hiding","claim_id":"c3","direction":"negative"}],"sources":[{"id":"s1","url":"https://www.theguardian.com/uk-news/2026/jun/03/former-officer-hampshire-hiding-after-being-falsely-linked-henry-nowak-arrest","kind":"news_report","access":"read","language":"en","translation_note":"Read in English on 2026-09-15 (datePublished 2026-06-03T16:28Z). Includes Hill's statement, the Grok screengrab reference, the Hampshire statement and the Home Secretary's account.","independence_group":"guardian"},{"id":"s2","url":"https://www.bbc.com/news/articles/cg7pl7zj024o","kind":"news_report","access":"read","language":"en","translation_note":"Read in English on 2026-09-15 (datePublished 2026-06-04T15:50Z; BBC Verify, Devlin & Nguyen, with André Rhoden-Paul).","independence_group":"bbc"}],"version":1,"ai_roles":["unknown"],"contexts":["justice","everyday_life"],"unknowns":["What Grok answered in sessions other than the screengrabbed post, and whether xAI corrected or constrained the false identification, is not reported.","The date the false posts began (during the trial) is not precisely stated; Hill first saw them around 03:00 BST on 2 June 2026.","Whether any platform removed the misidentifying content is not reported.","The jury inquest into Nowak's death is expected next year; its findings are pending and concern the police response, not the misidentification."],"geography":{"basis":"Event: the online spread about the Hampshire (Southampton) case and Hill's concealment in the UK. Affected persons: both officers are UK-based (Parsons was abroad at the time of the murder, not at the time of the misidentification). Court country: the Digwa murder trial and the expected inquest are in England; no proceeding by or against the misidentified officers is reported.","court_countries":["GB"],"event_countries":["GB"],"affected_person_countries":["GB"]},"publication":{"basis":"Published under the 2026-09-15 charter as a consequential false claim about identified people (made_claim_about): two officers wrongly named by AI platforms in a charged case, documented by two independent chains including the outlet's screengrab evidence and the constabulary's confirmation. Hill spoke publicly; Parsons is named by BBC Verify in a vindicating context. The Nowak case background is limited to what the claims require.","reviewed_on":"2026-09-15"},"ai_involvement":{"basis":"The Guardian carries a screengrab of a Grok post incorrectly naming Hill and reports in its own voice that Grok falsely named her and the other officer as the 'primary officers shown'; Hill's own statement names 'AI platforms such as Grok'; BBC Verify's interview confirms the Grok misidentification. xAI was approached for comment by both outlets.","status":"supported"},"person_relations":["made_claim_about"]},"name":"Grok falsely named former officer Christi Hill as an arresting officer in the Henry Nowak case; she is in hiding after threats","summary":"In early June 2026, social media posts and the AI chatbot Grok falsely identified former Hampshire police constable Christi Hill as one of the 'primary officers shown' in bodycam footage of the December 2025 arrest of Henry Nowak, who died after being stabbed. Hill had left the force in April 2024 — more than a year before the murder — and says the misidentification stems from a national police bravery award photo being misattributed. After 'endless threats' and 'threats of violence' she is hiding in a safe house. BBC Verify separately obtained evidence that serving officer Tristan Parsons, also wrongly accused online, was not in the country at the time; the Home Secretary said a misidentified male officer had to move out of his home. Hampshire Constabulary confirmed an unrelated officer was misidentified and received death threats.","incidentDate":"2026-06-02","incidentEndDate":"2026-06-04","incidentKind":"bounded_series","incidentDatePrecision":"range","exposurePattern":"repeated_interactions","reportedDate":"2026-06-03","aiSystem":"Grok (and other AI platforms, unnamed)","aiProduct":"Grok","aiCompany":"xAI","severity":"high","verificationStatus":"credible","harmCategories":[],"harmOutcomes":["psychological_distress","reputational_harm","loss_of_autonomy"],"harmOutcomeSummary":"A factually impossible identification by AI platforms including Grok put a former officer into hiding after death threats; a serving officer wrongly accused in the same wave had to move out of his home, per the Home Secretary.","frameworkFacets":[],"causationStatus":"supported","participantUsersAffectedMin":0,"otherPeopleHarmedMin":2,"affectedCountStatus":"exact","affectedCountEvidence":"Two documented harmed people: Hill (Guardian interview and statement; BBC Verify interview) and the male officer identified by BBC Verify as Tristan Parsons (BBC's evidence he was abroad; the Home Secretary's account that a male officer had to move home). No further misidentified officers are reported in the inspected sources.","victimAgeRange":"adult","jurisdiction":"GB","platformType":"chatbot","outcomeType":"media_coverage","outcomeStatus":"ongoing","primarySourceUrl":"https://www.theguardian.com/uk-news/2026/jun/03/former-officer-hampshire-hiding-after-being-falsely-linked-henry-nowak-arrest","primarySourceLabel":"The Guardian (3 Jun 2026) — Hill's statement, the Grok screengrab, Hampshire and Mahmood accounts","firstPublishedAt":"2026-09-15T09:25:27.124866+00:00","updatedAt":"2026-09-30T01:17:32.056946+00:00","scopeVersion":"facts-v3","tags":["made-claim-about","false-identification","grok","police","threats","uk"]}]}