UtahUtah sets consent and removal rules for fake intimate images
Starting in 2027, Utah law requires consent before image-generation services share counterfeit intimate images and sets origin-disclosure rules for some online content and state webpages.
What it does
Image-generation services must get consent before sharing counterfeit intimate images. Platforms must remove reported images after a valid notice, and people harmed by violations may sue.
Large platforms must help users inspect available origin data and avoid removing compliant data when feasible. Device makers and qualifying AI providers must add hidden disclosures to covered content.
If misleading media could harm someone using a state agency service webpage, Utah's chief information officer must set rules for accessible records about digital content and its edits.
Argument forPeople shown in fake intimate images could get images removed after valid notice and seek court orders or damages when services or platforms violate the rules.
Argument againstPeople harmed by fake intimate images may face a harder path to court because they must plead detailed facts about safeguards, and repeated failures may bring legal fees.
More detail
The law sets consent, removal, and lawsuit rules for fake intimate images. These rules cover qualifying image-generation services and covered platforms, and protect people identifiable in counterfeit intimate images. Image-generation services must get the depicted person's specific consent before sharing an image and verify who gave it; they may not demand more personal information than reasonably needed. Platforms must remove an image within 48 hours after a notice that meets the referenced federal law's requirements and make reasonable efforts to remove identical copies. A service or platform may qualify for safe-harbor protection if it meets specified safeguards and response requirements. A person suing must plead specific facts showing why that protection does not apply. These provisions take effect January 1, 2027.
The law requires certain platforms, device makers, and AI providers to show or preserve information about digital content's origin. The rules cover large public platforms, device makers producing devices for sale in Utah, and publicly accessible AI systems with over 1 million monthly users; internal-only AI systems are excluded. Large online platforms must detect available origin data, let users inspect it, and may not knowingly remove compliant data when technically feasible. Device makers must add hidden disclosures to captured content when technically feasible and consistent with accepted standards; users may be allowed to disable the disclosure. Covered AI providers must add hidden disclosures to qualifying image, video, and audio content they create or substantially modify, when technically feasible and reasonable. The chapter takes effect January 1, 2027. Device rules apply to devices made for sale in Utah on or after January 1, 2028.
The law directs Utah's chief information officer to set origin-record rules for some state agency webpages. This applies to public state agency webpages used for transactions or services when the chief information officer finds the stated risk. The rules apply when the chief information officer finds a substantial risk that misleading media could harm a resident using the agency webpage. Records must be digitally accessible and identify the software or tool, creation date, content identifier, and any previous content identifiers. The law takes effect January 1, 2027, and excludes digital content created before that date.
Where do you stand?
Choose your position
Tell your reps
Take a position to see your representatives and ways to contact them.
Where it stands
- Introduced
- Passed House
- Passed Senate
- To Governor
- Became Law
Looking ahead
No hearings or votes scheduled.
History
- 2026
- Mar 24Governor Spencer Cox SignedBecame Law
- Mar 12House/ to GovernorTo Governor
- Mar 12House/ received enrolled bill from PrintingMinor
- Mar 11House/ enrolled bill to Printing
- Mar 11Enrolled Bill Returned to House or SenateMinor
- Mar 6Draft of Enrolled Bill Prepared
- Mar 6Bill Received from House for EnrollingMinor
- Mar 6House/ signed by Speaker/ sent for enrollingMajor
- Mar 6House/ received from SenateMinor
- Mar 5Senate/ to House
- Vote recorded House/ concurs with Senate amendment. Result: pass.Lower
- Vote recorded Senate/ passed 2nd & 3rd readings/ suspension. Result: pass.Upper
- Mar 5Senate/ signed by President/ returned to HouseMajor
- Mar 5Senate/ received from HouseMinor
- Mar 5House/ to Senate
- Mar 5House/ concurs with Senate amendmentMajor
- Mar 5House/ placed on Concurrence Calendar
- Mar 5House/ received from SenateMinor
- Mar 5Senate/ to House with amendments
- Mar 5Senate/ passed 2nd & 3rd readings/ suspensionPassed Senate
- Mar 5Senate/ uncircled
- Mar 4LFA/ fiscal note publicly available for HB0276S02
- Mar 4Senate/ circled
- Mar 4Senate/ substituted
- Mar 4Senate/ uncircled
- Mar 4LFA/ fiscal note sent to sponsor for HB0276S02
- Mar 4LFA/ bill sent to agencies for fiscal input for HB0276S02
- Mar 4LFA/ bill assigned to staff for fiscal analysis for HB0276S02
- Mar 4Senate/ circled
- Mar 4Senate/ 2nd & 3rd readings/ suspensionMinor
- Feb 26Senate/ placed on 2nd Reading Calendar
- Feb 26Senate/ comm rpt/ amended [Senate Transportation, Public Utilities, Energy, and Technology Committee]Major
- Feb 26Senate Comm - Favorable Recommendation [Senate Transportation, Public Utilities, Energy, and Technology Committee]Minor
- Feb 26Senate Comm - Amendment Recommendation [Senate Transportation, Public Utilities, Energy, and Technology Committee]Minor
- Feb 24Senate/ to standing committee [Senate Transportation, Public Utilities, Energy, and Technology Committee]Minor
- Feb 23Senate/ 1st reading (Introduced)Minor
- Feb 20Senate/ received from HouseMinor
- Vote recorded House/ passed 3rd reading. Result: pass.Lower
- Feb 20House/ to Senate
- Feb 20House/ passed 3rd readingPassed House
- Feb 20House/ floor amendment
- Feb 20House/ 3rd readingMinor
- Feb 17LFA/ fiscal note publicly available for HB0276S01
- Feb 13House/ 2nd readingMinor
- Feb 13House/ comm rpt/ substituted/ amended [House Economic Development and Workforce Services Committee]Major
- Feb 13LFA/ fiscal note sent to sponsor for HB0276S01
- Feb 12House Comm - Favorable Recommendation [House Economic Development and Workforce Services Committee]Minor
- Feb 12House Comm - Amendment Recommendation [House Economic Development and Workforce Services Committee]Minor
- Feb 12House Comm - Substitute Recommendation [House Economic Development and Workforce Services Committee]Major
- Feb 12LFA/ bill sent to agencies for fiscal input for HB0276S01
- Feb 12LFA/ bill assigned to staff for fiscal analysis for HB0276S01
- Feb 6House/ to standing committee [House Economic Development and Workforce Services Committee]Minor
- Jan 26House/ received fiscal note from Fiscal AnalystMinor
- Jan 26LFA/ fiscal note publicly available for HB0276
- Jan 22LFA/ fiscal note sent to sponsor for HB0276
- Jan 20House/ 1st reading (Introduced)Minor
- Jan 20House/ received bill from Legislative ResearchMinor
- Jan 16LFA/ bill sent to agencies for fiscal input for HB0276
- Jan 16LFA/ bill assigned to staff for fiscal analysis for HB0276
- Jan 16Numbered Bill Publicly Distributed
- Jan 16Bill Numbered but not DistributedIntroduced
TechnologyAI & PrivacyConsumer Protection