Your browser.
Your requests.

The free companion fills reviewed broker forms in desktop Chrome. Optional automation can attempt reviewed initial submissions, recognize one local text challenge and check scoped removal-mail operations. Your profile stays in your workspace. Broker forms receive only the fields you approve.

1. Extract the ZIP into a folder you will keep.
2. Open Chrome’s extensions page at chrome://extensions. Turn on Developer mode.
3. Choose Load unpacked, then select the extracted folder containing manifest.json.
4. Open the companion’s toolbar icon. Choose Enable broker forms and accept access to the listed sites.
5. Refresh Erase Me. Choose Check companion, then start a broker action or choose Review form batch.
6. Updating an older companion? Replace its extracted files with this download, then choose Reload on Chrome’s extensions page. The current companion is version 0.13.0.

Follow the next step

Your workspace shows the email used for each started request and the information the broker still needs. For a supported FastPeopleSearch matching continuation, choose Enter missing information inside Erase Me. The companion checks the existing form’s required controls first. Review the exact values and accuracy statement, then approve Fill and submit once. Extra details stay in memory and are cleared after dispatch or closing; they are not saved in your ledger or backup. The broker currently marks DOB, street address and phone required despite wording that either DOB or address is enough. Erase Me explains that conflict before asking for the full set. You can cancel or hold instead. USPhonebook retains its direct official-form handoff.

The companion checks the existing tab and original document before switching to it. It opens no new request or confirmation link. If that tab was closed, changed or opened with an older companion, find it manually and review its current state. Held requests stay on hold.

Review and run a batch

Complete each route’s required details and own-record confirmations, then choose Review form batch. Review the selected official sites and exact outgoing fields, check the batch authorization and choose Fill selected forms. Held, already-started, incomplete and manual routes are excluded with reasons.

The optional submission control covers ten reviewed broker initial forms: FamilyTreeNow, SmartBackgroundChecks, USPhonebook, FastPeopleSearch, SearchPeopleFree, AdvancedBackgroundChecks, Apollo, No Sorgulama, NumaraAra and NumaraSor. Their exact agreements appear in the review. The companion checks those agreements, fields, purpose, challenge and controls again before using the native submit button. A checked submit event records an attempt; delivery, broker acceptance and deletion remain unverified.

Stop after current form leaves the remaining forms untouched. Closing the review also requests a stop after the current action. Changed details, an uncertain outcome or failed result storage stop the queue for review. Batch approval stays in page memory; reloading never resumes it.

Supported automation

FastPeopleSearch. Fills the first official form and can attempt its reviewed verification submission after you approve the communications agreement. It watches the original approved form for up to 12 seconds for the normal Turnstile widget's actual response. This is one foreground wait, with no repeated checks or challenge clicks. A changed form, navigation or unresolved challenge stops the action. An approved removal-mail pass can then open its authenticated matching-form link and check the prefilled name and contact. Its current required controls include full DOB, street address and phone; Erase Me discloses that conflict with the site’s DOB-or-address wording before an optional final attempt.

SearchPeopleFree. The initial form can submit once after review of its exact own-email agreement and policy sources. Its genuine Turnstile response is required; no vendor token is created. A personally owned local removal-only address is supported. Shared operator addresses remain unavailable for new requests. Its later record selection and confirmation still need a separate reviewed contract.

NumaraAra. Fills the reviewed request fields. With the optional local helper and Tesseract installed, it can try one five-character image-code answer and the reviewed request submission. Changed or unreadable challenges need attention. No accepted-request or deletion result has been established.

Apollo. Optional guarded submission uses only the separately confirmed business email associated with your record. A browser-enforced form-action policy blocks native GET fallback while the site’s normal submit handler can run. This is a verification-information attempt; removal-only aliases are not substituted and later verification remains outstanding.

People Data Labs. Retains the existing official deletion-portal email initiation. It requires an email associated with the record; a shared service mailbox is not substituted. Later portal steps remain outstanding.

Additional guarded submissions. AdvancedBackgroundChecks can start email verification after its exact communications agreement and policy sources are reviewed. No Sorgulama and NumaraSor can submit their separately approved request forms. The app leaves anti-forgery values unchanged, never fills optional unapproved identity fields, and records only a native submission attempt. NumaraSor may request additional ownership evidence later; Erase Me uploads no ID. Install companion 0.13.0 before selecting these submissions. Other confirmation and matching steps remain outstanding.

USPhonebook. The initial form can submit once after review of its own-request agreement and privacy statement, with a genuine Enterprise challenge response. No hidden agent details are added. This does not resume a held request or automate its final identity check.

Other reviewed forms. Spokeo and TelefonSorgulama retain their guarded prefill flows. Whitepages supports only the first suppression step: fill a direct person URL after explicit own-record review, with no Next click or phone verification. Apollo needs a separately approved business email; Spokeo needs a direct own-record URL. The structured request routes retain their own-request affirmations. NumaraSor alone receives the separately approved target phone number. Unreviewed final submissions and identity checks need attention.

Private US matching forms

MyLife, PeopleFinders and That’s Them have separate own-information reviews. MyLife uses the official privacy-request link to a pinned deletion/opt-out JotForm and fills name, city, state, ZIP and birth year. PeopleFinders fills only required name and US street, city and state, leaving optional email, phone and birth date empty. That’s Them fills the reviewed name, contact email, address and phone. Extra identity fields stay in memory and are excluded from saved workspace data, backups and companion result storage. These actions are outside standard batches. Review the official site’s certification, complete its genuine challenge and submit there yourself.

FamilyTreeNow separately supports a reviewed initial verification form with name, email, subject-only selection, exact communications authorization and genuine hCaptcha. Its optional native submission is an initial attempt; later email and record matching remain unverified.

People Trace UK private form

For a UK workspace, choose Enter private form details in the People Trace UK route. Enter your accurate DOB, telephone and postcode, plus any optional address components. Review the exact values and unchecked own-information authorization. The companion fills only the reviewed official form once; complete its genuine challenge and submission there. Extra identity details are excluded from saved workspace data, backups and companion storage. This separate route is not included in standard batches.

CMA mailing preference

For a Canadian workspace, choose Review mailing preference in the CMA route. Enter and review your own mailing address. The optional submission choice starts unchecked and requires a separate exact-field authorization. CMA registration suppresses eligible addressed marketing; it does not delete broker records. The address stays outside saved workspace data and backups. A native attempt does not prove registration acceptance.

SmartBackgroundChecks

The companion opens the official privacy page and verifies its published Opt-Out Form link before navigating to the reviewed removal form. No profile values go to the privacy entry page. Name/email filling and optional guarded initial submission require the exact own-request agreement and genuine challenge response. Blocked or changed navigation stops the action. Later confirmation, matching and deletion remain unverified.

More private form reviews

Intelius, TruthFinder, Instant Checkmate and US Search have separate association/relative opt-out prefills. These do not suppress complete background reports or delete accounts. Review your accurate name, birth date, city, state and contact email; complete final verification and submission on that brand’s site. No outcome propagates between brands.

DNCL and Residential TPS support only first-number preparation, not completed registration or broker deletion. 192.com fills your own first name, surname, full postcode and contact email, leaving optional phone and other people blank. Canada411 fills your own name, listed number, email and privacy reason for web-only removal. Challenges, email confirmation and final submissions remain on the official sites.

TruePeopleSearch’s initial name/email verification form supports an optional guarded submission after its exact contact authorization and genuine hCaptcha response. Its privacy-entry link and pinned form are checked before profile disclosure. Later matching and deletion remain unverified.

Set up removal-only email

The free local setup screen handles account details, file selection and installation on your computer. It reads no messages and uploads no credentials to the hosted app. A separate Gmail account is required. Eligible accounts can choose an app password in the local screen without a Cloud client; this option requires Google 2-Step Verification and app-password availability. Google sign-in with your own Desktop client remains available for other accounts. A shared publicly approved client is not included.

Download email setup · Full setup guide

1. Create a Gmail account used only for removal requests. For a new Google sign-in connection, prepare the Google connection file. A matching existing connection can be reused.
2. Extract the download into a folder you will keep. On Mac open tools/setup-removal-mail.command; on Linux run tools/setup-removal-mail.sh. A private local browser page opens. Choose Copy companion ID in the extension, paste it into the page, select your Google file and authorize only the separate account. No Terminal answers are needed.
3. Enable local connectors in the companion. Return to Erase Me and choose Connect my removal-only mailbox. This verifies account identity without reading messages.

If your file manager does not run the launcher, start the same page with python3 -I -B tools/mail_setup_web.py. The popup can copy this command with its ID already included. Python 3.10+ and macOS Chrome or Linux Chrome/Chromium are required; Windows and mobile native setup are not included.

The setup session is bound to your computer and expires after ten minutes. Choose Close local setup to stop further installation steps; an installation already started may finish. Closing the browser tab alone does not reliably cancel an authorized Google operation. No recurring work is installed.

Supported local contacts cover FastPeopleSearch, USPhonebook and SearchPeopleFree. The latter’s authenticated links remain held pending a reviewed continuation contract. Record-associated People Data Labs and Apollo addresses are never substituted. Holding a local route revokes its mail grant. Credentials, raw messages and private confirmation URLs stay outside workspace backups; scoped capabilities remain sensitive backup data.

Reviewed privacy-email sending

Seven fixed privacy contacts support a separate one-shot email action: 411.ca, ukphonebook.com, Das Örtliche/DTM, Cepten Numara Sorgula, NumaraAra, BeenVerified and PeopleLooker. The local setup option Allow reviewed privacy-email sending starts unchecked and requires fresh Google consent. Existing read-only connections stay valid. The same saved account can reuse its private Desktop client during an explicit reconnect.

Affirm an own-information request and enter an accurate own-record reference inside Erase Me. Review the exact dedicated From address, fixed To address, subject and body, then authorize Send once. The primary email is never appended automatically. The native helper reserves an operation before Google’s API call. It stores only hashes and outcome references, not the name, record reference or message body. Unknown results are held without automatic retry. Closing an unsent review revokes its grant; an already-reserved send may finish.

A Gmail-accepted message is not proof of delivery, broker acceptance or deletion. Support and registry contacts remain procedure drafts. Held requests stay held; no personal inbox or recurring check is used. See the recipient sources and safeguards.

Local text-challenge helper

The helper is a separate per-user installation for macOS Chrome or Linux Chrome/Chromium. It uses your local Tesseract executable and starts only for an explicit action. After installing it from the source instructions, choose Enable local challenge helper in the popup, grant optional nativeMessaging access, then choose Check local challenge helper in the workspace.

The helper sends no media to a recognition service and downloads no model. Its underlying audio capability does not enable a reviewed Chrome reCAPTCHA audio flow. Managed challenges, image grids and other site codes are not universally supported. Nothing fabricates vendor response tokens.

Install or check the local helper

Find and match a record

Find my listing opens a Google search only when you choose it. Google receives your name and optional city. Search results alone do not confirm a match.

The optional Spokeo structured-record check opens only the direct listing URL you approve. It can supply own-listing approval only from one compatible structured Person record on that exact page, with your normalized name and typed identity email. Age and city alone are insufficient. Missing data, conflicts and blocked pages need attention. The latest live Spokeo research returned HTTP 403; no current live match or deletion has been verified.

Removal-only mail

The dedicated-mail relay is a gated private operator pilot. It uses a separate removal-only Gmail account and a private operator key. It does not connect to personal inboxes. Contact aliases still require separate per-route authorization; a shared contact is not proof of a record’s identity.

Eligible removal contacts can be prepared together before a fresh exact-field review. An optional batch mail step checks qualifying bound operations once after all selected form results are saved. A mail-only pass can check existing bound operations without resending their forms. The operator key stays only in session memory and is cleared afterward. Pending mail starts no polling or future check.

USPhonebook and FastPeopleSearch have reviewed confirmation-form links. After authentication and field review, the companion can fill USPhonebook's approved name, city, state, ZIP and contact fields, or open FastPeopleSearch's matching form and check the already-prefilled name and contact. USPhonebook still requires additional identity information directly on its official form. FastPeopleSearch supports the transient in-app review described above; its current required controls include DOB, street address and phone. Accuracy statements, genuine challenges and unreviewed broker stages still need attention. Both live pilot requests remain held. SearchPeopleFree cannot issue new shared aliases. People Data Labs and Apollo retain their record-associated email requirements.

Hold and reconcile

Hold this route stops new form, search, matching and mailbox actions. Resume this route releases the hold explicitly while keeping the references that prevent duplicate actions. Holds survive private backups and campaign pause/resume.

Check existing broker tab can read a fresh verification acknowledgment from the original tab without resending its form. This remains limited to People Data Labs and USPhonebook’s first stage, with the original submission proof. Closed or changed tabs, lost browser-session proof and unreviewed outcomes remain unknown. Verification initiation is not a completed removal.

Other channels and limits

The catalog has 43 routes, with 28 reviewed form actions and eight privacy-email routes. NumaraAra overlaps both sets, so 35 routes have an executable form or email action and eight remain guidance-only. These are initial actions, not completed removals. Current route review shows official sources and limits for the 37 routes outside the original six. Marketing registrations such as CMA, DNCL and TPS set preferences; they do not delete broker records. Provider phone, postal and subscriber-SMS steps remain yours. The app makes no calls, sends no SMS and performs no paid lookup.

Official contact alternative offers local drafts for 24 fixed published contacts. A privacy channel needs your own record reference; a support or registry contact gets an identifier-free procedure question. Review, copy or download the draft privately. Nothing is sent by that draft feature.

There are no ID uploads, paid solvers, recurring checks or scheduled retries. Unsupported challenges, missing identity details, unreviewed email destinations and ambiguous records need attention. An interrupted action is held rather than repeated. A prepared form, submission attempt or confirmation email is not a verified deletion.

Mobile browsers can use the workspace and official broker links. Companion actions require desktop Chrome.

Clearing site data removes your workspace. Export a private backup first. Removing the extension deletes its local operation references and owned-tab metadata, not the browser workspace. These references contain outcomes and evidence tags rather than profile fields. Browser-session acknowledgment proof is temporary; losing it leaves an outcome unknown.