Google will expand its Play Age Signals API to Australia and Canada by mid-August, with a global rollout scheduled by the end of 2026, according to a new report from Sharjah24. The move means Android app developers in those regions can soon request a user’s age category—rather than a full date of birth—to tailor experiences for minors, all while keeping sensitive personal data off limits.

What’s Changing and How It Works

The Age Signals API isn’t brand new. It first appeared in Brazil, but the expansion to Australia and Canada marks a significant step toward its worldwide availability. At its core, the API lets an app ask Android for the user’s age band instead of trying to collect a precise birth date. The default categories Google defines are 0–12, 13–15, 16–17, and 18+, though developers can request custom ranges where supported.

Critically, the age signal isn’t a permanent identifier. An app must explicitly request it at runtime, and the user—or a parent, in the case of a supervised account—can choose whether to share that information. If the user declines, the app gets no age signal at all. In regions with mandatory age-assurance rules, the system may return a “verification required” status instead of an age band. Developers therefore need to handle three possible outcomes: an age category, a missing signal, or a demand for further verification.

The API is still in beta and works on Android phones, foldables, and tablets running Android 6.0 or later. For users with Google-supervised accounts (typically children), the sharing toggle lives inside the Family Link app. That centralization is a big deal: parents won’t have to approve age sharing in each individual app. Instead, they set a single preference in Family Link, and any participating app that asks for the age signal will receive it only if the parent has allowed it.

Who This Affects—and How

For Parents and Guardians

If you manage a child’s Android device through Family Link, this change gives you a new lever. When the update lands, you’ll see an option in Family Link to control age-signal sharing. You can decide whether apps can know your child’s age category. The sharing is off by default, so your child’s age data isn’t exposed to developers unless you flip the switch.

Because the signal communicates a broad band rather than an exact birth date, you retain a layer of privacy while still allowing apps to serve age-appropriate content. A video streaming app, for example, could restrict mature titles if it knows the user falls into the 0–12 range, but it won’t learn the child’s actual birthday. Google’s documentation makes clear that apps cannot use the signal to collect more data than they otherwise would—it’s a convenience feature, not a license to profile kids.

For App Developers

For anyone building Android apps that serve mixed-age audiences, the API offers a pragmatic alternative to rolling your own age-gating system. Instead of building date-of-birth pickers and parental consent flows, you can call a single method that returns an age band—provided the user has opted in.

You’ll need to think carefully about the three possible response states. If the user shares an age band, your app can adjust content accordingly. If they decline, you must decide how to treat unknown users: conservatively lock down features, or allow full access but with disclaimers. In jurisdictions with mandatory verification, the “verification required” prompt means your app must initiate a separate age-check process—perhaps by requesting a parent’s credit card or a government ID, depending on local law.

Google’s terms still require you to follow all Play Policies and applicable regulations. The age signal is not a silver bullet for compliance. For example, if your app collects personal data from children under a certain age, you may still need to obtain verifiable parental consent under COPPA or GDPR-K. The API simply removes the need to ask for a birth date when all you really need is a general age category.

For Enterprise IT and Mixed-OS Environments

IT teams overseeing Android devices alongside Windows endpoints won’t see an immediate operational impact. However, the trend is unmistakeable: app stores are evolving from mere distribution channels into active enforcement layers for age assurance. In the future, corporate devices with work profiles and managed Play Store settings may need to reconcile the company’s own age policies with Google’s API-driven signals. For now, the change is mostly a signal of things to come, not a fire drill.

The Road to This Rollout

Brazil served as the testbed because of its Digital Child and Adolescent Statute, which created specific obligations around age-appropriate services. The API gave Brazilian developers a standard way to comply without inventing their own mechanisms. The expansion to Australia and Canada makes sense: both countries have robust online harms legislation and active discussions about age-gating for social media, gambling, and adult content. Canada’s proposed Online Harms Act and Australia’s eSafety Commissioner mandates are creating a regulatory climate that rewards standardization like Google’s API.

Globally, the pressure is mounting. The United Kingdom’s Age Appropriate Design Code, various U.S. state laws, and the EU’s Digital Services Act all nudge platforms toward verifiable age assurance. Google’s approach—a centralized, opt-in signal managed at the account level—mirrors how Apple handles age ratings in its own ecosystem, but Google is baking it directly into the Play Store’s runtime permission model rather than relying solely on app store content ratings.

Family Link has been the linchpin of Google’s parental controls for years, handling app-install approvals, screen time, and content filters. Adding age-signal sharing to that dashboard is a logical next step. It consolidates a privacy-sensitive decision into a single, familiar interface rather than forcing parents to fumble through each app’s settings individually.

Immediate Steps to Take

  • Parents with supervised accounts: When the update reaches your region, open Family Link, review the new age-signal sharing option, and decide a policy for your child. Remember, it’s off by default, so if you want apps like YouTube Kids or games to auto-adjust content based on age, you’ll need to enable it.
  • Android developers: Start reading Google’s developer documentation on the Age Signals API (links below). If your app already has age-sensitive features, plan how you’ll request and handle the signal. Test all three response paths: signal shared, signal declined, and verification required. Update your privacy disclosures to explain how you use age category data.
  • IT administrators: No urgent action required, but consider adding this topic to your next policy review. As app stores become age gatekeepers, enterprise-managed Android profiles may eventually need to align corporate age restrictions with these signals.
  • Everyday users: If you aren’t managing a child’s device, you can mostly ignore this. The API only affects you if an app explicitly asks for your age category and you agree to share it.

Looking Ahead

The global rollout by the end of 2026 signals that age assurance is becoming a standard feature of mobile OS platforms. Expect more developers to adopt the API as they face mounting regulatory pressure, and watch for similar moves on other platforms. The next big question is whether Google will expand the signals beyond age—perhaps into content maturity ratings or parental consent status—and how interoperability with third-party age verification providers will play out. For now, the Age Signals API is a modest tool that shifts a complex privacy decision from dozens of app-specific prompts into a single, parent-controlled switch. That alone is a win for clarity and control.