Quick answer
Rule 8 of the DPDP Rules, 2025 has two parts. E-commerce entities and social media intermediaries with at least 2 crore registered users, and online gaming intermediaries with at least 50 lakh, must erase data three years after a user last engaged, with 48 hours' notice. Every Data Fiduciary must also keep personal data, traffic data and logs for at least one year. It applies from 13 May 2027.
- Section 8(7) of the Act requires erasure once consent is withdrawn or the purpose is no longer served; Rule 8 fixes when that point arrives for large platforms.
- The Third Schedule covers e-commerce and social media platforms with 2 crore or more registered users and online gaming intermediaries with 50 lakh or more.
- For those platforms, data must be erased three years after the user last approached them or exercised rights, or from the Rules' commencement, whichever is latest.
- Account access and access to virtual tokens usable for money, goods or services are carved out of the three-year erasure duty.
- Rule 8(3) separately requires every fiduciary to keep personal data, traffic data and processing logs for at least one year, even after account deletion.
Who this is for: Large e-commerce marketplaces and inventory platforms, Online gaming intermediaries, Social media intermediaries, Data engineering and platform teams, All Data Fiduciaries (for the one-year floor)
How does DPDP Rule 8 decide when data must be erased?
Section 8(7) of the DPDP Act requires a Data Fiduciary to erase personal data, and cause its Data Processors to erase it, once the Data Principal withdraws consent or as soon as it is reasonable to assume the specified purpose is no longer being served, whichever is earlier, unless retention is needed to comply with law. Section 8(8) treats the purpose as no longer served if the Data Principal does not approach the fiduciary or exercise her rights for a prescribed period.
Rule 8 supplies that prescribed period, but only for certain classes of fiduciary, and adds a universal floor.
| Sub-rule | Who | What |
|---|---|---|
| 8(1) | Third Schedule platforms | Erase after the Third Schedule period of inactivity, unless law requires retention |
| 8(2) | Third Schedule platforms | Warn the Data Principal at least 48 hours before erasure |
| 8(3) | Every Data Fiduciary | Keep personal data, traffic data and processing logs for at least one year from processing, then erase unless law requires longer |
So there are two clocks. A ceiling for large platforms: three years of inactivity. A floor for everyone: one year from each processing event. Most companies are not Third Schedule platforms, so for them Rule 8(3) and the general section 8(7) principle are what matter.
Rule 8 applies from 13 May 2027.
Which platforms the Third Schedule covers
The Third Schedule names three classes, each with the same purposes, exceptions and time period.
| Class | Threshold (registered users in India) | Period |
|---|---|---|
| E-commerce entity | Not less than 2 crore | Three years |
| Online gaming intermediary | Not less than 50 lakh | Three years |
| Social media intermediary | Not less than 2 crore | Three years |
Definitions in the Schedule note:
- E-commerce entity: a person who owns, operates or manages a digital facility or platform for e-commerce as defined in the Consumer Protection Act, 2019, excluding a seller offering goods or services on a marketplace e-commerce entity.
- Online gaming intermediary: an intermediary enabling users of its computer resource to access one or more online games.
- Social media intermediary: as defined in rule 2(1)(w) of the IT (Intermediary Guidelines and Digital Media Ethics Code) Rules, 2021.
- User: for e-commerce, any person who accesses or avails its computer resource; for gaming and social media, any person who does so to host, publish, share, transact, view, display, download or upload information.
The "user" definitions are wide. Registered users count, not active users, so a platform with a large dormant base may cross the threshold even if monthly actives are much lower. Measure registered users in India and document the count.
The three-year clock and its exceptions
For Third Schedule platforms, the period is three years from the latest of:
- the date the Data Principal last approached the fiduciary for the performance of the specified purpose;
- the date she last exercised her rights in relation to the processing; or
- the commencement of the DPDP Rules, 2025.
The duty covers "all purposes" except two:
- (a) enabling the Data Principal to access her user account; and
- (b) enabling access to any virtual token issued by or on behalf of the fiduciary, stored on its platform, that may be used to get money, goods or services, such as wallet balances, gift cards or in-game currency.
So a dormant user's account credentials and stored value may be retained, while her browsing history, order analytics or behavioural profile must go.
A reading point to check with counsel. The Rules commence in phases, and Rule 8 itself starts on 13 May 2027. "Commencement of the Rules" could be read as 13 November 2025 (the date Rule 1 commenced) or 13 May 2027 (when Rule 8 commenced). On the first reading the earliest erasures fall due on 13 November 2028; on the second, 13 May 2030. Either way, nothing is due in 2027, but the deletion system should be built and tested before the first possible date.
Retention required by any other law, such as tax or sectoral record-keeping, overrides the erasure duty.
The 48-hour pre-erasure notice
Rule 8(2) requires the fiduciary, at least 48 hours before the erasure period completes, to inform the Data Principal that her personal data will be erased on completion of that period unless she:
- logs into her user account;
- otherwise initiates contact with the fiduciary for the performance of the specified purpose; or
- exercises her rights in relation to the processing.
Any of those resets the clock, because the three-year period runs from her last approach or exercise of rights.
Implementation pattern:
- Track last-engagement per user, across every presence that forms her user account under Rule 2(1)(c), such as email, mobile, handle and app.
- Schedule the notice at T-minus a safe margin, for example seven days, and again at T-minus 48 hours, so delivery failures can be retried. The rule sets a minimum, not a maximum.
- Send through the user account and registered contact with a one-tap "keep my account" action.
- On no engagement, erase the in-scope data, keep the carve-outs (account access, value tokens), and log the erasure event.
- Handle legal holds where other laws require retention.
See the 48-hour pre-erasure notice playbook for message templates and edge cases.
Rule 8(3): the one-year retention floor for everyone
Rule 8(3) applies to every Data Fiduciary, whatever its size. For any processing undertaken by it or by a Data Processor on its behalf, it must retain such personal data, associated traffic data and other logs of the processing for a minimum of one year from the date of processing, for the Seventh Schedule purposes. After that, it must cause the data and logs to be erased, unless further retention is required by another law or Government notification.
The Seventh Schedule purposes are State use for sovereignty, integrity and security, State use for functions or disclosure obligations under law, and assessment for notifying Significant Data Fiduciaries.
Two illustrations in the Rule:
- E-book platform: after delivery, the platform must keep order details, personal data and processing logs (order confirmation, payment and delivery events) for at least one year from the transaction, even if the buyer deletes her account.
- Cloud provider: a company using a cloud provider as processor must ensure the provider also keeps the data and logs for at least one year before erasure.
The result is a two-stage deletion model: on account deletion or consent withdrawal, stop processing and remove data from live use, but keep a restricted, access-controlled copy of the relevant data and logs until the one-year floor passes. See one-year log retention.
Designing deletion that satisfies both floor and ceiling
A retention engine that handles DPDP properly needs per-record metadata and a small state machine.
| State | Meaning | Who can access |
|---|---|---|
| Active | Purpose being served | Normal application access |
| Restricted | Purpose served or consent withdrawn; inside one-year floor | Security, legal and compliance only |
| Legal hold | Another law requires longer retention | Named roles, with reason recorded |
| Erased | Floor passed and no hold | No one; erasure event logged |
Rules for the engine:
- Stamp every record with
last_processed_at,purpose_idandhold_reason. - Compute the floor as
last_processed_at + 1 year, and never hard-delete before it. - For Third Schedule platforms, compute the ceiling from last engagement and send the Rule 8(2) notice ahead of it.
- Propagate to processors. Section 8(7) requires you to cause processors to erase; Rule 8(3) requires you to ensure they retain for a year. Contracts and APIs must support both.
- Cover derived data. Analytics tables, search indexes, embeddings and model training sets derived from personal data need their own retention logic. See erasure in LLMs and vector databases.
- Log erasure itself without re-storing the erased content.
Further reading on suhasbhairav.com
- BlogData Minimization vs Data Retention: Practical Guidelines
- BlogRTBF in vector databases: production-grade handling
- BlogImmutable audit logging for enterprise security
- AI SkillsCursor Rules Template: GDPR DSAR with Node.js/Express/PostgreSQL
- AI AgentsAI Agents for Privacy and GDPR Requests: Uses + Example
Before 13 May 2027
Compliance checklist
Count registered users in India
Determine whether you cross the 2 crore (e-commerce, social media) or 50 lakh (online gaming) Third Schedule threshold.
Third Schedule
Track last engagement per user
Record the latest login, purpose-related contact or rights request across every presence in the user account.
Rule 8(1); Rule 2(1)(c)
Build the 48-hour warning
Notify users at least 48 hours before erasure with a simple way to keep the account.
Rule 8(2)
Preserve the carve-outs
Keep data needed for account access and for stored value tokens usable for money, goods or services.
Third Schedule (a), (b)
Enforce a one-year retention floor
Keep personal data, traffic data and processing logs for at least one year from processing, including after account deletion.
Rule 8(3)
Bind processors to retention and erasure
Require processors to retain for one year and erase on instruction after that.
Rule 8(3); Act s.8(7)
Register legal holds
Document every other law that requires longer retention and apply holds by record type.
Rule 8(1), 8(3)
Key dates
Rule 8 and the Third Schedule apply; one-year floor starts
Earliest possible Third Schedule erasure date if 'commencement' means 13 Nov 2025 (check with counsel)
Answers
Frequently asked questions
How long can companies keep personal data under DPDP?
How long can companies keep personal data under DPDP?
Only as long as the specified purpose is served or the law requires, under section 8(7) of the Act, but never less than one year from processing under Rule 8(3). Large e-commerce, social media and gaming platforms in the Third Schedule must also erase data after three years of user inactivity.
Which companies must erase data after three years under DPDP?
Which companies must erase data after three years under DPDP?
E-commerce entities and social media intermediaries with at least 2 crore registered users in India, and online gaming intermediaries with at least 50 lakh registered users in India, under the Third Schedule to the DPDP Rules. Sellers on a marketplace are excluded from the e-commerce class.
What is the 48-hour notice under DPDP Rule 8?
What is the 48-hour notice under DPDP Rule 8?
Rule 8(2) requires Third Schedule platforms to tell the Data Principal at least 48 hours before the erasure period ends that her data will be erased unless she logs in, contacts the platform for the specified purpose, or exercises her rights. Any of those actions resets the three-year clock.
If a user deletes their account, must I delete everything immediately?
If a user deletes their account, must I delete everything immediately?
No. Rule 8(3) requires every fiduciary to keep personal data, associated traffic data and processing logs for at least one year from processing for Seventh Schedule purposes, even if the user deletes her account, as the e-book illustration shows. Stop using the data for the original purpose, restrict access, then erase after the year.
What data can large platforms keep after three years of inactivity?
What data can large platforms keep after three years of inactivity?
Data needed to let the Data Principal access her user account, and data needed to let her access any virtual token issued by the platform that can be used for money, goods or services, such as wallet balances or vouchers. Data required by another law may also be kept.
When will the first DPDP three-year erasures happen?
When will the first DPDP three-year erasures happen?
Not before late 2028. The three-year period runs from the latest of the user's last engagement or the commencement of the Rules. Depending on whether commencement means 13 November 2025 or 13 May 2027, the earliest date is 13 November 2028 or 13 May 2030. Confirm the reading with counsel.
Legal references and sources
- Digital Personal Data Protection Rules, 2025 — Rule 8(1)–(3) (official text)
- Digital Personal Data Protection Rules, 2025 — Third Schedule (official text)
- Digital Personal Data Protection Rules, 2025 — Seventh Schedule (official text)
- Digital Personal Data Protection Act, 2023 — Section 8(7) and 8(8) (official text)
This guide explains the law for engineering and business teams. It is not legal advice; confirm how it applies to your organisation with qualified counsel, and check the Gazette for later notifications or amendments.
About the author

Suhas Bhairav
Systems architect and applied AI practitioner who designs production AI systems for Indian and global companies, with a focus on privacy-by-design under the DPDP Act and the EU AI Act.
Related guides
- DPDP Rules 2025DPDP One-Year Log Retention: What to Keep and for How LongTwo DPDP rules require one year of retention: Rule 6(1)(e) for security logs and Rule 8(3) for personal data, traffic data and processing logs. What to keep, where, and how to protect it.
- Templates & playbooksBuilding the 48-Hour Pre-Erasure Notice Under DPDPHow to engineer the Rule 8(2) pre-erasure notice for large e-commerce, gaming and social media platforms: who it applies to, how to compute the clock, notice content and system design.
- Sector guidesDPDP for E-Commerce Platforms: Retention, Consent and ErasureE-commerce entities with at least 2 crore registered users face automatic three-year erasure under the Third Schedule. Here is what every online marketplace and store must do.
- Sector guidesDPDP for Social Media IntermediariesSocial media intermediaries with at least 2 crore registered users face three-year inactivity erasure, plus children's, rights, breach and government-request duties under DPDP.
- Sector guidesDPDP for Online Gaming IntermediariesOnline gaming intermediaries with at least 50 lakh registered users face three-year inactivity erasure, and every gaming platform must handle minors, in-game tokens and logs under DPDP.
- AI & personal dataHandling DPDP Erasure Requests in LLMs and Vector DatabasesHow to honour a DPDP erasure request across vector databases, prompt logs, fine-tuning sets, eval sets and model weights — while respecting Rule 8(3)'s one-year retention minimum.