DPDPAE-CommerceSection 6ConsentProfiling
AMLEGALS / Data Privacy / E-Commerce Compliance
Digital Personal Data Protection Act 2023 — E-Commerce

Every cart, every click, every delivery address is personal data under the DPDPA

E-commerce platforms process personal data at a scale and velocity that makes DPDPA compliance an architectural decision, not a policy overlay. AMLEGALS builds the consent framework, notice architecture, rights-fulfilment systems and processor governance that let platforms operate within the statute.

Strategic context

Privacy by design for platforms that process data at scale

An e-commerce platform touches personal data at every stage of the customer journey: browsing behaviour, search queries, cart contents, delivery address, payment credentials, return requests and post-purchase reviews. Each touchpoint is a processing activity under the DPDPA that requires a lawful basis — consent under Section 6 or a legitimate use under Section 7. The platform’s privacy architecture must distinguish between data processed for order fulfilment (potentially Section 7) and data processed for marketing, profiling and third-party analytics (Section 6 consent required).

AMLEGALS works with e-commerce marketplaces, D2C brands and quick-commerce platforms to build DPDPA-compliant data architectures. The practice covers Section 5 notice design (itemised, purpose-specific, presented before data collection), Section 6 consent framework (granular, withdrawable, auditable), Section 8(2) processor contracts (payment gateways, logistics partners, marketing platforms), Section 9 children’s data safeguards and scalable rights-fulfilment systems under Sections 11–14.

Workstreams

Advisory workstreams

01

Notice and consent architecture

Designing the Section 5 notice flow and Section 6 consent framework across the customer journey — registration, checkout, marketing, profiling.

02

Purpose segregation and mapping

Separating processing purposes (fulfilment, marketing, analytics, seller services, fraud detection) and mapping each to its lawful basis.

03

Processor governance

Structuring Section 8(2) contracts with payment gateways, logistics partners, cloud providers, analytics vendors and marketing platforms.

04

Children’s data compliance

Implementing age-gating, parental consent mechanisms and restrictions on behavioural monitoring under Section 9.

05

Rights fulfilment at scale

Building automated systems for Data Principal access, correction, erasure and grievance redressal under Sections 11–14.

06

Breach response architecture

Establishing the Section 8(6) and Rule 7 breach intimation workflow for a platform handling millions of records.

Answers

Frequently asked questions

01Does the DPDPA apply to e-commerce platforms?

Yes. Every e-commerce marketplace, D2C brand, online retailer and quick-commerce platform that processes personal data of individuals in India is a Data Fiduciary under the DPDPA. The platform must provide itemised notice under Section 5 before collecting data, obtain consent under Section 6 for each processing purpose (order fulfilment, marketing, profiling, analytics, seller verification) and implement reasonable security safeguards under Section 8(5).

02How does consent architecture work for marketing and profiling?

Under Section 6, consent must be free, specific, informed and unambiguous, limited to the stated purpose. A blanket consent covering order fulfilment, marketing emails, push notifications, behavioural profiling and third-party sharing in a single tick-box is unlikely to meet the standard. Each distinct purpose requires separate, granular consent. Section 6(4) mandates that withdrawing consent must be as easy as giving it — platforms must provide a one-click opt-out, not a buried settings page.

03What about seller and delivery partner data?

Marketplace platforms collect personal data of sellers (identity, bank details, GSTIN, address), delivery partners (Aadhaar, driving licence, GPS location) and warehouse staff. Each category requires its own Section 5 notice with itemised purposes. Seller onboarding data processed for KYC and payment may rely on legitimate use under Section 7 (contractual necessity) but marketing use of seller data requires separate consent under Section 6.

04How must e-commerce platforms handle children’s data?

Section 9 prohibits processing personal data of a child (anyone under eighteen) without verifiable parental consent. Platforms must implement age-gating or age-verification mechanisms. Behavioural monitoring and targeted advertising directed at children are prohibited. Platforms that permit minors to create accounts or purchase products must build the parental consent mechanism into the registration flow.

05What Data Principal rights must platforms honour?

Sections 11–14 grant Data Principals the right to access a summary of their data and processing activities, the right to correction and erasure, the right to nominate and the right to grievance redressal. E-commerce platforms with millions of users must build automated fulfilment systems — a manual email-based process will not scale and will breach response timelines.

06Does an initial discussion create a lawyer-client relationship?

No. No engagement is treated as accepted until conflicts, scope and terms are confirmed in writing.

Engage AMLEGALS

Request a confidential assessment

Share the platform profile for a confidential assessment of DPDPA compliance requirements.

Request a confidential assessment

Business contact details are used only to respond to this request. No lawyer-client relationship arises until conflicts, scope and terms are agreed in writing.