We have updated our original post on this topic to address legislative changes that affect both the substance and effective dates of these laws, as well as the litigation challenging them.

What changed – the short version:

  • Texas is live. SB 2420 has been enforceable since June 4, 2026, when the Fifth Circuit stayed a district court injunction obtained by the Computer & Communications Industry Association (CCIA) and Students Engaged in Advancing Texas. The Supreme Court declined to vacate that stay on July 6, 2026 (not a merits ruling), and the appeal remains pending.
  • Alabama joined the club. Alabama enacted its App Store Accountability Act (HB 161, Act 2026-59) on Feb. 17, 2026. Modeled on the Texas and Utah laws, it takes effect Jan. 1, 2027, though the CCIA challenged it on First Amendment grounds on Oct. 28, 2026.
  • Utah, Louisiana, and California amended their laws. Utah’s obligations now begin May 6, 2027 and Louisiana’s on July 1, 2027. Both states narrowed developer obligations, made app store signals the primary compliance mechanism, and bought companies another year.
  • Utah eliminated government enforcement, leaving a private right of action as its only enforcement mechanism. Louisiana kept the AG but gave developers clearer guardrails. Both sets of amendments reflect lessons from the Texas litigation and appear designed to improve the laws’ odds under First Amendment scrutiny.
  • California tweaked its law. AB 1856, signed Sept. 10, 2026, amended the Digital Age Assurance Act (AB 1043) effective Jan. 1, 2027. Among other things, it exempts openly licensed operating systems from the definition of “operating system provider”; requires app stores to request the age signal from the operating system and pass it to developers on request; extends a developer’s actual knowledge to its websites and other points of access used to create or log into an account; treats age information an account holder provides about subaccount users as “clear and convincing information” that overrides the signal; bars prompting users to change their age information; and gives operating system providers and developers until July 1, 2027 to address devices and apps set up or downloaded before Jan. 1, 2027.
  • What to do now: (1) integrate Apple’s Declared Age Range API and Google’s Play Age Signals API; (2) map each age bracket to your COPPA, state privacy, and online safety obligations; (3) build a process to notify the app stores before any “significant change”; (4) handle parental consent revocations; (5) update your terms of service on enforceability against minors; and (6) lock down use, sharing, and retention of age data (Texas requires deletion after verification).
  • Which states have passed app store age verification legislation?
  • How do the laws compare at a glance?
StateEffectiveCoversKey ObligationsEnforcementLitigation
Texas (SB 2420)Jan. 1, 2026 (enforceable since June 4, 2026).App stores and developers.  App store age verification and per-transaction parental consent; Developers verify via app store, age-rate apps and in-app purchases, limit use of and delete age data.  AG under the DTPA; Up to $10,000 per violation.Injunction stayed by Fifth Circuit; Supreme Court declined to vacate;Appeal pending.  
Utah (SB 142, as amended by HB 498)May 6, 2027 (existing accounts within 12 months).App stores and developers, including pre-installed apps.  Age verification with parental attestation;Parental consent; Developers verify via app store, use lowest age category for defaults, may not share age data.Private right of action only (harmed minor or parent against app stores; Greater of actual damages or $1,000 per violation).  CCIA challenge voluntarily dismissed Apr. 21, 2026.  
Louisiana (HB 977 / Act 185)July 1, 2027.App stores and developers, including pre-loaded apps.  Age verification and parental consent;Developers rely on the app store signal unless they know their own data is more accurate;May not sell age data; Family account application exception.  AG; Up to $10,000 per violation after a 45-day cure period.None reported.  
Alabama (HB 161 / Act 2026-59)Jan. 1, 2027 (existing accounts by Oct. 1, 2027).App stores and developers, including pre-installed apps.Age verification and parental consent; Developers verify via app store, use lowest age category, may not share age data.AG only, for knowing or reckless violations;Up to $7,500 per violation.  CCIA suit filed Oct. 28, 2026 (M.D. Ala.); Preliminary injunction motion pending.  
California (AB 1043, as amended by AB 1856) Jan. 1, 2027 (pre-2027 devices and apps by July 1, 2027).Operating system providers, app stores, and developers.  Self-declared age at account setup; Age-bracket signal to developers; Developers request the signal at download and launch and are deemed to have actual knowledge; No parental consent requirement.AG; Up to $2,500 (negligent) or $7,500 (intentional) per affected child.None reported.
  • What types of organizations are covered?
    • Texas, Alabama, Louisiana, and Utah regulate app store providers (such as Apple, Google, and other app store operators) and app developers.
    • California regulates three groups: (1) operating system providers, meaning those that develop, license, or control the operating system on a computer, mobile device, or other general-purpose computing device (excluding those distributing software under open-source-style licenses); (2) covered application stores; and (3) developers. California’s law also reaches beyond mobile devices to computers and other general-purpose computing devices.
    • “Developer” is defined in most of these laws. Utah and Louisiana define a developer as a person that owns or controls an app made available through an app store in the state; Alabama adds owners or controllers of pre-installed apps; and California defines a developer as a person that owns an application, or maintains or controls its hosting, in a covered application store.
  • What are the app stores’ age verification obligations?
    • Texas, Utah, and Louisiana’s laws all require app stores to “use a commercially reasonable method” to verify an individual’s age, while Alabama requires use of “commercially available methods that are reasonably designed to ensure accuracy” or a compliant age verification system to sort an individual into one of the following categories:
      • Under 13 (“child”)
      • At least 13 and under 16 (“younger teenager”)
      • At least 16 and under 18 (“older teenager”)
      • At least 18 (“adult”)
    • Those laws therefore open up the possibility of methods beyond self-declared age (e.g., an age gate).
    • California’s law requires app stores to provide an accessible interface at account setup that requires an account holder to indicate the birth date, age, or both, of the user of that device, and categorize the user into age categories that are identical to the above categories (though, all under 18 users are referred to as a “child”). California’s law, therefore, effectively only requires an age gate.
  • Who do the laws contemplate will be verifying a minor user’s age to the app stores?
    • Texas, Utah, Louisiana: The individual who creates the app store account, which may be the minors themselves, or potentially parents. Apple’s guidance confirms this approach. 
    • Alabama and California: The parent. The California law requires the app stores provide an interface to the “account holder,” which is an individual over 18 or the parent or guardian of an individual under 18. Alabama’s law defines a “commercially available method” as one that includes “affirmative age attestation by an individual who is reasonably believed to be the parent or legal guardian of the minor.” It seems that the app stores will need to take a different approach than is currently contemplated in relation to Texas’ law in order to comply with Alabama and California’s laws.
  • What are the app stores’ obligations regarding parent accounts?
    • The non-California laws require app stores to associate each minor account with a parent account.
    • There is not an explicit requirement to do so in California. However, it does, in effect, require association of a minor account with an adult account. “Account holder” means “an individual who is at least 18 years of age or a parent or legal guardian of a user who is under 18 years of age in the state,” and age verification must be carried out by an “account holder.”
  • What are developers’ age assurance obligations under the Texas, Alabama, Louisiana, and Utah laws?
    • Developers must verify, using the app stores’ data sharing methods (e.g., APIs, as discussed in the app stores’ guidance), (i) the age category of users and (ii) for minor accounts, whether parental consent has been obtained.
    • Louisiana and Alabama also require developers to obtain parental consent for app downloads, purchases, and in-app purchases. Alabama alternatively requires age category data in lieu of parental consent for these activities. It is unclear how this would work in practice, such as if developers will have to build their own consent interface or whether the app store-provided consent flow will suffice.
    • The Texas law will require app developers to assign each app and each in-app purchase an age rating pursuant to the age categories discussed above.
    • Uniquely, the amended Louisiana law provides an exception for developers of “family account applications,” allowing them to (a) use the age range of the primary account holder as the applicable age category, and (b) permit the primary account holder to attest to the age categories of associated subaccounts. A “family account application” is defined as an app that does all the following:
      • Offers subaccounts or profiles within the app;
      • Requires a paid subscription or account creation with payment method as the app’s primary business model;
      • Does not permit account creation by individuals under eighteen years of age; and
      • Verifies that the primary account holder is an adult using commercially available methods that are reasonably designed to ensure accuracy.
    • What are developers’ age assurance obligations under the California law?
      • Developers must:
        • Request a signal with respect to a particular user when an app is downloaded and launched.
        • Apply age received “across all platforms of the [app] and points of access to the [app].”
        • Use the age range signal to comply with applicable law.
    • Is actual knowledge of age imputed to a developer through receipt of age information from app stores?
      • Texas, Louisiana, Utah, and Alabama: Yes, implicitly. Alabama, like Texas and Utah, has no express actual-knowledge provision, but its developer obligations turn on the age category data received from the app store.
      • California: Yes, explicitly.
      • With actual knowledge of users’ age being thrust upon developers, developers – in particular, those that do not independently carry out age assurance – will be forced to address obligations and restrictions under the Children’s Online Privacy Protection Act (COPPA), state consumer privacy laws that regulate children’s and teens’ personal data, and online safety laws that impose obligations and restrictions based on users’ ages.
      • By way of example, many developers that obtain actual knowledge of users under 13 from the app store will need to restrict ongoing access to their service by such users and delete such users’ personal information (if they process personal information for more than the narrow permitted internal operational purposes) in order to remain compliant with COPPA. Of course, there may be developers in this situation that have already otherwise obtained verifiable parental consent or are in the small minority of services (such as social media and gaming platforms) in which they are able to transition users to an age-appropriate experience (though, the COPPA deletion requirement would still apply). By way of another example, developers that obtain actual knowledge of users at least 13 but younger than 16 in California would have to apply age-related restrictions from the CCPA to such users, such as needing the users to opt in to sale and sharing, rather than only offering an opt-out right.
    • How do the laws address conflicts in age information possessed by developers and received from app stores?
      • Texas: The law provides a safe harbor based on “good faith” reliance on age and consent information from app stores.
      • Utah and Alabama: Each law provides a safe harbor for good faith reliance on app store age category data and consent notifications, but only if the developer also complied with the law’s developer requirements. Those requirements include using the lowest age category indicated by either the app store’s data or age data the developer independently collected when implementing safety-related features or defaults (in Utah, when initially implementing them; Utah also lets parents customize settings afterward). In practice, a developer holding its own lower age data cannot rely on the app store signal alone.
      • Louisiana: The law provides that in case of a conflict, “the developer may rely on the signal from the covered application store unless the developer has actual knowledge that its internal signal is more accurate… such as if the user provided proof of age to the developer,” in which case, “the developer shall use its internal signal or the lower of the two signals.”
      • California: The law provides that “a developer shall treat a signal received pursuant to this title as the primary indicator of a user’s age range for purposes of determining the user’s age.” However, it further provides that a “developer must not willfully disregard internal clear and convincing information otherwise available to the developer that indicates that a user’s age is different than the age bracket data indicated by a signal provided by an operating system provider or a covered application store.”
    • If we do not want to have minors download or purchase our app, can we prevent them from doing so?
      • The non-California laws permit developers to use personal data received from the app stores to enforce restrictions and/or protections. Therefore, it would seem permissible for developers to restrict certain age groups from using their apps based on age restrictions in their terms and conditions. It is unclear, however, whether it will be technically possible to prevent the download or purchase of an app once parental consent has been provided. Otherwise, developers will have to apply age-based restrictions when the minor user attempts to access or use the app following the download. Aside from understanding the technical requirements with such restriction of access, companies that decide to restrict their audience based on age groups should ensure that their terms and conditions support such restrictions.
    • How do the laws restrict developers from enforcing contracts against minors?
      • Under the non-California laws, a developer may not enforce a contract or terms of service agreement against a minor unless the developer has obtained verifiable parental consent. In Utah and Louisiana, the developer must verify through the app store that verifiable parental consent has been obtained.
    • Do the laws apply to existing app store accounts?
      • Texas and Louisiana: No. The laws apply only to new app store accounts.
      • Utah, Alabama, and California: Yes, after a grace period. Utah requires existing accounts to be addressed within 12 months after its obligations take effect; Alabama requires accounts existing on Oct. 2, 2026 to be checked before Oct. 1, 2027; and California provides a six-month grace period for app stores and developers as to existing account holders and users.
    • Do the laws cover pre-installed apps?
      • Alabama, Utah, and Louisiana: Yes. Alabama and Utah require app stores to provide available age category information and facilitate parental consent for pre-installed apps on a developer’s request, and require developers to request age category data or parental consent when an account holder launches a pre-installed app for the first time. Utah defines pre-installed apps as any app, or portion of an app, present on a mobile device at the time of purchase, initial activation, or first use by a consumer (including browsers, search engines, and messaging apps), excluding core operating system functions and apps necessary for basic device operation. Louisiana requires app stores to obtain parental consent before a minor accesses a “pre-loaded application.”
      • California: For apps downloaded before Jan. 1, 2027 and updated on or after Jan. 1, 2026, developers must request the signal before July 1, 2027.
    • How do the laws restrict a developer’s use of personal data received from an app store?
      • Under the Texas, Alabama, and Utah laws, a developer may only use personal data provided by app stores to:
      • The Texas law requires developers to delete personal data provided by app stores upon performing the required age verification.
      • All five states prohibit sharing such personal data for a purpose not required by these laws. Utah and Alabama explicitly prohibit developers from sharing age category data with any person. Louisiana, as amended by HB 977, instead prohibits developers from selling age category data to any person, and directs developers to use the app store’s age signal to enforce legally required minimum age restrictions, ensure compliance with law, and provide age-appropriate defaults, safeguards, or experiences.
    • Which app stores have released guidance addressing these laws?
      • Both Apple and Google have released guidance and tools. Apple has rolled out its Declared Age Range API and told developers that new Apple Accounts in Texas were subject to the law from June 4, 2026; Google has launched a beta version of the Play Age Signals API. These tools let developers receive users’ age information and consent status, report significant changes, and respond to parental revocations. Check the app stores’ documentation often – it is changing quickly.
    • What happens if my company does not take the actions required by the app stores?
      • If a developer fails to integrate with the app stores’ provided technical measures, it is likely that app store account holders who are verified minors (in the states where the laws are in place) will not be able to download the developer’s app(s), and in-app purchase flows will be blocked for under-18 accounts.
      • In addition, developers that do not implement the app stores’ technical measures will likely be out of compliance with these state laws.
    • How will these laws be enforced, and what are the penalties for non-compliance?
      • Texas’ law is enforced by the consumer protection division of the attorney general’s office; injunctive relief and up to $10,000 per violation in penalties are available. Violations of the Texas law are deceptive trade practices under the Texas DTPA.
      • Utah removed government enforcement entirely through HB 498 in March 2026, leaving only a private right of action:
        • Beginning May 6, 2027, a minor (or the minor’s parent) harmed by a violation of Subsection 13-76-201(2) may bring a civil action against an app store provider for the greater of actual damages or $1,000 per violation, plus reasonable attorneys’ fees and litigation costs. Developers are not subject to this private right of action, but Utah’s law expressly does not displace other remedies available under state or federal law.
      • In Louisiana, Alabama, and California, the attorney general may bring a civil action to enforce violations of the law.
      • Are any of these laws being challenged?
        • Yes. On Oct. 16, 2025, the Texas law was challenged on constitutional grounds by the CCIA and, in a parallel lawsuit, by Students Engaged in Advancing Texas and two individual teenagers. U.S. District Judge Robert Pitman consolidated the cases and granted a preliminary injunction on Dec. 23, 2025. The Fifth Circuit entered an administrative stay on May 28, 2026 and, on June 4, 2026, stayed the injunction pending appeal, allowing the Texas AG to enforce SB 2420. The Supreme Court denied the plaintiffs’ emergency applications to vacate the stay on July 6, 2026 – a denial of emergency relief, not a ruling on the merits. A Fifth Circuit panel heard oral argument on Aug. 4, 2026, and a decision is pending. Because the law is currently enforceable, developers should integrate with the app stores’ technical measures now while monitoring the appeal.
        • In parallel to its Texas lawsuit, the CCIA challenged the Utah law on similar First Amendment grounds on Feb. 5, 2026. However, on Mar. 18, 2026, the Utah legislature amended the law to delay operational compliance by one year and completely remove the AG’s enforcement authority, leaving the CCIA without a proper defendant or standing. As a result, the CCIA voluntarily withdrew its challenge to the Utah law on Apr. 21, 2026.
        • Most recently, on Oct. 28, 2026, the CCIA sued Alabama Attorney General Steve Marshall in the U.S. District Court for the Middle District of Alabama (No. 2:26-cv-00897), alleging the state’s App Store Accountability Act violates the First Amendment by burdening the speech of minors and parents and compelling speech from app developers and app stores, and violates the Commerce Clause by excessively burdening interstate commerce. The CCIA has moved for a preliminary injunction.
      • What should we watch for next?
        • Three things: (1) the Fifth Circuit’s merits decision on SB 2420; (2) the preliminary injunction ruling in the Alabama case ahead of the Jan. 1, 2027 effective date; and (3) the pending federal App Store Accountability Act, which could reshape the state-by-state landscape; the House version (H.R. 3149) was reported out of the Energy and Commerce Committee on a 26–23 vote in March 2026 but has not received a floor vote, and the Senate companion (S. 1586) has not advanced beyond committee referral.

For more information, contact the authors or your SPB relationship attorney.

Disclaimer: The content of this article is for general information only, and is not intended to constitute or be relied upon as legal advice.