The cheapest data breach is the one involving data you had already deleted. Yet most organisations keep personal data indefinitely "just in case". Privacy laws push the other way: India's DPDP Act requires erasure once the purpose is served, and the GDPR's storage limitation principle says the same. A retention schedule is how you turn that principle into practice.
What a retention schedule is
A table that answers, for each type of record: how long do we keep it, why, who owns it, and what happens at the end?
| Record type | Retention period | Starts from | Reason | Owner | End action |
|---|---|---|---|---|---|
| Customer account data | Life of account + 3 years | Account closure | Disputes and complaints | Head of Customer Ops | Delete |
| Invoices | 8 years | End of financial year | Tax law | Finance Controller | Delete |
| Job applicant CVs (unsuccessful) | 6 months | Decision date | Defend hiring decisions | HR Lead | Delete |
| Access logs | 1 year minimum | Log date | DPDP Rules, security investigations | CISO | Delete |
| CCTV footage | 30 days | Recording date | Security | Facilities | Overwrite |
The periods in this table are illustrations. Set yours from the laws that apply to you and your business needs.
Step 1: find the legal minimums and maximums
Some laws say keep at least this long: tax, company, employment and sector rules, plus security logging. India's DPDP Rules require personal data and processing logs to be kept for at least one year, and CERT-In requires ICT logs for 180 days. Privacy laws say don't keep longer than necessary. Your period sits between the two.
Step 2: decide the business need
Ask each owner what they actually use the data for, and how far back they really look. Expect answers like "forever, it might be useful". Push for evidence of how often old data is used. Typically, usage drops sharply after a year or two.
Step 3: define trigger events
"Seven years" means nothing without a start point. Use clear triggers: account closure, contract end, last login, end of financial year, decision date. For inactive accounts, India's DPDP Rules require large e-commerce, gaming and social media platforms to erase data after three years of inactivity, with 48 hours' notice to the user.
Step 4: decide the end action
Options include deletion, anonymisation (truly irreversible, which is harder than it sounds) and archiving with tighter access (still personal data, so still in scope). Prefer deletion where you can.
Step 5: handle legal holds
Litigation, investigations or regulatory requests may require you to suspend deletion for specific records. Run a simple legal-hold process: legal issues a hold, owners flag the records, deletion skips them, and the hold is lifted when the matter closes.
Step 6: make deletion happen
This is where most schedules fail. A policy on paper doesn't delete anything.
- Automate it. Scheduled jobs, storage lifecycle policies, database time-to-live settings, and email retention policies.
- Include backups. Deleted data often survives in backups. Either let backups age out on a known cycle or document that restored data is re-deleted.
- Include vendors. Contracts should require deletion at the end of the service, and you should ask for confirmation.
- Include the shadows. Spreadsheets, shared drives, exported reports and test environments with production data.
- Log deletions so you can prove they happened.
Step 7: review yearly
Laws, systems and business needs change. Review the schedule once a year and whenever you add a major system.
Quick wins
- Delete old unsuccessful job applications.
- Purge test and staging databases that contain real customer data.
- Set lifecycle rules on cloud storage buckets used for exports.
- Turn on mailbox retention for departed staff.
Learn more
Retention and erasure are part of the privacy operations module in our free Data Protection & Privacy Fundamentals course. See also our DPDP Rules timeline.
Written and reviewed by the DigiTrust Asia editorial team. How we research, review and correct articles.
General information, not legal advice. Laws and official guidance change; check the current text before acting.
Learn privacy properly
Data Protection & Privacy Fundamentals is a free, law-neutral course with a final exam and certificate.
Create a free account