[Analysis] Data Localisation in India under the DPDP Act – Section 16 Negative List | RBI Payment Data Storage | Transfer Impact Assessment
- Blog|Company Law|
- 11 Min Read
Data localisation and cross-border transfers under the DPDP Act: the section 16 negative list, Rule 15, the RBI payment data rule, the SEBI SaaS circular and transfer impact assessments.
- By Taxmann
- |
- Last Updated on 15 November, 2026
Table of Contents
- What is data localisation?
- Does the DPDP Act require data localisation?
- How does India’s approach differ from Europe’s?
- Which Indian rules require data to stay in India?
- What does the RBI rule on storage of payment system data require?
- What is a transfer impact assessment, and when is one needed?
- How should a business manage cross-border transfers?
- Quick answers
1. What is data localisation?
Data localisation, also spelt data localization, is a legal requirement that personal data, or specified categories of it, be stored or processed only within the country. A cross-border data transfer is the opposite movement: a Data Fiduciary sending personal data for processing to a country or territory outside India.
The arguments for mandatory localisation include law enforcement, preventing foreign surveillance, creating local jobs, keeping data breaches within the jurisdiction of Indian authorities and strengthening the Indian economy. The argument against is that many economies have yet to bring in a data protection law, and a blanket restriction on dealing with them would hamper business that could otherwise be done safely under the stricter rules Indian law already applies.
The stakes for India are large. Its services exports were projected at about 421 billion dollars in the financial year 2025-26. More than two thousand global capability centres run finance, human resources, engineering and analytics functions from Indian cities for companies headquartered elsewhere, and they employ around 2.36 million people. Each of these arrangements depends on data being able to move.
2. Does the DPDP Act require data localisation?
No. India has taken a permissive approach to sending personal data abroad. Section 16(1) of the DPDP Act allows the Central Government, by notification, to restrict the transfer of personal data by a Data Fiduciary for processing to any country or territory outside India that it notifies. Rule 15 of the Digital Personal Data Protection Rules, 2025 (DPDP Rules) adds that a Data Fiduciary must meet whatever requirements the Central Government specifies, by general or special order, for making personal data available to a foreign State or to a person or entity under its control.
Read together, data may go anywhere unless the Government says otherwise. This is usually called a negative list: the Government will notify the countries to which transfer is restricted, not a list of countries to which data may go. No country had been notified when the book stated the law, in October 2026.
Two qualifications matter. The power is discretionary and may be exercised at any time, which leaves businesses planning around a restriction that has not yet arrived. And section 16(2) preserves any other Indian law that provides a higher degree of protection for, or a stricter restriction on, transfers outside India, so sector rules such as the Reserve Bank of India’s rule on storing payment system data continue to apply on their own terms.
The restriction falls on the Data Fiduciary, not on a Data Principal who deals directly with a business processing data outside India. Because both the freedom to transfer and the restriction sit with the fiduciary, it stays liable for a breach of the law even where the processing is done abroad.
Section 16 and Rule 15 apply from 13 May 2027. Until then, a transfer of sensitive personal data is governed by Rule 7 of the Information Technology (Reasonable Security Practices and Procedures and Sensitive Personal Data or Information) Rules, 2011 (SPDI Rules). It is permitted only if the recipient ensures the same level of data protection as the SPDI Rules require, and the transfer is either necessary for a lawful contract with the person who provided the information or made with that person’s consent.
One exemption matters to India’s outsourcing industry. Section 17(1)(d) exempts processing in India of the personal data of people outside India, carried out under a contract with a person outside India by a person based in India. The exemption is partial: sections 8(1) and 8(5), on the Data Fiduciary’s responsibility for compliance and on reasonable security safeguards, still apply.
3. How does India’s approach differ from Europe’s?
The DPDP Act and the EU General Data Protection Regulation (GDPR) start from opposite ends. Abha Tiwari and Aditya Singhania put the contrast this way: India permits transfers everywhere until the Government notifies otherwise, while Europe permits transfers nowhere until a mechanism is established, and the exporter must establish it.
| Point | India (DPDP Act) | European Union (GDPR) |
|---|---|---|
| Starting position | Transfers allowed to any country until the Central Government notifies a restriction | No transfer outside the European Union unless a transfer mechanism is first established |
| Who carries the burden | The State, to justify a restriction | The business, to justify a transfer |
| Is the crossing regulated? | No. Exposure arises from the contract with the processor and from what is done with the data | Yes. An exporter without an appropriate transfer tool is in breach on that omission alone |
| Transfer tools | No separate transfer step; the business looks to its contracts | An adequacy decision, standard contractual clauses or binding corporate rules, or a narrow derogation |
| Transfer impact assessment | Not required | Required where the transfer relies on an Article 46 tool such as standard contractual clauses |
Under the DPDP framework, what matters is the functional role each party occupies. A Data Fiduciary remains answerable for personal data whose purpose and means of processing it determines, whoever carries out the processing and wherever they sit, and it discharges that responsibility largely through its contract with the processor. The practical result is that an Indian business sending data abroad has, for the present, no separate transfer step to clear and must look instead to its contracts, while a European business sending data to India must select a mechanism, document it and assess Indian law for itself.
4. Which Indian rules require data to stay in India?
The few localisation requirements in Indian law sit in sector rules, which section 16(2) leaves untouched, and in a power over Significant Data Fiduciaries.
| Rule | Who it covers | What must stay in India |
|---|---|---|
| Reserve Bank of India, Storage of Payment System Data, circular dated 6 April 2018 | Payment system providers authorised by the Reserve Bank, all banks operating in India, and the intermediaries, service providers, payment gateways and vendors they engage | The entire data relating to the payment systems they operate |
| SEBI circular on SaaS-based solutions dated 3 November 2020 | Stock brokers, depository participants and other SEBI intermediaries using software as a service for governance, risk and compliance | Critical data, kept within the legal boundary of India |
| Rule 13 of the DPDP Rules, from 13 May 2027 | Significant Data Fiduciaries | Personal data specified by the Central Government, together with the traffic data relating to its flow |
The SEBI circular responded to a specific risk. Financial sector institutions were adopting software as a service for their governance, risk and compliance functions, and the risk and compliance data often moved beyond India’s legal and jurisdictional boundary because of the shared cloud model. Following a CERT-In advisory, intermediaries were asked to keep control of critical systems through direct supervision while keeping critical data within India, and to report compliance every half year.
The DPDP Rules add a localisation power of their own for Significant Data Fiduciaries. Once designated, such a fiduciary must take measures to ensure that personal data specified by the Central Government is not transferred outside India. The specification is made on the recommendation of a committee that includes officials of the Ministry of Electronics and Information Technology. The power sits alongside the other obligations covered in Significant Data Fiduciary obligations.
Buyers of Indian businesses should check sector-specific localisation requirements, particularly in financial services and health, before planning to move acquired data into global systems.
5. What does the RBI rule on storage of payment system data require?
It requires payment data to be stored only in India. In its Statement on Developmental and Regulatory Policies of 5 April 2018, the Reserve Bank decided that all payment system operators must store the data relating to the systems they operate only within India, to secure unfettered access to payment data for supervisory purposes. It gave effect to that decision by a directive under section 10(2) read with section 18 of the Payment and Settlement Systems Act, 2007, issued by its circular of 6 April 2018.
The circular set three requirements:
- the entire data relating to the payment systems operated must be stored in a system only in India, including the full end-to-end transaction details, though data for the foreign leg of a transaction may also be stored abroad if required;
- compliance within six months, reported to the Reserve Bank by 15 October 2018; and
- a System Audit Report by a CERT-In empanelled auditor certifying completion, approved by the board of the system provider and submitted by 31 December 2018.
The data covered includes customer data such as name, mobile number, email, Aadhaar number and PAN, payment sensitive data such as customer and beneficiary account details, payment credentials such as OTP, PIN and passwords, and transaction data such as originating and destination system information, transaction reference, timestamp and amount.
Frequently asked questions issued on 26 June 2019 qualify the directive in four respects:
- it restricts storage, not processing, so payment transactions may be processed abroad, but the data must then be deleted from the foreign systems and brought back to India within one business day or 24 hours from processing, whichever is earlier;
- for a cross-border transaction, a copy of the domestic component may also be stored abroad if required;
- the directions reach all entities in the payments ecosystem engaged by operators and banks, including intermediaries, service providers, payment gateways and third-party vendors, while responsibility for compliance stays with the payment system operator; and
- payment data may be shared with an overseas regulator only with the Reserve Bank’s prior approval.
Data needed for a chargeback or a customer dispute is accessed from India, where it is stored; it is not kept abroad until the dispute window closes. Banks, especially foreign banks, that were earlier specifically permitted to store banking data abroad may continue to do so, but data on domestic payment transactions must be stored only in India.
6. What is a transfer impact assessment, and when is one needed?
A transfer impact assessment, or TIA, is the exporter’s due diligence before a transfer that relies on an Article 46 GDPR tool such as standard contractual clauses. It tests whether the mechanism can deliver equivalent protection in practice in the receiving country, by analysing that country’s laws, government access regime, judicial oversight and remedies, and by identifying supplementary measures where needed: technical, such as strong encryption and pseudonymisation; contractual, such as enhanced audit, notification and challenge obligations; and organisational, such as minimisation, access controls and data flow restrictions.
The need for it comes from Schrems II. After that judgment, regulators made clear that paper protections may fail in practice where the destination country’s laws, such as broad government access powers, prevent the importer from honouring its commitments. In July 2023 the Swedish authority IMY fined Tele2 SEK 12 million because standard contractual clauses together with Google Analytics’ built-in IP anonymisation, without further measures, did not secure an “essentially equivalent” level of protection. Companies that had used proxy servers or server-side substitution escaped a fine on the same facts.
Annexure C of the book is a TIA template based on the CNIL template and EDPB Recommendations 01/2020. After a summary page, it works through six steps:
- know your transfer, describing its purpose, sensitivity and volume;
- identify the transfer tool;
- assess the laws and practices of the destination country;
- identify and adopt supplementary measures;
- implement the supplementary measures; and
- re-evaluate at appropriate intervals, because a TIA is not a one-off.
Indian law does not require a TIA for data leaving India. It matters to Indian businesses in two ways: a business that exports data under the GDPR must carry one out, and a European business sending data to India must assess Indian law for itself before it relies on a transfer tool.
7. How should a business manage cross-border transfers?
Cross-border transfers should be managed as an ongoing risk, not a box to tick. The authors expect a mature programme to keep accurate data flow maps and registers of transfers and transfer tools, perform TIAs and document supplementary measures, review transfers periodically and whenever the law or the geopolitical position changes, and embed controls across procurement, contracting, security architecture and incident response. A record of processing activities that lists each transfer and the mechanism relied on gives that register a home.
Contracts carry most of the weight under Indian law. The template data processing agreement requires a processor to transfer personal data originating from India only in accordance with section 16 of the DPDP Act and Rule 15 of the DPDP Rules, never to a country the Central Government has restricted, and subject to any sector rule that data be stored or processed only within India. It also requires a record of every transfer outside India, its destination and the mechanism relied on, updated within thirty days of any change in sub-processors or processing locations.
Acquisitions need the same attention. Due diligence should examine every international transfer arrangement at the target: the mechanisms, destinations and categories of data, including intragroup transfers, which are often overlooked but make up the bulk of cross-border transfers in large multinational groups, and transfers to cloud providers and key vendors. After completion, moving acquired Indian data into the buyer’s global systems may be subject to notifications under section 16.
8. Quick answers
What is data localisation?
Data localisation is a legal requirement that personal data, or specified categories of it, be stored or processed only within a country. In India it comes from sector rules such as the Reserve Bank of India’s payment data storage rule, not from the DPDP Act generally.
Does the DPDP Act require data localisation?
No. Section 16 lets the Central Government restrict transfers to countries it notifies, and data may otherwise go anywhere. Separately, the DPDP Rules let the Central Government require Significant Data Fiduciaries to keep specified personal data in India.
What is the negative list under section 16?
It is the list of countries or territories to which the Central Government restricts the transfer of personal data. The Government notifies restricted destinations rather than approved ones, and no country had been notified by October 2026.
What does the RBI data localisation rule require?
Payment system providers must store the entire data relating to the payment systems they operate only in India, including full end-to-end transaction details. The rule, set by a circular of 6 April 2018, also binds the intermediaries, payment gateways and vendors they engage.
Can payment data be processed outside India?
Yes. The Reserve Bank restricts storage, not processing, but data processed abroad must be deleted there and brought back to India within one business day or 24 hours from processing, whichever is earlier.
Is a transfer impact assessment mandatory in India?
No. A transfer impact assessment is a GDPR requirement for transfers relying on tools such as standard contractual clauses. A European business sending data to India must still assess Indian law for itself.
Which rule governs transfers of personal data before 13 May 2027?
For sensitive personal data, Rule 7 of the SPDI Rules. The recipient must ensure the same level of protection, and the transfer must be necessary for a lawful contract with the person who provided the information or be made with that person’s consent.
Chapter 12 of Digital Personal Data Protection Law Practice and Compliance by Abha Tiwari and Aditya Singhania covers processing of personal data outside India: section 16 and Rule 15, the India and UAE Comprehensive Economic Partnership Agreement, the Reserve Bank of India’s rule on storage of payment system data with its clarifications, and SEBI’s guidance on SaaS-based solutions. Paragraph 1.6 compares the Indian and European transfer models, and Annexure C is a transfer impact assessment template.
Taxmann Advisory offers research support from a team of researchers who find the material a question needs, and implementation support that includes putting compliance SOPs in place.
Taxmann.com | Research carries the Digital Personal Data Protection Rules, 2025, including Rules 13 and 15, under Indian Acts & Rules, and Taxmann.com | Store has the Digital Personal Data Protection Act 2023 with Rules – Bare Act with Section Notes.
Related reading: cross-border data transfers under the DPDP Act · DPDP compliance for fintech and BFSI · the DPDP Act and the GDPR compared · obligations of Data Fiduciaries.
More in this series: the SPDI Rules and the DPDP Act · the Record of Processing Activities (ROPA) · the incident response plan · data retention and erasure · the privacy notice under Rule 3 · the data processing agreement · employee data and workplace monitoring · exemptions under the DPDP Act · legitimate uses under section 7 · the Data Protection Board of India · how a DPDP compliance audit is conducted · Significant Data Fiduciary obligations · Consent Managers under the DPDP framework · personal data breach intimation under Rule 7 · handling Data Principal rights requests · Data Fiduciary, Data Processor or both · children’s data and verifiable parental consent.
Law stated as updated till October 2026.
Disclaimer: The content/information published on the website is only for general information of the user and shall not be construed as legal advice. While the Taxmann has exercised reasonable efforts to ensure the veracity of information/content published, Taxmann shall be under no liability in any manner whatsoever for incorrect information, if any.

Taxmann Publications has a dedicated in-house Research & Editorial Team. This team consists of a team of Chartered Accountants, Company Secretaries, and Lawyers. This team works under the guidance and supervision of editor-in-chief Mr Rakesh Bhargava.
The Research and Editorial Team is responsible for developing reliable and accurate content for the readers. The team follows the six-sigma approach to achieve the benchmark of zero error in its publications and research platforms. The team ensures that the following publication guidelines are thoroughly followed while developing the content:
- The statutory material is obtained only from the authorized and reliable sources
- All the latest developments in the judicial and legislative fields are covered
- Prepare the analytical write-ups on current, controversial, and important issues to help the readers to understand the concept and its implications
- Every content published by Taxmann is complete, accurate and lucid
- All evidence-based statements are supported with proper reference to Section, Circular No., Notification No. or citations
- The golden rules of grammar, style and consistency are thoroughly followed
- Font and size that’s easy to read and remain consistent across all imprint and digital publications are applied


CA | CS | CMA