How to Report an Impersonating App on Google Play

Google expects a sequence: document the listing, try the developer’s published contact, then file through the right channel. The impersonation flag covers misleading apps with no IP rights required; the trademark complaint through Google’s legal troubleshooter is the stronger filing when you hold a registration. Nothing stops you from using both.

Pick the right channel first

Google Play handles two kinds of impersonation complaint, and they are not interchangeable:

• The impersonation flag is a policy report for apps that mislead users about who made them or what they are affiliated with. Google’s Impersonation policy prohibits apps that impersonate another developer, company, or entity, titles and icons so similar that users may be misled, and false claims to be the official app of an established entity. You do not need IP rights for this channel.
• The trademark complaint is a legal route for rights holders. Google’s Intellectual Property policy prohibits apps that infringe trademarks, and the complaint form asks for your registration details.

If you hold a registered mark, the trademark route is the stronger filing. If the app is merely trading on your name without a registration behind you, the impersonation flag is the open door. For apps doing both, there is no rule against using both channels.

Step 1: Document the listing

Capture the record while it is live:

• The Play Store URL and package name (the id= parameter), which identify the listing unambiguously.
• Screenshots of the title, icon, description, and any elements copying your brand.
• Developer identity as shown on the listing, including the published developer contact email, and any other apps in their catalog.

Step 2: Try the developer contact

Google’s own guidance asks trademark owners to reach out to the developer directly before filing. Every Play listing publishes a developer contact under the listing’s developer contact section. A short, factual request to remove your mark from the listing or unpublish the app often resolves a lazy clone quickly, and it creates a paper trail that strengthens the formal report if it comes to that.

Keep a copy of what you send and any reply. If the developer does not respond or refuses, that is the point where the formal channel earns its keep.

Step 3: File the report

• For a policy violation: use the flag-for-review process described in Google’s impersonation FAQs or the report a policy violation page. Describe specifically how the listing misleads users about its affiliation.
• For a trademark complaint: go through Google’s legal troubleshooter, choose Google Play, then the legal route for intellectual property, then trademark. The form asks for your trademark registration number and jurisdiction, and how the listing uses your mark.

After filing, Google reviews against the relevant policy. Outcomes range from requiring the developer to change the listing to removing the app, and repeated or serious violations can terminate the developer’s account entirely.

Why reporting works at scale

Google reports blocking over 1.75 million policy-violating apps from publishing in 2025 and banning more than 80,000 developer accounts, with over 10,000 safety checks run on every published app. Even so, targeted impersonation of a specific brand is exactly what automated review misses, because nothing about the app looks wrong until someone who owns the name objects.

For the iOS counterpart, see reporting an impersonating app on the Apple App Store.

Reports act on apps you have already found. App store monitoring checks Google Play and the App Store daily for listings carrying your brand name, so a copycat app is on record while it is still collecting its first installs.