Tap any paragraph to write a margin note. Your notes collect in the Desk below the text and file under cases with @. The side-by-side margin rail opens on a larger screen.

Code · Utah · Title 13 — Commerce and Trade · Chapter 76

13-76-202. Developer requirements.

405 words·~2 min read·/ut/title-13/chapter-76/13-76-202

A research copy — for the controlling text, always check the official state or federal source. Not legal advice.

Effective 3/18/2026
13-76-202. Developer requirements.
(1)Beginning May 6, 2027, a developer shall:
(a)verify through the app store's data sharing methods:
(i)the age category data of account holders located in the state; and
(ii)for a minor account, whether verifiable parental consent has been obtained;
(b)notify app store providers of a significant change to the app; and
(c)request age category data or parental consent:
(i)at the time an account holder:
(A)downloads an app;
(B)purchases an app; or
(C)launches a pre-installed application for the first time;
(ii)when implementing a significant change to the app; or
(iii)to comply with applicable laws or regulations.
(2)Beginning May 6, 2027, a developer may request age category data:
(a)no more than once during each 12-month period to verify:
(i)accuracy of age category data associated with an account holder; or
(ii)continued account use within the verified age category;
(b)when there is reasonable suspicion of:
(i)account transfer; or
(ii)misuse outside the verified age category; or
(c)at the time an account holder creates a new account with the developer.
(a)Beginning May 6, 2027, when initially implementing any developer-created safety-related features or defaults, a developer shall use the lowest age category indicated by:
(i)age verification data provided by an app store provider; or
(ii)age data independently collected by the developer.
(b)Subsection (3)(a) does not prohibit a developer from allowing a parent to customize age-related restrictions, safety-related features, or content settings for individual users within a minor account after the initial defaults described in Subsection (3)(a) are set.
(4)Beginning May 6, 2027, a developer may not:
(a)enforce a contract or terms of service against a minor unless the developer has verified through the app store's data sharing methods that verifiable parental consent has been obtained;
(b)knowingly misrepresent any information in the parental consent disclosure; or
(c)share age category data with any person.
(5)Beginning May 6, 2027, a developer may only use age category data received through the app store's data sharing methods to:
(a)enforce any developer-created age-related restrictions;
(b)ensure compliance with applicable laws and regulations; or
(c)implement any developer-created safety-related features or defaults.
(6)Beginning May 6, 2027, a developer may request that an app store provider prevent minor accounts from downloading or purchasing the developer's app.
Amended by Chapter 157 , 2026 General Session
★   the supreme law of the land   ★
Don't Tread on Me
E Pluribus Unum — out of many, one

"If you don't know your rights, you don't have any."

Marginalia · a citizen's law index
A research desk, not legal advice. Always read the cited source before relying on a summary.
Questions or an issue? support@self-law.org
disclaimerMarginalia is a research index, not a law firm. Nothing on this site is legal, tax, or financial advice and no attorney–client relationship is formed by using it. Statutes, regulations, and case law change; summaries, search results, AI output, and member posts may be incomplete, out of date, or wrong. Any interpretation drawn from material on this site should be validated by a licensed attorney in your jurisdiction before you act on it.