UtahSocial media companies must support selected data sharing starting July 2027
Starting July 1, 2027, covered social media companies must support selected transfers for Utah users and obtain consent before including someone’s data in another user’s transfer.
What it does
Starting July 1, 2027, covered social media companies must let Utah users choose personal data to share across services and keep it updated in real time, with limited exceptions.
Starting July 1, 2027, covered services must provide eligible data copies within five business days. Sharing requires consent, including from people whose data appears in another user’s transfer.
Starting July 1, 2027, temporary outages do not violate sharing rules if companies make good faith maintenance efforts and reasonably restore service. Companies need not accept incoming data.
Argument forChoosing which data to transfer could help users switch services while consent rules protect people whose information appears in others’ transfers.
Argument againstUsers might struggle to move their information to a chosen service because companies do not have to accept incoming data.
More detail
Covered social media companies must let users select personal data to share and keep it updated across services in real time. The rules cover people located in Utah using services with user-created content, social connections, connection lists, and shared posts. Email, cloud storage, and document viewing, sharing, or collaboration services are excluded. Companies must use and publicly identify an open technical standard and provide access on reasonable terms that treat other services equally. Companies may charge reasonable fees when requests exceed reasonable limits on frequency, type, and volume. Companies need not share internal analyses or algorithms. They may withhold data in a company-specific format only when no open standard is reasonably available and sharing would reveal protected internal information. The chapter excludes entities run by religious organizations that are also exempt from property taxes under state law. These requirements take effect on July 1, 2027.
Covered services must provide eligible requested data copies. Companies and third parties must obtain users’ consent before sharing or receiving personal data through service connections. Copy requests must fall under Utah’s personal-data request law. The sharing rules cover users located in Utah and exclude religious entities that are exempt from state property taxes. Copies must be portable where technically possible, usable where practical, and transferable without obstacles when the receiving organization processes data automatically. Companies must offer a clear, accessible, and lasting way to give consent. Consent must come before a person’s data is shared through someone else’s transfer. Companies and third parties must protect shared data. Transfers of users’ connections and interactions exclude other people’s private content and messages. These provisions take effect on July 1, 2027. Companies must provide eligible requested copies and carry out users’ consent decisions within five business days.
Companies receive protection for qualifying temporary sharing outages and do not have to accept incoming data through service connections. The outage protection covers temporary losses of continuous, real-time sharing. The receiving-data limit applies to social media companies. For outage protection, companies must show good faith efforts to maintain sharing and reasonable steps to restore it as soon as practical. Using an open technical standard approved by the state regulator gives a company a starting assumption that its access terms are reasonable and treat services equally. That assumption can be challenged. These protections and limits take effect on July 1, 2027.
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 23Governor 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 7Draft of Enrolled Bill Prepared
- Mar 7Bill Received from House for EnrollingMinor
- Mar 6House/ signed by Speaker/ sent for enrollingMajor
- Vote recorded House/ concurs with Senate amendment. Result: pass.Lower
- Mar 6House/ received from SenateMinor
- Mar 6Senate/ to House
- Mar 6Senate/ signed by President/ returned to HouseMajor
- Mar 6Senate/ received from HouseMinor
- Mar 6House/ to Senate
- Mar 6House/ concurs with Senate amendmentMajor
- Mar 6House/ placed on Concurrence Calendar
- Mar 6House/ received from SenateMinor
- Mar 5Senate/ to House with amendments
- Vote recorded Senate/ passed 2nd & 3rd readings/ suspension. Result: pass.Upper
- Mar 5Senate/ passed 2nd & 3rd readings/ suspensionPassed Senate
- Mar 5Senate/ uncircled
- Mar 5LFA/ fiscal note publicly available for HB0408S03
- Mar 5LFA/ fiscal note sent to sponsor for HB0408S03
- Mar 5Senate/ circled
- Mar 5Senate/ substituted
- Mar 5Senate/ uncircled
- Mar 5LFA/ bill sent to agencies for fiscal input for HB0408S03
- Mar 5LFA/ bill assigned to staff for fiscal analysis for HB0408S03
- Mar 5Senate/ circled
- Mar 5Senate/ substitute adoption failedMajor
- Mar 5Senate/ 2nd & 3rd readings/ suspensionMinor
- Mar 5Senate/ Rules to 2nd Reading Calendar
- Mar 5Senate/ 2nd Reading Calendar to Rules [Senate Rules Committee]Minor
- Mar 4LFA/ fiscal note publicly available for HB0408S02
- Mar 4LFA/ fiscal note sent to sponsor for HB0408S02
- Mar 4Senate/ placed on 2nd Reading Calendar
- Mar 4Senate/ committee report favorable [Senate Economic Development and Workforce Services Committee]Minor
- Mar 4LFA/ bill sent to agencies for fiscal input for HB0408S02
- Mar 4LFA/ bill assigned to staff for fiscal analysis for HB0408S02
- Mar 3Senate Comm - Favorable Recommendation [Senate Economic Development and Workforce Services Committee]Minor
- Mar 2Senate/ to standing committee [Senate Economic Development and Workforce Services Committee]Minor
- Vote recorded House/ passed 3rd reading. Result: pass.Lower
- Mar 2Senate/ 1st reading (Introduced)Minor
- Mar 2Senate/ received from HouseMinor
- Mar 2House/ to Senate
- Mar 2House/ passed 3rd readingPassed House
- Mar 2House/ uncircled
- Feb 27House/ circled
- Feb 27House/ 3rd readingMinor
- Feb 25House/ 2nd readingMinor
- Feb 25House/ comm rpt/ substituted [House Economic Development and Workforce Services Committee]
- Feb 24House Comm - Favorable Recommendation [House Economic Development and Workforce Services Committee]Minor
- Feb 24House Comm - Substitute Recommendation [House Economic Development and Workforce Services Committee]Major
- Feb 24LFA/ fiscal note publicly available for HB0408S01
- Feb 23LFA/ fiscal note sent to sponsor for HB0408S01
- Feb 20LFA/ bill sent to agencies for fiscal input for HB0408S01
- Feb 20LFA/ bill assigned to staff for fiscal analysis for HB0408S01
- Feb 17House/ to standing committee [House Economic Development and Workforce Services Committee]Minor
- Jan 30House/ received fiscal note from Fiscal AnalystMinor
- Jan 30LFA/ fiscal note publicly available for HB0408
- Jan 30LFA/ fiscal note sent to sponsor for HB0408
- Jan 28House/ 1st reading (Introduced)Minor
- Jan 28House/ received bill from Legislative ResearchMinor
- Jan 28LFA/ bill sent to agencies for fiscal input for HB0408
- Jan 28LFA/ bill assigned to staff for fiscal analysis for HB0408
- Jan 28Numbered Bill Publicly Distributed
- Jan 28Bill Numbered but not DistributedIntroduced
TechnologyAI & PrivacyConsumer Protection