Quick answer
Rule 8(2) requires Third Schedule Data Fiduciaries to inform a Data Principal at least 48 hours before her personal data is erased for inactivity, stating it will be erased unless she logs in, makes contact for the purpose or exercises her rights. It covers e-commerce and social media platforms with 2 crore or more registered users and online gaming intermediaries with 50 lakh or more.
- The 48-hour notice applies only to Third Schedule classes, not to every Data Fiduciary.
- Erasure falls due three years after the user last engaged or exercised rights, or from commencement of the Rules, whichever is latest.
- Account access data and stored virtual tokens usable for money, goods or services are excluded from erasure.
- Logging in, contacting the fiduciary for the purpose, or exercising rights resets the clock.
- Rule 8(3) still requires one-year retention of processing logs, so erasure needs a retention-aware design.
- The phrase 'commencement of the Rules' is open to two readings; design for either and take advice.
Who this is for: Large e-commerce marketplaces and platforms, Social media intermediaries, Online gaming intermediaries, Data platform and lifecycle engineers, CRM and messaging teams
What does Rule 8(2) require?
Section 8(7) of the DPDP Act requires erasure once the specified purpose is no longer served. Section 8(8) deems the purpose no longer served if the Data Principal does not approach the fiduciary for the purpose, or exercise her rights, within a prescribed time period. Rule 8 prescribes that period for certain classes.
Rule 8(1) requires a Data Fiduciary of a class in the Third Schedule, processing for the corresponding purposes, to erase personal data if, for the Third Schedule period, the Data Principal neither approaches it for the specified purpose nor exercises her rights, unless retention is necessary to comply with law.
Rule 8(2) requires that, at least forty-eight hours before completion of that period, the fiduciary must inform the Data Principal that her personal data will be erased on completion of the period, unless she logs into her user account or otherwise initiates contact for the specified purpose, or exercises her rights in relation to the processing.
What the notice must convey
- That her personal data will be erased.
- When: on completion of the period.
- How to prevent it: log in, initiate contact for the purpose, or exercise her rights.
Rule 8(2) does not prescribe a channel. Use the user account and the communication modes she has registered, consistent with how Rule 7 approaches breach notices.
Who must send the 48-hour notice?
Only the three classes listed in the Third Schedule:
| Class | Threshold (registered users in India) | Purposes covered |
|---|---|---|
| E-commerce entity | Not less than 2 crore | All purposes, except enabling access to the user account and to stored virtual tokens usable for money, goods or services |
| Online gaming intermediary | Not less than 50 lakh | Same |
| Social media intermediary | Not less than 2 crore | Same |
Definitions that matter
- E-commerce entity: a person who owns, operates or manages a digital facility or platform for e-commerce under the Consumer Protection Act, 2019, excluding a seller offering goods or services on a marketplace.
- 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, a person who does so for hosting, publishing, sharing, transacting, viewing, displaying, downloading or uploading information.
Platforms below the thresholds still owe the general section 8(7) erasure duty, but not the three-year clock or the 48-hour notice.
How do you compute the erasure date?
The Third Schedule period is three years from the date on which the Data Principal last approached the Data Fiduciary for the performance of the specified purpose or exercise of her rights, or the commencement of the DPDP Rules, 2025, whichever is latest.
The clock per user
last_engagement = max(
last_login_at,
last_purpose_contact_at, # order, support ticket, etc.
last_rights_request_at
)
clock_start = max(last_engagement, RULES_COMMENCEMENT)
erasure_due = clock_start + 3 years
notice_due_by = erasure_due - 48 hours (send earlier)
The commencement question
The Rules commence in phases: Rule 1(2) brought some rules into force on publication on 13 November 2025, while Rule 8 itself takes effect on 13 May 2027. "Commencement of the DPDP Rules, 2025" can therefore be read as either date.
| Reading | Earliest possible erasure for long-dormant users |
|---|---|
| Publication (first commencement) | 13 November 2028 |
| Commencement of Rule 8 | 13 May 2030 |
Make RULES_COMMENCEMENT a configuration value, not a constant buried in code, and confirm the position with counsel or any later clarification before the first batch falls due. Either way, no inactivity erasure under Rule 8(1) falls due before November 2028.
What counts as engagement that resets the clock?
Rule 8(1) and 8(2) name three activities:
- Logging into the user account.
- Otherwise initiating contact with the fiduciary for the performance of the specified purpose, such as placing an order, opening a support ticket or playing a game.
- Exercising rights in relation to the processing, such as an access or correction request.
Engineering the engagement signal
- Emit a single
principal_engagementevent from each qualifying source: auth service, order service, support desk, game server, rights portal. - Store
last_engagement_aton the principal record, updated idempotently. - Exclude non-qualifying signals: marketing email opens, push delivery receipts and passive background syncs are not the Data Principal initiating contact for the purpose. Treat ambiguous signals conservatively and document the decision.
Interaction with the notice
If the user logs in after receiving the 48-hour notice, cancel the scheduled erasure and recompute the date. Build that cancellation path first; a race condition that erases a user who has just returned is the worst failure mode of this feature.
Exclusions and the one-year retention overlap
Excluded purposes
The Third Schedule excludes two purposes from erasure:
- (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, reward points or in-game currency of value.
So erasure is partial: retain what is needed for account access and token access; erase the rest, such as browsing history, preferences, inferred profiles and old content metadata, unless another law requires retention.
Rule 8(3) one-year retention
Rule 8(3) applies "without prejudice to" Rule 8(1) and 8(2) and requires every Data Fiduciary to retain personal data, associated traffic data and processing logs for at least one year from the date of processing, for Seventh Schedule purposes. For a user dormant for three years, most processing logs will already be older than one year, but check log tables for recent system-generated processing of that user's data.
Other laws
Tax, consumer protection and sectoral rules may require keeping transaction records longer. The erasure job must consult a legal-hold and statutory-retention map before deleting.
A reference system design for the 48-hour notice
[engagement events] -> principal.last_engagement_at
|
daily scheduler: find principals where
erasure_due - now <= notice_lead_time
|
send notice (in-app + registered email/SMS)
record notice_sent_at, channel, template_version
|
wait until erasure_due
|
re-check last_engagement_at
- engaged since notice? -> cancel, recompute
- not engaged? -> erasure workflow
|
erasure workflow:
keep: account access data, virtual tokens
check: legal holds, statutory retention, Rule 8(3)
erase: primary DB, caches, search index,
warehouse, ML features, processors
record: erasure_completed_at, scope, evidence
Design choices
- Lead time: 48 hours is the minimum. Sending notices seven to fourteen days ahead, with a reminder close to the deadline, reduces surprise and still satisfies "at least 48 hours".
- Wording: plain language, with a single prominent "Keep my account" action that logs the user in.
- Undeliverable notices: record bounces. The rule requires you to inform; keep evidence of the attempt through registered channels.
- Processors: propagate erasure to vendors and keep confirmations.
- Batching: spread jobs to avoid one enormous run when the first cohort falls due.
Further reading on suhasbhairav.com
- BlogData Minimization vs Data Retention: Practical Guidelines
- BlogRTBF in vector databases: production-grade handling
- BlogPersistent Agent Memory and Privacy: Balancing Personalization with Data Retention Risks
- AI SkillsCursor Rules Template: GDPR DSAR with Node.js/Express/PostgreSQL
- AI LabBatuk sovereign AI chat workspace for GDPR export and erasure
Before 13 May 2027
Compliance checklist
Confirm whether you are a Third Schedule class
Check platform type and registered users in India against the thresholds.
Third Schedule
Build a single engagement signal
Capture logins, purpose-related contact and rights requests as qualifying events.
Rule 8(1)
Make the commencement date configurable
Store the Rules commencement reference as configuration pending legal confirmation.
Third Schedule
Send notices at least 48 hours ahead
Schedule notices with a longer lead time and record delivery evidence.
Rule 8(2)
State consequences and how to prevent erasure
Tell users data will be erased unless they log in, make contact or exercise rights.
Rule 8(2)
Cancel erasure on re-engagement
Re-check engagement immediately before erasure and recompute the date.
Rule 8(1)
Preserve account access and virtual tokens
Exclude account access data and value-bearing tokens from erasure.
Third Schedule
Check legal holds and Rule 8(3)
Consult statutory retention and one-year log requirements before deleting.
Rule 8(3)
Propagate erasure to processors
Instruct vendors to erase and keep confirmations.
Section 8(7)
Answers
Frequently asked questions
Who has to send the 48-hour pre-erasure notice?
Who has to send the 48-hour pre-erasure notice?
Only Data Fiduciaries in the Third Schedule: 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. Rule 8(2) requires them to notify users at least 48 hours before erasing personal data for inactivity.
What must the pre-erasure notice say?
What must the pre-erasure notice say?
Rule 8(2) requires the fiduciary to inform the Data Principal that her personal data will be erased on completion of the period unless she logs into her user account, otherwise initiates contact for the specified purpose, or exercises her rights. Use plain language and a clear action to keep the account.
When will the first inactivity erasures fall due?
When will the first inactivity erasures fall due?
Not before November 2028. The period is three years from the latest of the user's last engagement and the commencement of the Rules. If commencement means publication on 13 November 2025, the earliest date is 13 November 2028; if it means Rule 8's own commencement on 13 May 2027, it is 13 May 2030.
Does a marketing email open reset the three-year clock?
Does a marketing email open reset the three-year clock?
Probably not. Rule 8 refers to the Data Principal logging in, initiating contact for the specified purpose, or exercising rights. Passive signals such as email opens or push delivery receipts are not clearly the user initiating contact for the purpose. Treat them conservatively and document your position.
Do we delete wallet balances after three years of inactivity?
Do we delete wallet balances after three years of inactivity?
No. The Third Schedule excludes processing that enables the Data Principal to access her user account and any virtual token issued by or on behalf of the fiduciary, stored on its platform, that can be used to get money, goods or services. Wallet balances and gift cards fall within that exclusion.
Can we send the notice earlier than 48 hours?
Can we send the notice earlier than 48 hours?
Yes. Rule 8(2) says at least forty-eight hours before completion of the period, so 48 hours is a minimum. Sending a notice one to two weeks ahead with a final reminder gives users a realistic chance to respond and still complies.
Legal references and sources
- Digital Personal Data Protection Rules, 2025 — Rule 8(1) and Third Schedule (official text)
- Digital Personal Data Protection Rules, 2025 — Rule 8(2) (official text)
- Digital Personal Data Protection Rules, 2025 — Rule 8(3) (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 Data Retention and Erasure Under Rule 8 and the Third ScheduleRule 8 sets when personal data must be erased: three-year dormancy erasure for large e-commerce, gaming and social media platforms, a 48-hour warning, and a one-year retention floor for everyone.
- 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.
- 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 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.
- 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.
- 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.