Apple’s Declared Age Range API, live from iOS 26.2 with Xcode 26.2, gives apps a way to ask for a user’s age bracket — under 13, 13-15, or 16 and older — without ever seeing a birth date. It’s Apple’s answer to a wave of regional laws in Australia, Brazil, Singapore, Utah, Texas, Louisiana and others that require app stores and apps to verify age and secure parental consent for certain content. Parents manage sharing through Family Sharing; adults and teens outside a Family Sharing group choose for themselves whether to share at all.
The compliance box-ticking is the easy part. What most teams miss is that the API is a permission flow with three outcomes — share, decline, or later revoke — and none of those outcomes are guaranteed. A user can decline age sharing entirely, which means your age-gated content logic has to have a sane default for “unknown,” not just for “known and under 13.” A parent can revoke consent mid-session, which means an experience built around an age band has to handle that band disappearing without warning. If you’re not tracking how often each outcome happens, you’re flying blind on whether your age-appropriate experience actually reaches the users it’s built for, or silently degrades to the lowest-common-denominator default for a majority of your install base.
Data Points to Track
- Share vs. decline vs. no-response rate for the age range prompt, broken out by whether the user is in a Family Sharing group or an independent adult/teen
- Age band distribution among users who do share (under 13 / 13-15 / 16+), so you know how much of your experience is actually running age-gated logic day to day
- Consent revocation events — when a parent or guardian withdraws a previously shared age range, and what content/features that session was mid-way through
- Region at time of prompt, since the age band returned and the legal trigger for showing the prompt at all varies by jurisdiction (Utah and Texas differ from Australia, for example)
- Sandbox test coverage — which age scenarios, location-based restrictions, and consent-revocation paths have been exercised in the iOS 26.2 Sandbox environment before shipping
Setup Steps
- Build against the iOS 26.2 SDK with Xcode 26.2 or later — earlier SDKs don’t expose the full Declared Age Range framework.
- Instrument the prompt itself as a funnel step: shown → shared / declined / dismissed, tagged with Family Sharing membership status.
- Log the returned age band (not a raw birth date — the API never gives you one) as a property on the user’s session, and re-check it doesn’t leak into analytics payloads that weren’t built to handle a minor’s data.
- Handle the “unknown” and “declined” states as first-class paths in your event schema, not an afterthought — track how often users land there so you can see how much of your base is running default, non-personalised experiences.
- Test revocation and re-consent flows in the iOS 26.2 Sandbox across the documented scenarios, and log a distinct event type when a previously granted age range disappears mid-session.
Actionable Insights
A high decline/no-response rate tells you the prompt’s framing or timing is putting people off — worth testing placement (at first launch versus at the point content actually needs gating) before assuming it’s just user reluctance. A skewed age band distribution, especially a cluster right at a legal threshold like 13 or 16, is worth sanity-checking against your actual audience — it can be a genuine reflection of who uses your app, or a sign the prompt isn’t being understood.
Revocation events deserve their own dashboard, however rare: a spike after a specific release or region rollout usually means something in your age-gated UX confused a parent enough to walk back consent, and that’s a signal worth acting on before a regulator does.
Related Resources
Need help tracking this in your app?
Our team sets up analytics pipelines for mobile and web teams every day. Talk to us and get your first events flowing in under an hour.
Talk to an expert