Lenso.ai Removal: The Face-Search Engine That Says It Doesn't Re-Index You

Lenso.ai is a Polish-built AI reverse-image search engine. You give it a photo, it gives you back URLs across the open web where that photo (or a near-match of the face in it) appears. They index billions of web images, expose face search as a primary feature, and sell a developer API on top.

What makes them different from PimEyes or FaceCheck.ID isn't the search itself — it's the opt-out policy. Lenso's public privacy policy states that once you're delisted, they don't re-index you on future crawls. Most face-search engines re-crawl periodically and your removed photos drift back in. Lenso says they don't, and we haven't seen one of our delisted users re-appear in the months we've been monitoring.

What Lenso.ai Actually Is

Lenso describes itself as an AI image search engine across five categories: face, people, places, duplicates, and similar/related images. The face category is the one that matters for personal privacy. Upload a photo, get back every URL on the open web where that face appears.

Their indexing claim is "billions of images from all around the web." They don't publish a source list — meaning they crawl broadly rather than scraping specific platforms. That's actually useful for opt-out: a single removal request covers everything they have on you, regardless of where it came from.

Pricing tiers run from a free preview up to a Professional plan with Research Mode (10,000 results per query, advanced filters) and a developer API at up to 5,000 calls per month. The API tier is the reason Lenso shows up in third-party tooling — small reverse-image apps use Lenso under the hood without disclosing it.

Why Their No-Re-Index Policy Matters

Most face-search engines structure their opt-out so it removes you from the current index — but the next crawl re-finds the same photo on the same web page and re-indexes you. PimEyes is the notorious example. You file an opt-out, you're gone for three to six months, then the same exact photo (still on the same blog post, the same news article, the same conference recap) gets re-indexed and you're back in search results. The remediation is to re-file, annually at minimum.

Lenso says they treat opt-outs as an allowlist entry — once you're added, future crawls skip matches that resolve to your delisted identity. We can't inspect their backend to verify the implementation, but their stated policy commits to it, and in our monitoring of delisted users so far we haven't seen anyone re-appear. That said, no engine's policy is locked in; companies update terms, get acquired, or change behavior, so we still re-check Lenso periodically.

For users, this changes the math on whether opt-out is worth doing. With PimEyes, opt-out is recurring maintenance. With Lenso — assuming they continue honoring their stated policy — it's a one-shot you don't have to babysit monthly.

What They Probably Have On You

Lenso doesn't publish a source list, but the general crawl shape implies they have:

• Public news article photos — bylines, sports recaps, charity-event coverage, hometown-paper appearances.
• Old or current personal-website photos — about-me pages, professional bios, conference speaker pages.
• Social-media photos that ever went public — Instagram before you locked it down, LinkedIn (still public), Facebook profile photos.
• Forum and community posts — Reddit avatars, niche-community profile pages, hobby-forum signatures.
• Anything embedded in a Google Image-indexed page — Lenso uses Google's open-web crawl as one of its sources, so anything visible to Google Images is probably in Lenso.

What they likely don't have: anything behind a login, private cloud storage, anything robots.txt-blocked from general crawls.

How to File the Opt-Out

The form is at lenso.ai/en/opt-out. They don't publish a stated turnaround time, but in our experience verified requests are processed within roughly two weeks.

1. Provide a clear reference photo. The match-quality threshold is similar to PimEyes — front-facing, even lighting, no sunglasses. The clearer the reference photo, the more matches the system can resolve to you, and the more complete the exclusion.
2. Provide an email address you actually monitor. They reply via email, including with clarification questions if the request is ambiguous. A throwaway address that filters to spam will silently kill the request.
3. Cite the privacy basis. EU/UK residents should reference GDPR Article 17 (right to erasure) explicitly. The Polish-built engine takes GDPR requests seriously — Polish privacy regulators have an enforcement mandate. California residents should cite CCPA §1798.105. Everyone else can file under Lenso's general privacy policy without a statute reference.
4. Provide proof of identity. Lenso accepts an anonymized ID — you can redact the document number, full address, and any non-identifying fields. Leave only the name and the photo visible. We anonymize on behalf of users by default.
5. Submit and wait. Confirmation usually arrives within 24 hours. The actual delisting and exclusion-list update happens within ~14 days.

Mistakes That Slow It Down

• Submitting a low-resolution reference photo. The match-quality threshold is real. If the system can't confidently resolve your face from the photo, the exclusion only catches obvious matches, and lookalikes slip through. A clear 1080p+ photo is the floor.
• Skipping the ID document. Lenso explicitly asks for one. Requests without identity verification get queued under "unverified" and processed slowly, if at all.
• Submitting an un-anonymized ID. They don't need your driver's license number or address — only your name and photo. Sending the whole document over a web form is exposing data unnecessarily. Redact before upload.
• Filing once and assuming you're done with face-search entirely. Lenso's stated policy applies only to Lenso. It does nothing for PimEyes, FaceCheck.ID, Precheck.ai, Clearview, or the other ten engines that index the same photos. Each engine requires its own opt-out flow.

Realistic Expectations

A Lenso delisting removes you from Lenso's search results. It does not pull the underlying photos off the source websites — they still live on the news articles, blog posts, social profiles, and forum posts where they originally appeared. Anyone who Googles your name directly will still find those pages.

What changes is the cost of finding you via face alone. Without Lenso (and PimEyes, FaceCheck.ID, etc.) in the picture, someone who has only a photo of you has no fast way to convert that photo into a name. The expensive path — manual research, looking up clothes or background landmarks — stays open, but the cheap path closes.

Lenso removal is one piece of the larger face-removal stack. Their no-re-index policy is genuinely a competitive advantage, and at time of writing they're the only engine on our list where one filing seems to actually hold. Policies can change, so we still monitor — but it's the closest thing to "file once" in the face-search opt-out world right now.