How to remove yourself from people-search sites

If you've just searched your own name and found your home address, phone number, relatives, and employment history on a stranger's website, you're not alone — and there is a way out. This guide walks through how to remove yourself from people-search sites in plain English: who these aggregators are, which registry-backed brokers are most likely to list you, the legal rights that force them to delete you (in California under CCPA §1798.105 and in the EU under GDPR Art. 17), and why a one-time opt-out almost never sticks.

What people-search aggregators do

People-search aggregators are data brokers whose entire business model is buying public records, voter rolls, court filings, social profiles, and leaked marketing lists, then repackaging them into searchable profile pages. Their customers are not you — they are background-check services, debt collectors, marketers, fraud analysts, and curious strangers. The profiles they build are stitched together from many sources, which is also why a single "remove me" request is rarely enough to make you disappear.

A typical listing will bundle:

• Your full name and any known aliases (including maiden names).
• Current and past home addresses, often down to the unit number.
• Phone numbers — landline, mobile, and sometimes the original carrier.
• Email addresses pulled from old data breaches and marketing lists.
• Age, date of birth, and sometimes the names of immediate relatives.
• Employment history, education, and estimated income band.

The brokers PrivacyPulse monitors today

PrivacyPulse monitors the same set of brokers the product files removal requests against. Showing the list here — and pulling it from the registry, not typing it in — means the article stays correct as new brokers are added or retired. Each card links to the broker’s own opt-out page so you can act today, even before you sign up.

Your right to be forgotten: California (CCPA §1798.105)

In practice, because most people-search brokers either operate in California or sell to California residents, they accept these requests nationwide. The California Attorney General has repeatedly affirmed that opt-out requests submitted by agents (someone acting on your behalf) are equally valid.

What this means in practice:

1. Send a verifiable consumer request to each broker’s opt-out channel (web form or email — see the cards above).
2. The broker must verify your identity using reasonable methods — usually a name + address match against their own listing.
3. They must respond within 45 days and delete or de-identify the data, and they must notify any service providers they shared it with.
4. You can authorize an agent (a person or a service like PrivacyPulse) to file on your behalf — the broker must honor it.
5. If the broker refuses, you can escalate to the California Attorney General and the California Privacy Protection Agency.

Your right to erasure: GDPR Article 17

Article 17 is the European counterpart to the CCPA’s deletion right, with a similar shape and a tighter deadline (30 days instead of 45). Brokers that operate internationally typically honor GDPR erasure requests globally, because flagging opt-outs by jurisdiction is more work than just honoring them everywhere.

What this means in practice:

1. File an erasure request that identifies you and the data you want removed.
2. The controller responds within 30 days (extendable by 60 days for complex requests, with notice).
3. Narrow exceptions exist for public-interest journalism, legal compliance, and public-health research — but they do not apply to a commercial people-search listing.
4. If the controller refuses, you can file a complaint with your national Data Protection Authority (DPA) — most take individual complaints at no cost.

Why one-time removal fails

A single opt-out request removes today’s record, but the broker will re-ingest the same underlying public-records feeds next month — voter rolls, county assessor records, new marketing-database leaks — and your profile is rebuilt from scratch. Empirically, a listing removed in week 1 is back, in some form, by week 6. The fix is a continuous loop: scan → file → verify → re-scan. PrivacyPulse runs that loop for you so that "removed" stays removed.