Google has begun taking the Google Play Age Signals API beyond its initial test, giving Android app developers a way to ask for a child account’s age range rather than collect an ID scan or selfie. Google says the system is meant to help developers comply with app-store age verification rules while limiting how much personal data changes hands.
The rollout arrives as governments push harder on age checks online. Some rules target adult websites directly, while several U.S. states have aimed at app stores, making Google and Apple responsible for providing age-verification tools that developers can use.
Google said the Play Age Signals API is tied to Family Link, its parental controls app. A parent can choose to set an age range for a child’s managed Google account, such as 16 to 17, and allow that range to be shared with apps through Google Play. The app receives the bracket, not a full birth date, according to Google.
How does the Google Play Age Signals API work?
The API lets an app request an age range for a child account through Google Play. Google says the ranges are dynamic, so a young user may stay in one content bracket for a period and then move into another as they get older.
Parents control whether those ranges are set and shared. Google says the feature is optional for child accounts and can be switched off, which means the system depends on parents choosing to configure it in Family Link.
That design is more privacy-preserving than forcing every user to upload government documents, but it is also easier to bypass. A minor could use a different account and misstate their age, and some parents will not set up the feature at all. Google is offering a compliance mechanism, not a magic fence around the Play Store.
Where is Google rolling out the API?
Google first made the Play Store API available as a beta in Brazil. The company now says the broader rollout has started, with Australia and Canada next in line.
Developers in all countries, including the United States, are expected to get access to the Age Signals API by the end of 2026, according to Google. That timing lines up with state-level app-store laws that are starting to bite.
Google began testing the API late last year as it became clearer that multiple states planned to put age-verification duties on app stores. The Computer & Communications Industry Association, a trade group that represents technology companies, has opposed these laws.
In Texas, the legal posture shifted after the U.S. Supreme Court paused a lower-court injunction, allowing the state’s app-store age verification law to take effect. Louisiana and Utah have similar laws going into effect, according to the reported status of those measures.
The Texas law requires developers to actively use age-gating features offered by app stores. Google Play already assigns content ratings to apps, so developers should have a straightforward mapping from those ratings to the age ranges Google reports, though each developer still has to implement the API.
Google and other technology companies may keep contesting laws that turn app stores into age-control chokepoints. For now, Google’s answer is a narrow one: give developers an age-range signal, keep parents in the loop, and avoid building a universal ID checkpoint into every Android app install.
This story draws on original reporting from Ars Technica.
