Skip to main content
DPDP-AID Readiness Checkby

Retention and erasure

Personal data may be kept only as long as the purpose needs it. Erasure has to reach processors too, and some businesses must erase the data of inactive users.

Reviewed 16 September 2026Educational self-assessment content, not legal advice

Requirements
4
Must-do
3
Penalty ceiling
Up to ₹50 crore

Breach of any other provision. This is a statutory maximum the Data Protection Board applies case by case, never a predicted fine. 1 of these requirements are in the quick check.

What we assess in this area

  1. MustIn the quick checkRET-01

    A retention schedule for each purpose

    The law says you may keep personal data only as long as the purpose needs it. You must know, for each purpose, how long data is kept and when it must go. Keeping data "just in case" is not allowed.

    What good looks like

    Every purpose in your data inventory has a written retention period and a trigger for erasure. Legal minimums from other laws are noted. Teams know the schedule, and systems apply it rather than relying on memory.

    How to get there

    List each purpose from your data inventory. Set a retention period and an erasure trigger for each. Note any other law that requires longer storage. Get the schedule approved and share it with system owners.

  2. MustRET-02

    Data is erased when the purpose is served or consent is withdrawn, including at processors

    Once the purpose is served, or a person withdraws consent, you must erase their personal data. This applies unless another law requires you to keep it. You must also make your processors erase the data they hold for you.

    What good looks like

    Erasure runs on a schedule and on request, across main systems, backups where practical, and processors. Each erasure is recorded. Processors confirm erasure in writing, and exceptions required by other laws are documented.

    How to get there

    Map where each dataset lives, including at processors. Set up a repeatable erasure process with an owner. Add erasure duties and confirmation to processor contracts. Keep a log of what was erased and when.

  3. MustRET-03

    Inactive users' data is erased after the prescribed period, with prior notice

    Large e-commerce, social media and online gaming platforms must erase data of users who have been inactive for the period set in the Rules. They must warn the person before erasure, so the person can log in and keep the account.

    What good looks like

    You track each user's last activity. Accounts reaching the inactivity limit get an advance warning. Data is erased on time unless the user returns. The process is logged and tested.

    How to get there

    Confirm whether your platform crosses the user threshold in the Rules. Record last activity for every account. Build the warning message and schedule. Automate erasure and keep a record of each run.

  4. ShouldRET-04

    Logs needed by law are kept for the prescribed minimum even after erasure

    Erasing personal data does not mean deleting every record. The Rules require certain logs and traffic data to be kept for a minimum period. Other laws may also require you to keep some records for longer.

    What good looks like

    Your retention schedule separates records you must keep from data you must erase. Required logs are kept for the period set in the Rules, protected, and then deleted. Nothing else is kept past its purpose.

    How to get there

    Identify logs and records that the Rules or other laws require you to keep. Set their minimum and maximum periods. Protect them from change. Make sure erasure jobs skip only these records.

Other areas we assess

All 13 areas

Check this area against your own business

The free assessment scores this area with the rest and shows you where it ranks against your other gaps.

The DPDP-AID Readiness Check is a free self-assessment tool for educational and self-learning purposes. It is not legal advice. Disclaimer

A free self-assessment tool for educational use. Not legal advice.