Google Play age-restricted content and functionality policy: fixes and checks

By The Draftbit team · Updated
Sources checked

This guide is for Google Play apps with real-money gaming, core dating or matchmaking, random chat, or anonymous communication.

Declaring an adult audience isn’t the same as using Google’s required access controls. This policy requires covered apps to use Play Console tools to block minors.

Classify the real feature

Check whether the app’s core purpose is real-money gambling/games/contests, dating or matchmaking, random connections with strangers, or deliberately anonymous communication. We’d examine the actual onboarding and main workflow, not just the store category.

Google distinguishes incidental dating or matchmaking from an app built around it. Incidental features still need appropriate safeguards preventing minors from accessing those features.

Configure and verify the restrictions

Use the applicable Play Console controls and implement the required in-app feature restrictions. Check Child Safety Standards separately; an adults-only product can still fall within that policy.

Test the relevant age states with fictional accounts and inspect the saved console configuration. Give Google the classification, controls used, and route to the restricted feature. Keep regional or account-specific behavior explicit in your review instructions.

Messages this guide can help with

Age-restricted content and functionality; Age-restricted content and functionality policy violation; Age-restricted content and functionality rejection; Age-restricted content and functionality 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.

Your next stepSubmit a Google Play release with working review access