Google Play age Signals API policy: fixes and checks
By The Draftbit team · Updated
Sources checked
This guide is for Google Play apps using age or parental-consent information from the Age Signals API.
Age Signals data is for meeting applicable legal and regulatory obligations, such as providing appropriate age-based experiences. Google prohibits using it for advertising, marketing, personalization, analytics, profiling, or business intelligence.
Trace the response beyond the gate
Inspect logs, analytics events, account profiles, and third-party requests. We’d check default event logging before integrating the response into an ordinary user model; that can share more than the age-control feature needs.
Limit use and sharing
Keep the data confined to its permitted compliance purpose. Selling, sharing, or transferring it to third parties is prohibited except when strictly required by law. A general analytics disclosure doesn’t authorize it.
Test different age/consent responses with fictional fixtures and inspect outgoing events. Give Google the compliance purpose, data destinations, and correction. Don’t expose actual users’ age or parental-consent records in evidence.
Messages this guide can help with
Age Signals API; Age Signals API policy violation; Age Signals API rejection; Age Signals API denied
Official sources
We checked these instructions against the sources below. The console layout may change, and your review decision may call for different steps.
- Google Play: Age Signals API Checked 22 September 2026