Broker knowledge base

1000+ 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.

Browse the directory →Read the evidence methodology →Download the broker index →Open JSON index →Read the evidence roadmap →View enrichment priorities →View the evidence program →

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.

1018

catalogued broker records

data-broker categories

24-hour

page revalidation window

803

records with registry context

records needing evidence review

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.

524

Web route checks

read-only URL observations

493

DNS-checked email routes

mailbox not verified

524

Current web evidence

positive route signal

985

Observed URL routes

461 need route-semantics review

Route observation queue

failed URL observations queued for recheck

150,329

Evidence facts

source-linked observations

803

Registry context

matched public records

Evidence conflicts

kept explicit, not hidden

Deep evidence: 671Useful evidence: 347Basic 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.

Coverage snapshot as of 2026-08-13. 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.

Generate review-and-send drafts →

Advertising & Adtech

135 profiles

B2B & Sales Intelligence

134 profiles

Credit, Risk & Identity

231 profiles

Marketing & Audience Data

336 profiles

People Search & Public Records

99 profiles

74 profiles

Top German Data brokers

9 profiles

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 customer-ready catalog contains 1018 broker profiles. 803 have matched government-registry context, and the coverage dossier contains 150,329 evidence facts. These figures describe documented catalog evidence, not completed removals.

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 461 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.