Why Google Flags Apps for "Deceptive Behavior" and How to Avoid It
Google Play's deceptive behavior policy covers a broad set of issues: impersonating another app or brand, misleading claims in your listing, or functionality that doesn't match what's described. It's a common but vague-feeling rejection reason because it covers so much ground.
A frequent, avoidable trigger: using another well-known app's name, icon style, or screenshots that closely mimic a competitor, even unintentionally through template reuse.
The fix
Fix: have someone unfamiliar with your app review your icon, title, and screenshots side by side with any app you might resemble, before submission — not after a rejection.
The same check runs automatically when you upload your bundle to the AAB analyzer — permissions, SDK fingerprints, and version info in one pass, free.
Keep going
Run this check on your own AAB
Free analysis, exports when you need them.