Utah requires app stores to verify age before app installs

The test

On 26 March 2025, Utah's governor signed Senate Bill 142, the App Store Accountability Act, according to the legislature's own bill-status record. The enrolled text requires an app store provider to request age information from anyone creating an account in the state, and verify that person's age category using a commercially available method reasonably designed to be accurate, or one meeting rules the Division of Consumer Protection will adopt. Where verification finds the holder is a minor, the provider must link the account to a parent account and obtain verifiable parental consent before the minor may download an app or use certain features. The bill also bars enforcing a contract against a minor without verified consent, and designates some violations as deceptive trade practices.

What the evidence says

The enrolled text is the clearest evidence of what changes and when: definitions took effect 7 May 2025, core provider duties take effect 6 May 2026, and a private-right-of-action provision is scheduled for 31 December 2026, staggering compliance rather than imposing every obligation at once. The bill's summary states it requires the Division of Consumer Protection to establish standards for age verification methods, meaning the technical rules were delegated to a rulemaking process still to come. The legislature's tracking record confirms the signature and short title, adding no substantive detail beyond the enrolled text.

The sample and the variance

This record covers one state's enacted statute, not a national standard or a court's assessment of validity. Obligations apply to an app store provider as the bill defines that term, and to developers distributing through a covered store to Utah-located users; the text does not reach platforms outside that relationship. Because verification standards are still pending rulemaking, no compliance mechanism can yet be checked against the statute, and any detail beyond the bill's listed provisions would be forecast rather than documented fact.

What to try next

A platform operator, developer or observer tracking this law can treat the two dated milestones — May 2025 for definitions, May 2026 for provider duties — as checkpoints worth calendaring, rather than assuming one effective date covers the whole act. A developer distributing through a covered store can note the bill places verification duties on the store first, with developer-side duties to check age and consent status through it, and can watch for the Division's rules rather than build to an assumed standard. Neither step is a guarantee; it reads the enacted text's own timeline.

• Which specific age-verification methods will the Division of Consumer Protection's rules require or accept once adopted?
• Does a given app store's current age-check flow already meet the statute's 'reasonably designed to ensure accuracy' language, or does it depend on the pending rules?
• How will the law's private right of action, effective at the end of 2026, interact with the compliance safe harbor the bill also creates for developers?

Utah's enrolled bill is the only document this record relies on for what the law requires; it is not evidence of how any platform has implemented it, since core provider duties do not take effect until May 2026.