{"meta":{"exportedAt":"2026-10-06T07:44:16.857Z","formatVersion":2,"selection":{"q":"family","system":"","harm":"","context":"","country":"","role":"","relation":"contextual","evidence":"","year":"2026","response":"","severity":"","verification":"","view":"incidents","sort":"added"},"totalIncidents":3,"coverage":{"cases":3,"countries":1,"languages":2,"unknownLocation":1,"locationPending":0,"unknownLanguage":0,"unknownDate":0,"lawsuits":0,"regulatory":0,"minors":1,"coreRelations":1,"contextualRelations":3,"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-x-grok-reportedly-disclosed-adult-performer-legal-name-and-birthdate-in-reply-to-user","caseFacts":{"claims":[{"id":"c1","status":"reported","evidence":[{"locator":"Porn performer Siri Dahl’s personal information, including her full legal name and birthday, was publicly exposed earlier this month by xAI’s Grok chatbot.","relation":"supports","source_id":"s1"},{"locator":"so someone on X replied, “Who is she? What is her name?” and tagged @grok to get an answer.","relation":"supports","source_id":"s1"},{"locator":"Grok provided her personal information unprompted; the user likely only wanted information on what performer appeared in the clip.","relation":"supports","source_id":"s1"},{"locator":"revealing her legal name and birth date to users","relation":"supports","source_id":"s2"},{"locator":"Since grok doxxed me in early Feb, AI scrapers have reproduced my legal name on hundreds more websites","relation":"supports","source_id":"s3"},{"locator":"I asked 404 to publish my legal name in this article.","relation":"supports","source_id":"s3"}],"assertion":"In early 2026 (early February according to 404 Media and the performer, possibly earlier according to Stern), in reply to an X user who asked who the performer in a clip was and what her name was and tagged Grok, Grok answered with the performer's stage name together with her birthdate and legal name. 404 Media describes the personal details as unprompted and says the user likely wanted only to know which performer appeared in the clip.","causal_attribution":"The 404 Media article shows a screenshot of the X reply that was not inspected as an image. Mashable relays 404 Media. The affected person's own post gives the same account and dates the reply to early February. Grok's own reply text is not quoted here because it contains the personal details."},{"id":"c2","status":"reported","evidence":[{"locator":"Almost instantly, harassers started opening Facebook accounts in her name and posting stolen porn clips with her real name on sites for leaking OnlyFans content.","relation":"supports","source_id":"s1"},{"locator":"There are a ton of Facebook accounts that come up that are pretending to be me, using my real name,","relation":"supports","source_id":"s1"},{"locator":"There are now porn leak sites that are posting porn of me using only my legal name, not even putting my stage name on it.","relation":"supports","source_id":"s1"},{"locator":"Users are now asking Grok for the make and model of Dahl’s car, her address, and other dangerous personal information.","relation":"supports","source_id":"s1"},{"locator":"Now, Dahl is having to call her family and put defensive plans in place.","relation":"supports","source_id":"s1"},{"locator":"AI scrapers have reproduced my legal name on hundreds more websites, many of which have wildly inaccurate claims","relation":"supports","source_id":"s3"}],"assertion":"After the disclosure the performer reports that impersonating Facebook accounts using her legal name appeared, that stolen clips of her were posted under her legal name on leak sites, and that her legal name was reproduced on hundreds of other websites, some with inaccurate claims about her. 404 Media reports that users asked Grok for the make and model of her car and her address without an accurate reply, and that she is calling family members to put defensive plans in place.","causal_attribution":"The Facebook accounts, leak-site posts and the family measures are the performer's statements as quoted by 404 Media and in her own post. The queries to Grok about her car and address are stated in 404 Media's own voice. The impersonating accounts, leak-site posts and Grok queries were not inspected. The timing (\"almost instantly\") is 404 Media's wording. No physical harm or threat is reported."},{"id":"c3","status":"reported","evidence":[{"locator":"Dahl has used the name ... since the beginning of her career in the adult industry in 2012.","relation":"supports","source_id":"s1"},{"locator":"information she'd protected until now.","relation":"supports","source_id":"s1"},{"locator":"I've been paying for data removal services for like, at least six years now","relation":"supports","source_id":"s1"}],"assertion":"The performer had used her stage name since 2012 and had paid for data removal services for at least six years to keep her legal name private.","causal_attribution":"The performer's own account as reported by 404 Media. Her data removal spending was not documented."},{"id":"c4","status":"disputed","evidence":[{"locator":"It stated that Dahl's legal name and birthdate are already public on the internet, which Dahl denied.","relation":"supports","source_id":"s2"},{"locator":"been getting a lot of replies and reposts from people on here and twitter saying \"your name was on a random facebook page since september!\"","relation":"supports","source_id":"s4"},{"locator":"and my *real* name was NEVER published on any verifiable source associated with my stage name.","relation":"contradicts","source_id":"s5"},{"locator":"\"My legal name only became public after you doxxed me, and now thanks to you it's been proliferated all over the internet by other AI scrapers","relation":"contradicts","source_id":"s2"},{"locator":"Dahl said she doesn’t know where Grok originally got her legal name from.","relation":"context","source_id":"s1"},{"locator":"Bei Googles KI-Zusammenfassungen wird der Name als nicht bekannt angegeben.","relation":"context","source_id":"s6"}],"assertion":"Whether the legal name was already publicly available before Grok's reply is disputed. Grok's reply to the performer said the details were already public, and people told her a Facebook page carried the name since September. The performer denies it and says the name was never published on a verifiable source tied to her stage name. Stern reports that Google's AI summaries list the name as unknown and that ChatGPT, Claude and Gemini each say they would not release it.","causal_attribution":"The pre-existing availability of the name was not established either way. The Facebook page and any earlier X post were not inspected. The September date comes from replies the performer relays, and the year is not stated."}],"effects":[{"label":"Legal name and birthdate of an adult performer disclosed by Grok on X, followed by reported impersonation accounts, leak-site posts under the legal name and defensive plans she is putting in place with family","claim_id":"c2","direction":"negative"}],"sources":[{"id":"s1","url":"https://www.404media.co/grok-doxing-real-names-birthdates-siri-dahl/","kind":"news_report","access":"read","language":"en","translation_note":"","independence_group":"404-media"},{"id":"s2","url":"https://mashable.com/article/siri-dahl-doxxed-by-grok","kind":"news_report","access":"read","language":"en","translation_note":"","independence_group":"404-media"},{"id":"s3","url":"https://bsky.app/profile/siridahl.com/post/3mfa5dt66qs2h","kind":"social_post","access":"read","language":"en","translation_note":"","independence_group":"affected-person-posts"},{"id":"s4","url":"https://bsky.app/profile/siridahl.com/post/3mfio2pwq5c2l","kind":"social_post","access":"read","language":"en","translation_note":"","independence_group":"affected-person-posts"},{"id":"s5","url":"https://bsky.app/profile/siridahl.com/post/3mfip3jssec2y","kind":"social_post","access":"read","language":"en","translation_note":"","independence_group":"affected-person-posts"},{"id":"s6","url":"https://www.stern.de/digital/online/pornostar-hielt-ihren-namen-geheim---dann-plauderte-musks-ki-ihn-aus-37169054.html","kind":"news_report","access":"read","language":"de","translation_note":"German-language article read from an Internet Archive capture of 3 March 2026 (the direct request returned HTTP 403) and cited in English paraphrase. The quoted German passages are verbatim. No human translator checked the paraphrase.","independence_group":"stern"}],"version":1,"ai_roles":["others_use"],"contexts":["privacy","everyday_life"],"unknowns":["The date of Grok's reply within January and February 2026 is not fixed. 404 Media and the performer's 19 February post say early February, while a 23 February post refers to 'before Jan 20th' and stern.de says she found the reply weeks after it appeared.","The 404 Media page returned only its opening paragraphs to a direct request. The full text was read from an Internet Archive capture dated 19 February 2026, which may differ from later edits.","The original Grok reply, the screenshots, the impersonating Facebook accounts, the leak-site posts and the queries about her car and address were not inspected. The performer's Bluesky posts were read as text records, and her X posts only as quoted by Mashable.","Where Grok obtained the legal name is unknown. The performer says she does not know and wonders whether identity documents submitted to X for impersonation reports were the source, and no source read confirms or rules that out.","Whether the name was already published before the reply is disputed (claim c4). The earlier Facebook page and X post that people cited to her were not located or inspected.","No statement from xAI or X about the disclosure was found. 404 Media reports that X did not respond and Mashable reports that it asked the performer's representatives and xAI for comment.","The extent of the harassment beyond the performer's own statements, and whether the reported family measures were carried out, is not documented."],"geography":{"basis":"The inspected sources do not state where the performer lives or where the disclosure and harassment occurred. The disclosure happened on X, which is international. Grok's quoted description of the performer's nationality is not used as a location.","court_countries":[],"event_countries":[],"affected_person_countries":[]},"publication":{"basis":"The 404 Media article (full text via an archive capture), the Mashable article, three of the performer's Bluesky posts and the stern.de article were read. Mashable and stern.de relay 404 Media, and 404 Media and the performer's posts rest on her account, so the claims are reported and the prior-availability question is left disputed. The performer spoke publicly under her stage name, quoted by two outlets and in her own posts, and asked 404 Media to publish her legal name. The record names her and omits her legal name, birthdate and the pages that carry them.","reviewed_on":"2026-09-29"},"ai_involvement":{"basis":"404 Media reports that Grok's reply on X to a user's question gave the performer's legal name and birthdate, and shows a screenshot that was not inspected as an image. Mashable quotes a further Grok reply to the performer on X (\"I'm sorry you're upset.\") that said the details were already public. Grok's source for the name is unknown. The performer suggests it may have come from identity documents X held, and stern.de says Grok denied having such access. No xAI statement was found.","status":"reported"},"person_relations":["made_claim_about","communicated_with"]},"name":"Grok reportedly disclosed an adult performer's legal name and birthdate in an X reply, followed by reported impersonation accounts and leak-site posts under the legal name","summary":"In early 2026 (404 Media and the performer's 19 February post say early February, while Stern reports she found the reply weeks after it appeared) an X user replied to a clip of adult performer Siri Dahl, asking who the performer was and what her name was, and tagged Grok. According to 404 Media, Grok answered with her stage name, her birthdate and her legal name, and the user likely wanted only to know which performer appeared in the clip. Dahl has used the stage name since 2012 according to 404 Media, and she says she had paid for data removal services for at least six years to keep the legal name private. She reports that impersonating Facebook accounts and leak-site posts under the legal name then appeared and that the name spread across hundreds of websites. 404 Media reports that users asked Grok for the make and model of her car and her address without an accurate reply, and that she is calling family members to put defensive plans in place. Grok's reply to her protest said the details were already public, which she denies. Where Grok obtained the name is unknown. Dahl spoke publicly about the event and asked 404 Media to publish her legal name. This record omits the legal name and birthdate.","incidentDate":"2026-01-01","incidentKind":"single_event","incidentDatePrecision":"year","exposurePattern":"unknown","reportedDate":"2026-02-19","aiSystem":"Grok (xAI chatbot on X)","aiProduct":"Grok","aiCompany":"xAI","severity":"medium","verificationStatus":"unverified","harmCategories":[],"harmOutcomes":["other_material_harm","exploitation_or_abuse"],"harmOutcomeSummary":"The performer told 404 Media and said in her own posts that after Grok's reply gave her legal name and birthdate, impersonating Facebook accounts and leak-site posts under the legal name appeared and her legal name was reproduced on hundreds of websites (some with inaccurate claims). 404 Media reports that users asked Grok for her car details and address without an accurate reply and that she is calling family members to put defensive plans in place. She says she had spent years and thousands of dollars on data removal services to keep the name private. No physical harm or threat is reported.","frameworkFacets":[],"causationStatus":"alleged","participantUsersAffectedMin":0,"otherPeopleHarmedMin":1,"affectedCountStatus":"exact","affectedCountEvidence":"One performer who spoke publicly about the disclosure is reported harmed. Family members are mentioned as people she is warning and are not reported harmed, and the X user who asked Grok is not counted.","victimAgeRange":"adult","platformType":"chatbot","primarySourceUrl":"https://www.404media.co/grok-doxing-real-names-birthdates-siri-dahl/","primarySourceLabel":"404 Media: 'Grok Exposed a Porn Performer's Legal Name and Birthdate' (19 Feb 2026)","firstPublishedAt":"2026-09-29T21:16:30.069014+00:00","updatedAt":"2026-09-30T01:17:59.169171+00:00","scopeVersion":"facts-v3","tags":["historical-2026"]},{"id":"2026-us-meta-26-employees-sue-alleging-ai-assisted-may-layoff-selection-penalized-protected-leave","caseFacts":{"claims":[{"id":"c1","status":"documented","evidence":[{"locator":"OAKLAND DIVISION","relation":"supports","source_id":"s1"},{"locator":"Filed 07/13/26","relation":"supports","source_id":"s1"},{"locator":"Plaintiffs initiated this lawsuit on July 13, 2026, bringing claims against Meta","relation":"supports","source_id":"s2"},{"locator":"A group of 26 Meta employees has sued the company, claiming it used artificial intelligence systems to select people for layoffs, disproportionately targeting those on medical, parental or family leave.","relation":"supports","source_id":"s6"}],"assertion":"On 13 July 2026 twenty-six anonymous plaintiffs (Does 1 through 26) filed a complaint against Meta Platforms, Inc. in the US District Court for the Northern District of California, Oakland division, alleging employment discrimination in the May 2026 reduction in force.","causal_attribution":"The filing of the complaint is documented by the court record. The complaint establishes only the plaintiffs’ allegations."},{"id":"c2","status":"reported","evidence":[{"locator":"activity-monitoring data, AI-token-usage dashboards, and algorithmically assisted","relation":"supports","source_id":"s1"},{"locator":"artificial-intelligence-assisted systems to score, rank, and select employees for inclusion","relation":"supports","source_id":"s1"},{"locator":"algorithmic productivity scoring drawn from keystroke, screen-content, mouse,","relation":"supports","source_id":"s1"},{"locator":"The parties dispute whether Meta utilized AI in deciding to terminate plaintiffs’","relation":"supports","source_id":"s2"},{"locator":"They claim that Meta used a number of internal AI-assisted systems to score and rank employees on a termination list.","relation":"supports","source_id":"s7"}],"assertion":"The complaint alleges, on information and belief, that Meta used a set of internal AI-assisted systems to score, rank and select employees for the termination list: the Metamate internal large-language-model assistant, employee-trained \"second brain\" agents, keystroke and other activity-monitoring data, AI-token-usage dashboards, and algorithmically assisted performance ranking and calibration.","causal_attribution":"These are the plaintiffs’ allegations, pleaded on information and belief and supported by plaintiff declarations that were not inspected (they are quoted in the complaint and the order). Meta disputes them (claim c4). The news reports and the court order restate the complaint and are one reporting chain with it."},{"id":"c3","status":"reported","evidence":[{"locator":"be accumulated by an employee who is on protected medical or family leave, or whose","relation":"supports","source_id":"s1"},{"locator":"protected-leave-takers or accommodation-seekers for individualized human review. Meta","relation":"supports","source_id":"s1"},{"locator":"On information and belief, Meta did not neutralize any of the foregoing inputs for","relation":"supports","source_id":"s1"},{"locator":"result was that employees who took protected leaves were disproportionately selected for","relation":"supports","source_id":"s1"},{"locator":"Plaintiffs are twenty-six current and former Meta employees, each of whom Meta","relation":"supports","source_id":"s1"},{"locator":"selected for separation in the RIF, and each of whom","relation":"supports","source_id":"s1"},{"locator":"About half the plaintiffs had taken leave for caregiving or pregnancy-related reasons.","relation":"supports","source_id":"s6"}],"assertion":"The complaint alleges that the inputs to these systems cannot be accumulated by an employee on protected medical, family or parental leave, that Meta did not neutralise them for protected leave, and that employees who took protected leave were therefore disproportionately selected for layoff. It states that each plaintiff was selected for separation in the reduction in force and had, within the 24 months before it, taken, requested or been approved for protected leave, or requested or received a disability accommodation.","causal_attribution":"Allegation of the plaintiffs. The court found on 17 July 2026 only serious questions going to the merits and no likelihood of success on that record (claim c5). Whether any AI system affected any plaintiff’s selection is unresolved."},{"id":"c4","status":"reported","evidence":[{"locator":"Workforce management and organizational decisions were and are made by people, not AI.","relation":"supports","source_id":"s6"},{"locator":"selection decisions in the RIF were “made by human","relation":"supports","source_id":"s2"},{"locator":"promotion history over a defined period. There was no AI-","relation":"supports","source_id":"s2"},{"locator":"was selected based on leave status, disability, or any other protected characteristic,","relation":"supports","source_id":"s2"},{"locator":"“selection decision [was] made by ‘AI.’” Id. ¶ 11.","relation":"supports","source_id":"s2"},{"locator":"Selection decisions were made by human business leaders","relation":"supports","source_id":"s9"},{"locator":"defined period. There was no AI-assisted “scoring” or “ranking” related to employee","relation":"supports","source_id":"s9"},{"locator":"guidance does not permit AI adoption and usage metrics to be used as negative factors in","relation":"supports","source_id":"s3"},{"locator":"performance reviews in 2025 or as selection criteria in the RIF.","relation":"supports","source_id":"s3"}],"assertion":"Meta denies the allegations. A Meta spokesperson said workforce management and organisational decisions were made by people, not AI. In declarations filed by a Meta human-resources director, Meta states that selection decisions were made by human business leaders using documented neutral criteria, that no AI-assisted scoring or ranking of employee performance was used, that no plaintiff was selected on the basis of leave status or disability, and that no selection decision was made by AI.","causal_attribution":"Meta’s statements and declarations about its own process. They are a party account and had been tested only through briefing and court hearings (claims c5 and c7), not in discovery."},{"id":"c5","status":"documented","evidence":[{"locator":"described below, the TRO is DENIED.","relation":"supports","source_id":"s2"},{"locator":"The parties dispute whether Meta utilized AI in deciding to terminate plaintiffs’","relation":"supports","source_id":"s2"},{"locator":"plaintiffs have not shown a likelihood of success on the merits, but rather a “serious question[]”","relation":"supports","source_id":"s2"},{"locator":"Loss of health care, employment, protected leave, and unvested restricted stock units (“RSUs”) are","relation":"supports","source_id":"s2"},{"locator":"Loss of immigration status is different. Four of the plaintiffs have employment-based,","relation":"supports","source_id":"s2"},{"locator":"they were not in the rooms where it happened.","relation":"supports","source_id":"s2"}],"assertion":"On 17 July 2026 the court denied the plaintiffs’ motion for a temporary restraining order. The order records that the parties dispute whether Meta used AI in deciding to terminate the plaintiffs, finds serious questions going to the merits but no shown likelihood of success on that record, finds that loss of health care, employment, protected leave and unvested equity can be remedied in arbitration, and treats the possible loss of immigration status for four plaintiffs with Meta-sponsored visas as a potentially irreparable harm that needed more information.","causal_attribution":"A court order establishes what the court ruled and recorded. It does not establish that AI was or was not used in the selection."},{"id":"c6","status":"reported","evidence":[{"locator":"On May 20, 2026, Meta began notifying the selected employees by email, beginning with","relation":"supports","source_id":"s1"},{"locator":"finalized on or about July 22, 2026 (and on or about August 20, 2026 for New York","relation":"supports","source_id":"s1"},{"locator":"laid off on May 20, 2026.” Complaint (“Compl.”) [Dkt. No. 1] ¶ 45 (the “mass reduction in force”","relation":"supports","source_id":"s2"},{"locator":"Though they have been notified of their layoffs, all 26 remain employed by Meta, with separations set to begin July 22.","relation":"supports","source_id":"s6"},{"locator":"Meta in May notified nearly 8,000 employees, or about 10% of its global workforce, that they were losing their jobs","relation":"supports","source_id":"s7"},{"locator":"Laid-off workers remain on the payroll but lost access to Meta systems on May 20","relation":"supports","source_id":"s7"}],"assertion":"Meta began notifying employees selected in the reduction in force on 20 May 2026 (about 8,000 employees, roughly 10 percent of its workforce). The complaint says the plaintiffs were notified of their selection from that date, and that separations were scheduled for about 22 July 2026 (later for some plaintiffs). Meta said in court filings that laid-off workers stayed on the payroll but lost access to Meta systems on 20 May.","causal_attribution":"The notification date and the scheduled separation dates come from the complaint and Meta court filings as relayed by Reuters. The sources inspected do not report whether each separation took place on its scheduled date, although Courthouse News called the plaintiffs former employees on 24 August 2026."},{"id":"c7","status":"reported","evidence":[{"locator":"Hearing on Motion for Preliminary Injunction conducted via videoconference. The Court","relation":"supports","source_id":"s5"},{"locator":"summarizes tentative. Argument of counsel heard. Motion taken under submission; written order","relation":"supports","source_id":"s5"},{"locator":"I have a record I have to deal with and the record at the moment does not persuade me of the merits","relation":"supports","source_id":"s8"},{"locator":"categorical denial of any impact of AI in the termination process","relation":"supports","source_id":"s8"},{"locator":"whether what plaintiffs think happened, happened","relation":"supports","source_id":"s8"}],"assertion":"The court held a hearing on the plaintiffs’ preliminary injunction motion on 24 August 2026, heard argument and took the motion under submission with a written order to follow. Courthouse News reports that the judge said the record at that time did not persuade the judge of the merits, that the plaintiffs’ evidence raised some potential questions about Meta’s categorical denial of any impact of AI in the termination process, and that the case turns on whether what plaintiffs think happened, happened.","causal_attribution":"The minute entry documents that the hearing occurred and the motion was taken under submission. The judge’s remarks are reported by one news outlet and the transcript was not inspected. No written ruling on the preliminary injunction was found as of 29 September 2026."},{"id":"c8","status":"documented","evidence":[{"locator":"and only Plaintiff Doe 20, hereby voluntarily dismisses","relation":"supports","source_id":"s10"},{"locator":"remain parties and continue to prosecute this action","relation":"supports","source_id":"s10"},{"locator":"Doe 20 was voluntarily dismissed from this action on August 3, 2026 pursuant to Federal","relation":"supports","source_id":"s4"},{"locator":"is made on behalf of Doe 20, and no relief is sought on Doe 20’s behalf.","relation":"supports","source_id":"s4"}],"assertion":"One plaintiff (Doe 20) voluntarily dismissed all of that plaintiff’s claims without prejudice on 3 August 2026 (Dkt. 33), and the notice states that Does 1 through 19 and 21 through 26 remain parties. No reason is given in the notice.","causal_attribution":"A filing by the plaintiffs’ counsel records the dismissal. It does not say whether that plaintiff was selected in the reduction in force or why the dismissal was made."},{"id":"c9","status":"reported","evidence":[{"locator":"They recognize that their claims must be arbitrated, and they have initiated arbitration proceedings","relation":"supports","source_id":"s2"},{"locator":"with the American Arbitration Association (AAA). Here, they seek a temporary restraining order:","relation":"supports","source_id":"s2"},{"locator":"while they pursue their claims in private arbitration","relation":"supports","source_id":"s7"},{"locator":"from this Court only the status-quo-preserving provisional relief that Meta’s own","relation":"supports","source_id":"s1"},{"locator":"G. Reserve to the arbitral forum all relief on the merits, including but not limited to","relation":"supports","source_id":"s1"}],"assertion":"The 17 July 2026 order records that the plaintiffs recognize their claims must be arbitrated and that they have initiated arbitration proceedings with the American Arbitration Association. The complaint says the plaintiffs seek from the court only status-quo-preserving provisional relief pending an independent audit of the selection process and arbitration of the merits, and it reserves merits relief such as reinstatement, back pay and damages to the arbitral forum.","causal_attribution":"The order records the plaintiffs’ own statement about their arbitration filings. The arbitration itself is confidential and its progress is unknown."}],"effects":[{"label":"Employees on or after protected leave allegedly disproportionately selected for layoff by an AI-assisted process that did not account for leave (disputed by Meta)","claim_id":"c3","direction":"negative"},{"label":"Plaintiffs notified of selection for termination on 20 May 2026, with separations scheduled from 22 July 2026 and possible loss of health coverage, unvested equity and (for four plaintiffs) work-visa status","claim_id":"c6","direction":"negative"}],"sources":[{"id":"s1","url":"https://storage.courtlistener.com/recap/gov.uscourts.cand.474171/gov.uscourts.cand.474171.1.0.pdf","kind":"court_filing","access":"read","language":"en","translation_note":"","independence_group":"meta-complaint"},{"id":"s2","url":"https://storage.courtlistener.com/recap/gov.uscourts.cand.474171/gov.uscourts.cand.474171.25.0.pdf","kind":"court_order","access":"read","language":"en","translation_note":"","independence_group":"ndcal-court-record"},{"id":"s3","url":"https://storage.courtlistener.com/recap/gov.uscourts.cand.474171/gov.uscourts.cand.474171.42.1_1.pdf","kind":"court_filing","access":"read","language":"en","translation_note":"","independence_group":"meta-court-declarations"},{"id":"s4","url":"https://storage.courtlistener.com/recap/gov.uscourts.cand.474171/gov.uscourts.cand.474171.46.0.pdf","kind":"court_filing","access":"read","language":"en","translation_note":"","independence_group":"ndcal-court-record"},{"id":"s5","url":"https://storage.courtlistener.com/recap/gov.uscourts.cand.474171/gov.uscourts.cand.474171.49.0.pdf","kind":"court_record","access":"read","language":"en","translation_note":"","independence_group":"ndcal-court-record"},{"id":"s6","url":"https://www.cbsnews.com/news/26-meta-workers-sue-ai-aided-layoffs-medical-family-leave/","kind":"wire_report","access":"read","language":"en","translation_note":"","independence_group":"meta-complaint"},{"id":"s7","url":"https://www.spokesman.com/stories/2026/jul/17/us-judge-wont-block-meta-from-laying-off-workers-w/","kind":"wire_report","access":"read","language":"en","translation_note":"","independence_group":"reuters-tro-coverage"},{"id":"s8","url":"https://www.courthousenews.com/meta-workers-claiming-ai-fired-them-unlikely-to-see-relief/","kind":"news_report","access":"read","language":"en","translation_note":"","independence_group":"courthouse-news-hearing"},{"id":"s9","url":"https://storage.courtlistener.com/recap/gov.uscourts.cand.474171/gov.uscourts.cand.474171.31.0.pdf","kind":"court_filing","access":"read","language":"en","translation_note":"","independence_group":"meta-court-declarations"},{"id":"s10","url":"https://storage.courtlistener.com/recap/gov.uscourts.cand.474171/gov.uscourts.cand.474171.33.0.pdf","kind":"court_filing","access":"read","language":"en","translation_note":"","independence_group":"ndcal-court-record"}],"version":1,"ai_roles":["institutional_use"],"contexts":["work","health"],"unknowns":["Whether any AI system scored, ranked or selected any plaintiff is unresolved. The complaint pleads it on information and belief. Meta denies it in declarations. No discovery had occurred in the sources inspected, and the judge said on 17 July 2026 that plaintiffs were not in the rooms where the selections happened.","The sources inspected do not show how many people beyond the plaintiffs were selected because of leave, or how many of the roughly 8,000 laid-off employees were scored by any AI-assisted system. Only the plaintiffs are counted as reported harmed.","The order on the preliminary injunction motion (argued 24 August 2026, taken under submission) had not been found by 29 September 2026. The hearing remarks were read only through one news report and the transcript was not inspected.","Whether each plaintiff’s separation took place on its scheduled date (22 July 2026 for most, later for some) is not stated in the sources inspected. Reuters and CBS/AP describe the plaintiffs as still employed in July, and Courthouse News called them former employees on 24 August 2026.","One plaintiff (Doe 20) was voluntarily dismissed on 3 August 2026 and no reason is stated. The affected count therefore uses 25.","The complaint and declarations contain individual medical, pregnancy and immigration details. They are anonymised in the public copies and are deliberately not described here.","Reuters and WSJ pages for the initial filing could not be read (HTTP 401). Reuters coverage of the 17 July ruling was read through a Spokesman-Review copy. The Law.com article was behind a subscription wall and was not cited.","The complaint alleges that data captured by a separate Meta employee-monitoring program (the Model Capability Initiative) supplied inputs to the selection process, and Meta denies that AI was used in the selection. That program’s own privacy and security consequences are a different event, recorded as 2026-meta-mci-us-employee-keystroke-and-screen-capture-for-ai-training-then-internal-data-exposure, and are not part of this record."],"geography":{"basis":"The complaint states that the plaintiffs worked in California, Illinois, Washington, New York, the District of Columbia, Pennsylvania and Florida and the suit is in the US District Court for the Northern District of California. Meta also notified employees in other countries in the same reduction in force, but no plaintiff outside the US is described.","court_countries":["US"],"event_countries":["US"],"affected_person_countries":["US"]},"publication":{"basis":"The complaint, the court order denying the temporary restraining order, two Meta declarations, the plaintiffs’ notice of dismissal of one plaintiff and the hearing minute entry were read from the court record (CourtListener copies), with CBS/AP, Reuters and Courthouse News reports. Every AI-related statement is attributed. The plaintiffs are anonymous in the record and are not described individually. Meta denies that AI made or informed any selection decision and the court has not resolved the dispute.","reviewed_on":"2026-09-29"},"ai_involvement":{"basis":"The complaint alleges, on information and belief, that Meta used internal AI-assisted systems (Metamate, second-brain agents, activity-monitoring scoring, AI-token-usage dashboards, algorithmic ranking and calibration) to score, rank and select employees for the 20 May 2026 termination list. Meta’s declarations say selection decisions were made by human business leaders and that there was no AI-assisted scoring or ranking related to employee performance, and the court described the declarations as saying Meta did not use AI in any way with respect to the RIF. The court recorded that the parties dispute whether Meta used AI in deciding to terminate the plaintiffs and found on 17 July 2026 that the plaintiffs had not shown a likelihood of success on the current record. On 24 August 2026 the judge said the plaintiffs’ evidence raised some potential questions about Meta’s categorical denial. No discovery had tested Meta’s account in the sources inspected.","status":"disputed"},"person_relations":["made_decision_about","made_claim_about"]},"name":"US: 26 Meta employees sue alleging an AI-assisted May 2026 layoff selection penalized workers on protected leave, Meta says people made the decisions","summary":"On 20 May 2026 Meta began notifying about 8,000 employees (roughly 10 percent of its workforce) that they had been selected for layoff. On 13 July 2026 twenty-six anonymous employees who had taken or requested medical, pregnancy, parental or family leave, or a disability accommodation, sued Meta in the US District Court for the Northern District of California. The complaint alleges, on information and belief, that Meta used internal AI-assisted systems (including the Metamate assistant, keystroke and activity monitoring, AI-token-usage dashboards and algorithmic performance ranking) to score, rank and select employees, and that these inputs could not accumulate during protected leave, so plaintiffs on leave were disproportionately selected. Meta says workforce decisions were made by people, not AI, and that no selection decision was made by AI. On 17 July 2026 the court denied a temporary restraining order, recording that the parties dispute whether Meta used AI in the terminations and finding serious questions on the merits but no shown likelihood of success. One plaintiff was voluntarily dismissed on 3 August 2026. The preliminary injunction motion was argued on 24 August 2026 and taken under submission. The plaintiffs are pursuing their merits claims in arbitration and the allegations are unproven.","incidentDate":"2026-05-20","incidentKind":"single_event","incidentDatePrecision":"day","exposurePattern":"unknown","reportedDate":"2026-07-14","aiSystem":"Meta internal AI-assisted systems alleged in the complaint: the Metamate internal LLM assistant, employee-trained \"second brain\" agents, keystroke and activity-monitoring productivity scoring, AI-token-usage dashboards and AI-assisted performance calibration (Meta denies AI was used in selecting employees for the layoff)","aiProduct":"Meta internal AI systems (reported)","aiCompany":"Meta Platforms, Inc.","severity":"medium","verificationStatus":"disputed","harmCategories":[],"harmOutcomes":["professional_harm"],"harmOutcomeSummary":"The complaint alleges that 26 employees were selected for termination in Meta’s May 2026 reduction in force through an AI-assisted process that penalised protected leave, with separations scheduled from 22 July 2026 and asserted losses of employer-subsidised health coverage, unvested equity and, for four plaintiffs, work-visa status. Meta denies that AI was used in the selections. The court found the alleged harms other than immigration status remediable in arbitration and has not decided the merits.","frameworkFacets":[],"causationStatus":"disputed","participantUsersAffectedMin":0,"otherPeopleHarmedMin":25,"affectedCountStatus":"documented_minimum","affectedCountEvidence":"The complaint states that each of 26 plaintiffs was selected for separation in the May 2026 reduction in force. One plaintiff was voluntarily dismissed on 3 August 2026 without a stated reason, so 25 active plaintiffs are counted as a documented minimum. The roughly 8,000 other employees notified in the reduction in force are not counted because no source ties their selection to the alleged AI process.","victimAgeRange":"adult","platformType":"other","primarySourceUrl":"https://storage.courtlistener.com/recap/gov.uscourts.cand.474171/gov.uscourts.cand.474171.1.0.pdf","primarySourceLabel":"Complaint, Does 1 through 26 v. Meta Platforms, Inc. (N.D. Cal., filed 13 Jul 2026)","firstPublishedAt":"2026-09-29T21:16:06.345461+00:00","updatedAt":"2026-09-30T01:17:57.733761+00:00","scopeVersion":"facts-v3","tags":["historical-2026"]},{"id":"2026-utah-meta-ai-suggested-prompts-children-profile","caseFacts":{"claims":[{"id":"c1","status":"corroborated","evidence":[{"locator":"'Meta AI posed a series of invasive prompts under the video, such as \"Who's the child passenger?\" and \"Where does Kalie Robins live?\"'; 'pulled information from her past posts ... including her location'; 'drew on other profiles, such as her mother's account'.","relation":"supports","source_id":"s1"},{"locator":"'Who's the child passenger?'; 'their names, birth information, pictures and videos of them'; 'It pieced together my information to show people where I live'.","relation":"supports","source_id":"s3"},{"locator":"'suggested questions aimed at uncovering information about her children — including their names, birthdates, videos, newborn photos, even photos that had been deleted — and, ultimately, her live location'.","relation":"supports","source_id":"s2"}],"assertion":"Meta AI suggested prompts under Robins's 1 September car video including 'Who's the child passenger?' and 'Where does Kalie Robins live?', and clicking them produced her daughters' names, birth details, photos and videos from her own and relatives' posts, and assembled her likely location.","causal_attribution":"Robins's account given in separate interviews to CNET, NewsNation and Futurism; Meta does not dispute that the prompts were generated."},{"id":"c2","status":"corroborated","evidence":[{"locator":"'A Meta spokesperson told CNET in an email that it \"fixed\" the issue and that Meta AI will no longer suggest inappropriate, personal questions on users' posts'.","relation":"supports","source_id":"s1"},{"locator":"'\"While the content was available to this user, these prompts should never have been generated,\" Meta spokesperson Dina El-Kassaby said, according to The Verge'.","relation":"supports","source_id":"s4"},{"locator":"'its AI search feature \"missed the mark\"'; '\"fixed that issue\"'.","relation":"supports","source_id":"s3"}],"assertion":"Meta said the prompts 'missed the mark' and 'should never have been generated', that responses draw only on information the user can already access, and that it fixed the issue so Meta AI no longer suggests personal questions about people in posts.","causal_attribution":"Meta statements to three outlets."},{"id":"c3","status":"disputed","evidence":[{"locator":"'Meta also denied Robins' claim that its AI accessed a photo deleted years ago. Instead, Meta told CNET that the photo of Robins' kids was deleted right before the video was made and that a temporary bug briefly kept it visible. Robins disputed this'.","relation":"supports","source_id":"s1"}],"assertion":"Robins says one surfaced photo had been deleted years earlier; Meta says the photo was deleted shortly before the video and remained briefly visible because of a temporary bug.","causal_attribution":"Competing accounts from Robins and Meta reported by CNET."}],"effects":[{"label":"Meta AI prompts compiled a mother's young daughters' names, birth details and photos and her likely location; the mother reported distress and lost trust; Meta changed the feature","claim_id":"c1","direction":"negative"}],"sources":[{"id":"s1","url":"https://www.cnet.com/tech/services-and-software/meta-ai-viral-video-personal-prompts-about-kids/","kind":"news_report","access":"read","language":"en","translation_note":"Read in English on 2026-09-18 (CNET, 12 Sep 2026). Direct interview with Robins plus Meta's emailed statement to CNET and its dispute of the deleted-photo detail.","independence_group":"cnet"},{"id":"s2","url":"https://www.newsnationnow.com/business/tech/ai/mom-meta-ai-analyzing-posts-about-kids/","kind":"news_report","access":"read","language":"en","translation_note":"Read in English on 2026-09-18 via the MSN content API copy (NewsNation, 17 Sep 2026; the newsnationnow.com host returns 403 to this box). Interview with Robins including the distress quotation.","independence_group":"newsnation"},{"id":"s3","url":"https://torontosun.com/news/world/utah-mom-sounds-alarm-after-meta-ai-digs-up-details-about-her-children-im-done","kind":"news_report","access":"read","language":"en","translation_note":"Read in English on 2026-09-18 via the MSN content API copy (Toronto Sun, 15 Sep 2026). Relays Futurism's interview and Meta's statement to Futurism; treated as the Futurism chain.","independence_group":"futurism"},{"id":"s4","url":"https://www.dexerto.com/entertainment/meta-changes-ai-prompts-after-chatbot-asked-mother-to-identify-her-child-3408508/","kind":"news_report","access":"read","language":"en","translation_note":"Read in English on 2026-09-18 (Dexerto, 12 Sep 2026). Relays The Verge's report of Meta spokesperson Dina El-Kassaby's statement; treated as The Verge chain.","independence_group":"verge"}],"version":1,"ai_roles":["own_use","institutional_use"],"contexts":["privacy","everyday_life","relationships"],"unknowns":["What Meta changed and how many other users saw similar prompts about children is not disclosed.","Whether the compiled information was shown to anyone other than Robins is not established.","No regulator has announced an inquiry in the inspected sources."],"geography":{"basis":"Robins is described as a Utah mother (Toronto Sun/Futurism; TRT Haber); the posts and prompts occurred on her US Instagram/Facebook accounts. No court.","court_countries":[],"event_countries":["US"],"affected_person_countries":["US"]},"publication":{"basis":"Published under the 2026-09-15 charter as a privacy and made-claim-about case: an AI feature compiled identifying details about two young children and a named adult's location, the adult reported distress and loss of control, and the company acknowledged the prompts should not have been generated. Four sources across four reporting chains read; the children's details are not reproduced. Low severity.","reviewed_on":"2026-09-18"},"ai_involvement":{"basis":"Meta acknowledged to CNET and The Verge that its AI generated the suggested prompts and that they 'should never have been generated', and said it fixed the issue. The AI made claims about identified people (the children's identities and the mother's location) rather than conversing with them; the mother's clicks on the prompts are recorded as own_use, and the platform's default feature as institutional_use.","status":"supported"},"person_relations":["made_claim_about"]},"name":"Utah: Meta AI's suggested prompts under a mother's Instagram video compiled her young daughters' names, birth details and old photos and her likely home location; Meta said the prompts 'missed the mark' and changed the feature","summary":"On 1 September 2026 Kalie Robins, a Utah travel creator, posted a short Instagram video of herself singing in the car with one of her daughters; it was also shown on Facebook. The next day she noticed Meta AI had placed suggested questions under the post, starting with 'Who's the child passenger?'. Clicking the prompts, she said, produced her two daughters' names, birth information, photos and videos drawn from her own and relatives' past posts, including a newborn photo from her mother's account and a picture she believed she had deleted years earlier, and a further prompt, 'Where does Kalie Robins live?', assembled older and newer posts into her likely location. Her 2 September reaction video drew more than 310,000 likes. Meta told reporters the prompts 'missed the mark', 'should never have been generated' and had been fixed, while saying the feature only surfaces information the user can already access; it disputed that a long-deleted photo was used, saying the photo had been deleted shortly before the video and remained briefly visible through a bug. Robins said Meta never contacted her and that the episode left her feeling she had 'failed' her children.","incidentDate":"2026-09-02","incidentKind":"single_event","incidentDatePrecision":"day","exposurePattern":"single_interaction","reportedDate":"2026-09-10","aiSystem":"Meta AI (suggested-question prompts under Instagram and Facebook posts, drawing on the user's and related accounts' content)","aiProduct":"Meta AI","severity":"low","verificationStatus":"credible","harmCategories":[],"harmOutcomes":["psychological_distress"],"harmOutcomeSummary":"A mother experienced distress and a loss of control over her children's privacy after Meta AI's suggested prompts compiled her two young daughters' identifying details and her likely location from scattered family posts; Meta acknowledged the prompts should not have been generated and changed the feature.","frameworkFacets":[],"causationStatus":"supported","participantUsersAffectedMin":1,"otherPeopleHarmedMin":2,"affectedCountStatus":"exact","affectedCountEvidence":"Kalie Robins (who used the prompts and reported distress) and her two daughters, whose identifying details were compiled. Exact count of three; her mother and other relatives whose posts were drawn on are not counted as harmed.","victimAgeRange":"minor","jurisdiction":"US","platformType":"assistant","outcomeType":"internal_action","outcomeStatus":"resolved","primarySourceUrl":"https://www.cnet.com/tech/services-and-software/meta-ai-viral-video-personal-prompts-about-kids/","primarySourceLabel":"CNET, 12 Sep 2026: Mother calls for 'accountability' after Meta AI mines family posts for info on minors (interview with Kalie Robins; Meta statement)","firstPublishedAt":"2026-09-18T03:25:15.671921+00:00","updatedAt":"2026-09-30T01:17:58.137201+00:00","scopeVersion":"facts-v3","tags":["meta-ai","instagram","facebook","privacy","children","profiling","suggested-prompts","united-states","utah","made-claim-about"]}]}