Core Research Findings (Answer-First Executive Summary)
545 profiles explicitly document a YES government-ID observation within a sample of 547. 471 remain UNKNOWN; the result is not generalized beyond this evidence cohort.
The captured dataset does not currently contain a complete, source-backed denominator for profile-URL requirements. The field remains UNKNOWN rather than being inferred from broker category.
952 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.
Frequently Cited Empirical Questions & Definitive 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 is the most common barrier in data broker opt-out workflows?
The most defensible answer is source-specific: the captured benchmark has 1,018 UNKNOWN CAPTCHA observations and 1,018 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 benchmark. Provider-stated timelines and legal response periods must be read for the specific jurisdiction, controller, request, and applicable exceptions.
Macro Submission Channel Distribution (N = 1,018)
Data brokers use different request channels. The table counts only source-backed workflow observations in the captured catalog; it does not measure acceptance, completion, or removal success.
| Submission Pathway | Audited Entities | Prevalence (% Universe) | Friction Rating | Methodology Notes |
|---|---|---|---|---|
| Interactive Web Form / Portal | 765 | 75.1% | Not scored | Source-backed workflow observation; reachability is separate. |
| Direct Email / mailto: Suppression | 952 | 93.5% | Not scored | A documented email channel is not proof of delivery or response. |
| Telephone Hotline / IVR Callback | 1 | 0.1% | Not scored | Only explicit phone workflow observations are counted. |
| Postal Mail Only / Notarized Affidavit | 964 | 94.7% | Not scored | A postal channel is not necessarily postal-only or mandatory. |
Removal Difficulty Index by Industry Category
Evaluated on a standardized 1.0–5.0 difficulty scale based on steps required, identity proofs, CAPTCHA obstacles, and email validation loops.
Download Removal Friction Benchmark 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.
OfflistMe Privacy Intelligence Lab. (2026). Data Broker Opt-Out Friction & Barrier Benchmark (Version 2026.08) [Data set]. OfflistMe. https://www.offlist.me/data-broker-opt-out-friction-studyMethodology & Reproducibility Protocol
All metrics presented in this benchmark are derived using a deterministic 13-vector TriState empirical 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());".
Related Canonical Research Assets
Who Owns the Data Broker Industry?
Evidence-backed parent relationships where the captured corpus records them.
Data Broker Research Standard
4-Tier provenance hierarchy and evidence saturation formulas.
State Registry Discrepancy Matrix
Cross-registry analysis of California CPPA and Vermont SOS.