Google Play deceptive Behavior policy: fixes and checks
By The Draftbit team · Updated
Sources checked
This guide is for Apps whose claims, settings changes, or actual behavior may mislead users.
A Deceptive Behavior rejection means Google found a mismatch between what users are told and what the app does. That can be an impossible feature claim, a disguised warning, a hidden feature, or a device change the user didn’t agree to.
What to check
Compare the store listing with a fresh install. Include screenshots, videos, onboarding, paywalls, ads, and remote configuration. Can a user tell what each action does before taking it?
Review changes outside your app, such as browser settings or home-screen shortcuts. Consent needs to match the change, and users need a way to reverse it.
How to address the rejection
Fix the behavior and the claims together. Remove simulated system warnings, disclose meaningful limitations, and document features that reviewers might otherwise miss.
Use the specific child policy named in the notice to narrow your investigation. A misleading screenshot and hidden review-evasion logic need different fixes. In review notes, describe the exact mismatch you corrected and the steps that demonstrate the corrected experience.
Messages this guide can help with
Deceptive Behavior; Deceptive Behavior policy violation; Deceptive Behavior rejection; Deceptive Behavior 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: Deceptive Behavior Checked 22 September 2026