Google Play behavior Transparency policy: fixes and checks
By The Draftbit team · Updated
Sources checked
This guide is for Apps with remote configuration, conditional features, or functionality reviewers may not see.
Google prohibits hidden, dormant, or undocumented features and techniques that evade review. Your app’s real behavior needs to be reasonably clear to users and accessible to reviewers.
What to check
Compare review accounts with ordinary accounts. Inspect region checks, device checks, server flags, delayed activation, and code that recognizes a review environment. Include SDK behavior and remotely loaded content.
A feature being disabled at submission doesn’t make it acceptable to hide it until approval.
How to address the rejection
Remove review-evasion logic. Document legitimate conditions and provide the account, region, or setup needed to exercise each feature. Make the listing and review notes match the app that users will receive.
Test the submitted release build against the same backend configuration intended for users. Keep a record of the configuration you tested and the reviewer access instructions. If a feature needs a later policy review, submit the change through the normal process instead of silently enabling it after approval.
Messages this guide can help with
Behavior Transparency; Behavior Transparency policy violation; Behavior Transparency rejection; Behavior Transparency 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: Behavior Transparency Checked 22 September 2026