You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
1.2 Google Play Age Signals API (v3 / beta). Global Regulatory 2026
#1462
To help developers meet compliance obligations under age verification laws in jurisdictions such as Texas, Utah, Louisiana, and Brazil, Google Play provides a runtime client-side age signal interface.
Purpose and Scope: The Play Age Signals API retrieves age-related signals for users, notifies Google Play of significant app changes requiring parental approval, and receives notifications about revoked approvals. It only returns data for users based in regions where Play is required by law to provide age category data.
Terms of Service (ToS): Usage is heavily restricted. Developers may only use information from the Play Age Signals API to provide age-appropriate content and experiences in compliance with laws. You MUST NOT use the API for any other purpose including, but not limited to, advertising, marketing, user profiling, or analytics. Misuse will result in the termination of API access and immediate app suspension or takedown.
Integration & Dependency: Integrate using com.google.android.play:age-signals:0.0.3 (or subsequent versions). Supported on Android 6.0 (API level 23) and higher.
Bands: Default returned categories are 0-12, 13-15, 16-17, and 18+ (custom age ranges can also be received). Cached age signals are updated by Play within 2 to 8 weeks after the user's birthday.
Data Safety: No user data is collected, stored, or shared by the client-side library itself. Google Play's background services handle data governed by the Google Play ToS.
Rollout Timeline:
Brazil: Started rolling out on March 17, 2026, to meet requirements under Brazil's Digital ECA.
Texas: Started returning signals on May 28, 2026, for users who created accounts after that date to comply with Texas SB2420.
Ongoing updates are provided for other US states (Utah, Louisiana).
This is a maintainer FAQ for app-store-compliance, an open playbook and pre-submission guard for App Store and Google Play review. Run bash scripts/install.sh install, then run the guard on your project before you submit. Questions or a correction? Reply below.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
To help developers meet compliance obligations under age verification laws in jurisdictions such as Texas, Utah, Louisiana, and Brazil, Google Play provides a runtime client-side age signal interface.
com.google.android.play:age-signals:0.0.3(or subsequent versions). Supported on Android 6.0 (API level 23) and higher.Sources. Google Play Age Signals overview, Use Play Age Signals API (beta), Google Play Developer Help.
Source section. GLOBAL-REGULATORY-2026.md, 1.2 Google Play Age Signals API (v3 / beta).
This is a maintainer FAQ for app-store-compliance, an open playbook and pre-submission guard for App Store and Google Play review. Run
bash scripts/install.sh install, then run the guard on your project before you submit. Questions or a correction? Reply below.All reactions