Skip to main content

Broker knowledge base

1,000+ data broker profiles with evidence boundaries

Each profile records the provider route, request workflow, source-check date, identity-verification boundary, registry context when matched, and evidence to keep. Route reachability is not acceptance, delivery, deletion, or a promise that data will not reappear.

What makes OfflistMe different

A self-serve privacy workflow, with the evidence left visible

OfflistMe prepares broker-specific drafts and routes in the browser. You review the details, send or submit the request yourself, save any response, and follow up. That model means no OfflistMe account is required, no government ID is uploaded to OfflistMe, paid plans are one-time rather than recurring subscriptions, and the same paid access can be used by family and friends without an extra platform charge.

No account

Start without creating an OfflistMe account.

No ID upload to OfflistMe

If a broker asks for verification, you decide directly with that provider.

No recurring subscription

Paid access is designed around a one-time pass, not automatic renewal.

Family-friendly access

Share the same paid access with family and friends without an extra platform charge.

These are workflow and pricing distinctions, not a promise that a broker will accept, process, or complete a request. The person making the request remains responsible for reviewing and sending it.

Evidence completeness, precisely stated

All 1043 records have an explicit field state

The captured snapshot assesses 258 tracked fields per record. That gives every record a reviewable known, not-recorded, or unknown state; it does not claim every field is known or that every source was searched.

Open the full assessment →

146,575

Known states

122,456

Not recorded

63

Explicit unknowns

Opt-Out Burden Score by broker category

Median score across 1,034 catalog brokers is 28 of 100. 341 Light, 673 Moderate, 18 Heavy, 2 Severe.

  • Median Opt-Out Burden
  • Median Exposure Reach
Social, Marketplaces & Platforms33 burden
10 reach
Marketing & Audience Data28 burden
13 reach
Credit, Risk & Identity28 burden
13 reach
B2B & Sales Intelligence27 burden
18 reach
Advertising & Adtech26 burden
16 reach
People Search & Public Records26 burden
38 reach

Chart by OfflistMe · offlist.me

Burden weights: catalog difficulty 45, government ID 15, sensitive identifiers (SSN, date of birth, ID numbers) 10, confirmation loop 5, email-only route 10, noindex on the opt-out page 15. Categories with fewer than 20 brokers are omitted. OBS v1 (2026-10-31); ERS v1 (2026-10-31). Full method

Show the data as a table
Opt-Out Burden Score by broker category data table
CategoryBrokersMedian burdenMedian reachHeavy or Severe burden
Social, Marketplaces & Platforms6633100%
Marketing & Audience Data35228131%
Credit, Risk & Identity23528136%
B2B & Sales Intelligence14827181%
Advertising & Adtech14126160%
People Search & Public Records9226382%

Sources: OfflistMe broker directory · Removal friction benchmark (CSV) · State data broker registry crosswalk · Corporate ownership graph · Opt-out page noindex scan · Checked catalog snapshot at build

1,043

catalogued broker records

7

data-broker categories

24-hour

page revalidation window

817

records with registry context

31

records with unresolved conflicts

1026

records with open field review

20% authority focus

Start with the profiles where evidence adds the most clarity

The first 209 profiles are ordered by catalog impact, category relevance, documented gaps, and route state. This is a maintenance priority—not a broker-quality ranking, a market-share estimate, or a removal-outcome claim.

209

High-impact profiles

catalog impact signal

209

Workflow sources

profiles with source URLs

187

Registry context

matched official records

206

Open evidence gaps

fields requiring source review

Next authority tranche

Continue with the remaining High-impact profiles

View the full evidence roadmap →

The next 68 explicitly High-impact profiles are prioritized by evidence depth, route state, category relevance, and named gaps. This is a maintenance queue—not a ranking, competitor-share estimate, or removal-outcome claim.

21

Advertising & Adtech

8

B2B & Sales Intelligence

27

Marketing & Audience Data

12

Social, Marketplaces & Platforms

Evidence overview

A route map, not a removal promise

The counts below describe the evidence available for routing and research. They deliberately separate first-party or read-only route observations from mailbox acceptance and removal outcomes.

608

Web route checks

read-only URL observations

434

DNS-checked email routes

mailbox not verified

607

Current web evidence

positive route signal

1002

Observed URL routes

411 need route-semantics review

41

Route observation queue

failed URL observations queued for recheck

243,901

Evidence facts

source-linked observations

1011

Verified catalog records

provenance gate; outcomes not inferred

817

Registry context

matched public records

31

Evidence conflicts

kept explicit, not hidden

Deep evidence: 943Useful evidence: 100Basic evidence: 0

How to read these labels: a catalog route is the route currently attached to a broker record; a provider-source URL is a first-party page observed for context but not automatically promoted as the submission route; a failed observation is retained and queued for recheck; none of these states proves a request was sent, accepted, completed, or not republished.

Evidence snapshot as of 2026-10-23. Source and route dates are shown on each broker profile; the knowledge base is refreshed on a rolling evidence cadence.

Browse every broker profile

Editorial guides remain available for high-intent brokers; these profiles make the long tail explicit and inspectable.

Request Removal Now
FREE

Showing 12 of 141 profiles. View the complete category →

Showing 12 of 148 profiles. View the complete category →

Showing 12 of 235 profiles. View the complete category →

Showing 12 of 352 profiles. View the complete category →

Showing 12 of 92 profiles. View the complete category →

Showing 12 of 66 profiles. View the complete category →

What “source-backed” means here

OfflistMe connects official registries, provider privacy pages, request forms, published contacts, and bounded route observations. A canonical route observation is a positive read-only result for the catalog route. A provider-source URL observation confirms only that a provider-published page was observed; it is not promoted as a submission route until its semantics are reviewed. A failed observation may reflect the observation environment and remains queued for recheck. None of these signals proves that a provider accepted a request, removed a profile, or will not republish information. Users review, submit, save confirmation, verify, and follow up themselves.

Knowledge base FAQ

How many data broker profiles are in the OfflistMe knowledge base?

The current captured catalog contains 1,043 broker profiles. 1011 pass the catalog provenance gate and 1010 pass the bounded evidence-ready gate; 1026 still have open field review. 817 have matched government-registry context, and the coverage dossier contains 243,901 evidence facts. These figures describe documented catalog evidence, not completed removals.

Are all 1,043 broker records fully verified?

No—not fully. All 1010 captured records pass OfflistMe's bounded provenance and route-evidence gate, and explicit approval is required for all 1043. All 1043 records have an explicit state for each of the 258 tracked fields in the captured snapshot, but 17 enrichment field reviews are complete and 1026 remain open.

What does source-backed mean on an OfflistMe broker profile?

A source-backed profile connects provider-published routes, official registry records, published privacy contacts, workflow evidence, or bounded read-only observations to a broker record. A reachable route does not prove request acceptance, delivery, deletion, monitoring, or non-republication.

Does a route check prove that a data broker removed my information?

No. A route check only records what the URL or email-domain observation showed at the stated time. Users must review, send or submit, save confirmation, re-check the source listing, and follow up themselves.

What is the difference between a canonical route observation and a provider-source URL observation?

A canonical route observation is a positive read-only result for the catalog route. The knowledge base now records 482 read-only semantic dispositions for provider-source URLs, but does not promote any page as a submission route until route semantics and entity identity are reviewed. Failed observations remain queued for recheck.