Summary: Google Play announced on July 30, 2026 that the Age Signals API is live in Brazil, reaches Australia and Canada by mid-August, and rolls out globally before year-end. Parents can share a child’s age range through Family Link; developers receive an age range rather than an exact birthday and decide how to adjust safety settings. The signal is off by default.
Google Play used a July 30, 2026 announcement to flag a policy-level change that reaches every Android developer: the Age Signals API is being opened up to Play developers everywhere. Signed by Paul Feng, VP of Product Management at Google Play, the post sets out the sequence — the API is live in Brazil already, arrives for users in Australia and Canada by mid-August, and gets a full global rollout before the year is out.
From Brazil to Global: The Rollout Timeline
Three steps make up the schedule: Brazil now, Australia and Canada by mid-August, then everyone else. That reframes age signals for developers — no longer a market-specific option but a routine input for users around the world, which means any app with age-sensitive content belongs on this timeline in the product roadmap today.
How the Age Signals API Works
Privacy-first and parent-driven is the design. A parent may opt to pass a child’s age range (16-17, for instance) straight to apps; when an app prompts them, adults can share their own age as well. What developers receive is an age-range signal rather than an exact birthday, and they apply it to in-app safety settings and content so the experience fits the user’s age. Google is explicit that how the safety signals get integrated remains entirely the developer’s call — the API informs the experience, it does not dictate it.
That shape carries practical weight once a team integrates it. An age range is a coarse signal, so it maps naturally to coarse decisions: which content shelf a user lands on, whether a chat feature is exposed by default, how an algorithmic feed is filtered, what the default privacy settings are. Decisions that need precision do not map well, and precision is not on offer — the point is to make the safe default easy rather than to verify anyone’s identity. Teams arriving from self-declared birthdates inside their own apps should also register the trust upgrade: the signal comes from a parent-controlled, platform-level source instead of a signup form anyone can lie to.
Parents: Controls in One Place
Configuring safety settings across dozens of separate apps is not work a parent should have to do. Age-sharing controls live in one place, the Google Family Link app: a parent opts in to sharing their child’s age range, and once shared, every Play app using the Age Signals API can receive the signal. Kids land straight into age-appropriate content without parents hand-configuring each app. Two protections are worth noting: age ranges are never shared by default, and parents can update or turn the setting off at any time.
The one-place design is where the quiet product decision sits. A safety control that lives inside every individual app protects only the children whose parents are willing to repeat a setup flow twenty times; a control that lives in Family Link protects the family the moment it is set once, and keeps working as new apps are installed. Opt-in is the tradeoff — coverage depends on parents actually turning it on — but it is the trade that keeps the data flow minimal.
Developers: No One-Size-Fits-All Rules
Google’s own example is blunt: a weather app should not need the same safety settings as an entertainment or media app. Rather than enforcing one-size-fits-all rules, the company gives developers the flexibility to decide how they integrate safety signals and how they tailor content, features, and settings to their audience. The API also sits on top of Play’s existing safety machinery: apps designed for families already have to meet rigorous standards, the store continuously reviews and scans applications, Play Console ships a built-in Restrict Minor Access tool, and Family Link has long covered screen-time limits, PIN-based content filters, and app download approvals.
Context and What It Means
The post does not spell out its own context, but the timing speaks: legislative pressure to protect minors online keeps rising worldwide, and app stores are moving from content-rating labels toward age-signal infrastructure. When a child opens an app that was never built for them, regulators keep asking who, exactly, is responsible — a store-level API is Google’s answer to that question.
Three practical takeaways follow for developers. First, media, social, and entertainment apps should evaluate integrating the API now, and treat age-appropriateness as a product capability rather than a compliance checkbox. The Brazil-to-global sequence gives teams a staged window: watch how integration behaves in one market, then two more, before the whole planet arrives. Second, because the signal is off by default and depends on a parent’s choice, apps cannot assume they will receive age data — a sensible fallback experience still matters, and arguably reveals how well an app treats unknown-age users today. Third, when Google makes age signals a platform-level API, the boundary of responsibility shifts: the platform vouches for a trustworthy signal, and the developer is accountable for what they build with it. Between now and the end-of-year global rollout, this is one of the changes most worth tracking in the Play ecosystem.