Howdy, Stranger!
It looks like you're new here. If you want to get involved, click one of these buttons!
Quick Links
Categories
- 7.8K All Categories
- 12 Help with translations
- 4.3K General questions
- 107 Roadmap
- 359 Game & application design
- 322 Plugins
- 71 User experience
- 75 Marketplace
- 294 Code snippets
- 34 Building a team?
- 269 Suggestions & requests
- 352 Announce your apps made with Gideros.
- 91 Step by step tutorials
- 677 Bugs and issues
- 195 Introduce yourself
- 246 Announcements
- 107 Forum talk
- 405 Relax cafe
Android (& probably iOS too) Introducing Play Age Signals API (beta): Supporting you...
MobAmuse
Member
Endless new policy stuff of late it seems 
Service update
Hi Google Play Developer,
You are receiving this email because you have at least one app on Google Play that is available to or used by users in the U.S.
What’s happening
A few U.S. states, currently Texas, Utah, and Louisiana, have recently passed verification laws requiring app stores to verify users’ ages, obtain parental approval, and provide users’ age information to developers. These laws also create new obligations for developers who distribute their apps through app stores in these states.
Our plan to support you
While we have user privacy and trust concerns with these new verification laws, Google Play is designing APIs, systems, and tools to help you meet your obligations.
The first verification law to take effect is Texas’s SB 2420 on January 1, 2026. Given short implementation timelines, we are sharing details about the Play Age Signals API (beta) and have made the API integration guide available to you.
What this means for you
These laws impose significant new requirements on many apps that may need to provide age appropriate experiences to users in these states. These requirements include ingesting users’ age ranges and parental approval status for significant changes from app stores and notifying app stores of significant changes. It is important that you review these laws and understand your obligations.
If you have any additional questions, please contact our support team.
Thank you,
Your Google Play team
https://support.google.com/googleplay/android-developer/answer/7550024?hl=en
https://developer.android.com/google/play/age-signals/overview
Service update
Hi Google Play Developer,
You are receiving this email because you have at least one app on Google Play that is available to or used by users in the U.S.
What’s happening
A few U.S. states, currently Texas, Utah, and Louisiana, have recently passed verification laws requiring app stores to verify users’ ages, obtain parental approval, and provide users’ age information to developers. These laws also create new obligations for developers who distribute their apps through app stores in these states.
Our plan to support you
While we have user privacy and trust concerns with these new verification laws, Google Play is designing APIs, systems, and tools to help you meet your obligations.
The first verification law to take effect is Texas’s SB 2420 on January 1, 2026. Given short implementation timelines, we are sharing details about the Play Age Signals API (beta) and have made the API integration guide available to you.
What this means for you
These laws impose significant new requirements on many apps that may need to provide age appropriate experiences to users in these states. These requirements include ingesting users’ age ranges and parental approval status for significant changes from app stores and notifying app stores of significant changes. It is important that you review these laws and understand your obligations.
If you have any additional questions, please contact our support team.
Thank you,
Your Google Play team
https://support.google.com/googleplay/android-developer/answer/7550024?hl=en
https://developer.android.com/google/play/age-signals/overview
Comments
1) Doesn't compile for some methods
2) Just does nothing at all beside throwing a "Not yet implemented" exception.
It is completely useless for anything even just testing. How come they sent this message to every Android developer in the world as if there was something we could actually do to get ready ?
Likes: pie
I think that they are not even sure what to do about it exactly yet TBH.
I was just giving the heads up before next year, but it seems too early to make an informed decision on this requirement yet. Looks like Apple have to do the same in due course tho.
Likes: keszegh, MobAmuse, pie