Apple updates age assurance tools (Declared Age Range API) for Brazil, AU/SG, Utah and Louisiana
Apple is tightening how 18+ apps are downloaded in some regions, and expanding developer signals for age assurance and significant updates.
Original announcement (source): Apple Developer News - “Age requirements for apps distributed in Brazil, Australia, Singapore, Utah, and Louisiana” (Feb 24, 2026)
What Apple changed (plain-English)
1) Australia, Brazil, Singapore: 18+ downloads can be blocked
Starting Feb 24, 2026, Apple will block users in Australia, Brazil, and Singapore from downloading 18+ rated apps unless they’ve been confirmed to be adults (Apple says the App Store will do this confirmation automatically).
Apple also notes developers may still have separate legal obligations to confirm adulthood themselves.
2) Brazil: new signals for age category + method of assurance
For apps distributed in Brazil, the updated Declared Age Range API can return:
- the user’s age category (when the user, or parent/guardian where relevant, agrees)
- a signal about the method of age assurance
Apple also flags: if you identify loot boxes in the age rating questionnaire, your Brazil storefront rating may be updated to 18+.
3) Utah and Louisiana: age categories + “significant update” prompts
Apple is expanding tooling so apps can:
- request age category signals via Declared Age Range (Utah: new Apple Accounts from May 6, 2026; Louisiana: from July 1, 2026)
- show system-style acknowledgements for significant app updates (beta), and understand when parent/guardian permission is required
Useful links Apple points to:
- Declared Age Range API: https://developer.apple.com/documentation/declaredagerange/
- Age assurance Q&A: https://developer.apple.com/support/age-assurance/
- Design safe + age-appropriate experiences: https://developer.apple.com/kids/#age-assurance
Why this matters for app marketers
- Availability is now a marketing constraint. If downloads get blocked in key regions, your “campaign plan” can quietly fail before a user even sees onboarding.
- Your store promise must match your eligibility flows. If your product has 18+ content, make sure the first-run experience, support docs, and store listing language don’t conflict.
- Release comms become part of compliance. “Significant update” acknowledgements can change how you message big feature shifts.
Read the official update: https://developer.apple.com/news/?id=f5zj08ey
Want help with ASO?
If you want this implemented for your app, check out our services - or run your workflow in APPlyzer.