# Deceptive Behavior: Misleading Claims, Hidden Functionality, or Manipulated Reviews

**Guideline:** privacy-security/deceptive-behavior · **Store:** Google Play · **Risk:** medium · **Difficulty:** medium · **Typical turnaround:** 3-10 days for listing-copy fixes; 2-4 weeks for behavioral/technical fixes

Canonical URL: https://appstorereject.com/rejections/google/privacy-security%2Fdeceptive-behavior/deceptive-behavior-misleading-claims-hidden-functionality-or-manipulated-reviews

## Description

Google rejects or removes apps that deceive users through false claims in the store listing (title, icon, screenshots, description), through functionality that isn't disclosed upfront (hidden or dormant features, code dynamically downloaded to add undisclosed behavior), or through manipulated engagement signals like fake or incentivized reviews and ratings. 

It also covers cloaking — showing reviewers a different, compliant version of the app or listing than what real users see — and deceptive device-settings changes made without clear, reversible user consent. This is Google's broadest catch-all enforcement policy, and it's frequently cited alongside a more specific violation (impersonation, UGC, ads) when the underlying problem is that something about the app misrepresents itself to users or to Google's review systems.

## Common variations

- "Your app description makes claims about functionality that cannot be verified or does not exist"
- "Your app contains hidden or undocumented functionality not disclosed to users"
- "We detected review or rating manipulation associated with your app"
- "Issue found: Violation of Deceptive Behavior policy"
- "Your app changes device settings without the user's knowledge or consent"

## Example rejection email

```
Google Play Console

Issue found: Violation of Deceptive Behavior policy

App: [App Name] (com.example.app)

Your app has been removed from Google Play because it violates our Deceptive Behavior policy. We don't allow apps that contain false or misleading information, or that attempt to deceive users about the app's functionality.

Specifically, we found:
- Your app's store listing claims functionality (e.g., "Boosts phone speed by 300%") that your app does not actually perform.

Action required:
Update your app's title, description, screenshots, and in-app claims so they accurately reflect what your app does, then resubmit for review. Repeated or egregious violations of this policy may result in the suspension of your app and a strike against your Google Play Developer account.

If you believe this was an error, you can appeal from the Policy status page in Play Console.

- The Google Play Team
```

## Resolution steps

## How to Fix a Deceptive Behavior Violation
1. **Pin down which sub-category was cited**
   Play Console > Policy status will reference one of: misleading claims, hidden/undocumented functionality, manipulated media, review/rating manipulation, or deceptive device-settings changes. Each needs a different fix.
2. **For misleading store-listing claims**, audit the title, short/full description, icon, and every screenshot against what the app actually does on-device; remove or rewrite any claim (speed boosts, "antivirus," "official," impossible features) you can't literally demonstrate.
3. **For hidden functionality**, remove any dynamically downloaded code path that changes app behavior post-review, or disclose the feature clearly in-app and in the listing before the user encounters it. Google explicitly bans introducing undocumented features via dynamic code loading after approval.
4. **For review/rating manipulation**, stop any incentivized-review campaigns ("rate us 5 stars for a reward") immediately and remove in-app prompts that filter users toward only leaving positive reviews; this pattern is detected algorithmically and is hard to argue away in an appeal.
5. **For deceptive device-settings changes**, add an explicit, standalone consent prompt before changing any setting (default browser, notification permissions, home screen shortcuts) and ensure the change is easily reversible from within your app or system settings.
6. **For cloaking**, ensure the build and listing Google's reviewers see is identical to what ships to real users — no server-side flag that alters behavior based on request origin or user agent.
7. **Resubmit with reviewer notes summarizing the specific change**
   reference the exact claim, feature, or prompt that was corrected so the human or automated reviewer can verify quickly against the original citation.
8. **If suspended with an account strike, appeal from Policy status**
   click Appeal, select the Deceptive Behavior category, and include before/after screenshots; for repeat violations, consider whether the underlying business model (e.g., pay-for-reviews) needs to change, not just the copy.

## Appeal guidance

Listing-copy violations (overstated claims, wrong category) are the easiest to win on appeal — show the corrected text/screenshots and reviewers typically reinstate quickly since the fix is objectively verifiable. Review-manipulation and cloaking violations are much harder to appeal successfully because Google's detection is signal-based (unnatural review timing/velocity, server-side response differences) rather than a single flagged screenshot, so a denial without demonstrable behavior change (stopped campaigns, removed server-side branching) rarely gets reversed. If this is a second or third Deceptive Behavior citation on the same account, treat it as a suspension/termination risk rather than a routine fix-and-resubmit — repeat citations compound toward account strikes faster than any other policy category.

## Before / after examples

**Before:** A "phone cleaner" app's store listing and icon claim it "Boosts speed by 300%" and "Doubles battery life," with before/after speedometer graphics implying measured performance gains the app cannot produce.
**After:** Listing rewritten to "Clears cache and temporary files to free up storage" with screenshots showing the actual storage-freed number, removing all unverifiable performance percentage claims and speedometer imagery.
**Why it works:** Deceptive Behavior fixes require claims to match literally verifiable app behavior — vague performance percentages and implied benchmarks are treated as false claims even without explicit user complaints.

## Common questions

**Can you appeal a privacy-security/deceptive-behavior rejection?**

Listing-copy violations (overstated claims, wrong category) are the easiest to win on appeal — show the corrected text/screenshots and reviewers typically reinstate quickly since the fix is objectively verifiable. Review-manipulation and cloaking violations are much harder to appeal successfully because Google's detection is signal-based (unnatural review timing/velocity, server-side response differences) rather than a single flagged screenshot, so a denial without demonstrable behavior change (stopped campaigns, removed server-side branching) rarely gets reversed. If this is a second or third Deceptive Behavior citation on the same account, treat it as a suspension/termination risk rather than a routine fix-and-resubmit — repeat citations compound toward account strikes faster than any other policy category.

**How long does this typically take to fix?**

Typical turnaround is 3-10 days for listing-copy fixes; 2-4 weeks for behavioral/technical fixes (difficulty: medium). After resubmission, most re-reviews complete within 24-48 hours.

---
*Machine-readable source: https://api.appstorereject.com/api/rejections/detail?slug=deceptive-behavior-misleading-claims-hidden-functionality-or-manipulated-reviews*