Google wants every Android app to verify your age, and the developer community is divided

Google Wants to Be the Age Gate for Every Android App

Google is expanding its Play Age Signals API to all Play developers globally, and the developer community is largely skeptical of what the company is actually building.

The announcement, from Paul Feng, VP of Product Management for Google Play, describes a system that lets parents share their children's age brackets with any participating app through Google's Family Link 1. Google calls the tool "privacy-preserving" and says it puts parents "in the driver's seat" 1. A front-page Hacker News thread with hundreds of comments shows the discussion dominated by developers who see a structural power play, though a few acknowledged the safety problem the API addresses.

How the API works

Parents use the Family Link app to opt into sharing their child's age bracket with participating apps. Google gives the example of a 16-to-17 range 1. The company says age data is never shared by default and that parents can update or turn off sharing at any time 1. The API is already live in Brazil and is expanding to Australia and Canada by mid-August, with full global rollout planned for later this year 1.

The safety problem it addresses is real. Parents currently navigate a patchwork of age-gating systems across individual apps, each with its own verification method. Google's pitch: centralize age sharing through Family Link so a child's phone automatically communicates the right bracket to every participating app, without the parent configuring each one 1.

What the terms of service say

Google's own developer documentation spells out the dependency developers take on. The terms state that "Google may make changes to these terms at any time with notice" 2. The API is also restricted to apps "that are updated by Google Play," which means apps distributed outside the Play Store cannot access the age signal 2.

That restriction is where the power dynamic becomes visible. If regulators mandate age verification, developers building outside Google Play will need to construct their own systems or route users through Google's infrastructure. In the Hacker News discussion, one commenter suggested that once the framework is established for Google Play, Google could lobby for strict age-verification laws and then tell developers publishing outside the Play Store they must handle compliance themselves 3.

The terms also draw guardrails around the data. Developers "may not use the Play Age Signals API for any other purpose including, but not limited to, advertising, marketing, user profiling, or analytics" 2. Google's data safety disclosure states that the client library collects no usage data 2. These restrictions address a real concern: that an age-verification pipeline could double as a behavioral tracking layer. But they are Google's self-imposed rules, on infrastructure Google controls, under terms Google can revise.

The regulatory wave behind it

Google is not building this in a vacuum. California's AB 1043, signed into law in October 2025 and effective January 1, 2027, requires operating system providers to offer a real-time API that communicates a user's age bracket to apps 4. The law defines four categories: under 13, ages 13 to under 16, ages 16 to under 18, and 18 and older 4. Developers who receive a signal are legally deemed to have "actual knowledge" of the user's age range and must treat the signal as the primary age indicator 4. The law also prohibits operating system providers from using collected data "in an anticompetitive manner" 4.

Google's documentation notes the API already serves compliance needs in multiple jurisdictions, returning signals for users in Brazil under that country's Digital ECA law and for users in Texas under Texas SB2420 2.

The dependency question

Google's announcement leads with safety and emphasizes parental choice 1. The framing makes pushback difficult: opposing centralized age verification sounds like opposing child protection. But the structural question for developers is whether integrating Play Age Signals builds a dependency they can accept. The API replaces app-by-app age checks with a simple bracket from a centralized source. It also routes a core piece of app functionality through a Google-controlled pipeline whose terms can change and whose access is limited to apps Google approves.

Google is positioning its infrastructure as the compliance layer for a regulatory wave that is already here. The trade for developers is clear: convenience now, terms later.