6 mins

Section 11 Processor Disclosures for Indian E-Commerce Marketplaces

How e-commerce marketplaces identify specific Data Processors receiving customer data under Section 11 of the DPDP Act.

Written byVipul Abhishek· Former Advocate, Supreme Court of India

Last updated:

Section 11 Data Sharing Disclosure Requirements

Section 11(1) of the Digital Personal Data Protection Act, 2023 grants Data Principals specific rights regarding their information. E-commerce platforms operate as Data Fiduciaries. They collect large volumes of customer information during the checkout process. Under Section 11(1)(a), a user can request a summary of the personal data being processed and the specific processing activities undertaken. Section 11(1)(b) requires the marketplace to disclose the identities of all other Data Fiduciaries and Data Processors who received this personal data. The platform provides a description of the exact personal data shared with these external entities. A customer order routes personal data through multiple third parties. Payment gateways process financial details. Independent sellers view shipping addresses. Last-mile logistics providers use phone numbers for delivery updates. Responding to a Section 11 request requires naming the specific vendors that handled that individual customer's transaction. Supplying a static directory of all corporate vendors fails the statutory requirement. E-commerce platforms trace the exact data payload at the transaction level to maintain compliance.

E-Commerce Defensibility and Vendor Contracts

General Counsel face liability risks regarding third-party data flows. Vendor agreements define the data-sharing boundaries between the marketplace and its external processors. The legal team drafts limitation of liability clauses and indemnification terms to protect the enterprise. A regional logistics provider might misuse a delivery address or expose a shipping manifest. The contract specifies the financial penalties for such a breach. Paper agreements establish legal protection but fail to satisfy runtime regulatory inquiries. The Data Protection Board expects technical proof of where the data travelled. Relying on manual vendor tracking creates a 40 percent reduction in response efficiency for the compliance department. Legal teams separate governance protocols from runtime enforcement. Governance dictates the outside counsel spend for breach scenarios and establishes the data processing agreements. Runtime enforcement requires software automation to log the routing of personal data payloads at the point of sale. An automated identity registry maps each transaction to the specific processor that handled it.

Significant Data Fiduciary Designations

High-volume marketplaces frequently trigger additional regulatory obligations. Section 10(1) allows the Central Government to notify any Data Fiduciary as a Significant Data Fiduciary. The assessment considers the volume of personal data processed and the risk to the rights of the Data Principal. Other factors include public order and potential impact on the sovereignty and integrity of India. Section 10(2) outlines the duties of a Significant Data Fiduciary. The enterprise appoints a Data Protection Officer based in India. This individual represents the Significant Data Fiduciary under the provisions of the Act. The DPO remains responsible to the Board of Directors or a similar governing body. Processing Section 11 requests manually across millions of users strains this office. Implementing automated tracking yields a 3x faster response time for data subject requests compared to manual database queries. The DPO relies on these automated logs to demonstrate compliance during regulatory audits.

Lawful Purpose and Rule 3 Notice Translation

Section 4(1) states that a person may process personal data only in accordance with the provisions of the Act for a lawful purpose. Section 4(2) defines a lawful purpose as any purpose not expressly forbidden by law. The Act permits processing based on consent or certain legitimate uses. Marketplaces rely heavily on consent to process marketing and analytics data. The Digital Personal Data Protection Rules, 2025 dictate how platforms collect this permission. Rule 3 mandates itemised privacy notices that explain the specific personal data collected and the processing purpose. E-commerce companies cannot bundle basic terms of service with promotional marketing opt-ins. The platform separates shipping fulfillment data from promotional lists. Data Principals possess the right to access these notices in English or any of the 22 languages specified in the Eighth Schedule to the Constitution. Heavy banking compliance tools often struggle with this consumer-facing translation requirement. Marketplaces deploy systems engineered to manage high-volume consent requests across multiple regional languages without disrupting the checkout flow.

Procurement Tests for Privacy Software

Legal and procurement teams evaluate privacy software through specific technical trials. One primary acceptance test involves generating a simulated Section 11 disclosure report. The software output identifies only the processors involved in that single user's checkout history. A generic list of the entire corporate vendor registry results in an automatic failure of the trial. Another test evaluates the consent unbundler mechanism. The tool isolates marketing permissions from operational delivery data. Teams also review the audit trail capabilities. The system generates immutable logs for outside counsel to review during regulatory inquiries. Implementing dedicated privacy infrastructure achieves a precise mapping of data sharing at the transaction level. A marketplace operating without automated tracing struggles to identify which logistics partner received a specific phone number on a given date. Automated data discovery maps personal data to specific cloud assets and vendor APIs to close this operational gap.

Purpose-Level Consent Withdrawal

Customers hold the right to withdraw consent for specific processing activities. Operational errors occur when a platform treats a partial withdrawal as a mandate for total data deletion. Purpose-level withdrawal requires exact technical execution. A customer revoking consent for promotional campaigns stops the transmission of marketing emails. The platform retains the underlying order history and tax records. Transaction data retention operates under separate legal obligations and Section 7 legitimate uses. Deleting all financial records exposes the enterprise to statutory non-compliance in tax and corporate jurisdictions. The consent management platform selectively revokes data access based on the exact purpose the customer modified. Software architectures tag personal data with the specific lawful purpose used for collection. This tagging prevents a marketing withdrawal from erasing the active shipping address for a pending delivery.

Timeline and Action for General Counsel

The 13 May 2027 compliance deadline leaves legal heads 181 days to complete their DPDP infrastructure deployments. Relying on manual vendor tracking exposes the enterprise to unnecessary regulatory risk and operational delays. Large platforms depend on automated approaches to map processor sharing, serve regional language notices, and fulfill Section 11 disclosure requests. Software systems built for consumer scale handle the translation requirements of the Eighth Schedule languages natively. You can evaluate how a purpose-built solution handles these specific marketplace requirements at https://www.complydp.com/audit-preview before committing outside counsel budget to a manual review process.

Sources

Frequently asked questions

What information does a marketplace provide under a Section 11 request?

Under Section 11(1)(b) of the Digital Personal Data Protection Act, 2023, a Data Fiduciary provides the identities of all Data Processors and other Data Fiduciaries who received the customer's data. The marketplace also provides a description of the specific personal data shared.

Can we provide a master list of all our vendors to satisfy Section 11?

No. The disclosure applies specifically to the Data Principal making the request. You identify only the specific logistics partners, sellers, or payment gateways that actually processed that individual's personal data.

Does withdrawing consent mean we delete all customer order history?

No. Withdrawal applies to specific purposes. If a customer withdraws marketing consent, you stop promotional emails. You retain transaction and tax records as required by other laws or Section 7 legitimate uses.

How do the DPDP Rules 2025 affect our e-commerce privacy notices?

Rule 3 requires itemised notices that clearly explain the personal data collected and the purpose of processing. Platforms offer the option to access these notices in English or any of the 22 languages specified in the Eighth Schedule to the Constitution.

When is the compliance deadline for these DPDP obligations?

The compliance deadline for the Digital Personal Data Protection Act is 13 May 2027. Businesses map their consent management, processor tracking, and notice translation systems to be operational by this date.