Cross-border data transfer under the DPDP Act: Section 16, Rule 15 and sectoral localisation.
Almost every Indian startup sends personal data abroad, through cloud hosting, email tools, CRMs or support desks. Here is what the Act allows, where sector rules are stricter, and what to put in place now.
By Advocate Joginder Poswal · Updated November 2026
In short. The DPDP Act allows transfers abroad unless the government blacklists a country, and no such notification had been traced as of November 2026. Stricter sector rules still win, so payment data stays in India under the RBI's 2018 circular. You remain responsible for whatever your foreign vendors do with the data. Significant Data Fiduciaries can be told to keep specified data inside India. Indian companies processing foreigners' data under a foreign contract are largely exempt.
The negative-list model
Section 16(1) lets the Central Government, by notification, restrict the transfer of personal data by a Data Fiduciary to a country or territory outside India. Everything not restricted is allowed. Lawyers call this a negative list: instead of naming approved countries, the law names forbidden ones.
No notification under Section 16(1) had been traced at the time of writing. That position can change with a single Gazette notification, so a business that depends on a foreign region should check the MeitY website periodically and design its systems so that data can be moved if a restriction arrives.
Rule 15 and requests by foreign States
Rule 15 adds one condition to the general freedom. A Data Fiduciary that processes data in India, or abroad in connection with offering goods or services in India, must meet any requirements the Central Government specifies, by general or special order, about making personal data available to a foreign State or to any person or agency under its control. In plain terms, the government keeps the power to control what reaches foreign governments, whatever the commercial position. Rule 15 applies from 13 May 2027.
Stricter sectoral laws still apply
Section 16(2) says nothing in Section 16 restricts any other law that provides a higher degree of protection for, or restriction on, transfer of personal data outside India. The DPDP Act sets a floor. Sector rules can go further, and where they do, they prevail.
The best known example is the RBI circular on Storage of Payment System Data of 6 April 2018. It requires all payment system providers to store the entire data relating to the payment systems they operate in a system only in India, including the full end-to-end transaction details. For the foreign leg of a transaction, the data may also be stored abroad if required. A fintech that processes payments cannot read Section 16 as permission to move that data offshore.
Any business in a regulated sector should list the localisation or storage directions issued by its own regulator and treat them as binding alongside the DPDP Act.
Significant Data Fiduciaries and localisation
Rule 13(4) applies only to Significant Data Fiduciaries. It requires them to ensure that personal data specified by the Central Government, on the recommendation of a committee it constitutes, is processed so that the data and the traffic data about its flow are not transferred outside India. Ordinary Data Fiduciaries are not covered. For a large platform that may be designated, this is the provision to watch, because it allows targeted localisation of particular categories of data.
You stay responsible for foreign vendors
Moving data to a vendor abroad does not move the responsibility. Section 8(1) makes the Data Fiduciary responsible for compliance in respect of any processing done on its behalf by a Data Processor, irrespective of any agreement to the contrary. Section 8(2) allows a Data Processor to be engaged for activities related to offering goods or services to Data Principals only under a valid contract.
For foreign vendors, the contract should cover where the data is stored and processed, which sub-processors are used, security standards, breach notice to you fast enough for you to meet Rule 7, and erasure on instruction. Standard click-through terms of large cloud and SaaS providers often cover most of this. Read them against the Act rather than assuming they do.
Foreign companies serving Indian users
The Act also reaches outward. Section 3(b) applies it to processing outside India if it is in connection with any activity related to offering goods or services to Data Principals within India. A Singapore or Delaware company with an app aimed at Indian users is a Data Fiduciary under the Act, even if every server it uses is abroad.
The outsourcing exemption
Section 17(1)(d) protects India's outsourcing industry. Where a person based in India processes the personal data of Data Principals outside India under a contract with a person outside India, most of the Act does not apply: Chapter II, Chapter III and Section 16 are switched off, except Section 8(1) and Section 8(5).
So an Indian BPO or software company handling a US client's customer data under a services contract need not give DPDP notices or answer DPDP rights requests for those customers. It must still keep reasonable security safeguards under Section 8(5), and it remains accountable for compliance under Section 8(1). The client's own home law will usually impose its own duties through the contract.
What to do now
- Map where data goes. For each system and vendor, record the country where data is stored and processed, including backups and support access.
- Check your sector. Payments, banking, insurance, telecom and government contracts often carry their own storage rules.
- Fix the contracts. Make sure each foreign processor is engaged under a valid contract that covers location, sub-processors, security, breach notice and erasure.
- Keep an exit route. Prefer vendors that offer an Indian region or let you move data, so that a future Section 16 notification is an inconvenience rather than a crisis.
- Watch for notifications under Section 16(1), orders under Rule 15 and, for large platforms, specifications under Rule 13(4).
Frequently asked questions
Yes, unless the government restricts the destination country under Section 16(1) or a stricter sectoral law applies, such as the RBI payment data storage rule.
No Section 16(1) notification had been traced at the time of writing in November 2026. Check the MeitY website and the Gazette before relying on this.
Yes, under Section 3(b), where the processing is connected with offering goods or services to Data Principals in India.
Mostly not. Section 17(1)(d) exempts them from Chapter II, Chapter III and Section 16, except Section 8(1) and the security duty in Section 8(5).
Related reading
- DPDP Data Retention and Erasure: how long data may be kept and when it must go.
- DPDP Data Breach Notification: who has to be told after a breach, and by when.
- DPDP Act Compliance for Indian Startups: the full set of obligations and the timeline to 13 May 2027.
- DPDP Compliance: all guides on the Act in one place.
Enrolment: Bar Council of Punjab & Haryana | No.: PH/9616/2023
This page is informational and does not constitute legal advice. References are to the Digital Personal Data Protection Act, 2023, the Digital Personal Data Protection Rules, 2025 (G.S.R. 846(E), 13 November 2025) and the RBI circular of 6 April 2018 on Storage of Payment System Data. How these apply depends on the data and operations of each organisation.
