Evidence Snapshot • Page reviewed October 11, 2026

Data Broker Opt-Out Friction & Identity-Verification Evidence Snapshot

An evidence-gated examination of 1,043 catalog entities. Counts reflect documented source observations; unknown workflow fields are not converted into negative results.

Captured Population: 1,043 Catalog Entities
Bounded evidence-ready profiles: 1,010
Source snapshot: September 25, 2026 · CC-BY 4.0
Methodology: TriState workflow modeling

Core Evidence Findings (Answer-First Summary)

Government-ID observation
99.6%

561 profiles document a positive identity-document observation within a sample of 563. A positive observation can be conditional; 480 remain UNKNOWN, so this is not a universal mandate or provider outcome.

Sample: 563 | Unknowns: 480
Documented web form or portal
75.9%

792 profiles have a source-backed YES observation for an interactive web form or privacy portal. A documented form is a request channel, not evidence that a submission is accepted or completed.

Population: 1,043 | Unknown: 251
Documented email pathway
93.4%

974 profiles have a source-backed YES observation for a direct email workflow. DNS reachability alone does not establish mailbox ownership, legal entitlement, or request success.

Population: 1,043 | Unknown: 69

Profile-URL requirements are not reported: the catalog has no complete, source-backed denominator for them, so they are not inferred from broker category.

Frequently Asked Questions & Evidence-Bounded Answers

Q: Do people-search data brokers require photo ID to remove information?

The captured evidence does not support a universal yes/no answer for all people-search providers. Check the current provider workflow; UNKNOWN means the requirement was not documented, not that no ID can ever be requested.

Q: What does this snapshot show about common opt-out barriers?

The most defensible answer is source-specific: the captured snapshot has 1,043 UNKNOWN CAPTCHA observations and 1,043 UNKNOWN email-confirmation observations. No prevalence rate is published where the denominator is incomplete.

Q: How long does data removal take across different broker categories?

No universal turnaround average is published by this snapshot. Provider-stated timelines and legal response periods must be read for the specific jurisdiction, controller, request, and applicable exceptions.

Documented Submission and Verification Observations (N = 1,043)

Data brokers use different request channels, and some records separately document identity-verification steps. The table counts only source-backed workflow observations in the captured catalog; it does not measure acceptance, completion, or removal success.

ObservationAudited EntitiesRecorded Share (% Universe)Friction RatingMethodology Notes
Interactive Web Form / Portal79275.9%Not scoredSource-backed workflow observation; reachability is separate.
Direct Email / mailto: Suppression97493.4%Not scoredA documented email channel is not proof of delivery or response.
Phone verification observation40.4%Not scoredOnly explicit source-backed phone, SMS, or telephone verification observations are counted; a contact channel alone is not treated as verification.
Postal-mail pathway observation48346.3%Not scoredA documented postal channel is not necessarily postal-only, notarized, or mandatory.

Documented workflow signals, separated from unknowns

Each row uses the 1,043-entity catalog universe and preserves YES, NO, and UNKNOWN states. This makes missing evidence visible instead of treating it as a negative result.

Direct email / mailto support974 yes · 0 no · 69 unknown
YES 93.4%NO 0.0%UNKNOWN 6.6%
Web form / portal support792 yes · 0 no · 251 unknown
YES 75.9%NO 0.0%UNKNOWN 24.1%
Phone verification observation4 yes · 0 no · 1039 unknown
YES 0.4%NO 0.0%UNKNOWN 99.6%
Postal-mail pathway observation483 yes · 560 no · 0 unknown
YES 46.3%NO 53.7%UNKNOWN 0.0%
Government-ID observation561 yes · 2 no · 480 unknown
YES 53.8%NO 0.2%UNKNOWN 46.0%
Tri-state workflow observation counts
ObservationUniverseKnown samplePositive share of known sample
Direct email / mailto support1,043974100%
Web form / portal support1,043792100%
Phone verification observation1,0434100%
Postal-mail pathway observation1,0431,04346.3%
Government-ID observation1,04356399.6%

Chart by OfflistMe · offlist.me

Reading boundary: A YES observation can be conditional and does not prove that a request was delivered, accepted, completed, or successful. UNKNOWN means the field was not source-backed in this snapshot.

Catalog Difficulty Snapshot by Industry Category

Groups the catalog's recorded 1.0–5.0 difficulty labels by industry category. These are editorial evidence fields, not an independently measured effort, success, or removal-outcome score.

Credit, Risk & Identity2.9 / 5.0
235 cataloged broker entities
Marketing & Audience Data2.9 / 5.0
352 cataloged broker entities
People Search & Public Records3.0 / 5.0
92 cataloged broker entities
Advertising & Adtech3.1 / 5.0
141 cataloged broker entities
B2B & Sales Intelligence3.0 / 5.0
148 cataloged broker entities
Social, Marketplaces & Platforms3.0 / 5.0
66 cataloged broker entities
Top German Data brokers3.3 / 5.0
9 cataloged broker entities
Open Access Machine-Readable Research Dataset

Download Removal Friction Evidence Snapshot Dataset

Machine-readable JSON and CSV datasets containing captured coverage metrics, documented channel observations, denominator boundaries, and TriState values. License and reuse terms are stated in the dataset documentation.

Data Dictionary:View Schema Docs
Records Included:1,043 catalog entities; evidence status per profile
License:CC-BY 4.0 International
Version:v2026.08 (Reproducible)
Suggested Citation
OfflistMe Privacy Intelligence Lab. (2026). Data Broker Opt-Out Friction & Identity-Verification Evidence Snapshot (Version 2026.09) [Data set]. OfflistMe. https://www.offlist.me/data-broker-opt-out-friction-study

Methodology & Reproducibility Protocol

All metrics presented in this snapshot are derived using a deterministic TriState workflow-observation system. Observations are classified strictly into YES, NO, or UNKNOWN states. Unverified fields are never treated as negative evidence; they remain transparently reported as UNKNOWN.

Independent researchers can verify these calculations by cloning the OfflistMe repository and executing npm test and npx tsx -e "import { getRemovalFrictionBenchmark } from './lib/privacyIntelligence'; console.log(getRemovalFrictionBenchmark());".