Sector guidesUpdated 22 November 202610 min read

DPDP for E-Commerce Platforms: Retention, Consent and Erasure

E-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.

By Suhas Bhairav · Reviewed against the DPDP Rules, 2025 (G.S.R. 846(E), 13 Nov 2025)

Third Schedule threshold
≥ 2 crore registered users in India
Inactivity erasure period
Three years (whichever-is-latest rule)
Pre-erasure notice
At least 48 hours (Rule 8(2))
Carve-outs
User account access; virtual tokens for money/goods/services
Minimum retention
One year from processing (Rule 8(3))
Applies from
13 May 2027

Quick answer

E-commerce entities with at least 2 crore registered users in India must erase a user's personal data three years after she last approached them or exercised her rights, or from commencement of the Rules, whichever is latest, with 48 hours' notice, under Rule 8 and the Third Schedule. Every e-commerce fiduciary must also keep order data and logs at least one year under Rule 8(3).

  • The Third Schedule threshold for e-commerce is not less than 2 crore registered users in India.
  • Erasure runs three years from the user's last approach or exercise of rights, or from commencement of the Rules, whichever is latest.
  • Account access and stored virtual tokens usable for money, goods or services are carved out of erasure.
  • Rule 8(2) requires notice at least 48 hours before erasure; logging in or contacting the platform resets the clock.
  • Rule 8(3)'s e-book illustration requires order and logistics records to be kept at least one year, even after account deletion.

Who this is for: Marketplace and e-commerce platforms, Quick-commerce and food delivery apps, Online retailers and D2C stores, E-commerce engineering and data teams, Data Protection Officers

What does the Third Schedule require of e-commerce entities?

Rule 8(1) says a Data Fiduciary of a class in the Third Schedule must erase personal data processed for the listed purposes if the Data Principal neither approaches it for the specified purpose nor exercises her rights for the period stated, unless retention is necessary to comply with law.

Item 1 of the Third Schedule covers a Data Fiduciary who is an e-commerce entity having not less than two crore registered users in India:

  • Purposes: all purposes, except (a) enabling the Data Principal to access her user account, and (b) enabling her to access 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.
  • Time period: three years from the date she last approached the fiduciary for the specified purpose or exercised her rights, or the commencement of the DPDP Rules, 2025, whichever is latest.

Definitions in the Schedule's note matter:

  • "E-commerce entity" means any person who owns, operates or manages a digital facility or platform for e-commerce as defined in the Consumer Protection Act, 2019 — but not a seller offering goods or services on a marketplace e-commerce entity.
  • "User" means any person who accesses or avails any computer resource of the e-commerce entity.

Rule 8 applies from 13 May 2027. Because the Rules commenced in phases, whether "commencement" here means 13 November 2025 or 13 May 2027 is worth confirming with counsel; on either reading, no inactivity erasure falls due before November 2028.

Who is in scope: thresholds and sellers

The Third Schedule applies only above the 2 crore registered-user threshold. Below it, the general rule still applies: section 8(7) requires erasure when consent is withdrawn or the specified purpose is no longer served, whichever is earlier, unless law requires retention. The Third Schedule simply fixes when the purpose is deemed no longer served for large platforms.

EntityThird Schedule?Still applies
Marketplace with ≥ 2 crore registered users in IndiaYesAll DPDP duties
Inventory-model retailer with ≥ 2 crore registered usersYesAll DPDP duties
Seller on a marketplaceNo (excluded by Note (a))General s. 8(7) erasure
D2C store under 2 crore usersNoGeneral s. 8(7) erasure

Practical questions to settle:

  • Counting. "Registered users in India" — decide how you count dormant, duplicate and guest accounts, and document the method.
  • Group platforms. If several apps share one account system, take advice on whether users are counted per entity or per platform.
  • Approaching the fiduciary. Logging in, placing an order or contacting support counts. Passive receipt of marketing email is unlikely to.

Smaller D2C brands should read DPDP for D2C and retail brands.

Engineering the inactivity erasure and 48-hour notice

Rule 8(2) requires the fiduciary, at least 48 hours before the erasure period ends, to inform the Data Principal that her data will be erased unless she logs in, otherwise contacts the fiduciary for the specified purpose, or exercises her rights.

Build it as a pipeline:

  1. Activity ledger. Maintain last_engaged_at per user, updated by login, order, support contact and rights requests. This is the clock.
  2. Clock start. For existing users, the clock starts at the later of last engagement and the commencement date you adopt (see above).
  3. Notice job. A daily job selects users approaching three years and sends notice via registered email, SMS or push — well before the 48-hour minimum to allow delivery failures.
  4. Grace check. At expiry, re-check engagement; any login or contact resets the clock.
  5. Selective erasure. Erase personal data except what is needed for account access and for wallet balances, gift cards, store credit or loyalty points that are usable for money, goods or services.
  6. Legal retention. Keep invoices and records that tax, consumer-protection or other laws require; erase everything else.
  7. Processors. Propagate erasure to logistics partners, payment aggregators' tokenised references where you control them, and marketing tools.

The notice design is covered in building the 48-hour pre-erasure notice.

Rule 8(3): the one-year floor for orders and logs

Rule 8(3) applies to every Data Fiduciary, regardless of size. It requires retention of personal data, associated traffic data and other logs of processing for a minimum of one year from the date of processing, for Seventh Schedule purposes, and then erasure unless another law requires longer.

The Rule's first illustration is an e-commerce case: X buys an e-book on platform Y. Once delivery is complete, the purpose is served, but Y must retain order details, personal data and logs of the processing — such as order confirmation, payment and delivery events — for at least one year from the transaction, even if X deletes her account.

For e-commerce systems:

  • Account deletion is not instant purge. Remove the account from live use, but move order, payment-event and delivery-event records into restricted retention for the year.
  • Clickstream and search logs. These are processing logs too; keep at least a year, then erase, with masking where possible.
  • Seller and logistics systems. If they process on your behalf, Rule 8(3) covers their copies.
  • Longer legal retention. Tax and accounting laws may require longer retention of invoices; those prevail for that data.

The general log design is covered in one-year log retention.

Order fulfilment — using name, address and phone to deliver what the customer bought — fits the section 7(a) legitimate use: data voluntarily provided for a specified purpose where she has not indicated non-consent.

Other common e-commerce processing needs consent and a Rule 3 notice:

  • Marketing messages by email, SMS, WhatsApp or push.
  • Behavioural personalisation and recommendations across sessions.
  • Sharing with brands or advertisers, including retail media and audience-matching.
  • Third-party tracking SDKs and pixels.

Rule 3 requires an itemised description of data and specific purposes, plus an easy way to withdraw consent comparable to giving it. A single checkbox for "offers, personalisation and partner sharing" will not meet the specificity requirement.

Children: marketplaces have under-18 shoppers. Section 9(3) bars tracking, behavioural monitoring and targeted advertising directed at children, so age signals should switch off personalised ads.

Large platforms will also see Consent Managers — registrable since 13 November 2026 — as a channel customers may use to give and withdraw consent. See AI personalisation and recommendations and marketing, cookies and consent.

Security, breach and rights at e-commerce scale

E-commerce platforms hold addresses, phone numbers, order histories and payment references for millions of people — a high-value breach target.

  • Rule 6 safeguards. Encrypt or tokenise addresses and phone numbers in non-essential systems; mask phone numbers shown to delivery partners; control access to customer-service tools; log and review bulk exports.
  • Rule 7 breach notice. Every personal data breach must go to each affected user without delay and to the Board, with the detailed report within 72 hours. At marketplace scale, pre-build bulk notification through the app and registered channels.
  • Rights at volume. Rule 14 requires published request channels and identifiers — for e-commerce typically registered mobile, email or order ID — and a grievance response period of not more than 90 days. Automate access and erasure requests.
  • Rule 9 contact. Publish the DPO or contact person's details and include them in every rights response.
  • SDF readiness. Large platforms are candidates for Significant Data Fiduciary notification under section 10, based on volume and sensitivity of data and risk to rights. No SDF has been notified; once notified, Rule 13 adds annual DPIAs and audits, algorithmic due diligence and possible localisation of specified data.

Penalties: up to ₹250 crore for failing to take reasonable security safeguards and up to ₹200 crore for failing to notify a breach.

Further reading on suhasbhairav.com

Before 13 May 2027

Compliance checklist

  1. Count registered users in India against the 2 crore threshold

    Document the counting method, including dormant and duplicate accounts, and re-check periodically.

    Third Schedule item 1

  2. Build a last-engagement ledger

    Track login, order, support contact and rights requests per user as the Third Schedule clock.

    Rule 8(1)

  3. Send pre-erasure notices

    Notify users at least 48 hours before the three-year erasure point through registered channels.

    Rule 8(2)

  4. Preserve account access and wallet balances

    Exclude account access and virtual tokens usable for money, goods or services from inactivity erasure.

    Third Schedule item 1(a)–(b)

  5. Keep order and logistics logs for one year

    Retain order, payment-event and delivery-event records for at least one year, even after account deletion.

    Rule 8(3)

  6. Separate fulfilment from marketing consent

    Rely on s. 7(a) for delivery and seek specific consent for marketing, personalisation and partner sharing.

    DPDP Act ss. 6, 7(a); Rule 3

  7. Switch off targeted ads for under-18s

    Use age signals to disable behavioural ads and tracking for child users.

    DPDP Act s. 9(3)

  8. Mask customer data for delivery partners

    Use masked phone numbers and limit address exposure in partner apps.

    Rule 6(1)(a)

  9. Automate rights requests

    Publish channels and identifiers, and meet a grievance period of at most 90 days.

    Rule 14

  10. Pre-build bulk breach notification

    Prepare in-app and registered-channel notices and the 72-hour Board report template.

    Rule 7

Key dates

  1. DPDP Rules notified

  2. Rule 8 and Third Schedule apply to e-commerce entities

Answers

Frequently asked questions

Which e-commerce companies must erase inactive users' data under DPDP?

E-commerce entities with not less than 2 crore registered users in India, under item 1 of the Third Schedule. Sellers on a marketplace are excluded. They must erase personal data three years after the user last approached them or exercised rights, or from commencement of the Rules, whichever is latest.

When is the earliest that Third Schedule erasure can apply?

Rule 8 and the Third Schedule apply from 13 May 2027. The three-year period runs from the user's last engagement or the commencement of the Rules, whichever is latest. The Rules commenced in phases, so confirm which date you treat as commencement; on either reading, no inactivity erasure falls due before November 2028.

Does a user's wallet balance get erased after three years?

No. The Third Schedule excludes enabling the user to access her account and any virtual token issued by or on behalf of the platform, stored on it, that can be used to get money, goods or services. Wallet balances, store credit and similar tokens stay accessible.

If a customer deletes her account, can I delete her orders immediately?

No. Rule 8(3) requires every Data Fiduciary to retain personal data, traffic data and processing logs for at least one year from processing. Its illustration describes an e-book platform keeping order, payment and delivery records for a year even if the buyer deletes her account. Other laws may require longer retention for invoices.

What resets the three-year erasure clock?

The Data Principal approaching the fiduciary for the specified purpose or exercising her rights. Rule 8(2) gives logging in to the user account and otherwise initiating contact as examples. Placing an order or contacting support will normally count; receiving marketing messages without responding is unlikely to.

Do small online stores need to follow the Third Schedule?

No, the Third Schedule applies only to e-commerce entities with at least 2 crore registered users in India. Smaller stores must still erase data when consent is withdrawn or the purpose is served under section 8(7), keep logs for one year under Rule 8(3), and meet all other DPDP duties from 13 May 2027.

Legal references and sources

  • Digital Personal Data Protection Rules, 2025 — Rule 8(1)–(3) (official text)
  • Digital Personal Data Protection Rules, 2025 — Third Schedule, item 1 and Note (a) (official text)
  • Digital Personal Data Protection Act, 2023 — Sections 6, 7(a) and 8(7) (official text)
  • Digital Personal Data Protection Rules, 2025 — Rule 3 (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

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.