โ† Go back

How Do You Report an Impersonation App to the App Stores?

Published 2026-11-14 ยท Reviewed 2026-11-14 ยท By the Ingenious AI team

The short answer

Record the app's store URL, developer name and screenshots showing your brand assets in use, then file under Impersonation/IP โ€” not a generic content report โ€” through App Store Connect's IP inquiry or Google Play's impersonation report, with trademark evidence attached. Note any in-app links to the lookalike domain, and monitor store search for your brand weekly, because clones reappear under new developer accounts.

Run the free brand scan โ€” one domain, no account, no card

What is an impersonation app report?

An impersonation app is a mobile app that trades on your brand โ€” your name, logo or service identity โ€” without authorisation, often funnelling users to a lookalike domain. App stores are one of TakedownCoop's six packet channels, filed by the brand owner or their agent through each store's IP route.

What is an impersonation app report?

An impersonation app is a mobile app that trades on your brand โ€” your name, logo or service identity โ€” without authorisation, often funnelling users to a lookalike domain. App stores are one of TakedownCoop's six packet channels, filed by the brand owner or their agent through each store's IP route.

The scan behind this page works in one pass over your whole street. It generates typosquat, homoglyph, affix and TLD-swap candidates from your domain, checks every one against real DNS resolution, searches Certificate Transparency logs for lookalike certificates, and tries a public, no-login check for fake profiles using your exact brand handle. For an impersonation app report, that means the first artefact you work from is evidence โ€” what resolved, what holds a certificate, what could not be checked โ€” rather than a screenshot someone sent you.

How the scan ranks and records it

Prioritisation is built into the result list. A hit that resolves and holds a certificate scores 90; resolving without a certificate, 80; registered but not resolving, 50 with a certificate and 40 without; a name seen only in Certificate Transparency logs scores 35, or 30 when it neither resolves nor is registered. You therefore deal with an impersonation app report in the order an impersonator would exploit it โ€” live doors first โ€” while the scan states plainly which checks it could not perform.

File it as impersonation, not as a content complaint

The app-store checklist makes one routing point above all: file under Impersonation/IP, not a generic content report. The category decides which team and which evidence standard your report meets; a clone app reported as 'offensive content' is judged by the wrong test. The packet's subject line models the right framing โ€” an impersonation app trading on your brand, with the associated lookalike domain named.

The second point is recurrence. Clones reappear under new developer accounts, so the checklist's last step is a weekly watch on store search for your brand. TakedownCoop's part in that loop is the domain side: the in-app link to a lookalike domain lands in the same evidence block and the same case, so the app report and the registrar report reinforce each other instead of living in separate inboxes.

A worked example, end to end

A fictional fitness studio, Corehouse at corehousefit.com, finds a booking app using its name and class photos, built by a developer it has never heard of, with a 'member login' linking to corehouse-fit-login.com. The owner records the store URL and developer name, screenshots the listing and the login link, and files under Impersonation/IP with trademark evidence, naming the lookalike domain in the report. The domain itself scores 80 on the scan and gets its own registrar packet, and a case is opened for each target โ€” app and domain โ€” under one brand.

Turning evidence into a filing

A complaint says 'this is fake'; a packet proves it. The Pro packet generator turns a confirmed hit into a channel-correct evidence packet โ€” one for the registrar, one for the host, and separate ones for Meta, Google Ads, marketplaces and app stores where they apply โ€” each with a filing checklist written for that channel. The honesty rule is printed in every packet: TakedownCoop prepares the evidence and never claims to submit to a channel it cannot actually submit to. Filing stays with you or your agent, which is also why the evidence has to stand on its own.

  1. Record the app's store URL, developer name, and screenshots showing your brand assets in use
  2. File under Impersonation/IP (not a generic content report) and attach trademark evidence
  3. Note any in-app links to the lookalike domain from the evidence block
  4. Monitor store search for your brand weekly โ€” clones reappear under new developer accounts
  5. Open linked cases for the app and the domain so both filings cite the same evidence

After you file: tracking the case

What happens next is tracked, not hoped for. Each target becomes a case โ€” domain, fake store, social profile or scam ad โ€” moving through evidence collected, packet built, submitted, provider response, resolved or reappeared. TakedownCoop distinguishes what you attest (that you submitted, that a provider replied) from what is verified by re-scan (that the item is actually gone), and it schedules a recheck seven days after a case is submitted so silence from a provider becomes a prompt, not a dead end.

Where efforts like this usually go wrong

A second failure is overreach โ€” padding a filing with suspicions the evidence does not carry. TakedownCoop's scan is careful to separate what it confirmed from what it could not check, and a filing should inherit that discipline exactly: claim the resolving domain, the certificate, the screenshots you actually hold, and stop there. Reviewers act fastest on filings whose every sentence they can verify, and a single inflated claim taxes all the true ones beside it.

Finally, do not let a win delete the record. Brands that close a takedown by celebrating and clearing the folder meet the reappearance defenceless; brands that keep the case โ€” evidence, tickets, verified resolution and all โ€” meet it with precedent. In this product the record is not paperwork after the work. Kept properly, it is most of the work, because the second filing is always the one that ends the pattern.

Keeping it from coming back

Closing the loop matters because clones come back under new names and new accounts. Re-appearance monitoring re-scans and regenerates packets; the verified-genuine page lets a cautious customer verify your real door before paying anyone; and the case timeline โ€” every event, in order โ€” exports as JSON or CSV when a processor, insurer or marketplace asks how you handled it. That is the co-op model applied to an impersonation app report: walk the street, knock with evidence, keep watch.

Frequently asked questions

Which store route do I use?

App Store Connect's IP inquiry for Apple, and Google Play's impersonation report โ€” filed under Impersonation/IP, per the packet checklist.

Why does the category matter?

A generic content report is judged by content standards. An impersonation/IP filing is judged on your brand rights and trademark evidence.

What if the clone returns under a new developer name?

That is the expected pattern โ€” the checklist says clones reappear under new developer accounts, which is why weekly store-search monitoring is part of the routine.

Does the lookalike domain belong in the app report?

Yes. Note any in-app links to it; the domain is separate evidence and gets its own registrar and host packets.

Keep exploring

TakedownCoop home โ€” run the free brand scan ยท All TakedownCoop guides ยท Pricing โ€” Free, Pro and Agency ยท Get a license key ยท Takedown cases ยท My street (dashboard) ยท Terms ยท Privacy ยท Ingenious AI โ€” all platforms

Related guides