Google is taking the Play Age Signals API global. In a post on the Android Developers Blog, Google Play announced that the API is now open to every Play developer worldwide, letting apps ask Google Play what age bracket you fall into instead of asking you for a birth date. The user-facing side is arriving in stages: it is already live in Brazil, reaches users in Australia and Canada by mid-August, and Google says a “full global rollout to all users” follows later this year.
What the Play Age Signals API actually does
Rather than each app building its own age gate, an app calls Play at runtime and gets back an age range plus a sharing status. Google’s developer documentation lists the default brackets the API returns as 0-12, 13-15, 16-17 and 18+, and notes developers can request custom ranges. The API is still labelled beta, works on phones, foldables and tablets running Android 6.0 or newer, and ships as a Play library that any developer can now pull in.
For parents, the control sits in one place instead of thirty. Google’s post describes the API as “a privacy-preserving tool that puts parents in the driver’s seat allowing them to share their child’s age range (e.g. 16-17) directly with apps,” with the switch living inside the Family Link app. Flip it on once and every Play app that has integrated the API can read the bracket. Google also states plainly that “Age ranges are never shared by default, and parents can update or turn off these settings at any time.” Adults, separately, can share their own age when an app prompts them.
Google is explicitly not mandating what developers do with the signal. The post argues that “A weather app, for example, shouldn’t need the same safety settings as entertainment or media apps,” and leaves each developer to decide which content, features and settings to change. That flexibility is the point — and it is also the gap. An age bracket delivered to an app carries no obligation attached to it.
The part Google’s announcement leaves out
Read the blog post on its own and this is a story about parents and safety; the words “law,” “regulation” and “compliance” do not appear in it once. Google’s own developer documentation is far more direct about why this exists. It records that the API began returning age signals for users in Brazil on 17 March 2026 “for requirements under Digital ECA,” that it has started returning signals for eligible users in Texas who created their accounts after 28 May 2026 “as part of our compliance efforts for Texas SB2420,” and that “Ongoing updates will be provided in advance of age verification bills in other US states.”
That is a gap worth naming. The same feature is described to developers as compliance work tied to named statutes, and to everyone else as family safety, with no mention that any law is involved. Both descriptions can be accurate at once — but a reader deciding whether to switch this on deserves the version that includes the legal context, not only the reassuring one. It also sets the direction of travel: once the plumbing exists and works globally, the practical question stops being whether apps can ask your age and becomes how many of them will.
On the mechanics, Google’s privacy claim is reasonable as far as it goes. An age bracket is genuinely less revealing than a date of birth or a government ID scan, and keeping the toggle in Family Link and off by default is the right default. What Google has not published is how an adult’s age gets established when they choose to share it, how long a developer may retain a signal once received, or whether an app can treat a refusal as grounds to withhold service. Until those answers exist, “privacy-preserving” describes the shape of the data, not the size of the system being switched on.
Sources: Android Developers Blog, Android Developers documentation
