Skip to content
Back to search

identity-eraser

Claude Code skill that removes your own personal info from people-search sites and data brokers (discovery + automated opt-outs in your own browser).

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/akcodez--identity-eraser/badge.svg)](/listings/akcodez--identity-eraser)

HTML

<a href="/listings/akcodez--identity-eraser"><img src="/api/listings/akcodez--identity-eraser/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Paste this into your terminal:

git clone https://github.com/akcodez/identity-eraser.git ~/.claude/skills/identity-eraser

Then open Claude Code and just say:

> **"Erase my personal info from the data brokers."**

The skill takes it from there.

---

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

SKILL.md · Manifest · 129 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. ---
  2. name: identity-eraser
  3. description: >-
  4. Erase a person's personal information from people-search sites and data brokers, and confirm it's gone.
  5. Drives the operator's OWN authenticated browser (via Claude-in-Chrome) to (1) discover which brokers expose
  6. their name, address, phone, age, and relatives, then (2) submit each site's official opt-out / removal
  7. request one at a time, logging status and handing off to the operator only for verification codes.
  8. Covers Whitepages, Spokeo, BeenVerified, TruePeopleSearch, Nuwber, Radaris, MyLife, Intelius, PeopleFinders,
  9. FastPeopleSearch, USPhonebook, CheckPeople and similar sites. Use this whenever the user wants to remove,
  10. delete, scrub, suppress, hide, or opt out their personal info / PII from the internet, data brokers, or
  11. people-search sites; reduce doxxing, stalking, or harassment exposure; "get my information taken down"; or
  12. protect their online privacy — even if they don't name a specific site.
  13. ---
  14. # Identity Eraser
  15. A workflow for removing one person's personal information from the major people-search sites and data brokers, then verifying the removals. It runs in the operator's own browser through Claude-in-Chrome, so every request is made *as the operator*, by the operator, about the operator.
  16. ## What this does, in one breath
  17. For each target broker: find out whether the operator is listed and what's exposed (Phase 1, read-only), show them the picture, then walk the official opt-out form on each site where they're listed and submit it (Phase 2), pausing only when a human is genuinely required — a CAPTCHA image challenge, an SMS code, a phone call. Everything is logged so the operator ends with a clear record of what was submitted and what still needs follow-up.
  18. ## The one rule that matters most: scope
  19. **Only ever act on the data of the person running this skill — the "subject" — who is the operator of this browser.** This is a self-service privacy tool: a person removing their *own* information using their *own* authenticated session. That framing is the entire justification for the skill, so protect it:
  20. - Never submit a removal, suppression, or opt-out for anyone who is not the subject. People-search results are full of namesakes and relatives; removing the wrong person's listing is both wrong and, for the subject, useless.
  21. - Before you act on any listing, **confirm it's actually the subject** using at least two corroborating signals — date of birth/age, a known current or past address, or a known relative's name. If the match is ambiguous, **stop and ask the operator** rather than guessing.
  22. - Relatives' names are collected for *matching only*. They are how you tell the subject's record apart from a stranger's. They are never themselves a target.
  23. - Everything is free. If a site tries to charge to remove a listing, that's a funnel, not the opt-out — back out and find the official (free) suppression form, or log the site as "needs manual review."
  24. If you ever feel the task drifting toward acting on someone other than the subject, treat that as a hard stop and check in.
  25. ## Authorization & autonomy
  26. Invoking this skill *is* the operator authorizing action on their own behalf — they are removing their own data from their own browser session. So **run autonomously**: don't stop to ask "should I click submit?", "should I opt out of this one?", or "is it OK to proceed?" for the routine discovery and opt-out steps. Acting on those is the whole point.
  27. Pause and hand off **only** when a human is genuinely, mechanically required:
  28. - an image CAPTCHA / hCaptcha / escalating challenge you can't clear,
  29. - an SMS code or a live verification phone call,
  30. - an email confirmation link you cannot reach in the browser.
  31. For everything else — filling forms with the subject's info, clicking "Remove," "Opt Out," "Submit," accepting a site's opt-out terms, declining cookies — proceed. The scope rule above (act only on the subject's own records, confirm identity first) is the real guardrail; per-step confirmation is not, and asking for it just stalls a task the operator already greenlit.
  32. ## Prerequisites
  33. 1. **Claude-in-Chrome connected**, pointed at the operator's own Chrome where they are signed into their email (the brokers send verification links there). The browser tools are MCP tools that must be loaded before use — load them with `ToolSearch` (`select:mcp__claude-in-chrome__tabs_context_mcp`, `...navigate`, `...get_page_text`, `...read_page`, `...find`, `...form_input`, `...computer`, `...gif_creator`, `...browser_batch`) at the start of a run.
  34. 2. **Browser actions enabled.** In the Claude-in-Chrome extension, allow Claude to act on these sites (allowlist them or set "always allow") so the run isn't interrupted by per-action prompts.
  35. 3. **The operator is present** during the run, because some sites can only be finished by a human (SMS codes, phone-call verification, image CAPTCHAs).
  36. 4. Confirm the live browser state first with `tabs_context_mcp`, then open a fresh tab to work in. Never reuse a tab from another session.
  37. ## Step 0 — Collect the subject's profile
  38. Ask the operator for the information below. Explain that it's used only inside this session to find and submit *their* removals, and that it must **never be written into the skill files or committed anywhere** — keep it in conversation, or in a scratch log stored outside any git repository.
  39. Collect:
  40. - **Full legal name**, plus every variant: maiden/former names, common misspellings, nicknames, suffix (Jr./Sr./III). Brokers index all of these separately.
  41. - **Date of birth (or age).** This is the single best disambiguator against namesakes.
  42. - **Current address** (street, city, state, ZIP).
  43. - **Previous addresses**, especially the last ~10 years. Brokers feature old addresses heavily, and several forms ask you to confirm them.
  44. - **Phone number(s)** — cell and any landline.
  45. - **Email address(es)** to scrub, plus **one email the operator can check right now** for confirmation links.
  46. - **Close relatives' first names** (parents, siblings, spouse) — for matching only.
  47. Start a **status log** (see "Logging") and record these as the search inputs.
  48. ## Phase 1 — Discovery (read-only, safe)
  49. Walk the target sites (see the list and per-site search tips in `references/site-playbooks.md`). For each one:
  50. 1. Open the site's people search and query the subject's **name + city + state**; widen with previous cities if nothing matches.
  51. 2. In the results, identify the listing(s) that are actually the subject by cross-checking **age/DOB, an address, or a relative's name**. Note when there are several listings — common names, name variants, and old addresses each spawn their own record, and **each is a separate removal later**.
  52. 3. Capture, for the log: whether the subject is listed, **what's exposed** (full name, current/past addresses, phone numbers, relatives, age/DOB, anything sensitive), and the **exact profile URL(s)** — most opt-out forms need the URL.
  53. Then **present the discovery table to the operator before scrubbing anything** — this is a deliberate checkpoint, not a formality. Use this shape:
  54. ```
  55. | Site | Listed? | Exposed (name / address / phone / relatives / age) | Profile URL(s) | Notes |
  56. ```
  57. ## Phase 2 — Scrub (one site at a time)
  58. Read `references/site-playbooks.md` first — it has the verified opt-out URL, exact steps, required fields, verification method, expiry windows, and network/sister-site notes for each site. Then, for every site where the subject is listed, work it to completion before moving on (doing them one at a time keeps the log honest and avoids half-finished submissions):
  59. 1. Open the site's **official opt-out page** from the playbook.
  60. 2. Fill the form with the subject's info. Where the form wants a profile URL, use the one captured in Phase 1.
  61. 3. Submit, then handle whatever gate appears (see the handoff protocol below).
  62. 4. **Log the outcome** with one of these statuses, plus the timestamp and the next action:
  63. - `submitted` — request sent, no further action expected.
  64. - `pending verification` — an email link / SMS code is required to finalize (note the expiry window!).
  65. - `needs manual step` — a human-only step blocks completion (image CAPTCHA, phone call, account creation, paid funnel).
  66. - `blocked` — the site won't load or actively refused; note the symptom.
  67. - `removed-confirmed` — re-checked and the listing is gone.
  68. 5. Move to the next site.
  69. ### Verification & CAPTCHA handoff protocol
  70. The operator should only have to step in when a human genuinely must:
  71. - **Simple "I'm not a robot" checkbox:** attempt it yourself.
  72. - **Image challenge / hCaptcha / escalating CAPTCHAs** (FastPeopleSearch is notorious for stacking these): pause, ask the operator to solve it in the browser, then continue.
  73. - **Email confirmation link:** the operator is signed into their email in this very browser, so open their webmail in a tab and click the link yourself when possible; only ask the operator if you can't locate it. **Mind the expiry windows** — Intelius ~15 min, PeopleFinders/USPhonebook ~24 h, BeenVerified ~48 h — so don't queue these; finish each as it arrives.
  74. - **SMS code or live phone call** (e.g., Whitepages' automated call): you cannot do this — hand off to the operator, tell them exactly what code/page to expect, and wait.
  75. Never trigger a JavaScript `alert`/`confirm`/`prompt` dialog; it freezes the browser tools. If a page has a "Delete"/confirm dialog, warn the operator before interacting.
  76. ### Browser tactics
  77. - Begin with `tabs_context_mcp`; open a new tab with `tabs_create_mcp`.
  78. - Read pages with `get_page_text` / `read_page`; locate fields with `find`; type with `form_input`; click via `computer` when needed.
  79. - These sites hard-block non-browser fetchers (they 403 automated requests) — that's expected and is why we're in a real browser. If a *page* still won't load or throws bot walls repeatedly, don't hammer it: log `blocked` and tell the operator.
  80. - Optionally record each scrub with `gif_creator` so the operator has a visual receipt (capture a few frames before and after each action for smooth playback). Name files per site, e.g. `truepeoplesearch_removal.gif`.
  81. - If browser calls fail 2–3 times or the extension stops responding, stop and ask the operator rather than looping.
  82. ## Logging & final report
  83. Maintain a running status log throughout (a Markdown table is fine), and finish with a report the operator can act on:
  84. ```
  85. | Site | Listed? | Action taken | Status | Verification needed | Next step / recheck date |
  86. ```
  87. Call out anything in `pending verification` or `needs manual step` at the top — those are the operator's to-dos.
  88. ## After the run: monitoring & re-listing
  89. Removal is not permanent. Brokers re-scrape public records and re-list people over weeks to months, so recommend re-running this every **3–6 months**. Also flag **network/sister sites**: one opt-out sometimes clears a whole family (a single PeopleConnect suppression covers Intelius, TruthFinder, Instant Checkmate, US Search, ZabaSearch, and more), while other networks need each property done separately (Radaris's affiliated fleet; BeenVerified's sister brands; Whitepages' 411.com; the TruePeopleSearch/FastPeopleSearch pair and their `.info`/`.net`/`.io` variants). The playbook notes which is which.
README.md · README · 130 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. <div align="center">
  2. # 🫥 Identity Eraser
  3. ### Wipe your personal info off the internet — automatically.
  4. *Your name, home address, phone number, age, and relatives are sitting on dozens of "people-search" sites right now. Anyone can look you up in seconds. This erases you from them.*
  5. <br>
  6. ![Runs in your own browser](https://img.shields.io/badge/runs_in-your_own_browser-6c5ce7?style=for-the-badge)
  7. ![Your data stays on your machine](https://img.shields.io/badge/your_data-never_leaves_your_machine-00b894?style=for-the-badge)
  8. ![Free opt-outs only](https://img.shields.io/badge/cost-100%25_free-0984e3?style=for-the-badge)
  9. ![License MIT](https://img.shields.io/badge/license-MIT-636e72?style=for-the-badge)
  10. </div>
  11. ---
  12. ## 😨 The problem
  13. Type your own name into Google and you'll find sites like **Spokeo, Whitepages, and BeenVerified** showing:
  14. - 🏠 Your current and past home addresses
  15. - 📞 Your phone numbers
  16. - 🎂 Your age and birthday
  17. - 👨‍👩‍👧 Your family members' names
  18. They scraped it from public records and now they sell it — to anyone. Stalkers, scammers, and creeps use these sites every day. You can opt out of each one by hand… but there are dozens, every form is different, and they re-list you every few months. Nobody has time for that.
  19. **Identity Eraser does it for you.**
  20. ---
  21. ## ✨ How it works
  22. It runs as a [Claude Code](https://claude.com/claude-code) skill inside **your own browser**, in two simple phases:
  23. ```
  24. PHASE 1 — SEE IT PHASE 2 — ERASE IT
  25. ┌────────────────────┐ ┌────────────────────┐
  26. │ 🔍 Scans every │ │ 🧹 Opens each │
  27. │ data broker │ ────────▶ │ opt-out form │
  28. │ for your name │ │ and submits it │
  29. │ │ │ for you │
  30. │ Shows you exactly │ │ │
  31. │ what's exposed │ │ Logs what's done │
  32. └────────────────────┘ └────────────────────┘
  33. (read-only — (you only step in
  34. changes nothing yet) for the occasional code)
  35. ```
  36. > **Phase 1 — Discovery:** It searches each site and hands you a clean table: *here's what Spokeo has on you, here's what Whitepages has on you.* Nothing is changed yet — you just see the damage.
  37. >
  38. > **Phase 2 — Erase:** It opens each site's official removal form, fills in your details, and submits it — one site at a time — keeping a running log. It only pauses to tap you on the shoulder when a human is truly required (an image CAPTCHA, a text message code, a verification call).
  39. ---
  40. ## 🔒 Is this safe? (Yes — here's why)
  41. This is the part that matters most, so read it:
  42. | ✅ | What that means for you |
  43. |----|--------------------------|
  44. | **Your data never leaves your computer** | The skill asks for your info *while it's running* and uses it only inside your live browser. Nothing is saved, uploaded, or stored anywhere — except typed into the brokers' own removal forms. |
  45. | **It only ever removes _you_** | People-search sites are full of strangers with your name. The skill confirms it's really you (using your age + an address + a relative's name) before touching anything. If it's not sure, it stops and asks. |
  46. | **It runs as _you_, in _your_ browser** | Every request comes from your own signed-in session — which is exactly what makes this a legitimate "remove my own info" request, not hacking. |
  47. | **It's completely free** | Real opt-outs are always free. If a site tries to charge you to be removed, that's a scam funnel — the skill backs out and flags it. |
  48. ---
  49. ## 🧰 What you need
  50. - [ ] **Claude Code** with the **Claude-in-Chrome** extension connected to your Chrome
  51. - [ ] You're **signed into your email** in that browser (the sites email you verification links)
  52. - [ ] You're **around during the run** to tap in codes / solve the odd CAPTCHA
  53. That's it. No coding, no accounts, no payment.
  54. ---
  55. ## 📥 Install
  56. Paste this into your terminal:
  57. ```bash
  58. git clone https://github.com/akcodez/identity-eraser.git ~/.claude/skills/identity-eraser
  59. ```
  60. Then open Claude Code and just say:
  61. > **"Erase my personal info from the data brokers."**
  62. The skill takes it from there.
  63. ---
  64. ## ▶️ How to use it
  65. 1. **It asks for your details** — name (and any old/maiden names), age, current + past addresses, phone, and your relatives' first names (used *only* to tell your record apart from strangers').
  66. 2. **It shows you the damage** — a table of what each site is exposing. Take a breath.
  67. 3. **It erases you** — works through every site that listed you, marking each one: `submitted` · `pending your verification` · `needs a manual step` · `removed`.
  68. 4. **It hands you a report** — anything left for you to finish (a link to click, a code to enter), plus a reminder to re-run in 3–6 months.
  69. ---
  70. ## 🌐 What it covers
  71. > Whitepages · Spokeo · BeenVerified · TruePeopleSearch · Nuwber · Radaris · MyLife · Intelius *(and the whole PeopleConnect family)* · PeopleFinders · FastPeopleSearch · USPhonebook · CheckPeople — plus their sister sites.
  72. The full per-site playbook lives in [`references/site-playbooks.md`](./references/site-playbooks.md), and the complete workflow is in [`SKILL.md`](./SKILL.md).
  73. ---
  74. ## 💡 Good to know
  75. - **This is for _your own_ info only.** It automates the same free removal forms the law requires these sites to offer. It is not for looking up or removing anyone else.
  76. - **Removal isn't forever.** These sites re-scrape public records and quietly re-list you over the following months. Re-run it a few times a year to stay invisible.
  77. - **Some steps need you.** CAPTCHAs and text-message codes are designed to stop robots — so the skill hands those to you and keeps going after. That's by design.
  78. - **This is a privacy tool, not legal advice.**
  79. ---
  80. <div align="center">
  81. **Built for everyone who never agreed to be this easy to find.**
  82. MIT licensed · See [`LICENSE`](./LICENSE)
  83. </div>

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.