Data Broker Observatory
A transparent view of what two public data-broker registries disclose: who is listed, which sensitive categories are reported, and what consumer-request metrics appear in the California snapshot. This page does not claim that the imported snapshots are the current official registries; use the source links to verify live records.
How this fits the broader broker evidence base
The registry snapshots below are one evidence layer in OfflistMe's broader broker knowledge base. The catalog currently contains 1,043 profiles, including 817 with matched registry context. Route observations and semantic labels remain separate from user-authorized removal outcomes.
1,043
Captured catalog profiles
structured broker records
817
Registry-linked profiles
matched public context
541
Independent routes
read-only route observations
471
Semantic dispositions
review labels; no auto-promotion
The JSON broker index exposes the same bounded records for machine readers. The evidence roadmap explains what still requires independent observation or human review.
California records
603
CPPA snapshot; derived count
Vermont records
278
Secretary of State snapshot; derived count
Active Vermont records
177
Status field; derived count
California deletion requests
58,031,327
2024 fields summed; derived total
California: what registrants reported
The following values are calculated from the imported California registry fields. The source registry describes the underlying submissions; OfflistMe sums or counts them here.
Deletion requests
58,031,327
Sum of each record’s 2024 deleteTotal field
Reported complied
56,972,890
98.2% of the summed deleteTotal fields
Reported denied
890,712
1.5% of the summed deleteTotal fields
Reported sensitive categories
Source for each category flag: CPPA Data Broker Registry. Counts are OfflistMe-derived from the imported records.
Vermont: status and reported breaches
The imported Vermont snapshot contains 278 records, of which 177 have a status value of ACTIVE. The records report 4 breach events in the prior-year field. These are derived counts from the local snapshot, not an independent breach investigation.
Multi-State Registry and Source Matrix
Across the captured 1,043-profile catalog, we compared recorded matches across California CPPA, Vermont SOS, and SEC EDGAR sources:
California Snapshot Matches
623
Matched in captured CPPA registry data
Vermont Snapshot Matches
201
Matched in captured Vermont registry data
Multi-Source Overlap
82 (7.9%)
Present in at least two captured sources
Both CA & VT Snapshot Matches
78
Matched in both captured CA and VT snapshots
Evidence Completeness Matrix
OfflistMe evaluates 9 evidence dimensions across 1,043 captured catalog profiles (Identity, Data Practices, Ownership, Removal, Friction, Legal, Registry, Sources, Freshness). A known field is not the same as a verified outcome.
Verified catalog records
1043
Source + identity + route provenance gate
Evidence-ready profiles
1041
Identity + qualifying route-evidence gate passed
Partial profiles
2
Useful evidence; one or more gates remain
Review required
0
Conflict or insufficient identity/route evidence
Evidence-ready promotion queue
2 catalog records still need qualifying route evidence before the bounded gate can pass. The queue is generated from machine-readable blockers; adding qualifying first-party or read-only evidence and rerunning the generators updates the record. No row below is treated as a completed removal or delivery outcome.
| Record | Priority | Promotion blocker | Evidence profile |
|---|---|---|---|
| AnyWho anywho.com | P2_MEDIUM | email route validation required | 41.47% completeness; unknowns remain explicit |
| KOLs (Key Opinion Leaders) keyopinionleaders.com | P1_HIGH | route modality review required | 27.52% completeness; unknowns remain explicit |
Living Privacy Events & Temporal Stream
A dated audit log of source-backed data broker milestones, regulatory consent decrees, opt-out workflow migrations, and state registry filings:
Download California snapshot fields
This export contains imported registry fields and derived labels. Verify against the official source before republication.
What this page does not prove
- A registry entry does not prove that every disclosed field is accurate or current.
- A reported deletion metric does not establish a universal compliance rate or removal guarantee.
- A sensitive-category flag identifies a registry disclosure; it does not independently verify the broker’s collection practices.
- Derived totals describe this imported snapshot and may change when the underlying agency data changes.