All About Cookies is an independent, advertising-supported website. Some of the offers that appear on this site are from third-party advertisers from which All About Cookies receives compensation. This compensation may impact how and where products appear on this site (including, for example, the order in which they appear).
All About Cookies does not include all financial or credit offers that might be available to consumers nor do we include all companies or all available products. Information is accurate as of the publishing date and has not been provided or endorsed by the advertiser.
The All About Cookies editorial team strives to provide accurate, in-depth information and reviews to help you, our reader, make online privacy decisions with confidence. Here's what you can expect from us:
- All About Cookies makes money when you click the links on our site to some of the products and offers that we mention. These partnerships do not influence our opinions or recommendations. Read more about how we make money.
- Partners are not able to review or request changes to our content except for compliance reasons.
- We aim to make sure everything on our site is up-to-date and accurate as of the publishing date, but we cannot guarantee we haven't missed something. It's your responsibility to double-check all information before making any decision. If you spot something that looks wrong, please let us know.
As governments around the world tighten online age verification requirements, Google is rolling out a new system that it says can help app developers determine whether someone is a child, teenager or adult. All without requiring users to upload a government-issued ID or take a selfie.
The company is expanding its Play Age Signals API globally after months of testing, with Australia and Canada among the next markets slated to receive the feature. Google says developers worldwide, including those in the U.S., will have access by the end of 2026 as lawmakers increasingly require app stores to play a larger role in protecting minors online.[1]
Rather than verifying someone's exact identity, Google's system shares an age signal, allowing apps to provide age-appropriate experiences while collecting less personal information than traditional identity checks.
Google's approach attempts to satisfy new legal requirements without requiring sensitive documents like passports or driver's licenses.
How Play Age Signals works
Why privacy advocates still have concerns
It also isn't foolproof
What Android users should know
Why Google is rolling this out now
Google isn't introducing Play Age Signals in a vacuum. A growing number of jurisdictions have adopted or proposed laws requiring online platforms to determine whether users are minors before allowing access to certain apps or features.
Texas, Utah and Louisiana have all passed laws placing new responsibilities on app stores, shifting some of the burden away from individual app developers. Google says Play Age Signals is designed to help developers comply with those laws while continuing to meet Google Play policies.
The system was initially tested in Brazil before expanding internationally.
According to Google, developers will be able to request age-related information through the API and use it to provide age-appropriate content and experiences.
The company also limits how developers can use that information: it cannot be used for advertising, marketing, analytics, or user profiling. Misuse can result in enforcement actions or loss of API access.
How Play Age Signals works
Unlike many age verification systems, Google isn't asking users to prove who they are.
Instead, the system relies on Family Link, Google's parental controls platform.
Parents who supervise a child's Google account can choose whether to share an age range with participating apps. Rather than transmitting a birthday, the API returns an age band (such as 0-12, 13-15, 16-17 or 18+) that developers can use to tailor content or determine whether certain features should be available. Developers can also configure custom age ranges for their own applications.
For supervised accounts, parents manage those settings through Family Link.
For unsupervised users in jurisdictions where age verification requirements apply, Google may present an in-app prompt asking whether the user wants to share age information. If someone declines, developers won't receive age signals, although Google notes the prompt may appear several times before being suppressed.
Google also says its client library doesn't itself collect usage data and that developers remain responsible for complying with applicable privacy laws and accurately disclosing their own data practices.
Why privacy advocates still have concerns
Google's approach may be less invasive than asking users to upload identification documents, but that doesn't mean the broader debate over age verification has been settled.
The Electronic Frontier Foundation (EFF), which opposes mandatory age verification laws, argues that many existing systems rely on "government ID checks, biometric scans, or other dubious 'age estimation' methods" before allowing people to access online services. According to the organization, these approaches require users to hand over "sensitive and immutable personal information" that can later be leaked, hacked, or misused.
Those concerns have become increasingly relevant as lawmakers seek stronger protections for children online.
Traditional age verification methods often require users to submit driver's licenses, passports, and facial scans. The kind of information that reveals much more than simply whether someone is over a certain age.
The argument against the practice is that systems should instead follow the principle of data minimization by collecting only the information necessary for a particular purpose. Google's system moves closer to that model by sharing an age range instead of an identity document or exact birth date.
That doesn't eliminate privacy concerns entirely, however.
Participating apps still receive information about a user's approximate age, parents must actively manage settings for supervised accounts, and developers are responsible for handling that information appropriately once they receive it.
It also isn't foolproof
Play Age Signals also has practical limitations.
Parents can choose not to share age information for supervised accounts, and determined teenagers may still create unmanaged accounts using different birth dates. Developers must also integrate the API into their apps before any age-based experiences can work.
In other words, the system is designed to make age assurance easier, not impossible to bypass.
That reflects a broader reality facing online platforms: There is currently no age verification system that simultaneously guarantees accuracy, preserves user privacy, and prevents every attempt to circumvent it.
What Android users should know
If you use Family Link to manage a child's Android device, you'll eventually have the option to decide whether age information is shared with compatible apps.
Google says those apps receive an age range rather than a precise birthday, helping developers provide age-appropriate experiences while limiting how much personal information changes hands.
Even so, parents should periodically review Family Link settings, understand what information they're choosing to share and remember that age verification technology is only one part of keeping children safe online.
Conversations about responsible app use, privacy settings, and digital literacy remain just as important as any technical safeguard.