Google’s Play Age Signals API (beta) lets your Android app receive age-related signals from Google Play—such as whether a user is age-verified, under parental supervision (Family Link), and the user’s age range—so you can adapt features and flows to comply with U.S. state age-assurance laws. This is not a payments/billing API. Live responses start January 1, 2026 (Texas), with additional states following in 2026. (Android Developers)

In this post, we at Sigosoft will break down what the Play Age Signals API does, why it’s being introduced, the legal backdrop that led to it, and how we can implement it easily without breaking a sweat.

What Is the Play Age Signals API?

Play Age Signals is a Google Play client API that helps Android developers identify users’ age-related information such as verification status, supervision level, and age range.

By using Play Age Signals, apps can automatically adapt — restricting certain features, requesting parental consent, or customizing content to meet age-appropriate guidelines.

This API supports global safety laws like COPPA and the EU Digital Services Act, helping developers ensure compliance and build trust through safer, more transparent app experiences

What it is not

It’s not a billing or monetization tool and is unrelated to Google Play Billing or alternative billing. It is focused on age-assurance signals and related Play Console workflows.

Where and when it applies

Google is rolling this out to support developers ahead of U.S. state laws that start in 2026:

• Texas: takes effect January 1, 2026 (API returns live responses for applicable users starting this date).
  
• Utah: May 7, 2026.
  
• Louisiana: July 1, 2026.
  

Until January 1, 2026, the API throws an exception. Use the testing hooks described below.

Play Console features tied to Age Signals

Notify significant changes (for example, changes that would require renewed parental approval) without republishing.

See revoked app approvals (Play lists install IDs where a parent revoked approval; downloadable for a limited time).

What signals you can receive

The API can provide : Age verification or supervision status
Age ranges (via ageLower/ageUpper) used to gate features/content
Other applicable age-assurance signals defined by Google Play

Implementation Steps

Implementation (high level)

1) Add the dependency

// app/build.gradle

dependencies {

    implementation “com.google.android.play:age-signals:0.0.1-beta02”

}

(Version as of Oct 2025; check for updates.)  

2) Request age signals in your app
Call the client-side API and handle Age Signals Result (including unknown/unavailable cases). Before Jan 1, 2026, calls will throw until live responses begin.  

3) Handle edge cases
Users who are neither verified nor supervised in applicable regions may return UNKNOWN; direct them to resolve status in Play Store if needed. 

4) Testing before go-live
Use Fake Age Signals Manager to simulate responses in unit/early integration tests. It’s self-contained and does not hit Play back-end services.  

5) Play Console workflow
When your app has a significant change that would require parental re-approval, submit that in Play Console; also monitor the Revoked app approvals tab for any revocations. 

Developer FAQs

Is this mandatory for every app?
No, universal mandate is stated in the docs. It’s provided to help you meet obligations where applicable laws apply to your app and users. Review your audience/features and jurisdictions.  

Does it verify identity itself?
No. It exposes Google Play’s signals (age verification/supervision/age range). You must design your app’s behavior (gating, approvals, restrictions) around those signals. 

Is it part of Play Billing or “app store billing laws”?
No. The API is separate from billing/monetization changes and exists to support age-assurance compliance. 

Sources 

• Android Developers—Play Age Signals (beta) Overview and purpose. (Android Developers)
  
• Android Developers—Use Play Age Signals API (beta) (exceptions until Jan 1, 2026; integration). (Android Developers)
  
• Google Support—Changes to Google Play for upcoming app store bills (states & dates; features). (Google Help)
  
• Android Developers—Notify significant changes (Play Console). (Android Developers)
  
• Android Developers—Review revoked app approvals (Play Console). (Android Developers)
  

Android Developers—API references (Age Signals Result, testing with Fake Age Signals Manager). (Android Developers)

About the Authors

Sigosoft Android Engineering Team
At Sigosoft, we’ve spent over a decade helping global clients build, scale, and monetize Android apps. Our developers specialize in Google Play ecosystem compliance and building future-ready mobile architectures that adapt to evolving regulations effortlessly.

Disclaimer

This article is for informational purposes only and does not constitute legal advice. Always review your app’s compliance with U.S. state laws and Google Play policies before publishing or updating your app.