Data broker exposure is a broad Cunicula lane: people-search sites, location brokers, removal routes, required disclosure fields, re-listing, and verification.
Data Broker Exposure Is the Privacy Work Queue
Data brokers turn ordinary life into a searchable surface: names, home addresses, phones, emails, relatives, prior locations, property records, location signals, purchase segments, and derived inferences. For a privacy directory, that is not a side topic. It is one of the places where privacy becomes operational work.
The useful angle is not outrage. The useful angle is the work queue: who has the data, what they show, which route removes it, what must be disclosed, what blocks automation, and when the result needs to be checked again.
Primary sources
- Privacy Rights Clearinghouse data broker overview
- FTC action against Gravy Analytics and Venntel
- FTC action against Mobilewalla
- California DROP official page
- Google Results about you removal help
- unbroker upstream docs
The broader lane
unbroker is one tool inside a larger theme. The theme is companies collecting, inferring, packaging, reselling, exposing, or indexing personal data without a normal user relationship.
| Surface | What it exposes | What matters |
|---|---|---|
| People-search sites | Addresses, phones, relatives, aliases, age, prior locations | Opt-out route, parent cluster, re-listing rate, proof after re-scan |
| Location brokers | Mobile location trails, venue visits, sensitive-place segments | Source app path, consent claim, sensitive-location use, enforcement history |
| Marketing databases | Purchases, demographics, household segments, inferred traits | Opt-out method, data source, sharing chain, suppression limits |
| Public-record aggregators | Property, court, voter, business, license, and lien records | Source jurisdiction, suppression option, public-interest exception |
| Search indexes | Broker pages surfaced through Google and other search engines | Delisting path, source-page removal, cache refresh |
| Removal services | Managed opt-outs and monitoring dashboards | Coverage, verification, reporting, PII custody, pricing, blind spots |
| Agent workflows | Automated scans, opt-outs, email verification, ledgers, re-checks | Consent, local storage, least disclosure, human fallback |
What unbroker data is worth
The person-specific dossier is only the input for a run. The reusable value is the operational intelligence around brokers and removals. Cunicula now tracks that as a field model in What Data Broker Removal Runs Should Teach Cunicula.
| Data | Use | Cunicula value |
|---|---|---|
| Subject dossier | Names, aliases, emails, phones, current and prior locations for one consenting person | Run input. Useful for that person only. Not a dataset to sell. |
| Exposure map | Which brokers had a likely match and what kind of exposure appeared | Shows which brokers matter for a risk profile. |
| Removal route | Form, email, CCPA, GDPR, DROP, suppression, deletion, manual task | Turns privacy cleanup into a repeatable work queue. |
| Disclosure fields | The exact fields a broker forces before it will process removal | Measures privacy cost. Some opt-outs require too much data. |
| Parent clusters | Which broker brands are controlled by the same parent or covered by one request | Reduces wasted work and identifies high-leverage targets. |
| Failure modes | Hard CAPTCHA, phone callback, fax, ID request, paid-tier retention, hostile flow | Ranks which sites need human effort and which are not worth pretending to automate. |
| Verification result | Whether the listing stayed down after re-scan | Separates real removal from cosmetic or temporary suppression. |
| Re-listing timing | When a removed record comes back | Creates a monitoring cadence and a product reason to re-check. |
The product value
A normal directory says "here are tools." A data-broker exposure lane can say "here is the removal work, ordered by value." That is much more useful.
- Rank brokers by exposure severity, not brand awareness.
- Track parent companies and duplicate broker shells.
- Track which removals actually survive a re-scan.
- Track which removals are local, email-based, form-based, legal-request-based, or human-only.
- Track what personal fields a user has to disclose to get a removal.
- Compare self-hosted workflows with commercial removal services.
- Build privacy cleanup stacks for people dealing with doxxing, harassment, scams, or old public exposure.
Where Cunicula should go next
The lane should become a small data product and public guide set:
- A self-host unbroker guide.
- A comparison of unbroker, DeleteMe, Incogni, Optery, EasyOptOuts, and similar services.
- A broker exposure glossary.
- A removal effectiveness table with parent clusters, required fields, fallback type, and re-scan result.
- A privacy cleanup stack for people after doxxing or harassment.
- A buyer-grade export of broker categories, removal routes, source links, and review dates.
Start with the self-host unbroker guide, read the broker intelligence field model, then compare it with the older personal information scrubbing guide.
Frequently Asked Questions
What is data broker exposure?
Data broker exposure is the practical risk created when companies collect, package, index, sell, or expose personal information such as addresses, phone numbers, relatives, emails, location signals, purchases, and public-record links.
What is the value of unbroker data?
The reusable value is not the subject dossier. The reusable value is broker intelligence: where exposure appears, which parent companies matter, which removal paths work, which fields are required, which sites block automation, and which removals survive a later re-scan.