In short. Personal data must be erased when consent is withdrawn or the purpose ends, and your processors must erase it too. For large e-commerce, gaming and social media platforms, the Rules fix the purpose as ended after three years without the user coming back, with a 48-hour warning before deletion. At the other end, every business must keep data, traffic data and logs for at least one year from processing. Other laws, such as the Companies Act and GST law, can require much longer retention, and the DPDP Act gives way to them.

The basic rule: erase when the purpose ends

Section 8(7) requires a Data Fiduciary, unless retention is necessary to comply with any law, to erase personal data when the Data Principal withdraws consent, or as soon as it is reasonable to assume that the specified purpose is no longer being served, whichever comes first. Clause (b) of the same section requires the Data Fiduciary to make its Data Processors erase any personal data it gave them.

Two consequences follow. A purpose has to be specific enough that you can tell when it has ended, which is another reason to write narrow purposes in your notice. And erasure is a system-wide event that has to reach your vendors, backups and exports.

When a purpose is deemed over

Section 8(8) adds a deeming rule. The purpose is treated as no longer served if the Data Principal does not approach the Data Fiduciary for the specified purpose, and does not exercise any of their rights, for a period that the government may prescribe. Different periods can be set for different classes of Data Fiduciary and different purposes. Section 8(11) explains that a person has not approached you if they have not initiated contact, in person or by electronic or physical communication.

So far the government has prescribed periods only for the three classes in the Third Schedule, described next. For everyone else, the general test in Section 8(7) applies: erase once it is reasonable to assume the purpose is over.

The three-year rule for large platforms

Rule 8(1) and the Third Schedule set a fixed period for three kinds of large platform:

Class of Data Fiduciary Registered users in India Period
E-commerce entityAt least 2 crore3 years
Online gaming intermediaryAt least 50 lakh3 years
Social media intermediaryAt least 2 crore3 years

The three years run from the latest of three dates: the user's last approach to the platform, the user's last exercise of rights, or the commencement of the DPDP Rules, 2025. The rule covers all purposes except two: allowing the user to access their account, and allowing them to use virtual tokens that can be used to get money, goods or services. A wallet balance or gift card, in other words, does not vanish because the user has been away.

One point is uncertain. The Rules commence in phases, and the Third Schedule does not say which commencement date it means. Until this is clarified, a platform can reasonably treat 13 May 2027, when Rule 8 itself comes into force, as the earliest date the clock could start, since the duty to erase under Rule 8 does not exist before then.

The 48-hour warning

Rule 8(2) requires a platform covered by Rule 8(1) to tell the user, at least forty-eight hours before the period ends, that their data will be erased unless they log in, make contact or exercise their rights. That means a reliable contact channel and an automated notice job, timed per user.

The one-year minimum

The Rules also set a floor, and it applies to every Data Fiduciary, large or small.

  • Rule 8(3) requires personal data, the associated traffic data and other logs of the processing to be retained for at least one year from the date of processing, for the purposes in the Seventh Schedule. Those purposes concern use by the State for sovereignty and security, State functions and legal disclosures, and the assessment of whether a business should be notified as a Significant Data Fiduciary. After the year, the data must be erased unless another law requires retention. The Rules' illustration makes clear that this applies even if the user deletes their account, and that it binds processors too.
  • Rule 6(1)(e), part of the security safeguards, separately requires logs and personal data to be retained for a year so that unauthorised access can be detected, investigated and remediated, unless another law requires otherwise.

The result is a two-stage deletion. When a user leaves or a purpose ends, the data comes out of live systems at once. A restricted copy of what Rule 8(3) covers is kept, locked away from ordinary use, and destroyed when the year is up.

Other laws that require longer retention

Section 8(7) gives way whenever retention is necessary to comply with any law. Some of the periods that most businesses meet:

  • Companies Act, 2013, Section 128(5): books of account and the vouchers supporting them must be kept for at least eight financial years before the current one. Where an investigation is ordered, the government can direct a longer period.
  • CGST Act, 2017, Section 36: GST accounts and records must be kept until seventy-two months from the due date of the annual return for the year concerned, and longer where an appeal, revision or investigation is pending.
  • Prevention of Money-laundering Act, 2002, Section 12: reporting entities such as banks, NBFCs and other regulated financial businesses must keep transaction records for five years from the date of the transaction, and identity records for five years after the business relationship ends.

These laws justify keeping the specific records they require. They do not justify keeping everything else about the same customer.

Building a retention schedule

  1. List data by category, such as account data, orders and invoices, KYC documents, support tickets, marketing preferences, analytics events and server logs.
  2. Assign a purpose and a legal basis to each category, and the event that ends the purpose.
  3. Attach the retention period: the end of the purpose, the Third Schedule period if you are a covered platform, the one-year Rule 8(3) floor, and any longer statutory period.
  4. Automate deletion with scheduled jobs, including for backups and data held by vendors.
  5. Log the deletions. A record that erasure happened, without the erased data itself, is your evidence if the Board asks.

Common mistakes

  • Keeping marketing and analytics data indefinitely "in case it is useful".
  • Deleting logs immediately on account deletion, in breach of the one-year minimum.
  • Treating a GST or Companies Act duty as cover for keeping unrelated data.
  • Forgetting backups, data warehouses and vendors when erasing.
  • For large platforms, deleting dormant accounts without the 48-hour warning, or wiping wallet balances that the rule protects.

Frequently asked questions

Until consent is withdrawn or the purpose ends, whichever is earlier, under Section 8(7), unless another law requires longer. Large e-commerce, gaming and social media platforms have a fixed three-year inactivity period under the Third Schedule.

E-commerce entities and social media intermediaries with at least two crore registered users in India, and online gaming intermediaries with at least fifty lakh.

Under Rule 8(2), platforms covered by the three-year rule must warn the user at least forty-eight hours before the period ends.

No. Rule 8(3) requires data, traffic data and logs to be kept for at least one year from processing for the Seventh Schedule purposes.

No. Section 8(7) yields to retention required by any law, such as eight financial years for books of account and seventy-two months for GST records.


Related reading

Enrolment: Bar Council of Punjab & Haryana  |  No.: PH/9616/2023
This page is informational and does not constitute legal advice. References are to the Digital Personal Data Protection Act, 2023, the Digital Personal Data Protection Rules, 2025 (G.S.R. 846(E), 13 November 2025), the Companies Act, 2013, the CGST Act, 2017 and the Prevention of Money-laundering Act, 2002. How these apply depends on the data and operations of each organisation.