Google Play Impersonation Policy: What Counts as Impersonation and How to Avoid It
Google's Developer Policy Center puts it in one line: apps must not mislead users by impersonating someone else. The hard part is that "misleading" is judged from the user's point of view — not from your intentions.
Most impersonation flags we see aren't scams. They're companion apps, fan apps and tools for a popular service whose listing borrowed a little too much of the original's identity.
Scope note: SubmitSafe checks your store listing metadata only — title, descriptions, screenshots and listing notes. It does not analyze APK code, SDK behavior or malware. Examples on this page are hypothetical composites, not real apps. Google Play makes all final decisions.
The gap between the rule and how it's read
Developers often assume impersonation means pretending to be another company. In practice, the question is broader: could a reasonable user believe your app is made by, endorsed by or officially connected to someone it isn't? That covers the app name, icon, developer name, screenshots and description together.
A second misunderstanding: adding "unofficial" in small print doesn't cancel out an icon and title that look official. The overall impression is what counts.
Three ways it happens by accident
A stats tracker for a popular online game uses the game's logo as its icon and calls itself "[Game] Stats". The app is genuinely useful, but at a glance it looks like the publisher's own release.
An indie developer publishes a bank-balance widget under the developer name "Mobile Banking Team". No bank is named anywhere, yet a name that generic, next to a finance app, implies an institutional connection.
A messaging app copies the green speech-bubble icon and screenshot layout of a market-leading competitor, hoping to look familiar. Different name, same instant recognition — which is precisely the problem.
Common triggers in a listing
- Another brand's name at the start of your title, so it reads as the brand's product.
- Words like "Official" or "Authorized" without an actual authorization.
- Icons that reuse another company's logo, colour scheme and silhouette together.
- A developer name that mimics a known company or a government body.
- Screenshots taken from the other company's app or marketing.
How to differentiate clearly
- Lead with your own name: "RaidLog — stats for [Game] players" reads very differently from "[Game] Stats".
- Give the icon your own mark and colours; reference the other brand in words, not visuals.
- State the relationship plainly near the top of the description: independent, not affiliated, not endorsed.
- If you do have permission, be ready to show it — keep the written authorization on hand.
Developer identity also matters at account level — for organization accounts, see why your D-U-N-S record must match exactly. If you've already been flagged, the appeal checker covers next steps.
Practical next step
The free listing checker flags third-party brand names, "official" wording and affiliation claims in your title and descriptions. It can't run trademark searches or judge legal rights — treat it as an early warning, not legal advice.
Run your listing past a second pair of eyes
The free checker flags the listing-text patterns described above before a reviewer sees them.