[Analysis] Data Retention Policy under the DPDP Act – Section 8(7) Erasure | Third Schedule Periods | 48-Hour Notice
- Blog|Company Law|
- 8 Min Read
How long personal data may be kept under the DPDP Act: section 8(7) erasure, when a purpose is no longer served, Rule 8 and the Third Schedule, deletion methods and lessons from European cases.
- By Taxmann
- |
- Last Updated on 16 November, 2026
Table of Contents
- What does the DPDP Act say about data retention?
- When is the purpose no longer served?
- What retention periods does Rule 8 set?
- How should a data retention policy set retention periods?
- How should personal data be deleted at the end of the period?
- What do enforcement cases show about retention?
- Quick answers
1. What does the DPDP Act say about data retention?
It says personal data may be kept only while it serves the purpose for which it was collected, unless a law requires it to be kept longer. Section 8(7) provides that a Data Fiduciary shall, unless retention is necessary for compliance with any law for the time being in force:
- erase personal data upon the Data Principal withdrawing her consent, or as soon as it is reasonable to assume that the specified purpose is no longer being served, whichever is earlier; and
- cause its Data Processor to erase any personal data that the Data Fiduciary made available to it for processing.
Abha Tiwari and Aditya Singhania read section 8(7) as the principle of storage limitation, tied directly to the principle of purpose limitation that sections 4(1) and 6(1) adopt. Once data has served its purpose, keeping it only exposes it to risks such as data theft and unauthorised copying.
Two further points follow from the book’s reading. First, retaining data after its purpose is over does not take it outside the Act: every obligation under the DPDP Act continues to apply to the Data Fiduciary until the data is erased, because data that can identify individuals is still personal data. Second, where a law requires retention for a set period, the Data Fiduciary must erase the data as soon as reasonably possible once that period is over.
2. When is the purpose no longer served?
When the Data Principal stops engaging for a prescribed period. Section 8(8) deems the purpose no longer served if the Data Principal does not approach the Data Fiduciary for the performance of the specified purpose, and does not exercise any of her rights in relation to the processing, for the period prescribed, and different periods may be prescribed for different classes of Data Fiduciaries and different purposes.
Section 8(11) explains what “approached” means: a Data Principal is treated as not having approached the Data Fiduciary for any period in which she has not initiated contact with it for that purpose, in person or by communication in electronic or physical form.
Withdrawal of consent is the other trigger. Under section 6(6), when a Data Principal withdraws her consent, the Data Fiduciary must, within a reasonable time, stop processing her personal data and ensure its Data Processors do the same. The obligation is not absolute: personal data may still need to be kept and processed where the Act, its Rules or another applicable law in India requires or authorises it. The authors add that retention to defend or anticipate litigation must be justified under a valid legal ground, and kept limited, proportionate and clearly supported by law. Erasure that a Data Principal asks for directly, and when such a request may be refused, is covered in handling Data Principal rights requests.
3. What retention periods does Rule 8 set?
Rule 8 of the Digital Personal Data Protection Rules, 2025 (DPDP Rules) fixes the period for three classes of large platforms listed in the Third Schedule. A Data Fiduciary in one of these classes must erase the personal data if, for the period specified, the Data Principal neither approaches it for the specified purpose nor exercises her rights, unless retention is necessary for compliance with any law.
| Class of Data Fiduciary in the Third Schedule | Registered users in India |
|---|---|
| E-commerce entity | Not less than two crore |
| Online gaming intermediary | Not less than fifty lakh |
| Social media intermediary | Not less than two crore |
For all three classes the period is three years from the date on which the Data Principal last approached the Data Fiduciary for the specified purpose or exercised her rights, or the commencement of the DPDP Rules, whichever is latest. It applies to all purposes except two: enabling the Data Principal to access her user account, and enabling her to access any virtual token issued by or on behalf of the Data Fiduciary, stored on its platform, that may be used to get money, goods or services.
Two more duties sit in Rule 8. Under Rule 8(2), at least forty-eight hours before the period ends, the Data Fiduciary must tell the Data Principal that her data will be erased unless she logs into her user account, otherwise initiates contact for the specified purpose, or exercises her rights. Under Rule 8(3), a Data Fiduciary must retain personal data, associated traffic data and other logs of any processing, by itself or by a Data Processor, for a minimum of one year from the date of processing, for the purposes specified in the Seventh Schedule, and then have them erased unless another law requires further retention.
4. How should a data retention policy set retention periods?
By giving every category of personal data a specific and justifiable retention timeline, aligned either to legal or regulatory requirements, such as statutory retention of financial or employment records, or to documented business needs, such as contractual limitation periods or dispute management. Retention cannot be justified by convenience, inertia or speculative future use. The rationale must be clear, defensible and formally recorded, typically in the organisation’s Record of Processing Activities.
The illustrations to section 8(7) show both ends of the rule:
- X registers on an online marketplace run by Y to sell her used car, and consents to the processing of her personal data for that purpose. Once the marketplace helps conclude the sale, Y shall no longer retain her personal data.
- X closes her savings account with Y, a bank. A law applicable to banks requires Y to keep a record of its clients’ identity for ten years beyond the closing of accounts, so Y retains X’s personal data for that period.
Organisations therefore need to identify the laws they operate under and the retention each of them requires.
5. How should personal data be deleted at the end of the period?
By one of three methods: secure destruction of physical records, permanent deletion from digital systems, or “robust anonymisation” where applicable. Deletion must reach every instance of the data, including backups, archives, analytics platforms and shadow systems. That depends on an accurate data map: without full visibility of where data sits, effective deletion cannot be achieved.
The duty does not stop at the organisation’s edge. It extends to every processor and third party handling personal data on its behalf:
- data processing agreements should contain clear deletion provisions, with timelines and standards;
- processors must confirm that deletion has been carried out; and
- deletion obligations must flow down to sub-processors.
The organisation remains accountable until it can show that deletion has been carried out end to end across its data ecosystem.
6. What do enforcement cases show about retention?
That regulators expect a period to be fixed and data deleted when it expires, and that convenience is no excuse. The authors draw on three European cases:
- Taxa 4×35 (Denmark). The taxi company held records of close to nine million taxi trips. It said it anonymised them after two years, but it deleted only the customer’s name; the phone number stayed for another three years, and the trip records, including pick-up and drop-off addresses, could still be traced back to the person through it. The company said the phone number was the key to its records system. The authority did not accept this, and a fine of 1.2 million Danish kroner was recommended.
- Verkkokauppa.com Oyj (Finland). The retailer had set no retention period at all, keeping data until a customer asked for the account to be closed. The sanctions board fined it 856,000 euro, holding that data cannot be kept on the basis that the person might later ask for it to be deleted.
- Deutsche Wohnen SE (Berlin). The case concerned a failure to delete data once the purpose had gone, though the fine was later set aside on procedural grounds and the retention findings were never decided.
Two lessons come out of the Danish case. Removing one identifier is not anonymisation if what is left can still be linked to a person. And technical difficulty is not a defence, which matters because it is the reason organisations most often give.
7. Quick answers
How long can personal data be kept under the DPDP Act?
Only until the Data Principal withdraws consent or it is reasonable to assume the specified purpose is no longer being served, whichever is earlier, under section 8(7). Longer retention is allowed only where it is necessary for compliance with a law in force.
What retention period does the Third Schedule set?
Three years, for 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. The period runs from the Data Principal’s last approach or exercise of rights, or the commencement of the DPDP Rules, whichever is latest.
Must a Data Fiduciary warn a Data Principal before erasing her data?
Yes. Under Rule 8(2), at least forty-eight hours before the period ends, the Data Fiduciary must tell her that the data will be erased unless she logs in, otherwise initiates contact for the specified purpose, or exercises her rights.
Does the erasure duty cover Data Processors?
Yes. Section 8(7)(b) requires the Data Fiduciary to cause its Data Processor to erase any personal data it made available for processing, and deletion obligations should flow down to sub-processors.
Can personal data be kept after consent is withdrawn?
Processing must stop within a reasonable time under section 6(6), but the obligation is not absolute. Data may still be retained where the Act, its Rules or another applicable law in India requires or authorises it.
Is deleting a customer’s name enough to anonymise data?
No. Removing one identifier is not anonymisation if what is left, such as a phone number linked to trip records, can still be traced back to the person.
Do processing logs have to be retained under the DPDP Rules?
Yes. Rule 8(3) requires personal data, associated traffic data and other logs of processing to be retained for at least one year from the date of processing, for the purposes in the Seventh Schedule, and then erased unless another law requires longer retention.
Paragraphs 2.11.6 and 2.11.7 of Digital Personal Data Protection Law Practice and Compliance by Abha Tiwari and Aditya Singhania explain how to define retention periods and carry out deletion, with enforcement cases from Denmark, Finland and Berlin and a comparison with Singapore, China, Korea and Brazil. Paragraph 7.7 works through section 8(7), the deemed end of purpose in sections 8(8) and 8(11), Rule 8 and the Third Schedule, with the Act’s illustrations.
Taxmann.com | Research carries the Digital Personal Data Protection Rules, 2025, including Rule 8 and the Third Schedule, under Indian Acts & Rules, and Taxmann.com | Store has the Digital Personal Data Protection Act 2023 with Rules – Bare Act with Section Notes.
Related reading: rights of Data Principals · obligations of Data Fiduciaries · lawful processing and consent · the DPDP Act and Rules timeline.
More in this series: the SPDI Rules and the DPDP Act · the Record of Processing Activities (ROPA) · the incident response plan · the privacy notice under Rule 3 · the data processing agreement · data localisation and cross-border transfers · employee data and workplace monitoring · exemptions under the DPDP Act · legitimate uses under section 7 · the Data Protection Board of India · how a DPDP compliance audit is conducted · Significant Data Fiduciary obligations · Consent Managers under the DPDP framework · personal data breach intimation under Rule 7 · handling Data Principal rights requests · Data Fiduciary, Data Processor or both · children’s data and verifiable parental consent.
Law stated as updated till October 2026.
Disclaimer: The content/information published on the website is only for general information of the user and shall not be construed as legal advice. While the Taxmann has exercised reasonable efforts to ensure the veracity of information/content published, Taxmann shall be under no liability in any manner whatsoever for incorrect information, if any.

Taxmann Publications has a dedicated in-house Research & Editorial Team. This team consists of a team of Chartered Accountants, Company Secretaries, and Lawyers. This team works under the guidance and supervision of editor-in-chief Mr Rakesh Bhargava.
The Research and Editorial Team is responsible for developing reliable and accurate content for the readers. The team follows the six-sigma approach to achieve the benchmark of zero error in its publications and research platforms. The team ensures that the following publication guidelines are thoroughly followed while developing the content:
- The statutory material is obtained only from the authorized and reliable sources
- All the latest developments in the judicial and legislative fields are covered
- Prepare the analytical write-ups on current, controversial, and important issues to help the readers to understand the concept and its implications
- Every content published by Taxmann is complete, accurate and lucid
- All evidence-based statements are supported with proper reference to Section, Circular No., Notification No. or citations
- The golden rules of grammar, style and consistency are thoroughly followed
- Font and size that’s easy to read and remain consistent across all imprint and digital publications are applied


CA | CS | CMA