Apple: Texas SB2420 age assurance requirements (what changes for accounts, consent, and your app)

Original announcement (source): Apple Developer News - “New requirements for apps available in Texas” (Oct 8, 2025)

• https://developer.apple.com/news/?id=btkirlj8

What’s happening (in plain English)

Texas’ SB2420 (effective Jan 1, 2026) introduces age assurance requirements that touch both:

• the App Store (account + consent plumbing), and
• developers (new capabilities and behavior changes inside apps).

Apple explicitly says it shares the child-safety goal, but is concerned the law pushes ecosystems toward collecting sensitive personal data for everyday app downloads. Their stated approach is to meet the requirement while staying as privacy-preserving as possible.

What changes for users (as Apple describes it)

Once the law is in effect, Apple says:

• New Apple Accounts created by users located in Texas must confirm whether they are 18+.
• New Apple Accounts for users under 18 must join a Family Sharing group.
• Parents/guardians must provide consent for:
  • App Store downloads
  • app purchases
  • IAP transactions for the minor

What changes for developers (the part growth teams should care about)

If your app serves Texas users, you should treat this as a distribution + UX dependency. Apple flags developer-side obligations and points to privacy-preserving tooling.

1) Declared Age Range API

Apple highlights the Declared Age Range API:

• docs: https://developer.apple.com/documentation/declaredagerange/
• available to implement now
• will be updated to provide the required age categories for new Texas accounts

Practical implication: onboarding, paywalls, and feature gating may need to respond to age category signals.

2) “Significant change” consent flows (later APIs)

Apple describes upcoming APIs intended to support the law’s notion of a “significant change”:

• a system experience to let a user request parental consent be re-obtained
• parental ability to revoke consent for a minor continuing to use an app

This matters because it introduces a new failure mode: a “normal” feature update can become a consent event that affects retention, conversion, and support volume.

Editorial take

The thing to internalise is not “Texas only”. Apple explicitly calls out similar requirements coming in Utah and Louisiana as well.

Treat download eligibility and parental consent workflows like you treat payments and auth: owned, monitored, and tested before launch weeks.

Tiny wins

• Make a one-page doc listing every market where age assurance could block downloads (Texas, plus any 18+ enforcement regions you operate in).
• Write one checklist for release managers: “what counts as a significant change” and “what happens when consent is revoked”.

Read the official announcement: https://developer.apple.com/news/?id=btkirlj8