Google Play prominent disclosure and consent policy: fixes and checks
By The Draftbit team · Updated
Sources checked
This guide is for Google Play apps whose sensitive-data access, collection, use, or sharing may be outside users' reasonable expectations.
A privacy-policy link isn’t a substitute for an explanation at the moment it matters. Google requires prominent in-app disclosure when sensitive-data handling may surprise users, such as collection in the background.
Put the explanation before access
Show it during normal use, before the consent or runtime-permission request. Name the data and explain its use or sharing. Keep it focused on that data handling rather than bundling it with unrelated terms.
We’d test the first launch with network inspection. A disclosure shown after an SDK’s first request is too late to explain that collection beforehand.
Make the choice real
Consent needs a clear affirmative action before access begins. Back, Home, dismissing the screen, or waiting for a message to expire can’t count as agreement. If relying on another legal basis, meet its requirements and Google’s applicable in-app disclosure rules.
Test acceptance, refusal, and returning later. For SDK-related evidence requests, the policy specifies 2 weeks unless Google’s request gives a longer period. Follow the actual notice and supply the screens, request timing, and test steps demonstrating the correction.
Messages this guide can help with
Prominent disclosure and consent; Prominent disclosure and consent policy violation; Prominent disclosure and consent rejection; Prominent disclosure and consent 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: Prominent disclosure and consent Checked 22 September 2026