App Store RejectionGuideline Google Play — Deceptive Behavior — Deceptive Behavior Policy

Google flagged your app as deceptive. Here's what that actually means.

Deceptive behavior covers a wide range: fake UI elements, impersonation, misleading functionality claims, and dark patterns. Google Play takes this seriously and rejections under this policy can escalate to account-level action if not handled properly. Here's how to address it.

What Apple said

“Your app has been found to violate the Deceptive Behavior policy. Your app contains elements that deceive users, including interface elements designed to mislead users into unintended actions or misrepresentation of the app's core functionality.”

What this actually means

Google's deceptive behavior policy catches apps that trick users — fake close buttons that open ads, subscription flows designed to confuse, functionality that's completely different from what the listing promises, or UI that mimics system dialogs. Even if it was unintentional, these patterns will get you rejected.

What Apple needs to see

  • Every interactive element in the app works as a user would reasonably expect it to
  • No fake system dialogs, fake notifications, or simulated OS-level UI that misleads users
  • Subscription and purchase flows that are transparent about price, terms, and renewal
  • App functionality that matches what your store listing and screenshots describe
  1. 1Walk through your app as a first-time user and identify any moment where a user might be confused about what a button or UI element does
  2. 2Remove any ad units that use close buttons positioned to redirect clicks, overlapping fake system UI, or auto-expanding interstitials
  3. 3Audit your subscription flow — the price, billing period, and cancellation method must be clearly visible before the user confirms purchase
  4. 4Update your terms of service to clearly explain any subscription terms, auto-renewal, and cancellation policy — BaseTerms generates terms that include compliant subscription disclosure language
  5. 5Compare your app's actual functionality to your store listing screenshots and description and remove or update anything that overstates what the app does

While you're at it — Apple also requires these pages for every app.

Fix this rejection, then make sure you're covered on the compliance side too. Apple requires every app to link to a hosted Privacy Policy, Terms of Service, Support page, and Data Deletion page. No link means another rejection — just for a different reason.

Privacy Policy
Terms of Service
Support Page
Data Deletion Page
Generate my compliance pages — FREE

Common questions

Can I appeal a Deceptive Behavior rejection?
Yes, but the bar is high. Appeals work best when the reviewer misunderstood a legitimate UI pattern. If there are genuinely deceptive elements, fix them first, then appeal with a clear explanation of what you changed and why the remaining app is honest and transparent.
My dark pattern was in a third-party ad SDK — am I still responsible?
Yes. Google holds you responsible for the behavior of every SDK in your app. Review your ad network's creative policies and ensure you're using their ads in compliant placements. Some ad networks have specific SDK configuration options to disable deceptive ad formats.
What's the difference between a firm CTA and a dark pattern?
A firm call to action is clear about what it does. A dark pattern is designed to obscure the real outcome. A button that says 'Start Free Trial' leading to a subscription is fine if the terms are displayed. A button that says 'Continue' that quietly starts a subscription without visible terms is a dark pattern.