Artificial Intelligence Policy Tracker

AI incident ·

Lyft Driver in Boca Raton, Florida, Allegedly Used Purported Google Gemini-Generated Image to Support False $75 Damage Fee

3 news reports Synced from source · record last edited 8 Sep 2026
On this page 7 sections

In brief

An AI system built by Synthetic media generation technology developers, Synthetic image generation technology developers and 1 other and deployed by Unnamed Lyft driver, Synthetic media creators and 3 others allegedly harmed Women and girls, Road users and 9 others.

Risk domain
Not classified
Occurred
Coverage
3 reportsMay 2026

What happened

A Lyft driver in Boca Raton, Florida, allegedly submitted an AI-generated image showing spilled food and drink to support a $75 damage fee against teenage passengers. The riders' family identified a Google Gemini logo in the image and disputed the claim. Lyft later acknowledged the image was AI-generated, reimbursed the charge, and removed the driver from the platform.

Laws on record for this risk area

No instrument on record yet covers this risk area where it happened. See the open queue.

Matched from the record's risk category and country to the instruments in effect recorded here: a law listed covers the area, which is not a finding that it applies to this incident. A reviewer can correct the match in the repository (data/external/incident_overrides.yaml).

News reports (3)

Titles link to the original publisher; report text is not reproduced here.

Who was involved

Alleged harmed party
Women and girls Road users Passengers Minors Lyft customers Girls Epistemic integrity Consumers Bert Gor Adolescents Adolescent girls

AI systems implicated

Synthetic media generation technologySynthetic image generation technologyLyft damage claim processGoogle GeminiGeminiDamage claims processes

Classification (MIT AI Risk Repository taxonomy)

Risk domain
—
Risk subdomain
—
Causal entity
—
Intent
—
Timing
—
Harm level
—
Sectors
—
Countries
—

Linked by editors or by text similarity in the source dataset.

Source record: incident #1679 on the AI Incident Database · all 3 reports