A marketing-database clean-up method covering source, age, purpose, channel, consent evidence, TRAI controls, suppression and inactive leads.
A database is not valuable merely because it is large. Unverifiable and stale leads increase complaint, spam and impersonation risk.
The DPDP framework is phased. The 14 November 2025 commencement notification brought specified institutional and enabling provisions into force immediately; Consent Manager-related provisions follow after one year; most operating duties and Rules follow eighteen months after Gazette publication. As of 22 June 2026, the control should distinguish current obligations from future-state DPDP readiness.
Future DPDP consent controls require specified purpose and meaningful withdrawal.
TRAI separately regulates commercial messages, sender registration, templates, consent and customer preferences.
Purchased, event, referral, partner and legacy leads should not be merged without provenance.
| Check | What to examine |
|---|---|
| Source | Where and when the lead was collected. |
| Purpose | Requested response, customer service or promotion. |
| Channel | Email, SMS, WhatsApp, call or push. |
| Evidence | Notice, consent, sender and timestamp. |
| Status | Active, stale, withdrawn, bounced or disputed. |
A company imports five-year-old event leads into WhatsApp campaigns. The spreadsheet has names and numbers but no form wording, date or channel permission. The data should not be treated as current consent.
Score leads by evidence and age. Quarantine records lacking source rather than treating silence as permission.
Synchronise suppression across CRM, dialler, agency, telecom and data warehouse.
Identify the people, data, systems, purpose, owner, processor, user journey and failure scenario. Review source, purpose and channel together. A policy statement or vendor assurance cannot replace evidence of how the live product behaves.
Apply the 14 November 2025 commencement notification provision by provision. Continue complying with currently operative CERT-In, banking, telecom, insurance, employment, consumer, contract and criminal-law requirements. Build the scheduled DPDP workflow now, but do not describe a future provision as already enforceable.
Run the workflow in the live or controlled test environment. Preserve screenshots, approvals, logs, vendor responses, user communications, exceptions and remediation. Assign a named owner and completion date to every failed control so management can distinguish an operating safeguard from a policy intention.
Privacy and cyber maturity are visible in operating behaviour: what the organisation collects, who can use it, how vendors are controlled, how users exercise choices, how incidents are handled and whether evidence survives scrutiny.
Use the current official instrument, portal or regulator publication before acting. This panel separates the category authority from page-specific references.