Quick answer
D2C and retail brands are Data Fiduciaries under the DPDP Act for customer data from their own sites, apps, stores and loyalty programmes. From 13 May 2027 they must give Rule 3 notices, take Rule 6 security safeguards, report every breach under Rule 7 and keep order logs for one year (Rule 8(3)). The three-year erasure rule applies only to e-commerce entities with 2 crore or more registered users.
- A brand selling through its own website or app is an e-commerce entity; a seller only on a marketplace is not, under the Third Schedule.
- Order fulfilment can rely on data voluntarily provided for that purpose; marketing and loyalty profiling need consent.
- Rule 8(3) requires order, payment and delivery logs to be kept for at least one year, even after account deletion.
- Couriers, payment gateways, WhatsApp vendors and agencies are typically processors needing Rule 6(1)(f) contract clauses.
- Every personal data breach must be intimated to customers and the Board, with detail within 72 hours.
Who this is for: D2C founders and operators, Retail chains with stores and apps, E-commerce and CRM managers, Loyalty programme owners, Brand marketing and growth teams
How does DPDP apply to D2C and retail brands?
A D2C or retail brand decides why and how it uses customer data, so it is the Data Fiduciary for that data. That covers names, phone numbers, addresses, order history, payment references, loyalty points, store visit data, returns and support conversations.
The DPDP Act applies to digital personal data and to non-digital data that is later digitised. Paper loyalty forms entered into a CRM, and in-store billing that captures a mobile number, are both in scope once they are digital.
Where retail data usually lives
- Storefront platform and checkout
- Order management and warehouse systems
- Payment gateway and refunds
- Courier and logistics integrations
- CRM, CDP and loyalty engine
- WhatsApp, SMS and email platforms
- POS systems in stores
- Customer support desk and call recordings
Core obligations apply from 13 May 2027. Until then, section 43A of the IT Act and the SPDI Rules continue to apply, so existing privacy policies and security practices remain relevant during the transition.
Is a D2C brand an 'e-commerce entity' under the Third Schedule?
It matters because the Third Schedule imposes a time-based erasure rule only on certain large platforms. Item 1 covers a Data Fiduciary that is an e-commerce entity having not less than two crore registered users in India.
The note to the Third Schedule defines an e-commerce entity by reference to the Consumer Protection Act, 2019, as a person who owns, operates or manages a digital facility or platform for e-commerce. It excludes a seller offering goods or services on a marketplace e-commerce entity.
| Brand model | E-commerce entity? | Third Schedule erasure? |
|---|---|---|
| Sells only on marketplaces | No (excluded as marketplace seller) | No |
| Runs its own website or app | Yes | Only if ≥ 2 crore registered users in India |
| Both own site and marketplaces | Yes, for its own platform | Only if the threshold is met |
For brands above the threshold, personal data must be erased three years after the customer last approached the brand or exercised rights, or from the commencement of the Rules, whichever is latest, except data needed for account access or stored virtual tokens such as wallet balances or gift cards. A notice at least 48 hours before erasure is required under Rule 8(2). See the 48-hour pre-erasure notice.
Brands below the threshold still owe section 8(7): erase when the purpose is no longer served, unless law requires retention.
Which customer data uses need consent?
Section 7(a) allows processing of data a customer voluntarily provides for a specified purpose where she has not indicated non-consent. Fulfilling an order she placed fits; repurposing her data for something else does not.
| Retail use | Likely ground |
|---|---|
| Processing a checkout, delivery and returns | Section 7(a) voluntary provision |
| GST invoicing and statutory records | Legal obligation, plus retention under the relevant law |
| Sending marketing on WhatsApp, SMS or email | Consent |
| Loyalty programme profiling and personalised offers | Consent |
| Uploading customers to ad platforms for retargeting | Consent |
| Capturing mobile numbers at billing for marketing | Consent, collected separately from billing |
Consent must be specific and unbundled. A checkbox at checkout reading "Send me offers on WhatsApp", unticked by default, is a reasonable pattern. Making marketing consent a condition of completing a purchase is not, because consent must be free and limited to necessary data.
For tracking pixels and cookies, follow DPDP for marketing teams.
How should brands manage couriers, gateways and agencies?
Most retail operations depend on partners who touch customer data. Under section 8(1) the brand remains responsible for processing done on its behalf, and Rule 6(1)(f) requires processor contracts to include appropriate provisions for reasonable security safeguards.
Typical partner map
- Logistics and courier partners: name, phone, address, order contents. Limit the fields shared and require deletion after the delivery window, subject to the one-year log rule.
- Payment gateways: often separate regulated entities. Card and payment data are also governed by RBI rules; keep only tokens and references on your side.
- WhatsApp and SMS providers: processors for messaging; they must honour opt-outs pushed from your system.
- Agencies and performance marketers: processors when using your accounts and data; never let them hold unmanaged copies of customer lists.
- Marketplaces: when you sell through a marketplace, the marketplace collects and controls most buyer data; you receive only what it passes for fulfilment.
Contract essentials
Purpose limitation; security measures aligned with Rule 6; breach reporting to you without delay; assistance with rights requests; one-year log retention then erasure; sub-processor controls. Use the DPA clauses template.
What must be retained, and what must be erased?
Rule 8(3) is the clause retail teams most often miss. Every Data Fiduciary must retain personal data, associated traffic data and other logs of processing for a minimum of one year from the date of processing, for the Seventh Schedule purposes, and then erase them unless another law requires longer retention.
The Rules' own illustration is retail-shaped: an e-book platform must keep order details, personal data and processing logs such as order confirmation, payment and delivery events for at least one year from the transaction, even if the customer deletes her account. A second illustration requires the fiduciary to ensure its cloud provider also retains data and logs for that year.
A retention schedule that works
| Data | Minimum | Then |
|---|---|---|
| Order, payment and delivery events | 1 year (Rule 8(3)) | Keep longer only where tax or other law requires |
| Marketing consent records | Life of consent plus 1 year | Erase |
| Support tickets and call recordings | 1 year after processing | Erase unless a dispute is open |
| Abandoned-cart data | Purpose-bound; 1 year for logs | Erase |
Restrict post-deletion data to a locked archive so it cannot be re-marketed. Background: one-year log retention.
Rights requests, breaches and the contact person
Rights requests
Rule 14 requires brands to publish how customers can make requests and the identifiers they need, such as registered mobile number, email or order ID. Grievances must be answered within a published period not exceeding 90 days. Build a self-serve privacy centre in the account section, and a verified channel for store customers without accounts.
Contact person
Rule 9 requires prominent publication of the business contact information of a person who can answer questions about processing, and that contact must appear in every response to a rights request. A Data Protection Officer is mandatory only for a Significant Data Fiduciary.
Breaches
Retail breaches often come from exposed admin panels, leaked courier manifests or compromised marketing tools. Under Rule 7 every personal data breach must be intimated to each affected customer without delay and to the Board, with a detailed report within 72 hours of becoming aware. There is no threshold below which a breach is exempt. Prepare templates in advance with the breach response playbook.
Further reading on suhasbhairav.com
- BlogAI in Retail vs Ecommerce: Store Ops Optimization & Personalization
- BlogPrivacy-First AI Marketing in a Post-Cookie World
- BlogAgent-based vendor risk auditing for sub-processors
- Prompts100 Best Gemini Prompts for E-commerce Stores
- AI AutomationAI Automation for Privacy and GDPR Requests: Uses + Example
Before 13 May 2027
Compliance checklist
Map customer data across every channel
Cover storefront, POS, CRM, loyalty, messaging, support and partner integrations.
Rule 3(b)(i)
Confirm Third Schedule status
Check whether you operate your own platform and whether registered users in India reach 2 crore.
Rule 8(1); Third Schedule
Unbundle marketing consent from checkout
Use an unticked, separate opt-in for WhatsApp, SMS and email offers.
Section 6
Publish a Rule 3 notice at checkout and sign-up
Itemise data collected, purposes and routes to withdraw, exercise rights and complain.
Rule 3
Sign processor contracts with all partners
Include security, breach reporting, retention and erasure clauses for couriers, vendors and agencies.
Rule 6(1)(f)
Retain order logs for one year
Keep order, payment and delivery logs for at least one year, even after account deletion.
Rule 8(3)
Publish rights request channels and identifiers
State the means and identifiers such as order ID or mobile number on the site or app.
Rule 14(1)
Publish a contact person
Show business contact details prominently and include them in every rights response.
Rule 9
Prepare breach intimation templates
Draft customer and Board templates covering the Rule 7 content requirements.
Rule 7
Answers
Frequently asked questions
Does the DPDP Act apply to small D2C brands?
Does the DPDP Act apply to small D2C brands?
Yes. The Act has no size threshold for ordinary Data Fiduciaries. A small D2C brand processing customer data digitally must meet notice, consent, security, breach, retention and rights obligations from 13 May 2027. Only the Third Schedule erasure rule depends on size, applying to e-commerce entities with at least 2 crore registered users in India.
Do I need consent to deliver an order?
Do I need consent to deliver an order?
Generally no. Section 7(a) allows processing of personal data a customer voluntarily provides for a specified purpose, such as delivering an order she placed, as long as she has not indicated that she does not consent. Using that data for marketing or profiling is a different purpose and needs consent.
Can I send WhatsApp offers to customers who bought from me?
Can I send WhatsApp offers to customers who bought from me?
Only with consent for that purpose. A purchase does not imply consent to marketing under the DPDP Act. Collect a separate, unticked opt-in at checkout or in the account, explain it in a Rule 3 notice, and give a one-step opt-out inside every message.
If a customer deletes her account, must I delete everything?
If a customer deletes her account, must I delete everything?
Not immediately. Rule 8(3) requires every Data Fiduciary to retain personal data, traffic data and processing logs for at least one year from processing. The Rules' e-book illustration says order, payment and delivery logs must be kept even after account deletion. After that year, erase unless another law requires longer retention.
Is a marketplace seller a Data Fiduciary?
Is a marketplace seller a Data Fiduciary?
For any customer data it decides how to use, yes. But the Third Schedule excludes a seller on a marketplace from the definition of e-commerce entity, so the three-year erasure rule does not apply to it. The marketplace itself is the e-commerce entity for its platform users.
Do retail brands need a Data Protection Officer?
Do retail brands need a Data Protection Officer?
Not unless the brand is notified as a Significant Data Fiduciary. Every Data Fiduciary must, however, publish the business contact information of a person who can answer questions about processing under Rule 9, and include it in every response to a rights request.
Legal references and sources
- Digital Personal Data Protection Rules, 2025 — Rule 8 and Third Schedule (official text)
- Digital Personal Data Protection Rules, 2025 — Rule 3 (official text)
- Digital Personal Data Protection Rules, 2025 — Rule 7 (official text)
- Digital Personal Data Protection Act, 2023 — Sections 6 and 7 (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
- 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 Marketing Teams: Cookies, Tracking and ConsentHow the DPDP Act and Rules apply to cookies, pixels, tracking and marketing consent in India, and what marketing teams must change before 13 May 2027.
- 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.
- Templates & playbooksDPDP Data Processing Agreement Clauses TemplateCopy-ready data processing agreement clauses for India, mapped to DPDP section 8(2), Rule 6(1)(f), Rule 7 breach timelines and Rule 8(3) one-year retention.
- Sector guidesDPDP for Small Businesses: A Proportionate Compliance PlanA proportionate DPDP compliance plan for Indian small businesses, MSMEs and early startups: what applies regardless of size, what to prioritise and what to leave until later.