Google Play Impersonation policy rejection: app names, icons and developer names that look like someone else's

Google thinks your app looks like something it is not. Usually that means your title, icon or developer name resembles an established brand, a well-known app, or an official body closely enough that a user scrolling Play could mistake one for the other. The policy does not require that you intended it.

How it is worded

This almost always arrives as a policy email rather than a console message, and it names the policy but rarely the specific element:

"Your app impersonates another app, developer, or entity."

"Your app's title, icon, or developer name may mislead users about its relationship to another product or service."

The published policy is short and worth reading in full. Its opening line is the whole test:

"We don't allow apps that mislead users by impersonating someone else (for example, another developer, company, entity) or another app."

And the scope:

"app icons, descriptions, titles, or in-app elements that could mislead users about your app's relationship to someone else or another app"

What it means

Four distinct things get bundled under one policy name, and knowing which one you were hit with decides your fix.

Confusing similarity. The policy prohibits "App titles and icons that are so similar to those of existing products or services that users may be misled". This is the one that catches honest developers. You built a habit tracker, called it something obvious, picked a clean icon, and it landed next to an app with a similar name and a similar glyph in a similar colour.

Unauthorised brand or trademark use. Using someone else's name, logo or product name in your title, icon, screenshots or description without the rights to do so. This includes the softer versions: "for Instagram", "unofficial Netflix", a football club crest in a screenshot.

False affiliation. Implying a relationship you do not have. A developer name that reads like a bank, a government department, or a platform vendor. The policy calls out national emblems and the logos of recognised businesses.

Claiming to be a person. The policy's own example: "Titles like 'Justin Bieber Official' are not allowed without the necessary permissions or rights." Fan apps are the usual offender.

Note that the developer name is in scope, not just the app. An account named so it reads as a subsidiary of a known company violates the policy on its own, even if every app under it is clearly named.

Why it happens

• Your name is a near-miss on an existing app. Two-word compounds in a crowded category collide constantly. Check Play search for your exact title before you ship, not after.
• The icon is generic in the same way as someone else's. A white glyph on a blue-to-purple gradient is a genre convention, and Play sees a lot of them. Similarity of style is not the problem; similarity that could be mistaken is.
• You used a platform name to describe compatibility. "Client for X", "X downloader", "Widgets for X". Some platforms permit this in their brand guidelines with a specific format, most do not, and Play will not check for you.
• A trademark holder complained. Play acts on third-party notices, and enforcement then arrives with no warning against an app that has been live for years.
• You put a real brand in a screenshot. Mock-ups showing your app integrating with a named service, or a device frame with another company's logo visible.
• Your developer name contains a word with an owner. Adding "Labs", "Studio" or "Technologies" to a trademarked word does not make it yours.
• The app is a fan app. Even a non-commercial one. Affection is not a licence.

How to fix it

1. Work out which element was cited. Read the email for the specific asset. If it names none, compare all four candidates yourself: app title, icon, developer name, and any brand appearing in screenshots or description.
2. Search Play for your exact title, then the obvious variants. Note anything in the first two rows with a name or icon in the same neighbourhood as yours. That is the comparison a reviewer made.
3. Rename with distance, not with a suffix. "Pro", "2", "Plus" or a space does not create separation. Change a word. The safest rename is one where a user searching for the other app would never land on yours.
4. Redraw the icon so the silhouette differs. Reviewers compare thumbnails at small sizes, where colour and shape read before detail. Change the shape first, then the palette.
5. Strip third-party marks from every asset. Title, subtitle, short description, full description, screenshots, feature graphic, in-app splash. Where you need to state compatibility, use functional language that names no brand, or the exact format that brand's guidelines permit if it permits one.
6. Fix the developer name if that was the finding. This is changed in Play Console under Settings > Developer account > Account details, and it propagates to every listing you have.
7. Gather your permission if you have it. A trademark licence, a brand-use agreement, or written consent from the rights holder, in a form you can attach.
8. Check your other apps. Impersonation findings are usually pattern findings. If one listing tripped it, the sibling built from the same template will too.

Appeal, or change the listing?

Appeal when you hold the rights, or when the similarity is coincidental and you can show it. A good appeal is factual and short. State what you own or what you changed, attach the evidence, and name the app you are alleged to resemble so the reviewer is looking at the same comparison you are.

Do not appeal a name you chose because it borrowed recognition. If the app is called something adjacent to a famous product because that helps discovery, Google is looking at exactly what you did. Rename and resubmit, which is faster than an appeal you will lose.

If the enforcement came from a trademark holder's complaint rather than a policy sweep, the fastest resolution is often the rights holder withdrawing it. Contact them, agree what you will change, and mention that agreement in your appeal.

Be ready for one frustration: you may never learn which app yours was compared to. Google does not routinely name it, and asking rarely produces an answer. So the reliable fix is to make the listing distinctive enough that the question stops arising, rather than to argue about degrees of similarity.

AppSubmit checks a title and icon against the live Play and App Store results for the same terms before you submit, and flags near-collisions in the top rows. It is the same search you can run by hand in the store app; the value is only that it happens before the rejection rather than after.