Apple pauses Texas age assurance rollout (SB2420) after injunction, but keeps the tooling in sandbox

Original announcement (source): Apple Developer News - “Update on age requirements for apps distributed in Texas” (Dec 23, 2025)

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

What changed

Apple says a district court injunction has suspended enforcement of Texas state law SB2420 (age assurance requirements for app marketplaces and developers). Because of that, Apple will:

• pause its previously announced Texas implementation plans, and
• monitor the ongoing legal process.

What did not change (and why this still matters)

Apple explicitly says the tooling it announced previously will remain available for sandbox testing, including:

• Declared Age Range API
• Significant Change API (under PermissionKit)
• a new age rating property type in StoreKit
• App Store Server Notifications updates

Apple’s point: even if Texas is paused, these tools can also help with obligations under other laws coming into effect in Utah and Louisiana in 2026.

Reference (previous announcement): https://developer.apple.com/news/?id=2ezb6jhj

Practical implications for app teams

1. Treat “download eligibility” as a launch dependency. If you ship an 18+ experience, your campaign plan can break before onboarding even loads.

2. Build the compliance workflow now, even if enforcement shifts. Legal timelines move, engineering lead times don’t.

3. Keep marketing and product messaging aligned. If you’re asking users (or parents/guardians) for age signals or consent, the store promise and first-run flow need to match.

Tiny win

Write a one-page “age assurance readiness” checklist with one owner per item (markets, API integration status, fallback UX, and support copy). Then run it before the next release you plan to promote.

Read the official update: https://developer.apple.com/news/?id=8jzbigf4