Purchased list age verification
Why it matters
GDPR Art. 5(1)(d) requires that personal data be kept accurate and up to date. Purchased contact lists degrade rapidly — industry benchmarks cite 22–30% annual data decay on B2B contacts. Importing a 6-month-old list without a date check means you are processing data the vendor has already cycled out, inflating your bounce rate and contacting people who have changed roles or departed. GDPR Art. 13 requires you to inform data subjects of the data source; stale lists may have been collected under expired consent. CCPA §1798.100 adds a parallel obligation to ensure data accuracy.
Severity rationale
High because importing stale purchased lists without age verification risks GDPR Art. 5(1)(d) accuracy violations and exposes the company to outreach based on outdated, potentially withdrawn consent.
Remediation
Add an age validation step to every list import path that rejects lists exceeding 90 days since collection date. The validation must run before any records are inserted.
// src/lib/list-import/validate-age.ts
export function validateListAge(collectedAt: Date): void {
const ageDays = (Date.now() - collectedAt.getTime()) / 86_400_000
if (ageDays > 90) {
throw new Error(
`List is ${Math.round(ageDays)} days old. Purchased lists must be collected within the last 90 days (GDPR Art. 5(1)(d) accuracy requirement).`
)
}
}
Record the collected_at date on the import job row so compliance teams can audit which lists were accepted and when.
DetectionPro
The detection method for this pattern is part of AuditBuffet Pro.
The full method (what to look for, pass and fail conditions, and how results get reported) ships inside the Data Sourcing & Provenance Audit. The pattern definition, severity rationale, and remediation remain openly licensed under CC-BY-4.0.
External references
- gdpr · Art. 5(1)(d) — Accuracy — personal data must be accurate and kept up to date
- gdpr · Art. 13 — Information to be provided — source and collection date required for transparency
- ccpa · §1798.100 — Right to accurate information about data source and collection
Taxons
History
- 2026-04-18·v1.0.0·Initial import from data-sourcing-provenance·automated