Actress Rupali Ganguly seeks Bombay High Court protection over AI deepfake images and morphed videos on adult websites
Preliminary Why: Publisher not yet named · subject to change
Status: no action reported
No source states: loss or records, developer and model, agent tool, could do, deployer.
Severity moderate: the personal likeness of a third party was touched across multiple platforms, a bounded scope stated, with no loss figure given.
Television actress Rupali Ganguly approached the Bombay High Court seeking legal protection against the unauthorised use of her photographs, videos and other personal attributes across online and offline platforms. She alleged that her images were being misused by various businesses and websites, including platforms hosting adult content featuring AI-generated deepfake images and morphed videos, and also by boutiques, celebrity booking agencies, artist management firms and online portals. Through her lawyer, Sana Khan, she urged the court to direct removal of objectionable content and to safeguard against unauthorised commercial and digital use of her name, image and likeness. The matter is scheduled for hearing before Justice Madhav Jamdar on November 4.
What happened
No source tells the story step by step yet.
What was done
No source states an action or fix.
Risks
Sorted by rule from the case's fields; not yet read from the sources.
Controls
Not yet read for controls. Controls that mitigate the primary risk:
ModelMarking machine-made output · Abuse monitoring and account enforcement · Content safety classifiers
ApplicationPeople told they are dealing with AI
Infrastructure / targetEvidence
- Legal action a case filed
No source states: a step-by-step account, when it happened, when it was found, how many records were exposed, the direct loss, a count of the other parties affected, the cause, what set it off, what was done.
Show every field, with its source and grade
What happened
Impact
Context
Notes on gaps
No date of the deepfake creation or posting is given; only the publication date (2026-11-03) and the scheduled hearing date (November 4) are stated. Extractor proposed values without quotes; dropped: .
LR-2026-0832 · version 1 · published 2026-11-04 after automatic checks; not yet checked field by field by a person · JSON