Texas App Store Accountability Act 2026: Age Rules

Quick Answer

The Texas App Store Accountability Act, enacted as Senate Bill 2420 (SB 2420), requires app-store operators such as Apple and Google to verify the age of users in Texas and to obtain verifiable parental consent before anyone under 18 downloads an app or makes an in-app purchase, and it requires app developers to assign an age rating to their apps using the law's categories: children under 13, younger teens 13–15, older teens 16–17, and adults 18 and older. The Act was scheduled to take effect on January 1, 2026. Its start was complicated by litigation: in December 2025 a federal district judge temporarily blocked it, in late May 2026 the U.S. Court of Appeals for the Fifth Circuit allowed Texas to enforce the law while it considers the constitutional questions, and on May 28, 2026 the U.S. Supreme Court declined to block it, with the Fifth Circuit scheduling an expedited hearing in early August 2026 — so as of mid-2026 the law is being enforced while the underlying appeal continues. Apple states that new Apple Accounts for Texas users must confirm whether the user is 18 or older, that new accounts for under-18s must join a Family Sharing group with parental consent for App Store downloads, purchases and in-app transactions, and that developers can use its Declared Age Range API plus new parental-consent re-validation and revocation capabilities. Google has begun rolling out age-verification signals and a Play Store age-verification flow for new Texas accounts. Enforcement sits with the Texas Attorney General. Comparable laws in Utah and Louisiana have passed but had not yet taken effect. Map the multi-state picture with the Legal Compliance Scan, and track commencement and litigation on the Policy Change Tracker.

Scan ad copy for policy triggers — try the free Keyword Risk Checker

Texas App Store Accountability Act (SB 2420) in 2026: Age Verification, Parental Consent and Developer Obligations

What the App Store Accountability Act Requires

The Texas App Store Accountability Act, enacted as Senate Bill 2420, places two connected obligations at the centre of the mobile app ecosystem in Texas: app-store operators must determine the age of their users and obtain verifiable parental consent before a minor downloads an app or makes an in-app purchase, and app developers must classify their apps by age category. It is one of a group of state laws that shift age assurance toward the app store as a central checkpoint, rather than leaving it to each individual app.

The law sorts users into four age brackets — children under 13, younger teens aged 13 to 15, older teens aged 16 to 17, and adults 18 and older — and ties parental-consent requirements to users under 18. For businesses, the significance is structural: the app store becomes the point at which age is established and parental consent is gathered, and developers are expected to align their apps with that framework.

"Users located in Texas who create a new Apple Account will be required to confirm whether they are 18 years or older.
— Apple, developer guidance on Texas SB 2420"

This guide explains the law's requirements, its timeline and current legal status, the specific obligations on Apple and Google, what developers need to build, and how the law affects app marketing. For the wider US state picture on minors and advertising, see the state age-verification guide, and define terms in the compliance glossary.

Timeline and Legal Status

The Act's path to enforcement has involved several steps, and getting the sequence right matters because it determines what applies now. The law was scheduled to take effect on January 1, 2026, but its early status was shaped by litigation over constitutional questions.

Key Dates

Date	Event
January 1, 2026	Scheduled effective date of SB 2420
December 2025	A federal district judge temporarily blocked the law pending review of constitutional questions
Late May 2026	The Fifth Circuit Court of Appeals allowed Texas to enforce the law while it considers the appeal
May 28, 2026	The U.S. Supreme Court declined to block the law
Early August 2026	An expedited hearing scheduled before the Fifth Circuit

The practical position as of mid-2026 is that the law is being enforced while the appeal over its constitutionality continues, so businesses are operating under active obligations even though the litigation is unresolved. Because the legal status can change as the appeal proceeds, the correct posture is to comply with the current requirements while monitoring the case. Enforcement authority rests with the Texas Attorney General. Track the litigation and any changes to the effective requirements on the Policy Change Tracker, and map how it fits alongside other US obligations with the US compliance reference.

Obligations on Apple and Google

The law's primary duties fall on the app-store operators, and both Apple and Google have published guidance describing how they are implementing age verification and parental consent for Texas users. These are the mechanics developers and marketers will encounter in practice.

How the Operators Are Implementing It

Apple — account age confirmation: new Apple Accounts for users located in Texas are required to confirm whether the user is 18 or older.
Apple — Family Sharing and consent: new Apple Accounts for users under 18 are required to join a Family Sharing group, with a parent or guardian providing consent for App Store downloads, app purchases and In-App Purchase transactions by the minor.
Apple — developer APIs: Apple provides a Declared Age Range API to communicate age categories, along with capabilities for parental-consent re-validation when an app makes a significant change, and for parents to revoke consent.
Google — Play Store flow: Google has begun rolling out age-verification signals and a Play Store age-verification flow for new Texas accounts.

The common design across both stores is that age is established at the account level and parental consent flows through the store's own mechanisms, then age-category signals are passed to developers so their apps can respond. For developers, that means integrating with the store-provided signals rather than building an independent age-verification system, and for marketers it means the audience reaching an app through the store has already passed through an age gate. Screen how these obligations interact with other jurisdictions using the Legal Compliance Scan, and for sector-specific implications see the SaaS and tech compliance guide.

What App Developers Must Do

Developers have their own set of obligations under the law, centred on age classification and on responding to the store-provided age and consent signals. These are engineering and product tasks, not just policy statements.

The Developer To-Do List

Assign an age category: classify the app as appropriate for children under 13, younger teens 13–15, older teens 16–17, or adults 18 and older, consistent with the law's brackets.
Integrate age signals: adopt the store-provided age-range signals — for example Apple's Declared Age Range API — so the app behaves appropriately for the user's age category.
Handle consent changes: support re-validation of parental consent when the app makes a significant change, and respect revocation of consent by a parent or guardian.
Align app behaviour: ensure features, data practices and purchase flows are consistent with the age category and the consent status of the user.

Apple has stated that developers "will need to adopt new capabilities and modify behavior within their apps to meet their obligations under the law," which captures the practical reality that compliance requires product changes rather than a policy update alone. Because the age categories and consent status now arrive as signals from the store, the developer's job is to consume those signals reliably and adjust the app experience accordingly, including for significant changes that may require consent to be re-obtained. Audit how an app's data and targeting practices align with age signals using the AI Compliance Audit, and for children's-data context see the COPPA amendments guide.

Impact on App Marketing and Advertisers

Although the law's direct duties fall on app stores and developers, it has clear implications for how apps are marketed and how audiences are reached, because it changes what is known about a user's age at the point of acquisition and constrains what minors can do without parental involvement.

What Changes for Acquisition

Age is established earlier: because the store determines age category at the account level, the population reaching an app has already passed an age gate, which affects assumptions about who app-install campaigns reach in Texas.
Minor conversions require consent: downloads and in-app purchases by under-18s depend on parental consent, so acquisition and monetisation funnels involving minors have an added step outside the advertiser's control.
Age-appropriate creative and targeting: aligning creative and targeting with age categories reduces the risk of reaching minors with content or offers intended for adults.
Multi-state complexity: because comparable laws are advancing in other states, app marketers operating nationally face a patchwork rather than a single rule.

The strategic takeaway for advertisers and app marketers is that age assurance is moving upstream to the app store, which changes both the composition of the reachable audience and the steps required for minors to convert. Campaigns that assume unrestricted download and purchase behaviour for younger users will need to account for the parental-consent layer, and creative and targeting should be aligned with the age categories the law defines. Because the requirements differ by state and are still being litigated, building to the framework while monitoring changes is the durable approach. Map the multi-state exposure with the Legal Compliance Scan, and track new state laws and effective dates on the Policy Change Tracker.

Compliance Checklist

[ ] Confirmed whether the app is distributed to users in Texas through Apple's App Store or Google Play
[ ] Assigned an age category using the law's brackets (under 13, 13–15, 16–17, 18+)
[ ] Integrated store-provided age-range signals (e.g. Apple's Declared Age Range API)
[ ] Built support for parental-consent re-validation on significant app changes
[ ] Built support for parental-consent revocation by a parent or guardian
[ ] Aligned app features, data practices and purchase flows with the user's age category
[ ] Reviewed app-install creative and targeting for age-appropriateness in Texas
[ ] Accounted for the parental-consent step in minor acquisition and monetisation funnels
[ ] Mapped comparable obligations in Utah, Louisiana and other states
[ ] Confirmed current requirements and litigation status against official Apple, Google and state sources

Frequently Asked Questions

What is the Texas App Store Accountability Act (SB 2420)?

The Texas App Store Accountability Act, enacted as Senate Bill 2420, is a state law that requires app-store operators to verify the age of users in Texas and to obtain verifiable parental consent before anyone under 18 downloads an app or makes an in-app purchase, and it requires app developers to classify their apps by age category — a design that places age assurance at the app-store level rather than leaving it to each individual app. The law defines four age brackets that structure its requirements: children under 13, younger teens aged 13 to 15, older teens aged 16 to 17, and adults aged 18 and older. Users under 18 fall within the parental-consent requirements, so the store must establish that a user is an adult or, if not, route the minor's downloads and purchases through a parent or guardian's consent. This is a meaningful shift in where age assurance happens. Historically, responsibility for determining a user's age and applying age-appropriate treatment has largely sat with individual apps and services. By assigning the verification and consent duties to the app store, the law creates a central checkpoint through which downloads and purchases pass, and it asks developers to align their apps with the store-provided age framework by assigning an age category and responding to age and consent signals. For the businesses involved, that produces a division of labour: the store establishes age and gathers parental consent, and the developer consumes the resulting signals and adjusts the app's behaviour accordingly. The law is enforced by the Texas Attorney General, which means compliance is backed by state enforcement authority rather than being purely advisory. It is also one of several comparable state measures, so it is best understood not as an isolated Texas rule but as part of a broader movement toward app-store-level age assurance in the United States. Because the specific obligations, age brackets and effective requirements are defined by the statute and by the operators' implementations, businesses should confirm the details against official sources rather than a summary. Map how the Texas law fits alongside other jurisdictions with the Legal Compliance Scan, and track its status on the Policy Change Tracker. The organizing principle is that SB 2420 makes the app store the point of age verification and parental consent for minors, with developers assigning age categories and responding to the store's signals.

When did the law take effect, and what is its current legal status?

The Texas App Store Accountability Act was scheduled to take effect on January 1, 2026, but its early status was shaped by litigation, and the practical position as of mid-2026 is that the law is being enforced while an appeal over its constitutionality continues. The sequence matters for understanding what applies now. The law had a scheduled effective date of January 1, 2026. In December 2025, a federal district judge temporarily blocked it pending review of constitutional questions, which meant that at the start of 2026 the law was not being enforced. That changed in late May 2026, when the U.S. Court of Appeals for the Fifth Circuit allowed Texas to enforce the law while it considers the appeal, and on May 28, 2026 the U.S. Supreme Court declined to block the law. The Fifth Circuit scheduled an expedited hearing in early August 2026 to consider the constitutional questions on a faster timetable. The net effect is that, although the underlying legal challenge has not been finally resolved, the law is currently being enforced, so businesses are operating under active obligations rather than waiting for the litigation to conclude. Enforcement authority rests with the Texas Attorney General. For businesses, this creates a specific compliance posture: comply with the current requirements now, because the law is being enforced, while monitoring the appeal, because the legal status could change as the case proceeds. It would be a mistake to treat the ongoing litigation as a reason to defer compliance, given that enforcement is active; it would equally be a mistake to assume the current position is permanent, given that the appeal continues. The prudent approach is to build to the framework while watching for developments. Because dates and legal status can move, confirm the current position against official court and state sources rather than relying on a point-in-time summary. Track the litigation timeline and any changes to the effective requirements on the Policy Change Tracker, and for the surrounding US framework see the US compliance reference. The organizing principle is that the law was scheduled for January 1, 2026, was temporarily blocked, and is now being enforced while an appeal continues, so businesses should comply now and monitor the case.

What must Apple and Google do under the law?

Under the Texas App Store Accountability Act, the app-store operators — Apple and Google — carry the primary duties of verifying user age and obtaining parental consent for minors, and both have published guidance describing how they are implementing those duties for Texas users through account-level age confirmation, family-linked consent, and signals passed to developers. Apple's implementation, as it has described it, includes several elements. New Apple Accounts for users located in Texas are required to confirm whether the user is 18 or older, which establishes the adult-or-minor distinction at account creation. New Apple Accounts for users under 18 are required to join a Family Sharing group, and a parent or guardian must provide consent for App Store downloads, app purchases and In-App Purchase transactions made by the minor — so a minor's ability to download and buy flows through parental consent. Apple also provides developer-facing capabilities: a Declared Age Range API for communicating age categories, and mechanisms for parental consent to be re-validated when an app makes a significant change and for parents to revoke consent. Google, for its part, has begun rolling out age-verification signals and a Play Store age-verification flow for new Texas accounts, applying comparable age-assurance and consent mechanics on its platform. The common architecture across both operators is that age is established at the account level and parental consent is gathered through the store's own family and account systems, after which age-category signals are made available to developers so their apps can respond appropriately. This matters for everyone downstream: developers integrate with the store-provided signals rather than building independent verification, and marketers can assume that the audience reaching an app through the store in Texas has already passed through an age gate, with minors' downloads and purchases subject to parental consent. Because the operators' implementations are described in their own developer documentation and can be updated, developers and marketers should confirm the current mechanics against Apple's and Google's official guidance. Map how these store-level duties interact with other obligations using the Legal Compliance Scan, and for platform-policy context see the Google Ads policy guide. The organizing principle is that Apple and Google establish age at the account level, gather parental consent through family systems, and pass age-category signals to developers, who then build to those signals.

What must app developers do to comply?

App developers must classify their apps by the law's age categories and integrate with the store-provided age and consent signals so their apps behave appropriately for each user's age and consent status — obligations that require product and engineering changes rather than a policy statement alone. The core developer tasks break down into a few areas. First, age classification: developers must assign their app to the appropriate category among the law's brackets — children under 13, younger teens 13 to 15, older teens 16 to 17, and adults 18 and older — which determines how the app should treat different users. Second, signal integration: because the app store establishes age and passes age-range signals to the app, developers need to adopt those signals, for example Apple's Declared Age Range API, so the app can adjust its behaviour to the user's age category rather than assuming an adult user. Third, consent handling: developers must support re-validation of parental consent when the app makes a significant change — a scenario Apple's guidance specifically addresses — and must respect a parent or guardian's revocation of consent, discontinuing the minor's continued use where consent is withdrawn. Fourth, behavioural alignment: the app's features, data practices and purchase flows should be consistent with the user's age category and consent status, so that, for instance, purchase and data-collection behaviour appropriate for adults is not applied to minors without the required consent. Apple has framed this by noting that developers will need to adopt new capabilities and modify behaviour within their apps to meet their obligations, which underscores that compliance is a build task. The practical implication is that a developer cannot treat the law as satisfied by the store alone; while the store handles verification and consent collection, the developer must consume the resulting signals reliably and shape the in-app experience around them, including handling significant changes that may trigger a fresh consent requirement. Audit how an app's data and targeting practices align with age signals using the AI Compliance Audit, and for sector-specific guidance see the SaaS and tech compliance guide. The organizing principle is that developers must assign an age category, integrate the store's age and consent signals, support consent re-validation and revocation, and align app behaviour with each user's age and consent status.

How does the law affect app marketing and advertising?

Although the App Store Accountability Act's direct duties fall on app stores and developers, it has real implications for app marketing and advertising, because it changes what is known about a user's age at the point of acquisition, adds a parental-consent step for minors, and — combined with comparable laws in other states — creates a multi-state patchwork that national app marketers must navigate. The most immediate effect is on the acquisition funnel. Because the app store establishes an age category at the account level, the population that reaches an app through the store in Texas has already passed an age gate, which changes assumptions marketers can make about who their app-install campaigns are reaching and how younger users are treated. For any funnel that involves minors, downloads and in-app purchases depend on parental consent, so there is now a step between the campaign and the conversion that sits outside the advertiser's direct control — a parent or guardian must consent for a minor to download or buy. That has practical consequences for how minor-facing acquisition and monetisation are modelled, because the consent layer can affect conversion and should be accounted for rather than assumed away. A second effect is on creative and targeting. Aligning creative and targeting with the age categories the law defines reduces the risk of reaching minors with content or offers intended for adults, and it fits the broader direction of regulation toward age-appropriate treatment of younger users. A third effect is structural: because comparable app-store age-assurance laws are advancing in other states, an app marketer operating nationally faces differing obligations by state rather than a single uniform rule, which argues for building to the framework and monitoring state-by-state developments rather than treating any one state's rule as the whole picture. The durable approach for advertisers is to recognise that age assurance is moving upstream to the app store, to account for the parental-consent step in funnels involving minors, and to keep creative and targeting age-appropriate. Map multi-state exposure with the Legal Compliance Scan, and track new state laws on the Policy Change Tracker. The organizing principle is that the law moves age assurance to the app store, adds a parental-consent step for minors, and creates multi-state complexity that app marketers must build around.

How does the Texas law relate to Utah, Louisiana and other state laws?

The Texas App Store Accountability Act is part of a broader movement of US state laws directing age assurance and parental consent to the app-store level, with comparable measures having passed in Utah and Louisiana, so the most accurate way to view the Texas law is as one instance of an emerging multi-state pattern rather than an isolated rule — a framing that matters because national app businesses face a patchwork of similar-but-not-identical obligations. Texas moved to active enforcement first among this group in practical terms, having been scheduled for a January 1, 2026 effective date and, after litigation, being enforced from mid-2026 while its appeal continues. Utah and Louisiana have passed comparable legislation, which Apple has described as coming into effect on a later timetable, meaning that the obligations they impose are expected to phase in after Texas rather than simultaneously. The shared architecture across these laws is what makes them a recognisable pattern: they place age verification and parental-consent duties on the app store, define age categories that developers must apply, and tie minors' downloads and purchases to parental involvement. For a business that operates nationally, the practical consequence is that building to a single state's rule is insufficient, because other states are adopting their own versions with their own effective dates and details. The efficient response is to build a compliance framework around the common elements — app-store-level age verification, age categorisation by developers, and parental consent for minors — and then track the state-by-state variations and timelines, rather than re-engineering separately for each law. It also means watching the litigation, since the constitutional questions being considered in the Texas appeal could influence how these laws develop across states. Because the number of states, their effective dates and the specific requirements are all subject to change, businesses should monitor developments against official sources rather than assume the current map is settled. Track new and amended state laws and their effective dates on the Policy Change Tracker, and map cross-state exposure with the Legal Compliance Scan. The organizing principle is that the Texas law is one instance of a multi-state pattern of app-store age-assurance laws, including Utah and Louisiana, so national businesses should build to the common framework and track state-by-state variations.

Don't miss the next policy change.

Create a free account — track every policy change across 8 platforms, get instant alerts, and access every free compliance tool. Or try our Keyword Risk Checker first.

Create Free Account

Report Keywords — Run AI Compliance Audit

#App Store Accountability#SB 2420#Age Verification#Parental Consent#Texas#Kids & Teens#Google Play#App Developers#State Regulation#2026 Policy#Compliance Guide 2026#Minors

Share This Report

Tweet Share

Platforms

Industries

Knowledge

Blog

Texas App Store Accountability Act (SB 2420) in 2026: Age Verification, Parental Consent and Developer Obligations

What the App Store Accountability Act Requires

Timeline and Legal Status

Key Dates

Obligations on Apple and Google

How the Operators Are Implementing It

What App Developers Must Do

The Developer To-Do List

Impact on App Marketing and Advertisers

What Changes for Acquisition

Compliance Checklist

Frequently Asked Questions

Don't miss the next policy change.

Report Keywords — Run AI Compliance Audit

Share This Report

Related Posts

Google's €890 Million DMA Fine in 2026: Self-Preferencing, Anti-Steering, and What It Means for Advertisers and Brands

The FTC Consumer Review Rule in 2026: Fake Reviews, AI Testimonials and Fake Social Proof

FTC 'Made in USA' Enforcement in 2026: The July Warning Letters and Origin Claims on Social Media

Related Resources

All Tools

Platform Guides

Knowledge Hub

Policy Tracker