Google Expands Privacy-Preserving Age Signals for Android Apps

Google plans to expand its Play Age Signals API worldwide by the end of 2026. The technology lets Android developers receive an age range that can be used to tailor content and safety settings without requiring access to a user's exact date of birth.

The system is already available in Brazil and will reach Australia and Canada by mid-August before a broader rollout. Parents can enter a child's age range through Google's Family Link controls and choose to share that signal with participating applications. Adults may also provide an age range when a developer requests it.

Google says the information is not shared by default. Centralizing the choice in Family Link avoids asking parents to repeat the same process inside every app. Developers can use the signal to limit discovery, change features or provide experiences intended for younger users.

The expansion responds to laws and regulatory pressure requiring app stores and online services to protect minors. Apple introduced related tools globally in February. Both companies are trying to satisfy age-assurance requirements while reducing collection of identity documents and other sensitive data.

Developers will need guidance on what experiences are appropriate for each age range. A signal is useful only when it leads to consistent design choices around messaging, purchases, recommendations and data collection. Google can improve adoption by providing tested defaults rather than leaving every small developer to interpret child-safety requirements independently.

Age signals can help developers avoid asking every child for an identity document, but they concentrate responsibility in the platform. Google must explain accuracy, appeals and how long evidence is retained. Families also need controls when a device is shared or a teenager is incorrectly placed in a younger group. Developers should receive only the minimum category needed to provide an appropriate experience, not a detailed profile that can be reused for advertising. Global rollout will require adaptation to local definitions of children and consent rather than one age threshold applied everywhere.

Age ranges are less intrusive than exact birth dates, but they still influence access and may be incorrect or disputed. Google should provide correction and appeal processes and limit how developers retain the signal. A privacy-preserving design is valuable only if age information cannot quietly become another advertising identifier or a permanent label attached to the account.