UtahUtah sets rules for state digital IDs and personal data
Eligible Utah residents may apply for a state digital identity, which can prove age or share selected details without revealing a birth date.
What it does
Utah’s Department of Government Operations runs a state digital identity program. Eligible residents may apply, and the department may charge fees.
Digital IDs must let people share selected details, including proving they meet an age requirement without revealing their birth date. People may still use physical identification.
Some government systems and health care providers must accept a state digital ID. Providers are covered only if they receive at least $10 million a year in public funding and already accept digital IDs.
Digital wallet providers and identity checkers must tell people how they will handle identity details and get consent before processing them. They must use only the details needed for the stated purpose.
Argument forPeople could prove they meet an age requirement or share selected identity details without revealing more personal information than the check needs.
Argument againstPeople may not be able to use a digital ID at some agencies or health care providers right away if those organizations show they cannot accept it yet.
More detail
The Department of Government Operations runs the state digital identity program and issues digital identities. People are not required to apply for or obtain a digital identity. Applicants must be Utah residents, be lawfully present in the United States, and pass identity checks. Adults and emancipated minors may apply themselves; a minor who is not emancipated needs a digital guardian’s consent. The department may charge fees. The law took effect May 6, 2026.
A state digital identity must let holders choose which details to share and prove they meet a minimum age without revealing their age or birth date. These requirements apply to state-endorsed digital identities and their use by people and government entities. People may choose a physical identity instead, and the state may not require them to use a digital identity in its place. The department may not track presentations of a digital identity, except as authorized by law. The law took effect May 6, 2026.
Some government entities and health care providers must accept a state-endorsed digital identity. The health care provider rule covers only providers meeting both the public funding and digital identity system tests. A government entity is covered if it implements a new system that accepts digital identities on or after May 6, 2026. A health care provider is covered only if it receives at least $10 million a year in public funding and has a system that accepts digital identities. An entity may delay acceptance if it shows the department that acceptance is not technically feasible and provides a plan to accept the ID as soon as feasible. It need not accept the ID if the law requires a specific form of identity. Government entities must accept the ID within three months after the first one is issued. Covered health care providers have two years from that first issuance.
Digital wallet providers, verifiers, and relying parties must protect identity details and limit how they process them. These rules cover providers of digital wallets, people who verify digital IDs, and people or organizations that rely on those checks. Before processing identity details, they must give clear notice about what they collect, how they use it, why they process it, and how long they keep it, and obtain the holder’s consent. They may process presentation records only for the main purpose of the presentation or when the law requires it. A holder may complain to the data privacy ombudsperson, who may refer a complaint to the attorney general. The law took effect May 6, 2026.
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 Senate
- Passed House
- To Governor
- Became Law
Looking ahead
No hearings or votes scheduled.
History
- 2026
- Mar 25Governor Spencer Cox SignedBecame Law
- Mar 13Senate/ to GovernorTo Governor
- Mar 13Senate/ received enrolled bill from PrintingMinor
- Mar 12Senate/ enrolled bill to Printing
- Mar 12Enrolled Bill Returned to House or SenateMinor
- Mar 6Draft of Enrolled Bill Prepared
- Mar 6Bill Received from Senate for EnrollingMinor
- Mar 5Senate/ signed by President/ sent for enrollingMajor
- Mar 5Senate/ received from HouseMinor
- Mar 5House/ to Senate
- Mar 5House/ signed by Speaker/ returned to SenateMajor
- Mar 5House/ received from SenateMinor
- Mar 4Senate/ to House
- Vote recorded Senate/ concurs with House amendment. Result: pass.Upper
- Vote recorded House/ passed 3rd reading. Result: pass.Lower
- Mar 4Senate/ concurs with House amendmentMajor
- Mar 4Senate/ placed on Concurrence Calendar
- Mar 4Senate/ received from HouseMinor
- Mar 4LFA/ fiscal note publicly available for SB0275S02
- Mar 4LFA/ fiscal note sent to sponsor for SB0275S02
- Mar 4House/ to Senate
- Mar 4House/ passed 3rd readingPassed House
- Mar 4House/ substituted
- Mar 4House/ uncircled
- Mar 4House/ circled
- Mar 4House/ 3rd readingMinor
- Mar 4LFA/ bill sent to agencies for fiscal input for SB0275S02
- Mar 4LFA/ bill assigned to staff for fiscal analysis for SB0275S02
- Mar 4House/ 2nd readingMinor
- Mar 4House/ Rules to 3rd Reading Calendar
- Mar 2House/ return to Rules due to fiscal impact [House Rules Committee]
- Mar 2House/ comm rpt/ substituted/ amended [House Economic Development and Workforce Services Committee]Major
- Feb 27House Comm - Favorable Recommendation [House Economic Development and Workforce Services Committee]Minor
- Feb 27House Comm - Amendment Recommendation [House Economic Development and Workforce Services Committee]Minor
- Feb 27House Comm - Substitute Recommendation [House Economic Development and Workforce Services Committee]Major
- Feb 27LFA/ fiscal note publicly available for SB0275S01
- Feb 26LFA/ fiscal note sent to sponsor for SB0275S01
- Feb 25House/ to standing committee [House Economic Development and Workforce Services Committee]Minor
- Feb 24LFA/ bill sent to agencies for fiscal input for SB0275S01
- Vote recorded Senate/ passed 3rd reading. Result: pass.Upper
- Vote recorded Senate/ passed 2nd reading. Result: pass.Upper
- Feb 24LFA/ bill assigned to staff for fiscal analysis for SB0275S01
- Feb 24House/ 1st reading (Introduced)Minor
- Feb 24House/ received from SenateMinor
- Feb 24Senate/ to House
- Feb 24Senate/ passed 3rd readingPassed Senate
- Feb 24Senate/ uncircled
- Feb 24Senate/ circled
- Feb 24Senate/ 3rd readingMinor
- Feb 24Senate/ passed 2nd readingMinor
- Feb 24Senate/ 2nd readingMinor
- Feb 13Senate/ received fiscal note from Fiscal AnalystMinor
- Feb 12LFA/ fiscal note publicly available for SB0275
- Feb 12Senate/ placed on 2nd Reading Calendar
- Feb 12Senate/ committee report favorable [Senate Government Operations and Political Subdivisions Committee]Minor
- Feb 12LFA/ fiscal note sent to sponsor for SB0275
- Feb 11Senate Comm - Favorable Recommendation [Senate Government Operations and Political Subdivisions Committee]Minor
- Feb 10Senate/ to standing committee [Senate Government Operations and Political Subdivisions Committee]Minor
- Feb 9Senate/ 1st reading (Introduced)Minor
- Feb 9Senate/ received bill from Legislative ResearchMinor
- Feb 9LFA/ bill sent to agencies for fiscal input for SB0275
- Feb 9LFA/ bill assigned to staff for fiscal analysis for SB0275
- Feb 9Numbered Bill Publicly Distributed
- Feb 9Bill Numbered but not DistributedIntroduced
TechnologyAI & PrivacyGovernment & Ethics