AgeBridge guide
Apple's Declared Age Range API: what it gives you and what it doesn't
How iOS apps request a user's declared age range, why it stays on-device, and how to use it for feature gating without collecting birth dates.
What it is
Apple's Declared Age Range framework lets an app ask for the age range of the signed-in user — set by the user or, for child accounts, by the parent — instead of collecting a birth date. The response is a range, shareable only with user/parent consent, and designed to keep raw age data out of your servers.
What it is not
It is not identity verification and not a government-ID check; it's a declared signal with parental controls behind it. Regulators and platforms treat it as a legitimate age-assurance input, but your app still owns what happens when the range is missing or declined.
Using it well
Request the range only where a feature actually needs it, map it into your normalized age vocabulary, and route the UNKNOWN case through an explicit policy decision. Keep the range on device where requirements permit — send your server the compliance state, not the age.
Authoritative sources
This guide is general information, not legal advice. Requirements change; the linked sources are authoritative.