Apple Developer: Texas App Store age assurance (Declared Age Range + PermissionKit Significant Change)

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

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

The headline

If your app is available in Texas, you may need to implement new age-assurance and parental-consent plumbing, not just change copy.

Apple says that following a court ruling (Texas SB 2420), new Apple Accounts in Texas are now subject to age assurance requirements for app marketplaces and developers.

What changes in practice:

• Age assurance + parent/guardian consent for minors under 18, covering downloads and in-app purchases.
• Consent can also be required when there are “significant changes” associated with an app.
• Parents/guardians can revoke consent for an app they previously approved.

What Apple is pointing developers to (the concrete bits)

Apple highlights a few implementation hooks that matter operationally:

• Declared Age Range API: apps can request the user’s declared age category data.

  • https://developer.apple.com/documentation/declaredagerange/

• PermissionKit: Significant Change API: used when a “significant change” requires renewed consent.

  • https://developer.apple.com/documentation/PermissionKit/SignificantAppUpdateTopic/

• StoreKit: new age rating property type (for age-rating handling in code).

  • https://developer.apple.com/documentation/storekit/appstore/ageRatingCode

• App Store Server Notifications: Apple says developers can configure a server notification to learn when parental/guardian consent has been withdrawn.

  • https://developer.apple.com/documentation/appstoreservernotifications/notificationtype

Why this matters for app teams (beyond compliance)

This will surface as growth and retention work whether you like it or not:

• More friction on “first value”. If consent gates downloads, IAP, or updates, your onboarding and paywall flows need to be resilient.
• Support load shifts. Revoked consent is going to look like “my purchase disappeared” or “why can’t I update?”, unless you pre-empt it with clear UI states and customer support macros.
• Release discipline matters. Apple explicitly puts responsibility on developers to decide what counts as a “significant change”, which means you need an internal rule-set and an audit trail, not vibes.

Tiny win

Create a one-page internal checklist for Texas release readiness:

1. Do we know which app events trigger Significant Change in our product (new social surface, new UGC, new data sharing, etc.)?
2. Is our paywall and purchase recovery flow safe if consent is missing or revoked?
3. Can support diagnose this in one reply (with the right help-center link and next step)?

Read the original: https://developer.apple.com/news/?id=sg176nne