6 mins
DPDP Act Section 16 Explained: Cross-Border Transfers and the Negative List
Section 16 of the DPDP Act permits cross-border data transfers by default. The Central Government holds the power to restrict destinations via a negative list. This article details how restrictions apply and the 50-crore penalty exposure for non-compliance under the Act and the DPDP Rules 2025.
Last updated:
The Section in One Paragraph
Section 16 of the Digital Personal Data Protection Act, 2023 governs the transfer of digital personal data outside India. The statute permits cross-border transfers by default. Through official notification, the Central Government possesses the authority to restrict transfers to specific countries or territories. Data flows freely until a destination receives an explicit ban. Privacy officers map their data flows to detect exposure to a restricted territory immediately upon publication of a negative list. The DPDP Rules 2025 provide the operational framework for regulatory enforcement if a Fiduciary violates these boundaries.
Exact Statutory Text Anchors
Section 16(1) grants the Central Government direct authority over international data flows. The government may restrict the transfer of personal data by a Data Fiduciary to any country or territory outside India. Section 16(2) creates an explicit carve-out for stricter laws. It clarifies that nothing in Section 16 overrides any other Indian law providing a higher degree of protection or restriction on data transfers. This clause preserves sectoral data localization mandates. For example, financial institutions face Reserve Bank of India directions on payment system data. These specific directions compel local storage. Fiduciaries cannot use the default permission of Section 16 to bypass existing localization requirements. The negative list relies on separate government notifications published in the Official Gazette. Relying entirely on the general transfer permission causes immediate compliance failures if a primary hosting region appears on a newly published restricted list.
Territorial Scope Intersection
Cross-border rules bind entities caught by the territorial scope of the Act. Section 3(a) covers processing of digital personal data within India. Section 3(b) extends the Act to processing outside India if the activity connects to offering goods or services to Data Principals within the territory of India. A foreign company selling software to users in India acts as a Data Fiduciary. This entity collects data in India and processes it abroad. If the Central Government restricts the country where this foreign entity hosts its servers, the entity faces an immediate legal conflict. The Fiduciary halts the transfer of any new data from India to that region. Section 3(c) provides specific exemptions. The Act ignores personal data processed by an individual for a domestic purpose. It also exempts personal data made publicly available by the Data Principal or by another person under a legal obligation. The negative list does not apply to these exempt data categories.
The Day a List Appears
Publishing a restriction notification under Section 1(2) and Section 16 alters the legal status of the affected destination immediately. The Official Gazette publication sets the effective date. The restriction takes effect the day it is published unless the notification specifies a transition period. Data Fiduciaries execute stop-processing protocols on that exact date. Routing data to a restricted server after publication constitutes an illegal transfer. Network architecture teams reroute data traffic to servers located in permitted jurisdictions. Legal counsel sends immediate cessation notices to processors operating within the restricted territory to ensure compliance with the DPDP Rules 2025.
Who This Binds and When
This obligation binds every Data Fiduciary transferring digital personal data across borders. It applies whether the transfer supports primary processing, backend storage, or third-party analytics. Processors execute the technical transfer, but the Data Fiduciary bears the legal liability. A generic compliance tool often fails to map data subsets from India to specific destination countries. General geographic tags lack the required granularity. Fiduciaries record exact country locations to respond to sudden negative-list updates. Enterprises relying on a single global cloud provider configure failover regions located in unrestricted countries.
How to Comply
Section 16 compliance requires readiness to halt data flows to newly restricted countries. Privacy teams establish specific protocols to handle this mechanism in alignment with the DPDP Rules 2025.
1. Maintain a dynamic data map. The privacy team creates a real-time data flow diagram. This record identifies the host country of every processor and sub-processor touching data originating from India.
2. Filter sectoral conflicts. Legal counsel documents an assessment confirming whether financial or telecom localization rules override the general Section 16 transfer permission.
3. Establish a rapid-response transfer kill switch. The Data Protection Officer writes a standard operating procedure. This protocol dictates how to migrate or terminate processing in a destination immediately following a government restriction notification.
4. Update vendor contracts. Procurement executes data processing agreements requiring vendors to notify the Data Fiduciary before moving data to a new geographic region.
Penalties for Getting It Wrong
Failing to stop transfers to a restricted country violates a core provision of the Act. The Schedule of the DPDP Act, 2023 states that breach of any other provision of the Act or Rules carries a maximum penalty of 50 crore rupees. The Data Protection Board determines the final penalty amount. The Board evaluates the volume of data transferred illegally and the duration of the violation. A global program unable to segregate data belonging to Data Principals in India from its global lakes risks continuous illegal transfers. This exposure compounds daily if a major hosting hub lands on the negative list. The Fiduciary cannot blame the vendor for the violation. Section 8(1) holds the Data Fiduciary responsible for compliance regardless of any agreement with a Data Processor.
Deadline Pressure
The DPDP hard compliance deadline of 13 May 2027 is 175 days away. Relying on a global privacy suite that treats the cross-border rules of India exactly like European transfer mechanisms creates a blind spot. Companies evaluate their vendor maps now. They apply these steps to confirm they can produce evidence on demand if the government issues a negative list.
Validate whether your current global compliance setup handles the negative-list mechanics required by Section 16 and the DPDP Rules 2025. Run a section-level gap check at https://www.complydp.com/audit-preview to test your cross-border data flow readiness.
Sources
Frequently asked questions
Does Section 16 require us to sign standard contractual clauses for India?
No. The DPDP Act permits cross-border transfers by default. The statute does not require specific transfer instruments. The government uses a negative list to restrict transfers to specific countries.
Can we transfer data anywhere without restrictions under the DPDP Act?
You can transfer data freely unless the Central Government notifies a specific country as restricted. Section 16(2) keeps stricter sectoral localization laws in place. Financial data often falls under these localized rules.
What penalty applies if we transfer data to a restricted country?
Transferring data to a restricted territory breaches the Act. This triggers the Schedule penalty for breach of other provisions. That specific penalty carries a maximum fine of 50 crore rupees.
How do we prepare for a negative list before one is published?
You set up a precise map of where your processors host data. If a country lands on the restricted list, you migrate processing out of that territory immediately to avoid illegal transfers.
Does our global compliance platform cover cross-border rules for India automatically?
Many global suites treat cross-border rules uniformly. You need a setup that tracks the specific differences of the DPDP Act and Rules 2025. This setup must map vendor locations to respond to sudden government notifications.
ComplyDP