How to report a cloned app

To report a cloned mobile app, preserve the exact store listing and the evidence of impersonation, then choose the reporting route that matches the claim. A platform-policy complaint is different from an intellectual-property claim submitted by an authorized rights holder.

For brand-security teams, the case should identify the app, publisher, affected market, copied brand elements and any observed harmful behavior. A familiar icon or screenshot is a signal to investigate, not proof that every aspect of the app is fraudulent.

How Outtake reports cloned apps autonomously

With Outtake Brand Protection, your team can manage cloned-app investigations and reporting in one platform instead of preparing and filing each supported app-abuse report manually. Outtake's Remediation Agents handle the reporting workflow described in its platform overview.

• Investigate the impersonation. Connect the suspected app with the protected brand and related websites or accounts, rather than treating the listing as an isolated finding.
• Package the evidence. Assemble the app listing and evidence of the misleading affiliation for the receiving provider.
• Submit and escalate. Send supported reports through autonomous remediation and route the case through the provider's escalation process.
• Verify the outcome. Distinguish a submitted report from a confirmed takedown, then investigate connected assets that may remain active.

Your team supplies the brand information and any rights-holder authorization the reporting route requires. The app store still controls enforcement. Removing a listing does not delete copies already installed on devices.

The manual instructions below explain the provider process for teams handling a report themselves. Outtake handles that reporting work on supported, authorized response paths.

Establish what the app claims to be

Compare the suspected listing with your official app inventory. Confirm your legitimate publisher name, store links and app identifiers. Check whether a partner is authorized to publish an app on your behalf before alleging impersonation.

Record the relationship the listing claims. Does its name, icon, description or publisher presentation make it appear official? Does it direct users toward a different website or support channel? Does it request credentials, payment or sensitive permissions during an approved investigation?

Separate visible observations from untested behavior. A store screenshot can establish copied imagery. It cannot establish that the installed app steals credentials unless that behavior has been observed through authorized analysis or supported by other evidence.

Do not install a suspected app on a personal phone, production device or device containing customer information. Use your security team's approved mobile-analysis environment if testing is necessary.

Capture an app-specific evidence record

Generic brand-abuse screenshots are not enough to identify a mobile app reliably. Store names and presentation can change, while versions and regional availability complicate verification.

These are recommended case fields, not a statement that every platform form requires every item. Use the current form's requirements and avoid sending unnecessary personal information.

Report impersonation on Google Play

Google Play's Impersonation FAQs distinguishes misleading affiliation from trademark and copyright claims. Its impersonation policy addresses apps that mislead users about their connection to another developer, company, entity or app.

If the complaint concerns that misleading presentation, use the policy-reporting route linked from Google's guidance. The Google Play reporting page also explains the in-app flagging process. Open the listing in the Google Play app, select More, choose Flag as inappropriate, select a reason and submit.

For an enterprise case, preserve your internal evidence record before reporting. Follow the linked developer-policy process when that is the appropriate route. Explain the misleading connection plainly and point to the exact listing elements that create it.

If you own or represent rights that the app infringes, assess the separate copyright, trademark or other legal reporting process. Google warns that using the wrong form can delay or prevent processing. Have your legal team confirm the claim and the submitter's authority rather than treating a policy flag as an IP notice.

A public negative review is not a substitute for the platform's reporting process. Google distinguishes reviews, which describe a genuine user experience, from reports requesting policy review.

Choose the right Apple reporting path

Apple's App Store safety guidance directs users who suspect suspicious activity in an app they downloaded to reportaproblem.apple.com. That is a user-facing safety route. It should not be described as the same process as a brand's rights-holder claim.

For alleged infringement of your intellectual-property rights, Apple's Dispute Forms directory includes an App Store route. Apple says a submitter must provide contact details, identify and describe the alleged infringement, and represent under penalty of perjury that they are or represent the authorized rights holder.

Send an accurate, authorized claim. Do not ask an analyst to certify rights they have not verified. Counsel should distinguish copied protected material, alleged trademark infringement and suspicious app behavior, even when they occur in the same listing.

Apple says it usually responds by email with a reference number. Follow up through that correspondence with the reference number rather than resubmitting its dispute form to chase an existing case. Its forms cover Apple services, not disputes about unrelated third-party services.

The sources describe reporting paths, not guaranteed removal outcomes or response times. Keep the case open for review and verification.

Investigate linked infrastructure separately

An app listing may lead to a fake support site, credential portal or other external destination. Store enforcement and infrastructure enforcement are different actions.

Preserve observed links and assign each relevant asset for review. If a reported backend remains active after the app disappears, users may still reach it through other distribution channels. Conversely, removing a website does not establish that the app listing is gone.

Outtake's Brand Protection overview describes investigating cloned apps alongside other brand-abuse surfaces. This article's reporting workflow remains usable without adopting a particular vendor. The immediate task is to create an accurate case and route each claim to the service that can review it.

Verify the result in the affected market

Record the submission, reference number, platform response and independent checks. Revisit the exact listing in the affected storefront using approved methods. Distinguish a removed listing from a listing that is temporarily unavailable only in your test region.

Do not claim that installed copies have disappeared merely because new downloads are unavailable. Removal of distribution is a different outcome from remediation on devices that already received the app.

Check the publisher profile, connected listings and observed external destinations for remaining exposure. Watch for a replacement listing with a new identifier or changed presentation. Keep uncertain findings labeled as uncertain rather than declaring the whole campaign removed.

Related reading

Read the brand impersonation guide for the wider campaign model and the phishing takedown guide for provider-level evidence and closure principles.

Sources

• Google Play, Impersonation FAQs.
• Google Play, Flag an app or review.
• Apple, Maintaining a safe App Store experience.
• Apple Legal, Dispute Forms.
• Outtake, Brand Protection.
• Outtake, Platform, evidence packaging, automated reporting, platform escalation and verified takedown.

Sources reviewed October 1, 2026.