Data Provenance
Data provenance is the documented history of where a piece of data originated, how it was collected, what consents accompanied collection, and what transformations have been applied — critical for compliance defense, quality assessment, and downstream usage rights.
Why This Matters
Provenance documentation has shifted from nice-to-have to compliance-critical. CCPA, CPRA, GDPR, and emerging state privacy laws require organizations to know where consumer data came from and what consents apply. For MCA buying lead data, provenance answers: who collected this, on what website, with what consent disclosure, and what's the data lineage from source to vendor to me. Vendors who can't document provenance create downstream compliance liability for buyers — and increasingly, insurance underwriters and audit committees demand provenance records as part of risk management.
Frequently Asked Questions
Frequently Asked Questions
What provenance information should I require from lead vendors?
Original source URL or platform, consent disclosure text and acceptance timestamp, data collection date, any intermediate brokers in the chain, and applicable state-level disclosures. Vendors who treat provenance as proprietary or refuse to disclose are red flags.
Why is data provenance important for MCA?
TCPA defense relies on documented consent. FCRA defense relies on documented permissible purpose. State privacy law compliance requires source disclosure. Without provenance, every compliance challenge becomes harder to defend, and your insurance and reputation exposure grows.