Thursday, 19 November 2026 Tracking Indian retail every day
Policy Explainer

DPDP Act and retail customer data, explained

Consent, notice and purpose limitation now decide how Indian retailers can collect, store and use customer data — and the main obligations begin on 13 May 2027.

DPDP Act and retail customer data, explained

The short answer

The DPDP Act, 2023 requires Indian retailers and ecommerce marketplaces to collect personal data only with free, specific and informed consent, to state the purpose clearly, and to honour rights to access, correction, erasure and withdrawal. MeitY opened consent manager registration on 13 November, while the main obligations for data fiduciaries begin on 13 May 2027.

Key takeaways

  • The DPDP Act makes free, specific and informed consent the default basis for retail marketing, profiling and data sharing, while order fulfilment can rest on legitimate uses.
  • MeitY opened consent manager registration on 13 November, with applications submitted via the dpbi.gov.in portal to the DPBI, but the main obligations for data fiduciaries begin on 13 May 2027.
  • Loyalty programmes and purchased marketing lists need purpose-by-purpose consent and re-permissioning, with withdrawal honoured across every channel.
  • Retailers remain responsible for third-party processors and tracking pixels, so contracts need purpose limits, breach timelines and deletion clauses.
  • Compliance is a build-and-run budget, not a one-time legal fee, and the 72-hour breach reporting duty needs a tested runbook.

The Digital Personal Data Protection Act, 2023 — DPDP Act for short — is India's law governing how businesses collect and use personal data, meaning any information that can identify a living person. For a retailer or an ecommerce marketplace, that covers a phone number at checkout, an address on a delivery label, a loyalty card linked to a birthday, a WhatsApp number used for offers, and the browsing pixels quietly loading on a product page. The law treats the shopper as a data principal and the business as a data fiduciary — the entity that decides why and how the data is processed.

According to MeitY's announcement, the Ministry of Electronics and Information Technology opened the registration process for consent managers on 13 November, launching a portal at dpbi.gov.in where applications are submitted to the Data Protection Board of India (DPBI). The substantive obligations for data fiduciaries, including consent, security safeguards and breach reporting, take effect on 13 May 2027. That gap is the planning window. Retailers who treat it as a deadline will spend the last quarter of the window firefighting; those who treat it as a build schedule will fold compliance into work they were doing anyway.

What does the DPDP Act actually require of a retailer?

Four obligations do most of the work in a retail setting.

  • Notice. Before or at the point of collecting data, the business must tell the shopper what is being collected and why, in clear language, with a link to withdraw consent later.
  • Consent. Consent must be free, specific, informed, unconditional and unambiguous, and given by a clear affirmative action. As a matter of legal interpretation, a pre-ticked box inside terms and conditions would not appear to qualify.
  • Purpose limitation. Data collected for order fulfilment cannot be repurposed for unrelated marketing without a separate basis. This is the clause that quietly breaks most loyalty and CRM setups.
  • Data principal rights. Shoppers can ask to see their data, correct it, erase it, nominate someone to act for them, and withdraw consent. Withdrawal must be as easy as giving consent.

There is also a security and breach-reporting duty. According to our coverage, breach reporting requires notifying affected individuals without delay and filing a detailed report with the DPBI within 72 hours, with maximum penalties of up to ₹250 crore for security failures under the Act's statutory penalty schedule.

How does consent work across a retail journey?

A retail customer journey touches data at many points: account sign-up, checkout as guest, newsletter pop-ups, app notifications, loyalty enrolment, WhatsApp campaigns, returns, and third-party analytics pixels. Each is a separate consent question, and bundling them into one "I agree" is exactly what the law discourages.

A practical approach is to map the journey first, then assign a lawful basis to each touchpoint. Order fulfilment and fraud checks generally rest on a legitimate use rather than marketing consent. Promotional messages, profiling and sharing with advertising partners need consent, and that consent must be separable from the terms of sale. If a shopper refuses marketing consent, the order must still go through.

What is a consent manager, and does my store need one?

A consent manager is an entity registered with the DPBI that lets individuals give, review, manage and withdraw consent through an interoperable platform. According to our coverage, MeitY said the framework "enables data principals to exercise greater control over consent". Two details matter: consent managers are accountable to the data principal, not to the brand paying for the service, and the platform must be interoperable, so a shopper's choices work across services rather than being trapped inside one app.

Eligibility is narrow. According to our coverage, applicants must be Indian-incorporated companies with a minimum net worth of ₹2 crore and adequate technical, operational and financial capacity, and the DPBI will publish a list of registered consent managers. Most retailers will be integrators, not consent managers. The operational question is whether your consent capture can hand off to, and receive signals from, a registered consent manager without breaking the checkout flow.

What changes for loyalty programmes and marketing lists?

Loyalty programmes are the hardest area because they were built on the assumption that enrolment equals perpetual permission. Under the DPDP Act, enrolment consent must state each purpose: points accrual, transactional messaging, profiling for personalised offers, and sharing with coalition partners are four different uses. A programme that shares member data with a partner brand needs that purpose named at enrolment, not added by an email update.

Marketing lists carry a similar burden. A purchased or rented list is the riskiest asset in the database, because the retailer cannot show how consent was obtained. Old lists collected under pre-DPDP norms need re-permissioning or retirement. Withdrawal must be honoured across every channel — email, SMS, WhatsApp, app push — which usually means a single suppression list that all sending systems check before dispatch.

What about third-party data processors and pixels?

A data processor is a vendor that handles personal data on the retailer's behalf: the cloud host, the CRM, the logistics partner, the call centre, the analytics provider. The retailer remains responsible for what the processor does, so contracts need purpose limits, security obligations, breach notification timelines and deletion-on-exit clauses.

Marketing and analytics tags deserve separate attention. A pixel that fires before consent is captured, or that shares hashed identifiers with an ad platform, is a processing activity that needs a basis. Tag governance — deciding which scripts load before and after consent — is now a compliance control, not a marketing preference.

The NCDRC's ruling upholding a ₹20 lakh CCPA penalty on Weblink.In, operator of ExportersIndia.com, is a useful signal on a related point: according to the NCDRC order, the commission rejected the company's Section 79 safe-harbour defence, holding that intermediary protection depends on due diligence. Marketplaces that assume platform status shields them from responsibility for what flows through their systems should read that ruling carefully.

What does compliance cost a retailer?

Costs split into one-time build and recurring run. One-time work includes data mapping, consent-flow redesign, contract renegotiation with processors, and consent-platform integration. Recurring work includes consent records, grievance handling, security testing and audit. Smaller D2C brands can often absorb this inside existing agency and SaaS spend; large marketplaces with multiple apps, seller data and ad businesses face a longer programme.

Worked example (hypothetical, illustrative only — figures are invented and not benchmarks): Say a mid-sized apparel brand with 4 lakh loyalty members budgets ₹18 lakh in year one. That covers ₹6 lakh for a consent management platform and integration, ₹4 lakh for data mapping and legal review, ₹3 lakh for contract renegotiation across 20 processors, ₹3 lakh for tag governance and security testing, and ₹2 lakh for training and a grievance-handling desk. Year two run-rate falls to about ₹9 lakh as build costs drop away. If re-permissioning recovers only 55% of the old list, the brand should model the lost campaign reach as a marketing cost, not just a compliance line.

What should a founder check before 13 May 2027?

  1. Map every place personal data enters the business, including offline store forms and delivery apps.
  2. Separate marketing consent from the terms of sale at every touchpoint.
  3. Audit old marketing lists and decide what to re-permission and what to delete.
  4. Rewrite processor contracts with purpose limits and deletion clauses.
  5. Build one withdrawal mechanism that reaches every channel.
  6. Test a data access or erasure request end to end, and time how long it takes.
  7. Draft a breach response runbook that can file with the DPBI within 72 hours.

Common mistakes

  • Treating the privacy policy as the notice. The notice must be at the collection point, not buried in a footer.
  • Assuming loyalty points are payment for data, and therefore consent is implied.
  • Letting each channel team run its own opt-out list, so a withdrawal in email never reaches WhatsApp.
  • Forgetting offline data — store enrolment forms, delivery address books, call-centre notes.
  • Signing processor contracts without a deletion-on-exit clause, then discovering data cannot be purged.

What it means for Indian retailers

Data quality is about to become a revenue variable. Lists built on clear, specific consent will convert better than lists padded with stale, unverifiable contacts, because the compliant list can still be mailed. Retailers who start now can fold consent capture into checkout redesigns and app updates already on the roadmap. Those who wait will pay for rushed retrofits, and the penalty ceiling for security failures — up to ₹250 crore under the Act's statutory penalty schedule, according to our coverage — is not a number any operator wants to test.

In this story

Frequently asked questions

When do DPDP Act obligations start for retailers?

According to our coverage, the substantive obligations for data fiduciaries, including consent, security safeguards and breach reporting, take effect on 13 May 2027. MeitY opened consent manager registration on 13 November, with applications submitted via the portal at dpbi.gov.in to the DPBI.

Can a retailer rely on pre-ticked consent boxes?

As a matter of legal interpretation, no. Consent must be free, specific, informed, unconditional and unambiguous, given by a clear affirmative action. A pre-ticked box inside terms and conditions would not appear to meet that test, and marketing consent must be separable from the terms of sale.

Does a loyalty programme need separate consent?

Yes, in practice. Points accrual, transactional messaging, profiling for personalised offers and sharing with partner brands are distinct purposes. Each should be named at enrolment, and withdrawal must be as easy as giving consent.

Who is a data processor and what must a retailer do about them?

A data processor is a vendor handling personal data on the retailer's behalf, such as a CRM, cloud host, logistics partner or analytics provider. The retailer stays responsible, so contracts need purpose limits, security obligations, breach notification timelines and deletion-on-exit clauses.

What is a consent manager under the DPDP Act?

A consent manager is a DPBI-registered entity that lets individuals give, review, manage and withdraw consent through an interoperable platform. According to our coverage, applicants must be Indian-incorporated with a minimum net worth of ₹2 crore.

WiseRetail

The week in Indian retail, ecommerce and D2C — in one short email every Friday.