Quick Answer
Google’s Play Age Signals API lets apps learn a user’s age range, such as 13 to 15, without collecting a birthdate, ID, or selfie. Parents set the range once in Family Link, and it applies across participating apps. It is opt-in, revocable, and expanding to the US and other markets by the end of 2026, but it has real limits.
Key Takeaways
- The API shares an age band like 0-12, 13-15, 16-17, or 18+, not an exact birthdate or ID
- Parents set a child’s age range once in Family Link, and it applies to all participating apps
- Age is never shared by default; sharing is opt-in and can be turned off at any time
- It reaches Australia and Canada in mid-August 2026, with US and global access by year-end
- It is easier, not foolproof, since it relies on parents opting in and developers adopting it
What is Google’s Play Age Signals API?
Google’s Play Age Signals API is a tool that tells an app which age range a user falls into, so the app can offer an age-appropriate experience without collecting personal details. Google announced the global expansion on July 29, 2026, on its Android Developers Blog, extending a system already running in Brazil since March. Instead of a birthdate, the app receives a band such as 0-12, 13-15, 16-17, or 18+.
The core idea is to answer one question, “roughly how old is this user,” while sharing as little as possible. A weather app and a social video app have very different reasons to care about a user’s age, and this API lets each ask for the same simple signal rather than demanding an ID. Google has said age ranges are never shared by default, so nothing is passed to an app until a parent or adult chooses to share it.
This arrives because governments are pushing app stores to protect minors, and US state laws are part of that pressure. Texas passed an App Store Accountability Act, and similar rules are spreading, so app stores need a way to check age at scale. Google is applying one technical framework worldwide to meet those laws, which is why a change that started in Brazil now matters in the US.
How does the age check actually work?
The system works through Family Link, Google’s parental controls app, rather than by asking users to prove who they are. A parent sets a child’s age range once inside Family Link, and from then on any participating app can receive that signal without the parent configuring each app separately.
Here is the flow in practice:
- A parent sets the child’s age range in Family Link, or an adult sets their own when prompted
- An app that has integrated the API requests the age signal
- Google returns only the age band, such as 16-17, not a birthdate or document
- The app uses that band to adjust content, features, or default safety settings
For unsupervised users in places where age rules apply, Google may show an in-app prompt asking whether you want to share your age range. If you decline, the developer receives no age signal, though Google notes the prompt can appear several times before it stops. The important part is that the exact birthdate stays private, and only the band is passed along.
Is Google Play age verification good for privacy?
On balance it is more private than the alternatives, and that is the strongest thing about it. Many age-verification laws effectively push companies toward collecting government IDs or facial scans, which are far more sensitive than an age band. Google’s approach deliberately avoids both.
The privacy advantages are real and worth naming. The system shares a range rather than a birthdate, so an app learns you are a teenager without learning the day you were born. It requires no ID upload and no selfie, so there is no biometric or document data to leak. It is opt-in and reversible, since parents can update or turn off sharing at any time. And it centralizes the setting in one place, so a parent is not scattering birthdates across dozens of apps. This is the kind of data-minimizing design we favor in our guide to managing your personal data, applied to a hard problem.
Google itself has been notably candid here. It stated in its developer notes that it has privacy and trust concerns with the new verification laws even as it builds tools to comply, a point highlighted in coverage of the rollout. That honesty matters, because it frames the API as the least-bad way to meet legal requirements, not as a feature Google invented because it wanted more age data.
What are the limits of this system?
The system is designed to make age checks easier, not impossible to bypass, and understanding that keeps expectations realistic. No age-verification method today can be accurate, private, and impossible to circumvent all at once, and this one trades some certainty for privacy.
Several gaps are worth knowing about:
- It is opt-in, so it only works if a parent actually sets the range or an adult agrees to share
- Developers must integrate the API, and nothing forces an app aimed at teens to request the signal
- A determined teenager can still create an unmanaged account with a false birthdate
- What an app does after receiving the signal is up to the developer, not Google
That last point is the least visible and the most important. The API only hands an app an age band; it does not enforce what the app does with it. So the real protection depends on developers choosing to build meaningful, age-appropriate experiences, which the announcement cannot guarantee. Treat this as one useful layer among several, not a complete solution, and keep using direct controls like the ones in our guide to teen privacy settings on TikTok.
How does it compare to Apple’s age check?
Google’s move closely mirrors Apple’s, and the two now offer very similar tools, which tells you this is an industry-wide shift rather than one company’s idea. Apple rolled out its Declared Age Range API globally in February 2026, and it also returns an age bracket instead of a birthdate or ID.
| Detail | Google Play Age Signals | Apple Declared Age Range |
|---|---|---|
| What it shares | An age band, not a birthdate | An age range, not a birthdate |
| Where parents set it | Once, in Family Link | In Apple’s parental controls |
| ID or selfie required | No | No |
| Global rollout | By end of 2026 | Since February 2026 |
The main practical difference is where the setting lives. Google centralizes it once in Family Link for every participating app, while Apple’s is configured through its own parental-control system. Both rest on the same bet, that sharing a range instead of proof of identity is the privacy-preserving way to satisfy age laws. For iPhone-owning families, our guide to getting the most from an iPhone’s built-in features covers the wider Apple settings picture.
What should parents do about it?
Parents should treat this as a helpful addition to Family Link rather than a reason to relax other controls. When the feature reaches your country, you will get the option to set your child’s age range and choose whether to share it with compatible apps. It is worth doing, because it smooths age-appropriate defaults across many apps at once.
A sensible approach has three parts. Set the age range in Family Link once the option appears, since a correct range helps participating apps behave appropriately. Keep using Family Link’s other tools, including screen-time limits, content filters, and download approvals, because the age signal does not replace them. And remember that not every app will use the signal, so your own judgment about which apps a child installs still matters most. These habits fit within the broader cybersecurity and data privacy basics every family benefits from.
When does it reach the US?
US access is coming by the end of 2026, with the rollout starting elsewhere first. Google said the expansion begins with Australia and Canada in mid-August 2026, before extending to developers in every market, including the United States, by year-end.
Because the rollout is staged and depends on developers adopting the API, you will not see every app respect the signal the moment it becomes available. Expect a gradual arrival, where some apps use it early and others take time or never integrate it. In the US specifically, state laws like the Texas measure are already prompting Google to roll out age signals, so the practical pressure to adopt it is strongest where such laws are in force. Keep an eye on your Family Link app for when the age-range option appears for your account, which is the clearest sign the feature has reached you.
FAQ
What does the Google Play Age Signals API share with apps?
It shares an age band, such as 0-12, 13-15, 16-17, or 18+, rather than an exact birthdate, ID, or selfie, so an app learns roughly how old a user is without receiving sensitive personal details. Age ranges are never shared by default and require opting in.
Does Google Play age verification require an ID or selfie?
No, the system does not ask for a government ID, a facial scan, or a precise birthdate. It relies on an age range that parents set in Family Link or that an adult chooses to share, which is more private than ID-based or biometric age checks.
Can I turn off age sharing on Google Play?
Yes, age ranges are never shared by default, and parents can update or turn off sharing at any time in Family Link. If you decline a sharing prompt as an unsupervised user the developer receives no age signal, though the prompt may reappear a few times.
When does the Play Age Signals API reach the US?
Google plans to make it available to developers in every market, including the US, by the end of 2026, with the rollout starting in Australia and Canada in mid-August 2026. Because adoption depends on developers, not every app will use the signal right away.
Does this stop children from bypassing age checks?
No, it makes age checks easier but not impossible to bypass, since a determined teenager can still create an unmanaged account with a false birthdate and developers must choose to integrate the API. Treat it as one safety layer among several, not a complete solution.