Old leads are not automatically valuable assets; they can become untraceable consent and breach liabilities.
Quick View
Keep only contacts with a defensible source, current purpose and working suppression control.
Export all contact sources.
Source and import logs.
Buying unverified lists.
Why It Matters
The Digital Personal Data Protection Act, 2023 and the final Rules notified in November 2025 follow phased commencement. As of 25 June 2026, organisations should separate duties already operative from consent, grievance, rights, children, Significant Data Fiduciary and other operational provisions scheduled for later commencement, while continuing to comply with the IT Act, CERT-In directions and sector-specific rules already in force.
Future DPDP consent and withdrawal duties should be built into CRM governance, while current telecom, consumer and platform requirements continue to apply.
Database cleanup should preserve suppression identifiers where necessary to prevent re-marketing, without keeping the full profile indefinitely.
Control Framework
| Area | What to establish | Operating rule |
|---|---|---|
| Source | Form, partner, event or purchase. | Prove provenance. |
| Age | Last valid interaction and purpose. | Set review trigger. |
| Preference | Channel and withdrawal status. | Centralise. |
| Copies | CRM, spreadsheets and vendors. | Delete consistently. |
Action Checklist
- Export all contact sources.
- Remove records with no provenance.
- Separate customers from leads.
- Consolidate suppression lists.
- Stop vendor re-imports.
- Document deletion and retained suppression keys.
Practical Example
Evidence to Keep
- Source and import logs.
- Consent or preference record.
- Campaign history.
- Suppression list.
- Vendor deletion confirmation.
- Cleanup approval.
Warning Signs
- Buying unverified lists.
- No source field.
- Suppressing email but not phone.
- Retaining dormant profiles forever.
- Restoring old backups into live campaigns.
Detailed Review
A reliable control should connect the individual, data field, purpose, notice or sector disclosure, system, employee access, vendor access, retention rule and closure evidence. A policy statement that cannot be traced through this chain is difficult to operate.
Maintain a legal-timing matrix. Record the DPDP provision, phased commencement status, current IT Act or sectoral duty, business owner, system dependency and implementation deadline. Avoid one blanket label such as compliant or not compliant.
Build controls into technology and workflow. A written instruction cannot stop an SDK from collecting contacts, a campaign tool from re-importing suppressed users or an agent from downloading medical records unless the system enforces the decision.
Use proportionate verification. Weak checks can expose another person’s information; excessive checks create more Aadhaar, health, payroll or bank data that must be protected and deleted later.
Generate evidence during ordinary operations: versioned screens, event logs, access approvals, vendor tickets, complaint chronology, deletion reports, test recordings and management decisions.
Run a negative-path test: refusal, withdrawal, account closure, vendor breach, employee exit or child-user flow. The control should continue to protect data outside the happy path.
Management reporting should show overdue actions, repeat complaints, failed tests and residual risk rather than only the publication of policies.
Control Test
Select one real user or transaction journey and trace it from collection through sharing, access, retention, withdrawal, complaint or closure. Capture the evidence at each stage.
Test the control on production-like systems rather than screenshots alone. Review network traffic, event logs, suppression status, vendor responses, role access and deletion output.
Run an adverse scenario: the vendor is breached, the user is a child, the borrower alleges harassment, the employee leaves or the app permission is revoked. Record the response and gaps.
Compare public wording with actual behaviour. Product forms, call scripts, privacy notices, contracts, SDKs and support tools should tell the same story.
Assign a named owner, funded action and closure date to each gap. Retain the reason when management accepts residual risk or chooses a less intrusive alternative.
Escalation Route
Start with the privacy, security, product or regulated-business owner and preserve system evidence before changing configuration or deleting records. Separate current sector and CERT-In obligations from future DPDP readiness.
For serious complaints, children’s data, financial harassment, medical exposure or suspected cybercrime, involve qualified legal, privacy, cyber, banking, insurance or healthcare specialists and use the applicable official channel.
Common Questions
Should every old lead be deleted?
Review purpose, permission, legal need and suppression requirements.
Can suppression data be retained?
A limited identifier may be needed to prevent future contact.
Who should approve imports?
A defined marketing-operations and privacy control.
How often should cleanup run?
Continuously for withdrawals and periodically for age, inactivity and provenance.
Official Sources
- MeitY — Digital Personal Data Protection Act 2023 PDF
- MeitY — Digital Personal Data Protection Rules 2025
Use current commencement notifications, final Rules, CERT-In directions and sectoral regulator material. Applicability depends on dates, roles, systems, users and facts.