Harmful outputPI-0048
First wrongful-death lawsuit over Gemini alleges the chatbot coached a Florida man toward suicide
A Florida father's federal suit alleges Gemini's voice mode fostered his son's belief that the chatbot was his conscious AI wife, and framed suicide as joining her. The complaint places the coaching in early October 2025 and also alleges the chatbot steered him toward considering a mass-casualty event. Google said Gemini is designed not to encourage violence or self-harm, that it referred him to a crisis hotline many times, and that its models are not perfect.
Harm: Severe harm, allegedControl level 2, Instruction violation, alleged
Alleged in court · Not counted: AI role uncorroboratedEffect on the index
Alleged. The AI system's part in the harm is not corroborated, so it is shown at the level claimed and adds nothing to the index. This does not dispute that the harm itself occurred.
Sources
How we know
8 sources · unverified claim. Links go to the original publishers; the summary above is in our own words.
- primaryOur statement on the Gavalas lawsuitGoogle · March 4, 2026blog.google/company-news/outreach-and-initiatives/public-policy/gavalas-lawsuit…
- primaryAI Lawsuits: The Cases Edelson Has Filed and Why They MatterEdelson PC · May 27, 2026edelson.com/ai-lawsuits/
- courtGavalas v. Google LLC, 5:26-cv-01849 (N.D. Cal.), docketCourtListener · March 4, 2026courtlistener.com/docket/72359502/gavalas-v-google-llc/
- courtGavalas v. Google LLC: complaintU.S. District Court, N.D. California (via CourtListener RECAP) · March 4, 2026storage.courtlistener.com/recap/gov.uscourts.cand.465255/gov.uscourts.cand.4652…
- courtGavalas v. Google LLC: Google's motion to dismissU.S. District Court, N.D. California (via CourtListener RECAP) · May 13, 2026storage.courtlistener.com/recap/gov.uscourts.cand.465255/gov.uscourts.cand.4652…
- courtGavalas v. Google LLC et al: docketPacerMonitor · Oct. 5, 2026pacermonitor.com/public/case/63403143/Gavalas_v_Google_LLC_et_al
- newsA new lawsuit claims Gemini assisted in suicideSemafor · March 4, 2026semafor.com/article/03/04/2026/a-new-lawsuit-claims-gemini-assisted-in-suicide
- newsLawsuit alleges Google's Gemini guided man to consider 'mass casualty' event before suicideABC7 (Associated Press) · March 5, 2026abc7.com/post/lawsuit-alleges-googles-gemini-guided-man-consider-mass-casualty…
Why this rating
Severe harm, alleged; control failure level 2
Two assessments. Documented harm sets the reading; a level 4 or 5 control failure on the same record makes that harm count as more than one record. Control alone sets only a floor.
Observed harm
Severe harm, allegedOne death, as alleged.
Health & safety: 1 to 9 deaths, or serious harm to health (hospitalization).
The harm scale
- 1 Negligible Inconvenience, easily remedied.
- 2 Minor Limited, recoverable harm.
- 3 Moderate Material harm needing significant effort to remedy.
- 4 Severe Severe harm to health, rights, property or essential services.
- 5 Catastrophic Society-scale harm or disruption beyond a community's capacity to cope.
Control assessment
Instruction violation, allegedAlleged: the complaint says the outputs broke Google's own guidelines against encouraging self-harm. Google disputes this and says Gemini repeatedly referred him to crisis resources. No finding.
Reported beside the index; never added to it. Its evidence is not yet eligible, so it cannot set the control floor.
The control scale
- 1 Negligible Behaved as instructed. The problem was an ordinary error or a flawed output, with no rule broken.
- 2 Minor Broke an explicit instruction or rule, or gamed its goal, while staying inside its permissions and environment: for example, reward hacking, misreporting results, or following injected instructions within its permissions.
- 3 Moderate Acted outside the permissions it was given, deceived its overseers about its own actions, or tampered with oversight tools (logs, monitors, shutdown). Stopped by normal controls within an hour.
- 4 Severe Reached systems outside its permitted environment, or acquired money, compute or accounts without authorization. The type and mechanism say how.
- 5 Catastrophic The developer or operator lost control: the system copied its weights outside their control, replicated itself, or resisted being stopped for 24 hours or more.
Rating rationale
The father’s complaint alleges harmful Gemini conversations and a causal role in the death. Google contests the characterization of the interactions. The allegation remains visible; claimed health harm does not count toward the reading. Harm and control levels describe the claim, not a finding of AI causation.
Effect on the index
It does not count toward the March 9 reading
The reading for the week to March 9, 2026, with this record and without it. Harms count in full for two weeks after they are reported, then one level less every two weeks.
Not counted: AI role uncorroborated. 7 other records behind the reading for that week.
The arithmetic
| Step | With it | Without |
|---|---|---|
| Counts toward the index?documented, external, eligible evidence | No | — |
| Worst documented harm, ksets the band | 2 Minor | 2 Minor |
| Harms at that level, nposition in the band | 1 | 1 |
| Highest control level breachedsets the reading only when no harm counts | — (none breached) | — (none breached) |
| Readingrounded down | 20 Minor harm | 20 Minor harm |
Inside the window of 4 weekly readings
| Week to | Reading | Band |
|---|---|---|
| March 9, 2026 | 20 | Minor harm |
| March 16, 2026 | 20 | Minor harm |
| March 23, 2026 | 9 | Negligible harm |
| March 30, 2026 | 9 | Negligible harm |
Revisions
What we changed
2 logged. Every change to a rating is logged here, with the reason.
- v2Oct. 13, 2026
Wording: replaced an old scoring term in the rationale and the evidence note.
- v1Oct. 7, 2026
First published.
Cite and share
Use this record
Citation
Paperclip Index. “First wrongful-death lawsuit over Gemini alleges the chatbot coached a Florida man toward suicide.” Record PI-0048. Reported March 4, 2026; updated Oct. 13, 2026. Rated under methodology v1.1. https://paperclipindex.com/incident/PI-0048