The DPDP Act has a simple rule and a few important qualifications. The rule: erase personal data when the person withdraws consent, or as soon as it is reasonable to assume the purpose is no longer being served, whichever comes first. The qualification: unless keeping it is necessary to comply with a law.
Three things that trigger erasure
- Consent is withdrawn.
- The purpose has been served — the contract has ended, the enquiry is closed, the service is no longer used.
- The person asks for erasure and no law requires you to keep the data.
You must also cause your Data Processors to erase the data they hold for you.
Fixed periods for the largest platforms
For three classes of Data Fiduciary — large e-commerce entities, online gaming intermediaries and social media intermediaries above user thresholds set in the Rules — the purpose is deemed no longer served three years after the person last approached the service or exercised their rights. For everyone else, the period is whatever is reasonable for the purpose, and you have to be able to justify it.
The 48-hour warning
Where data is to be erased under these fixed periods, the Rules require the fiduciary to tell the person at least 48 hours beforehand that their data will be erased unless they log in or get in touch. It is good practice for any deletion of an inactive account.
The one-year floor
Erasure has a counterweight. The Rules require personal data, associated traffic data and logs of processing to be retained for at least one year from the date of processing, for purposes that include detecting and investigating breaches, after which they are erased unless another law requires longer. So the question for each kind of data is not only how soon you must delete it, but also how long you must keep it.
Building a retention schedule
| Kind of data | What usually sets the period |
|---|---|
| Customer and billing records | Tax and company law |
| Employee records | Labour and tax law, and limitation periods for claims |
| Job applicants who were not hired | Your own stated period, with their consent to keep the file |
| Support tickets and recordings | The contract with the customer, then your stated period |
| Access and audit logs | At least one year under the Rules; longer if a contract or standard requires |
| Marketing contacts | Until consent is withdrawn or the contact goes stale |
- Write the period and the reason against each kind of data.
- Make deletion a scheduled job with a record, not a clean-up someone remembers.
- Include backups: say how long a deleted record survives in them.
- Review the schedule once a year.
- How long can I keep personal data under the DPDP Act?
- Only as long as the purpose requires, unless a law requires longer. Logs and related data must be kept for at least one year.
- Must I delete data when consent is withdrawn?
- Yes, and have your processors delete it, unless a law requires you to retain it.
- Does the three-year rule apply to all companies?
- No. It applies to large e-commerce, online gaming and social media intermediaries above the thresholds in the Rules.
- Do backups count?
- Yes. Personal data in backups is still personal data; state how long backups are kept.
This is a working summary for people who have to act on the law, not legal advice. Read the Act and the Rules, and take advice on your own facts.