Precheck.ai Removal: The Mugshot-Backed Face Search Most People Have Never Heard Of

Precheck.ai isn't on most people's radar. It doesn't get the press PimEyes does. It hasn't been hit with the Clearview-scale lawsuits. But it does something more invasive than either: it stacks reverse-image face search on top of mugshot databases, court records, government sites, and social-media scraping, and sells the combined identity lookup for a dollar a query, no account required.

That makes it the engine people actually find you on. Employers running ad-hoc checks. Landlords. Online dates. Anyone with $1 and a photo.

What Precheck.ai Actually Is

Precheck.ai positions itself as a "background check" service. The product is three things stitched together:

• Reverse-image face search. Upload a photo, get back URLs where that face appears across the public web.
• Reverse phone / email lookup. Enter a number or email, get back names, social profiles, and (often) addresses tied to it.
• "Background" page composition. The site combines hits from the above with what they've indexed from mugshot databases, court sites, and government records, and renders a single profile page for the subject.

Pricing is the part most people miss. Phone and email lookups are $1 each, no account required. Face search runs on a credit system. That low friction is what makes Precheck different from the law-enforcement-only engines (Clearview AI, NEC Corp). Anyone, anywhere, with $1, can pull a profile on you.

They state on their site that they scan "billions of images from diverse internet sources, such as news websites, mugshot databases, court sites, government sites, social media platforms, and online forums." That's the most honest description of the source mix any face-search company publishes.

Why Removal Is Different From PimEyes

PimEyes' opt-out removes you from the face-search index only. Your photos still exist on the original web pages. Precheck.ai has the same face-search index — but they also have your composed profile page: the one that sits at a precheck.ai URL with your name, photo, mugshot if any, court records if any, social handles, phone numbers.

That means you have to remove two separate things:

1. Your face from the search index — so a stranger uploading your photo doesn't get back your composed profile.
2. The composed profile itself — so someone Googling your name doesn't land on a precheck.ai page about you with a photo, court records, and contact info.

The removal form covers both, but only if you select the right options. Picking just "Remove my face / image" leaves the composed profile alive.

What They Probably Have On You

Before you file, it helps to know what's actually in their index. The categories that show up most often, based on Precheck's own stated source mix:

• Social media photos — anything public on Facebook, Instagram, LinkedIn, X, or Twitter before you locked your account down.
• News articles — sports recaps, wedding announcements, charity-event coverage, op-eds, anything where your face appeared in a hometown paper.
• Mugshot mirror sites — even if you were never charged or were exonerated. Most state mugshot publication is governed by public-records law and gets aggregated by commercial mirrors who Precheck then re-indexes.
• Court records — civil filings, divorce records, small-claims judgments, traffic tickets in jurisdictions where those records are public.
• Government sites — voter rolls, property tax records, occupational license rosters (real estate, medical, legal, contracting).
• Online forums — Reddit posts under a username that resolves to your real name elsewhere, niche-community profile pages.

The "GDPR data export request" option on their form gets you a list of exactly what they have. EU/UK residents should use it before filing the deletion — knowing what's there helps you write a more specific request and check that everything actually got removed.

How To File the Removal Request

The form is at precheck.ai/removal-request. They state "verified requests are processed within 7 business days" and confirmation lands by email. The fields are minimal, which is exactly why getting them right on the first submission matters.

1. Full name. Use your legal name as it appears on government ID and on any court / mugshot records they may have. If a court case used your middle name and your social profiles use a nickname, list both: "Jane M. Doe (also Janie Doe)".
2. Email. Use one you actually monitor — they email confirmation and reply if they need clarification. A throwaway address that goes to spam will silently kill the request.
3. Request type — this is the field people get wrong. The options are:
   • Remove my face / image — index removal only. Doesn't touch any composed profile page.
   • Delete my account & all data — fully removes any composed profile + face index entry + cached lookups. This is what most people actually want.
   • Remove search history — only useful if you have a Precheck account and want past queries scrubbed.
   • GDPR data export request — Article 15 right-of-access; gets you a copy of everything they have. EU/UK should run this first.
   • Other — for edge cases (estate-of-deceased, third-party-authorized removal, etc.). Explain in the message field.
4. Country (optional but file it). EU / UK / California addresses elevate the request from discretionary to legally compelled. Skipping the field is leaving leverage on the table.
5. Account email (optional, if different). Fill it if you ever made a Precheck account — even a free trial. Otherwise the account stays alive after the lookup data is removed.
6. Confirm + submit. The required confirmation checkbox says you're the person or legally authorized. Note the timestamp; if no email confirmation arrives within an hour, re-submit.

Mistakes That Get Requests Rejected

• Selecting "Remove my face / image" when you wanted full deletion. The face-search index loses your photo. The composed profile page with your name, address, and mugshot stays up. By far the most common mistake on this form.
• Submitting without a country. Manual reviewers prioritize compelled requests (GDPR, CCPA) over discretionary ones. Discretionary requests still get processed but slip down the queue.
• Using a different name than the one on their records. Their reviewers match the submitted name against the indexed records. If your social profiles use "Janie" but your court records use "Jane M.", a request under just "Janie" won't reach the court-record entries. List every variant you can think of.
• Not following up. The site promises 7 business days for verified requests. If nothing arrives in 14 calendar days, re-submit referencing the original timestamp in the "other" message field. Manual review queues miss things.
• Filing once and assuming you're done. Precheck re-crawls its sources continuously. A photo you removed last year can re-appear if it gets re-indexed from a new article, social-media repost, or news aggregator. Re-file annually.

Realistic Expectations

Even a clean removal from Precheck.ai doesn't pull your face off the source sites. The mugshot mirror, the news article, the LinkedIn photo — all of those still exist. What changes is whether the next person who pays $1 to look you up gets back a composed identity page.

That matters more than it sounds. The composed profile is what makes Precheck dangerous: it's the difference between a stranger having to spend an hour Googling you and getting back a one-click dossier. Killing the composed profile breaks the easy path. The expensive path — manual aggregation by a determined person — stays open, but the cost-per-lookup goes from $1 to "actual effort."

Precheck removal is one of several requests that have to be filed in parallel. PimEyes, FaceCheck.ID, Clearview AI, Lenso.ai, Eagle Eye Search, Yandex — each maintains its own index, each requires its own removal flow. None of them share data with each other. None of them share with Precheck. The work compounds.