# Report a Fake App Impersonating Your Brand

Report a fake app or extension that impersonates your brand: the right form on each store, the evidence to attach and what to do while it is live.

---


To report a fake app that impersonates your brand, use the store's own route, not only a user flag: Apple's App Store Content Dispute form for trademark claims and its Report an app form for other concerns, Google Play's trademark or flagging routes, and each browser store's report or legal form for extensions. Attach proof that the listing copies your name, logo or identity, and proof that you own the rights you are asserting.

Which route fits depends on what the fake copies. A listing that uses your registered name or logo is a trademark matter. A listing that only pretends to be you, with no protected mark involved, is an impersonation matter, and stores handle that through a different door. Choosing the wrong one is the most common reason a report stalls.

This guide covers the Apple App Store, Google Play, the Chrome Web Store, Firefox add-ons and Microsoft Edge Add-ons. It states what each store's own pages say, as of the pages read for this guide, and flags where a page says nothing. Policies change, so check the linked page before you file.

<div class="box"><b>The short version</b>
<ul><li>Pick the route by what the fake copies: a protected name or logo goes to the store's trademark or IP form, a pretender with no mark involved goes to its impersonation or flagging route.</li><li>Build one evidence file first: listing links, store IDs, screenshots with dates, your proof of rights, and a statement of what is copied.</li><li>Expect Apple to pass your name, email and comments to the developer, so write every field as if the other side will read it.</li><li>None of the store pages read for this guide gives a review timeline to the person reporting, so plan the weeks before removal as a live exposure period.</li><li>While the listing is live, publish your official store links, brief your support team, and report on every store the clone appears on.</li></ul></div>

## Match the report to what the fake copies

Choose the trademark route when the fake uses your name, logo or product name, and the impersonation route when it pretends to be you without using a protected mark. The two routes sit in different forms, and Google Play warns about this directly: its impersonation FAQ says to use the correct reporting form because incorrect submissions may delay or prevent processing.

Three cases cover most files:

- **The fake uses your registered brand name or logo.** This is a trademark claim. It goes to the store's IP form.
- **The fake uses a name close to yours, with a similar icon.** It is both. File under trademark if you own the mark, and flag the impersonation too where the store separates them.
- **The fake claims to be official but uses no mark you own,** for example a personal name, a public-figure persona or an unregistered product label. Trademark forms may not fit. Use the store's impersonation or flag route, and take advice on whether a mark can be registered for the future.

A registered mark makes the file simpler, because you can name the mark and the office that holds it. Whether you hold enforceable rights in an unregistered name differs by country, so that question belongs to your own counsel.

<aside class="callout">
<span class="callout-label">Rule</span>
<h4>Only file what you can stand behind</h4>
<p>Apple's form asks you to declare under penalty of perjury that you own the rights or act for the owner, and Mozilla's page warns that a notice with material misrepresentations can bring liability. File on facts you can show, and keep your own counsel in the loop if the mark is contested.</p>
</aside>

## Build the evidence file before you report anything

A strong report identifies the listing exactly, shows what it copies, and proves you hold the rights. Gather it once, then reuse it on every store.

For the listing itself, save:

- The full store URL and the technical identifier in it: the app ID on Apple, the package name on Google Play, the extension ID on browser stores.
- The developer name and any contact details or website the listing shows.
- Dated screenshots of the title, icon, screenshots, description and reviews, saved the day you find it, because listings change or vanish.
- The same details for every other listing from the same developer, because clones often come in sets.

For your side, save your trademark registrations (number and office) if you have them, your official app and extension links, the dates your own listings went live, and any user messages showing people were misled.

Do not install the fake on a device you use for work. If you must see inside, use a spare device that holds none of your accounts, or leave it to a security team. The listing alone is enough for most reports.

## Apple App Store: the dispute forms and the Report an app form

For an iPhone or iPad app, use Apple's App Store Content Dispute form if the app violates your intellectual property, and its App Name Dispute form if an app is blocking you from using your trademark as an app name. For a pretender with no mark behind the claim, Apple publishes a separate Report an app form. Apple's App Review Guidelines point rights holders to the web form.

The guidelines give you the standards to cite. Sub-section 4.1(b) says that submitting apps which impersonate other apps or services is a violation of the Developer Code of Conduct that may result in removal from the Apple Developer Program. Sub-section 4.1(c) says you cannot use another developer's icon, brand or product name in your app's icon or name without approval. Section 5.2.1 bars protected third-party material such as trademarks without permission, and misleading or copycat names or metadata, including in the developer name.

What the Apple Content Dispute form shows, as read for this guide:

- A required rights owner and submitter, with a checkbox for an authorized agent, such as a firm acting for the owner.
- Links to the disputed app, with up to 50 apps in one dispute.
- A required description and a required Trademark field. The form has no evidence upload: it says attachments can be sent by email once the dispute is opened.
- A declaration, under penalty of perjury, that you are the owner or an authorized agent.
- Sharing: your name and email go to the app provider, and the form says anything in the comments field is shared with the provider of the app selected.

After you submit, Apple says it contacts the provider of the disputed content and asks them to work with you directly. For a name dispute, it says that in most cases it contacts the providers of the apps blocking the name. No response time appears on these pages, and Apple states that it does not investigate claims about branded terms used as Search Ads keywords.

Apple's Report an app page covers an app that presents a trust or safety concern or does not meet the App Review Guidelines. It asks for identifying information such as the App Store URL, a specific description of what you observed, and the guidelines you believe the app does not meet, so cite 4.1(b) or 4.1(c). It does not name impersonation or fraud, and it says App Review cannot share the outcome of an investigation into another developer's app with you.

## Google Play: flag it, then use the right legal form

On Google Play, flag the listing for a policy violation and, where you own a trademark, send a trademark complaint. The two are separate tracks and can run together.

The Google Play impersonation policy says apps must not impersonate or misrepresent their identity, ownership or primary purpose, and must not suggest a relationship or authorization that does not exist. Its examples include a copied business logo that implies an official app, an icon or title confusingly close to an existing product, and false "official" claims: a title like "Justin Bieber Official" is not allowed without the necessary permissions or rights.

Google Play's intellectual property policy says it does not allow apps that infringe trademarks, defined as improper or unauthorized use of an identical or similar trademark that is likely to cause confusion about a product's source. That page encourages trademark owners to contact the developer directly first and, if that does not resolve it, to submit a complaint through Google's trademark form. A counterfeit notice form and a copyright route also exist for those separate problems.

For the flag, Google's Play help page gives these steps in the Android app: open the app's detail page, tap More, tap Flag as inappropriate, choose a reason, and submit. It says flagging reports an issue or policy violation to Google's team for review and potential action, and the steps read for this guide are those for the Android app.

The Play impersonation FAQ adds a split worth using: if you do not assert intellectual property rights over the content, report through the general flagging process; if you do, use the copyright, trademark or other legal forms. It also recommends consulting your own counsel on the differences between trademark, copyright and impersonation.

Contacting the developer first is a judgment call. With a competitor that copied you by accident, a direct message can resolve it fast. With a fraud operation, it warns them and gives them time to republish. When the listing collects logins or payments, skip it.

## Chrome Web Store: Flag Issue and the legal form

In the Chrome Web Store, use Flag Issue for policy violations and the linked legal form for trademark or copyright. The Chrome Web Store flagging page gives the steps: sign in, open the item, click Flag Issue at the bottom left, complete the form and submit. It sends copyright and trademark infringement to a separate legal form instead of the Flag Issue button, and for legal reports it says the team reviews the report and takes any necessary action.

Chrome's program policies are the standards to cite. They say not to pretend to be someone else and not to infringe the intellectual property rights of others, and that a product's visibility may be affected if Google believes it potentially infringes. The developer troubleshooting page lists "the extension impersonates another entity" as a common reason for removal.

## Firefox and Microsoft Edge: two different doors

Firefox separates abuse from legal claims, and Edge's published help page covers only copyright and trademark reports. In both, name the right route in your report.

**Firefox add-ons.** Mozilla's reporting page describes reporting from the add-on's page on addons.mozilla.org or from inside Firefox. The closest category to impersonation is "Pretends to be something it's not," which covers false or misleading descriptions and imagery. The page says copyright and trademark issues must be reported in a separate process. Mozilla's infringement page describes a Trademark Notice handled like a copyright notice, which carries a statement under penalty of perjury, but it does not mention add-ons, so confirm the route when you file. Confirmed abuse leads to removal from the site until the developer fixes the issues.

**Microsoft Edge Add-ons.** Microsoft's extensions contact page says that if you think an item violates a copyright or trademark, you complete the Reporting Infringement form and, in Step 3, select Microsoft Store on Windows under Product/Service/App. That page describes no separate impersonation route and no timeline, so trademark is the practical basis there.

## Which route to use on each store

The table sets the routes side by side. Where it says not stated, the pages read for this guide did not state it.

<div class="tablewrap"><table><thead><tr><th>Store</th><th>Impersonation route</th><th>Trademark route</th><th>Stated timeline</th></tr></thead><tbody>
<tr><td><strong>Apple App Store</strong></td><td>Report an app form, citing the guideline</td><td>Content Dispute or Name Dispute form</td><td>None stated</td></tr>
<tr><td><strong>Google Play</strong></td><td>Flag as inappropriate in the app</td><td>Trademark complaint form</td><td>None stated</td></tr>
<tr><td><strong>Chrome Web Store</strong></td><td>Flag Issue on the item</td><td>Legal form, shared with copyright</td><td>None for reporters</td></tr>
<tr><td><strong>Firefox add-ons</strong></td><td>Report with the "Pretends to be something it's not" reason</td><td>Separate infringement notice</td><td>None stated</td></tr>
<tr><td><strong>Edge Add-ons</strong></td><td>Not described on the page read</td><td>Reporting Infringement form</td><td>None stated</td></tr>
</tbody></table></div>

No store read here promises a removal time to the person reporting. Plan around that gap.

## What to do while the listing is live

While the fake is up, protect your users directly, in parallel with the reports.

1. **Publish your official links.** Put the exact store links to your real app or extension on your own site, in your email footer and on your verified social profiles, with a plain line that these are the only official versions.
2. **Brief support.** Give your support and social teams a short script: how to tell the real listing from the fake, and what to ask a user who installed it.
3. **If the fake takes logins or money, say what to do.** Tell affected users to remove it, change the passwords they used in it, and contact their bank or payment provider for any payment made.
4. **Watch for the clone elsewhere.** The same developer often appears on several stores, or returns under a new name. Search each store for your brand name, product names and common misspellings, and set up <a href="/reputation-monitoring">monitoring</a> so you hear about the next one quickly.
5. **Mind what you say in public.** Name the facts (this listing is not ours) and avoid accusing a named person or company without evidence.

A fake that ranks for your name can also shape what search engines and AI assistants say about you, which is why this belongs in a reputation plan and not only a legal one.

## A realistic first month, with one worked scenario

Stores usually act in days to a few weeks on a clear trademark file, and longer when the claim is thin or contested. That range is our experience, not a promise and not a store statement.

Take a fictional scenario: a payments brand, Northline Pay, finds an Android app and a browser extension called "Northline Pay Official" on the same day. Both copy its logo. Assumptions: Northline holds a registered mark, the app asks for a card number, and no store has contacted it.

<figure class="fig">
<figcaption><b>First month for the Northline Pay scenario</b></figcaption>
<ol class="fig-steps">
<li><b>Day 0: capture</b>Save both listings with IDs, dates and screenshots. Do not install either on a work device.</li>
<li><b>Day 0 to 1: report</b>Flag the app on Google Play and send the trademark complaint. Flag the extension on the Chrome Web Store and use its legal form. Search the other stores for the same developer.</li>
<li><b>Day 1: warn</b>Post the official links and a short notice on the brand's own channels, and brief support.</li>
<li><b>Day 3 to 7: follow up</b>Check each listing. If it is still live, add anything new (more reviews, a new website, a payment complaint) to the existing report rather than opening duplicates.</li>
<li><b>Week 2 to 4: escalate</b>If a store has not acted, restate the specific policy line and trademark, and bring in counsel on a direct notice to the developer or the developer's website host.</li>
<li><b>After removal: verify</b>Confirm the listing is gone from search inside the store, and keep watching for a re-upload under a new name.</li>
</ol>
</figure>

## When the store refuses or the clone comes back

If a store declines your report, the usual cause is a mismatch between the claim and the form, or too little proof of rights. Read the response, fix the specific gap, and resubmit with the policy line cited.

A re-upload under a new name needs a fresh report, but cite the earlier one and show the link between the two listings: the same developer details, the same icon, the same website. A pattern is stronger than a single listing, and Apple's form lets you list up to 50 apps in one dispute.

If the developer's site is separate from the store listing, that is a second target, with its own host and domain registrar. The rules differ by provider and country, so take advice before sending a legal threat.

Do not use fake reviews, mass flagging by staff or bought pressure to push a store to act. Those tactics can breach store rules and be turned against you.

## What to do today

Capture the listing, choose the route by what it copies, and file on every store where it appears. If the file is contested, or the fake is already harming customers, Reputation Partners can run a private audit of what is live, which stores to file on and what to say publicly.

<div class="box hot"><b>If this is happening to you now</b>
<p>Save the listings, file on the stores that carry them, and publish your official links today. If you want a second pair of eyes on the evidence and the order of reports, start with a private audit at <a href="/audit">the audit page</a>.</p></div>

## Questions people ask

### Can I report a fake app if I have no registered trademark?

Yes, you can flag it or use Apple's Report an app form, but the legal forms are built around rights you can name. Google Play says to use general flagging if you do not assert intellectual property rights. A registered mark makes a trademark complaint stronger. Ask counsel whether an unregistered name gives you rights in your country.

### Does the developer see my report?

Sometimes. On Apple's dispute form, yes: the form says your name and email are supplied to the provider and that the comments field is shared with them. Write it as if the other side will read it, and leave out private data you do not want them to have.

### Can an agency or lawyer file for me?

Apple's dispute form has a checkbox for an authorized agent, such as a firm representing the rights holder, and it still requires the declaration that the filer is authorized. Mozilla's infringement page likewise refers to the owner or a person authorized to act for the owner. Give the agent your proof of rights so the filing can be backed up on request.

### Should I contact the developer before reporting?

Google Play's intellectual property policy encourages trademark owners to try it first. Apple's pages do not require it. For a harmless copy, a message can be quick. For a fraudulent app, it usually only gives the operator time to move, so report first.

### What if the fake is not on a store at all?

Then the store forms do not apply. An app file shared from a website, a message link or a QR code points to a separate host, registrar or messaging platform, each with its own abuse process. Tell users the official links, and report the page and account that distribute it to the service that hosts them.

### How do I stop the same fake coming back under a new name?

You cannot stop an upload, but you can shorten its life. Watch each store for your brand terms, keep your evidence in one file, and report each return with a reference to the earlier case and the matching developer details.
