Google has announced a new tool called the Google Play Age Signals API. It lets Android app developers ask Google for an age range for a user, instead of making the app collect and verify that information itself. The tool is currently in testing in Brazil, with plans to expand to Australia and Canada in mid-August and to roll out globally before the end of the year. Engadget

The tool sorts users into four age groups: 0–12, 13–15, 16–17, and 18+. Instead of sharing a person's exact birthday, Google tells the app only which age group they fall into. Parents can set up their own or their child's age group through the Google Family Link app. Once that is set, any app that uses the tool can read the age group and adjust its content, features, and settings to match. Engadget

Google announced the tool on the Google Android Developers Blog in July 2026. Android Developers Blog

Google has said the tool gives developers flexibility rather than enforcing a single approach. Developers keep full control over how to adjust their app based on the age group. A developer can use the age signal to restrict certain features, change what content is shown, or adjust privacy settings, but the tool itself does not tell them what those changes should look like. Engadget

For developers, the setup is simple. Instead of building their own age-check screen, asking for a birthday, and storing that data, developers ask Google's tool for the age group and get a response back. The information flows through Google's systems, so the app developer never directly collects or stores a birthday. For developers in countries with laws requiring age checks for minors, this shifts the responsibility for verification and data handling onto Google.

The broader context here is that age verification for children online has become a major regulatory issue in many countries. Several countries have passed or are considering laws that require app stores and platforms to verify user age and restrict access to certain content based on that verification. By handling age ranges at the platform level, Google is putting itself in the middle between regulators and individual app developers. This is similar to how Google Play and Apple's App Store already handle parental controls and content ratings through their own systems rather than leaving each app to handle it alone.

The choice of Brazil as the first test market, followed by Australia and Canada, lines up with countries that have been active in online safety for children. Australia passed the Online Safety Act in 2021, which targets harmful content accessible to minors. Canada has been working on its own online safety legislation. Brazil's internet laws and child-protection measures have placed obligations on platforms regarding young users. Google has not said the rollout schedule is tied to specific regulatory deadlines, but the sequence suggests the company wants to test the tool first in markets where age-verification expectations are already in place.

One design decision worth noting is the use of age ranges rather than exact ages. The four groups roughly match developmental and legal categories: pre-teen, early teen, late teen, and adult. Sharing only a range reduces how much personal data gets handed to app developers, which may ease some privacy concerns, but it also means less detail. A developer who wants to tell the difference between a 13-year-old and a 15-year-old, for example, cannot do so through this tool alone. Whether that level of detail is enough will depend on what each app needs and how regulators interpret age-verification requirements that may call for narrower age thresholds.

Because any app using the tool can read an age group once a parent has set it up, a single action in Family Link applies across all participating apps, saving parents from setting age limits in each app separately. The tradeoff is that parents are trusting Google to handle that data consistently across apps, and the tool's testing status means the way it works may still change before it is finalized.

For developers, the next steps are evaluating whether the tool meets their age-verification needs, watching the developer documentation for changes as testing continues, and planning for the global rollout before year-end. Google's developer documentation on the tool is live, and the testing label means that changes that could break existing integrations remain possible. Android Developers Documentation