Play Age Signals API: What to Ship This Year
Google is expanding the Play Age Signals API from Brazil to Australia and Canada, then worldwide later in 2026. Here is what the privacy-preserving age range actually is, what you may not use it for, and how the store listing has to match the in-app experience.
Quick answer
What is the Google Play Age Signals API and how should developers use it in 2026?
The Play Age Signals API is a privacy-preserving way for apps to receive a user’s age range so they can tailor in-app experiences. Google announced a global expansion on July 29, 2026: Brazil already had it; Australia and Canada were next by mid-August; remaining markets follow later in 2026. You may use the signal only for age-appropriate content and legal compliance, not ads, profiling, or analytics. Request access, implement the API, and keep the Play listing consistent with what different ages actually see.
- Parents share a child’s age range in Family Link; it is off by default
- Adults can share an age range when an app prompts them
- The client library does not collect extra developer-side usage data
- Prohibited uses include advertising, marketing, user profiling, and analytics
- Listing screenshots should not promise an unrestricted experience the age path will hide
On this page
Age assurance used to feel like a lawyer problem for social networks. In 2026 it is a product problem for any Play app that might be used by a teen: chat, media, UGC, dating-adjacent discovery, even a utility with a public feed. Google’s answer is not “collect a birthday.” It is a Play-mediated age range.
On July 29, 2026, Google said it is expanding the Play Age Signals API to all Play developers globally. Brazil already had it. Australia and Canada were scheduled by mid-August, with a full rollout later this year. The Android documentation also notes Texas signals for eligible accounts created after May 28, 2026, tied to SB 2420.
What you actually receive
Google describes the API as a privacy-preserving tool. Parents can share a child’s age range (for example 16–17) with apps through Family Link . Adults can share an age range when prompted. Age ranges are never shared by default, and parents can change or turn off sharing. You do not get a date of birth to store in your own profile table.
| Piece | Who controls it | What you should do |
|---|---|---|
| Child age range | Parent in Family Link | Read the range and tailor features; do not nag for a birthday. |
| Adult age share | The user, when you prompt | Ask only when the experience actually depends on age. |
| Default | Off until someone shares | Handle “unknown / not shared” as a first-class state. |
| Allowed purpose | Age-appropriate content and legal compliance | Do not feed ads, marketing, profiling, or analytics. |
| Data safety form | You, in Play Console | Disclose your own app practices; the client library collects no extra usage data. |
The API is a runtime signal from Play, not a new identity graph. Use it to change the product, then stop.
Not every app needs the same lock
Google’s own example is useful: a weather app should not need the same safety settings as an entertainment app. You choose how to integrate the signal. That flexibility is also a listing risk. If screenshot one shows an unrestricted social feed, and a 13–15 user lands in a locked-down mode, the store lied even if the API worked.
- Map features that change by age: comments, public discovery, DMs, UGC remix, in-app spend.
- Decide the default when no signal is shared. “Unknown” is not “adult.”
- Write the Play description so it does not promise a social product to a child you will later lock out.
- Keep Restrict Minor Access and content ratings in Play Console aligned with the same story.
Keep the Play listing aligned with the age path
Store visitors do not see your Age Signals branch. They see the icon, short description, and screenshots. Those assets should describe the product a typical new user actually gets, or they should make age limits visible in plain language — not in a footnote under a party screenshot.
| Asset | Unsafe pattern | Safer pattern |
|---|---|---|
| Screenshot one | A public feed of strangers as the only opener | The core job of the app, with social extras later in the set |
| Caption | “Meet everyone nearby” with no age limit | The real audience and the real first action |
| Short description | Teen slang wrapping an 18+ social graph | Factual outcome plus who it is for |
| Feature graphic | Nightlife collage for a mixed-age utility | The product, not a club flyer |
Age Signals changes the session. The listing still has to be a truthful preview of that session, or conversion and policy risk both go up.
A practical Age Signals pass for a small Play app
Read the current regional status
Confirm whether your users are in a live market (Brazil, Texas-eligible accounts, Australia/Canada, or later global rollout) before you treat the API as universal.
Request API access and implement the client
Follow Google’s request-age-signals guide. Handle shared ranges and the not-shared state.
List features that must change by age
Write the allow/deny matrix. Keep it short enough that support and App Review can understand it.
Update Data safety and content ratings
Disclose your own data practices. Do not copy the “client library collects nothing” row as if it described your whole app.
Refresh Play screenshots from the real age-appropriate UI
Export an on-size set in AppGrowthKit so the first frames match the session you will permit.
Age Signals questions
Is Play Age Signals required for every app?
Google presents it as a tool for age-appropriate experiences and regional compliance, not as a mandatory SDK for a weather app. You are responsible for using it where law and Play policy require age-appropriate treatment.
Can I use the age range for ads?
No. Google’s terms prohibit advertising, marketing, user profiling, and analytics uses of Age Signals information.
Do parents have to share a child’s age?
No. Google says age ranges are never shared by default, and parents can update or turn off sharing in Family Link.
Does the API replace content ratings?
No. Content ratings, Designed for Families rules, and Restrict Minor Access still exist. Age Signals is an in-app signal on top of those store controls.
Sources, verified 2026-08-19:
Free tools that help here
ASO Character Counter
Count characters for every App Store and Google Play metadata field against exact store limits. Live counts and over-limit warnings - nothing gets truncated at submission.
Screenshot Beautifier
Add polished backgrounds, padding, shadows, and rounded corners to any screenshot in seconds. Perfect for social posts, docs, and portfolios.
If the in-app path changes by age, the listing has to stay true
AppGrowthKit helps you turn the real product UI — including the age-appropriate first session — into an editable Play screenshot set instead of a collage that oversells features a minor will never see.
Try AppGrowthKit for Free