Data brokers price data the way derivatives desks price risk: not by the asset itself, but by the liability attached to it. As a compliance auditor, I read broker contracts the way I read swap confirmations — tracing what changes hands, who can unwind it, and at what latency.
A broker's quote has three verifiable drivers:
1. Match rate and freshness. A record with a verified email, current employer, and device ID carries a premium because it converts before decaying. Walk away from any contract that lacks a last_verified_at timestamp in the data dictionary. Refusal to expose it is an admission that the data is stale.
2. Redistribution scope. "Full license" versus "single-campaign use" changes price by an order of magnitude. The audit mechanism here is mundane but essential: every downstream table must carry a license tag. Without that tag, you cannot prove to a regulator that a third-party query did not repackage the data. Trace the license terms down to the SQL query, not the contract signature page.
3. Regulatory exposure. GDPR Art. 17 and CCPA/CPRA deletion obligations turn data into a running cost. A broker that cannot demonstrate deletion within the statutory window is selling a liability. The premium charged by brokers with an auditable deletion workflow is justifiable — but verify it via the deletion endpoint, not the sales deck.
What I check as an auditor during broker negotiation:
Provenance manifest. Every record must carry origin source, collection timestamp, and consent scope. "Inferred interests" is a red flag — I have seen contracts where "inferred" meant three links of resold data, none of which had consent. Ask for the inference logic in writing. If the broker calls it proprietary, the risk is yours.
DSAR propagation. Ask how the broker routes subject access requests. Do they propagate the request upstream to their own sources, or do they delete only their copy? If the latter, the buyer inherits every downstream obligation. That is a process failure you can test with a sandbox record.
Deletion latency. Measure time from deletion request to actual removal across all replicas. A deleted email that survives in a monthly backup restored for analytics is not deleted. Demand the restore-and-purge window in the SLA.
The trade-offs are concrete. A compliant broker charges more because compliance is real engineering: consent receipts, retention windows, deletion scripts, audit logs. That premium is observable and defensible. A cheap broker transfers the residual risk to you — also observable, also defensible, only if your risk budget says so.
Compute a fair price from your own data processing register. For each dataset, estimate match rate, refresh cadence, consent coverage ratio, and deletion latency. Price per record should rise with match rate and consent coverage, and fall with deletion latency. When the broker quote deviates sharply, demand the audit artifacts before signing.
Pricing power shifts the moment the buyer can verify the underwriting assumptions. If a broker claims raw logs, ask to inspect a sample. If they claim consent coverage, ask for the receipts. If they cannot produce either, the data is worth exactly zero — because the first regulator who asks will have the same question, and the broker's pricing formula will be irrelevant to the fine.
Top comments (0)