Texas age assurance on iOS (SB 2420): what Apple’s June 3 update means for consent, significant changes, and server notifications

Original post (source): Apple Developer News - “Update for Apps Distributed in Texas” (June 3, 2026)

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

What Apple says is changing

Apple says a court ruling lifted an injunction on Texas law SB 2420, so new Apple Accounts in Texas are now subject to age assurance requirements.

The headline impacts:

• age assurance and parent/guardian consent for minors under 18
• consent can apply to:
  • app downloads
  • Apple In-App Purchases
  • “significant changes” associated with an app
• parents/guardians can revoke consent for any previously approved app

Apple says the changes take effect starting June 4, 2026.

The practical implementation hooks Apple points to

Apple links developers to:

• Declared Age Range API (request age category data)
• Significant Change API (PermissionKit) for the “significant change” flow
• a new age rating property type in StoreKit
• an App Store server notification for consent withdrawal

Apple also recommends validating in sandbox.

Why this matters for growth and product teams

This is the kind of platform change that shows up as:

• “mysterious” conversion drops
• unexpected support tickets
• review rejection risk if your compliance story is fuzzy

In practice, it forces teams to treat compliance flows like real funnel steps:

• the consent UX is part of trust
• consent revocation is a retention and re-activation risk
• “significant change” definitions need to be decided in advance, not during a hotfix

Tiny win

Do a quick readiness pass for Texas accounts:

1. write down what your team will classify as a significant change (one page, plain language)
2. verify you can handle a consent revocation without breaking core user flows
3. add a lightweight QA script: new account (TX) → install → IAP attempt → major settings change

You do not need perfect certainty, you need fewer surprises.