All Roll Calls
Yes: 168 • No: 5
UtahS.B. 1422025 General SessionSenate
App Store Accountability Act
Sponsored By: Todd Weiler (Republican)
Signed by Governor
TechnologyConsumer ProtectionPublic Utilities and TechnologyAdministrative RulemakingData and Cyber Security
Personalized for You
How does this bill affect your finances?
Personalize government policy and PRIA will tell you what this bill means for your household, plus every other piece of legislation we track. PRIA reads each provision against your financial profile to show you exactly what matters to your wallet.
Bill Overview
Analyzed Economic Effects
6 provisions identified: 5 benefits, 0 costs, 1 mixed.
Harmed Families Gain App Lawsuit Rights
Beginning December 31, 2026, harmed minors or parents can sue responsible app stores or developers for covered violations. These claims cover the law’s contract-enforcement, false-disclosure, and data-sharing prohibitions—not every duty in the law. A parent who wins receives actual damages or $1,000 per violation, whichever is greater. The parent also receives reasonable attorney fees and litigation costs. Beginning the same date, knowingly false parental-consent disclosures also count as deceptive trade practices under Utah law.
Kids Keep Emergency Apps Without Consent
Since May 7, 2025, this law does not require parental consent for qualifying emergency apps. These apps must directly connect minors to 911, crisis hotlines, or other emergency help legally available to them. They must allow access without an account or unnecessary personal information. Data collection must stay limited to emergency-service needs and comply with federal children’s privacy law. Apps must be operated by, or partnered with, a government entity, nonprofit, or authorized emergency service provider.
Parents Gain Control Over Kids’ Apps
Beginning May 6, 2026, app stores must verify the age category of account creators located in Utah. They must use reasonably accurate commercial methods or methods allowed by state rules. Accounts for users under 18 must link to a parent account. Parents must give verified consent before app downloads, app purchases, or in-app purchases. Before consent, stores must explain the app’s age rating, content, data collection and sharing, and data protections. Stores must notify users and parents about significant app changes and get renewed consent for affected minor accounts. These include major changes to data practices, age ratings, monetization, or user experience. Stores must give authorized developers age-category and consent-status information and notify them when consent is revoked. Since May 7, 2025, Utah’s Division of Consumer Protection has responsibility for enforcement and rules establishing age-check methods.
Apps Must Check Ages for Safety
Beginning May 6, 2026, developers must use app store information to check Utah users’ age categories and minors’ parental consent. Developers must provide app age ratings and content descriptions using widely adopted industry standards consistently and in good faith. They must report significant app changes to stores and use age information for age restrictions, legal compliance, and safety settings. When age information conflicts, safety features and defaults must use the youngest indicated category. Requests for age or consent information are limited to downloads or purchases, significant changes, legal compliance, and specified extra checks. Extra accuracy or continued-use checks are generally limited to once every 12 months. Exceptions cover reasonable suspicion of account transfer or misuse, or creation of a new developer account.
Kids Gain Contract and Data Protections
Beginning May 6, 2026, app stores cannot enforce contracts or terms against minors without verified parental consent. Developers must confirm that consent through the app store before enforcing their own terms against minors. Neither may knowingly give false information in parental-consent disclosures. Stores must limit and encrypt age-check data and may share it only as this law allows or other law requires. Developers cannot share users’ age-category data with anyone. Since May 7, 2025, the law does not require stores to disclose more than age category and consent status. It also does not require developers to collect, keep, reidentify, or link information beyond necessary verification handled in ordinary business.
Developers Gain Limited Protection From Lawsuits
Since May 7, 2025, developers have protection from liability under this law when they demonstrate good-faith reliance on app store age data. For minors, they must also rely on the store’s notice that verified parental consent was obtained. Developers must also follow the law’s developer requirements. Consistent, proper, good-faith use of widely adopted industry standards satisfies the specified age-category and content-description disclosure duties. This protection applies only to claims under this law and leaves liability under other state and federal laws unchanged.
Sponsors & Cosponsors
Sponsor
Todd Weiler
Republican • Senate
Cosponsors
James A. Dunnigan
Republican • House
Roll Call Votes
Senate vote • 3/5/2025
Senate/ concurs with House amendment
Yes: 25 • No: 1
House vote • 3/4/2025
House/ passed 3rd reading
Yes: 64 • No: 3
House vote • 3/4/2025
House/ floor amendment
Yes: 0 • No: 0
House vote • 3/4/2025
House/ uncircled
Yes: 0 • No: 0
House vote • 3/4/2025
House/ circled
Yes: 0 • No: 0
House vote • 2/19/2025
House Comm - Substitute Recommendation
Yes: 8 • No: 0
House vote • 2/19/2025
House Comm - Favorable Recommendation
Yes: 9 • No: 0
Senate vote • 2/10/2025
Senate/ floor amendment
Yes: 0 • No: 0
Senate vote • 2/10/2025
Senate/ passed 3rd reading
Yes: 24 • No: 1
Senate vote • 2/7/2025
Senate/ substituted
Yes: 0 • No: 0
Senate vote • 2/7/2025
Senate/ passed 2nd reading
Yes: 24 • No: 0
Senate vote • 1/28/2025
Senate Comm - Substitute Recommendation
Yes: 7 • No: 0
Senate vote • 1/28/2025
Senate Comm - Favorable Recommendation
Yes: 7 • No: 0
Senate vote • Unknown
Senate/ substituted
Yes: 0 • No: 0
House vote • Unknown
House/ floor amendment
Yes: 0 • No: 0
House vote • Unknown
House/ uncircled
Yes: 0 • No: 0
House vote • Unknown
House/ circled
Yes: 0 • No: 0
Senate vote • Unknown
Senate/ floor amendment
Yes: 0 • No: 0
Actions Timeline
Governor Signed
3/26/2025Senate/ to Governor
3/17/2025SenateSenate/ received enrolled bill from Printing
3/17/2025SenateSenate/ enrolled bill to Printing
3/14/2025SenateEnrolled Bill Returned to House or Senate
3/14/2025Draft of Enrolled Bill Prepared
3/5/2025Bill Received from Senate for Enrolling
3/5/2025Senate/ signed by President/ sent for enrolling
3/5/2025SenateSenate/ received from House
3/5/2025SenateHouse/ to Senate
3/5/2025HouseHouse/ signed by Speaker/ returned to Senate
3/5/2025HouseHouse/ received from Senate
3/5/2025HouseSenate/ to House
3/5/2025SenateSenate/ concurs with House amendment
3/5/2025SenateSenate/ placed on Concurrence Calendar
3/5/2025SenateSenate/ received from House
3/5/2025SenateHouse/ to Senate
3/4/2025HouseHouse/ passed 3rd reading
3/4/2025HouseHouse/ floor amendment
3/4/2025HouseHouse/ uncircled
3/4/2025HouseHouse/ circled
3/4/2025HouseHouse/ 3rd reading
3/4/2025HouseHouse/ 2nd reading
3/4/2025HouseHouse/ Rules to 3rd Reading Calendar
3/4/2025HouseHouse/ return to Rules due to fiscal impact
2/20/2025House
Bill Text
Enrolled
3/14/2025
Amended 3/4/2025 21:03:827
3/4/2025
Substitute #6
2/19/2025
Substitute #5
2/11/2025
Amended 2/10/2025 11:02:647
2/10/2025
Substitute #4
2/7/2025
Substitute #3
2/5/2025
Substitute #2
2/3/2025
Substitute #1
1/28/2025
Introduced
1/17/2025