DPDP Retention Schedule Setup Guide
Establish clear timelines for deleting or archiving personal data. Ensure your business complies with DPDP purpose-limitation and. Get expert help.
Discuss this page with an LLM
DPDP Action Sheet
Use this before your next workflow goes live. It keeps the useful parts visible and turns DPDP into checks your team can actually answer.
For DPDP Retention Schedule Setup Guide, the DPDP question is how personal data enters the workflow, where it is stored, which tools touch it, what purpose was explained, and how deletion or withdrawal will work.
1. Lead Forms
Check:
- What data are you collecting?
- Is the purpose clear at the point of collection?
- Is marketing consent separate from service communication?
- Can the user withdraw consent later?
Common mistake: one checkbox that silently covers newsletters, sales calls, partner sharing and remarketing.
2. Email and WhatsApp
Check:
- Who is on the list?
- Where did consent come from?
- Is the list imported from a vendor, event, webinar, scrape or old CRM?
- Can you prove the source of consent?
Common mistake: treating every lead as permanently marketable.
3. Ads and Retargeting
Check:
- Are pixels or ad platforms receiving identifiable user behavior?
- Are audiences built from customer lists?
- Are lookalike or remarketing audiences using personal data?
Common mistake: assuming "the ad platform handles it" means your company has no DPDP responsibility.
4. Website Analytics
Check:
- Which tools run on the site?
- Are IP address, device identifiers, session IDs or form fields being captured?
- Is analytics used only for measurement, or also for profiling and targeting?
Common mistake: installing tools first and asking privacy questions later.
5. Vendor List
Make a quick list:
- CRM
- Email platform
- WhatsApp provider
- Analytics
- Ad pixels
- Form tool
- Landing page builder
- Webinar tool
For each vendor, answer: what data goes there, why, who can access it and how deletion works.
6. This Week's Action
Map one campaign from first click to final follow-up. Mark every place personal data is collected, enriched, shared, uploaded or used for targeting.
If your team cannot answer where the data came from and where it goes next, start with a data flow map before rewriting policy copy.
Book a DPDP clarity callWant all of this handled, end to end? Sanctum is the all-in-one DPDP compliance programme behind this site: legal position, data map, gap analysis, implementation, tooling, training, readiness opinion, and breach cover under one accountable owner. How all-in-one DPDP compliance works or see the Sanctum programme.
Defining the Data End-of-Life
DPDP mandates that personal data must be erased as soon as the specific purpose for its collection is satisfied. This requires an automated or manual trigger for every category of data. Holding onto data for future marketing or vague research without fresh consent violates the principle of purpose limitation. A retention schedule acts as a legal map for when data must move from active use to archives, and finally to permanent deletion.
Data Retention Risks by Workflow
| Department | Data Type | Retention Driver | Deletion Trigger |
|---|---|---|---|
| Recruitment | Resumes, ID proofs | Hiring process | Position filled or 6 months post-interview |
| Customer Support | Chat logs, call recordings | Quality assurance | 90 days after ticket resolution |
| Marketing | Email, browsing behavior | Lead nurturing | 12 months of inactivity or consent withdrawal |
| Finance | PAN, billing address | Tax compliance | 7 years as per Income Tax Act |
| Security | Visitor logs, CCTV | Premise safety | 30-60 days unless incident reported |
Balancing Statutory Laws with DPDP
A primary conflict exists between the Income Tax Act, which requires seven years of records, and DPDP, which demands deletion after purpose fulfillment. To resolve this, separate the “transaction record” from the “marketing profile.” You may keep a digital invoice for the tax authorities while deleting the customer’s behavioral tracking data or precise location history once a delivery is complete. Use “logical deletion” or archiving for legal holds while ensuring the data is no longer accessible to general staff.
This week
Identify one high-volume data category, such as “Unsuccessful Job Applications” or “Resolved Support Tickets.” Map the exact date the purpose for that data ends. Create a manual or automated process to delete these specific records if they are older than your defined threshold.
Now think about your work. Where does personal data enter your workflows? Where does it sit? Who else touches it?
Frequently asked questions
Can we keep data indefinitely if the user never asks for deletion?
No. DPDP requires data deletion once the specific purpose for collection is fulfilled, regardless of whether the user makes a request. You must proactively delete data that is no longer necessary for the original transaction.
What happens if tax laws require keeping records longer than DPDP?
Statutory requirements like the Income Tax Act take precedence over DPDP deletion rules. You should archive the specific data required for legal compliance in a restricted environment and delete all other non-essential personal identifiers.
Does a retention schedule apply to data stored in offline physical files?
Yes. DPDP applies to personal data collected digitally or collected on paper and later digitized. Physical files containing personal data must follow the same retention and secure shredding timelines as digital records.