Remove a fake profile or account impersonating you.

Before you report

Find who controls the impostor.

Fake-account work is not one universal form. A clean file separates who controls the account, where the photos live, what proof the reviewer needs, and whether search is only a fallback.

Start with the platform's impersonation path.

Major social platforms publish identity-abuse channels for accounts that pretend to be you. Those channels matter because reviewers expect impersonation claims to be separated from general abuse reports.

Each platform runs its own review queue, proof posture, and ceiling. Public copy can name that difference; which claim fits which queue, what proof belongs in the file, and how the file moves stay inside the client record.

One honest caveat: platforms generally expect the person being impersonated, or an authorized representative, to control the request. If the imposter is using someone else's name, that person must authorize the work.

• 01Known social clone: a profile or Page is pretending to be you.
• 02Cross-platform clone: the same identity misuse is spread across several services.
• 03Respawn pattern: the fake disappears, then comes back under a changed name.
• 04Off-platform page: a dating profile, scam page, scraper, or search result is using your likeness.

When the platform path isn't enough.

A single, obvious clone may resolve through the platform's own queue. A managed case becomes useful when the problem is bigger than one form:

• 01There are several fake accounts across several platforms at once, each with its own review queue and proof boundary.
• 02The fake keeps coming back under a new handle after every takedown — a respawn problem, not a one-time problem.
• 03Your photos are being used on dating apps, catfish profiles, or scam pages that have no real reporting process.
• 04The platform rejected the first pass, or the proof boundary is unclear.
• 05The impersonator is using your name to defraud your contacts, your clients, or your employer, and you need the file documented carefully.

Removed at the source — or de-listed from search.

There are two outcomes, and we never blur them. Removal at the source means the fake account itself is taken down by the platform — the strongest result, and the goal for in-platform impersonation. Search de-listing means a page (for example, a catfish profile on a site that won't act) is hidden from Google results in your name. De-listing is a fallback, never a substitute for removal — it hides the result without deleting the page.

For an account on a mainstream platform, the basis is usually the platform's own impersonation and authenticity policy. For photos used elsewhere, the boundary may involve source control, search visibility, ownership, or legal referral. We tell you up front which boundary your case realistically supports without publishing the filing playbook.

Honest timing: a clean, authorized file helps reviewers understand the claim, but timing varies by platform, evidence quality, and review posture. Individual results vary under your written service agreement.

What we won't promise.

We do not sell certainty, and you should walk away from anyone who does. No private service controls every platform, host, or repost. Our work is results-based and defined in a written service agreement, with a 48-hour acceptance review: if it's outside the boundary or something we can't accept, you're refunded before any work begins.

We also won't pretend de-listing is deletion, or promise we can stop a determined person from making a new account. What we can do is keep the file authorized, separate source status from search visibility, keep follow-up inside one record, and review identified re-creations under a written boundary. We're a removal agency, not a law firm — if your situation needs an attorney, we'll say so.