Quick answer
Under Rule 15 of the DPDP Rules, 2025, personal data may be transferred outside India, subject to any requirements the Central Government specifies by general or special order about making it available to a foreign State or entities under its control. Section 16 of the Act lets the Government restrict transfers to notified countries, and stricter sectoral laws prevail. Rule 15 applies from 13 May 2027.
- DPDP has no general data localisation; transfers abroad are permitted by default.
- Section 16 uses a negative-list approach: the Government may restrict transfers to countries it notifies.
- Rule 15 lets the Government impose requirements, by general or special order, on making data available to foreign States or their agencies.
- Rule 13(4) can require Significant Data Fiduciaries to keep Government-specified data and its traffic data in India.
- Sector rules such as RBI's payment data storage circular still apply and can be stricter.
Who this is for: SaaS companies using foreign cloud regions, Indian subsidiaries of global groups, CTOs and cloud architects, AI teams calling overseas model APIs, Legal and procurement teams
Can personal data be transferred outside India under DPDP?
Yes. The DPDP framework permits cross-border transfers by default, with three layers of possible restriction.
Rule 15 of the DPDP Rules, 2025 states that any personal data processed by a Data Fiduciary under the Act "may be transferred outside the territory of India subject to the restriction that the Data Fiduciary shall meet such requirements as the Central Government may, by general or special order, specify in respect of making such personal data available to any foreign State, or to any person or entity under the control of or any agency of such a State."
Read carefully, Rule 15 does two things:
- It confirms that transfers are allowed.
- It reserves power for the Central Government to set conditions focused on foreign-State access: governments, their agencies, and entities they control. It is not a general adequacy or contract-clause regime.
The Act itself, in section 16, adds a negative list: the Central Government may, by notification, restrict transfer of personal data to countries or territories it specifies. Section 16 also preserves any Indian law that provides a higher degree of protection or restriction on transfers, so sectoral localisation continues.
Finally, Rule 13(4) allows data localisation for Significant Data Fiduciaries for categories the Government specifies.
Rule 15 comes into force on 13 May 2027. No restricted country list or Rule 15 order has been issued as of this guide; check the Gazette before relying on that.
The three layers of DPDP transfer restrictions
| Layer | Source | Who it binds | What it does | Status |
|---|---|---|---|---|
| Negative list | Section 16(1) of the Act | All Data Fiduciaries | Restricts transfers to countries notified by the Government | No list notified as of this guide |
| Foreign-State access requirements | Rule 15 | All Data Fiduciaries | Requirements, by general or special order, on making data available to foreign States or their agencies or controlled entities | No order issued as of this guide |
| SDF localisation | Rule 13(4) | Significant Data Fiduciaries only | Specified personal data and its flow-related traffic data must not leave India | Depends on SDF notification and specification |
| Stricter sectoral law | Section 16(2) of the Act | Regulated entities | Sector rules with higher restrictions continue to prevail | Live (for example RBI payment data) |
The structure is very different from GDPR's Chapter V. There is no adequacy decision process, no mandated standard contractual clauses, and no transfer impact assessment requirement in the DPDP Rules. Instead, the default is open and the Government intervenes by notification or order.
Rule 13(4) is worth reading closely: it covers "personal data specified by the Central Government, on the basis of the recommendations of a committee constituted by it", and extends the restriction to "the traffic data pertaining to its flow". Rule 13(5) says the committee includes MeitY officials and may include officials from other ministries. That traffic-data element matters for architectures that route metadata through global observability or CDN layers.
How sectoral localisation still applies
Section 16's preservation of stricter laws means DPDP does not override existing sectoral localisation. The most cited example is RBI.
RBI payment data
RBI's circular of 6 April 2018 on storage of payment system data requires system providers to store the entire payment data only in India. For the foreign leg of a transaction, data may be processed abroad but must be brought back and stored in India; RBI's June 2019 FAQs say data processed abroad should be deleted there within one business day or 24 hours, whichever is earlier.
Other sectors
- Insurance: IRDAI rules require certain records to be maintained in India.
- Telecom: licence conditions contain restrictions on transferring certain subscriber and network information abroad.
- Government data: public-sector workloads typically use MeitY-empanelled cloud services hosted in India.
Requirements in these sectors change through circulars and licence amendments, so check the latest circular from the relevant regulator rather than relying on a summary.
Practical effect
A fintech using an overseas analytics platform may be fine under DPDP Rule 15 and still breach RBI's payment data rules. Build the transfer register around the strictest applicable regime, not just DPDP.
How to map and control cross-border flows
Because restrictions can arrive by notification or order with little notice, the key engineering capability is knowing exactly where personal data goes.
Build a transfer register
For each flow, record:
- dataset and categories of personal data;
- source system and destination country or region;
- processor or recipient, and whether it is, or is controlled by, a foreign State or its agency;
- legal basis for the processing and any sectoral constraint;
- traffic data and logs that travel with it.
Common hidden transfers
- Overseas cloud regions, backups and disaster-recovery replicas.
- SaaS tools: CRM, support desks, analytics, product telemetry.
- Observability, logging and error-tracking platforms.
- LLM and AI model APIs, including prompt and completion logs retained by the vendor.
- Group-company shared services abroad.
Design for reversibility
- Prefer region-pinned deployments with India regions available.
- Keep data classification tags in schemas so specific categories can be geo-fenced if Rule 13(4) or section 16 is triggered.
- Contract for data location commitments and notice of any foreign-government access requests.
These controls also support Rule 6 safeguards and breach investigation under Rule 7, because you cannot report the location of a breach if you do not know where data lives.
What does foreign-State access mean in practice?
Rule 15's focus on "making such personal data available to any foreign State, or to any person or entity under the control of or any agency of such a State" is unusual. It targets access by foreign governments rather than transfers to private companies in general.
Until the Government issues an order, the content of these requirements is unknown. Reasonable preparation includes:
- Identify state-linked recipients. Flag vendors, partners or customers that are government agencies or state-owned or state-controlled entities abroad.
- Track foreign legal process. Ensure contracts with overseas processors require notice of government data requests where lawful, and a documented response process.
- Know your cloud provider's jurisdiction. Data stored with a provider in one country may still be reachable under another country's laws because of corporate control. Record both the storage location and the controlling entity.
- Prepare for general and special orders. Rule 15 allows a general order (applying broadly) or a special order (applying to particular fiduciaries or situations). Your register should let you answer a special order quickly.
This is distinct from Rule 23, under which the Indian Central Government may call for information from a Data Fiduciary for Seventh Schedule purposes. See government information requests.
Interplay with GDPR and transfers into India
Many Indian companies receive personal data from the EU as well as sending Indian data abroad. The two directions are governed differently.
- Data leaving India is governed by section 16, Rule 15, Rule 13(4) and sectoral rules.
- Data arriving from the EU is governed by GDPR Chapter V (Articles 44–49). India has no EU adequacy decision, so EU exporters typically use Standard Contractual Clauses under Commission Implementing Decision (EU) 2021/914 plus a transfer impact assessment.
For Indian companies processing non-Indian residents' data under a contract with a foreign person, section 17(1)(d) of the DPDP Act exempts that processing from most of Chapter II (except sections 8(1) and 8(5)), Chapter III and section 16. Security safeguards and the fiduciary's overall responsibility still apply.
See DPDP Act vs GDPR for a wider comparison.
What to do before 13 May 2027
- Build the transfer register covering all systems, processors and AI vendors.
- Check sectoral rules for RBI, IRDAI, telecom or government data and comply with the strictest.
- Tag data categories so specific categories can be geo-fenced quickly.
- Review processor contracts for location commitments, sub-processor notice and handling of foreign government requests.
- Assess SDF exposure. If you could be notified as an SDF, plan for Rule 13(4) localisation of specified data and its traffic data.
- Monitor the Gazette for section 16 notifications and Rule 15 orders.
- Update Rule 3 notices if your purposes or processors change.
Most companies will find the DPDP default permissive. The real work is visibility: being able to show where data is, and to move it if the Government acts.
Further reading on suhasbhairav.com
Before 13 May 2027
Compliance checklist
Create a cross-border transfer register
Record each flow's data categories, destination, recipient and legal basis.
Rule 15; Section 16
Identify foreign-State-linked recipients
Flag recipients that are foreign governments, their agencies or entities they control.
Rule 15
Apply sectoral localisation
Comply with RBI payment data storage and other sector rules that are stricter than DPDP.
Section 16(2)
Plan for SDF localisation
If you may be an SDF, design to keep specified data and its traffic data in India.
Rule 13(4)
Map AI and SaaS vendor transfers
Include LLM APIs, observability and support tools that receive personal data abroad.
Rule 15
Tighten processor contracts
Add data location commitments and notice of foreign government access requests where lawful.
Section 8(2); Rule 6(1)(f)
Monitor notifications and orders
Track the Gazette for section 16 country restrictions and Rule 15 orders.
Section 16(1); Rule 15
Key dates
DPDP Rules, 2025 published, including Rule 15
Rule 15 and section 16 transfer provisions apply
Answers
Frequently asked questions
Does the DPDP Act require data localisation?
Does the DPDP Act require data localisation?
No, not generally. The DPDP Act and Rules allow personal data to be transferred outside India by default. Localisation arises only under Rule 13(4) for Significant Data Fiduciaries and Government-specified data, if the Government restricts a country under section 16, or under stricter sectoral laws such as RBI's payment data rules.
What does Rule 15 of the DPDP Rules say?
What does Rule 15 of the DPDP Rules say?
Rule 15 allows personal data to be transferred outside India, subject to requirements the Central Government may specify by general or special order about making that data available to a foreign State, or to any person or entity controlled by or an agency of such a State. It applies from 13 May 2027.
Has India notified a blacklist of countries under DPDP?
Has India notified a blacklist of countries under DPDP?
No restricted country list had been notified under section 16 as of this guide. Section 16 lets the Central Government restrict transfers to specified countries by notification, so companies should monitor the Gazette and design systems that can stop flows to a particular country if needed.
Do I need standard contractual clauses for DPDP transfers?
Do I need standard contractual clauses for DPDP transfers?
The DPDP Act and Rules do not require standard contractual clauses or transfer impact assessments. However, section 8 still requires a valid contract with Data Processors and Rule 6 requires security safeguard clauses, so contracts with overseas processors remain essential.
Can I use a US or EU cloud region for Indian user data?
Can I use a US or EU cloud region for Indian user data?
Generally yes under DPDP, unless the destination is restricted under section 16, a Rule 15 order applies, you are an SDF handling Rule 13(4) specified data, or a sector rule such as RBI's payment data circular requires storage in India. Check sector rules first.
Does sending prompts to an overseas LLM API count as a transfer?
Does sending prompts to an overseas LLM API count as a transfer?
Yes, if the prompts contain personal data. Sending personal data to a model provider abroad is a cross-border transfer and a processor relationship. Record it in your transfer register, check sector restrictions, and ensure the contract covers security safeguards and data retention.
Legal references and sources
- Digital Personal Data Protection Rules, 2025 — Rule 15 (official text)
- Digital Personal Data Protection Act, 2023 — Section 16 (official text)
- Digital Personal Data Protection Rules, 2025 — Rule 13(4) (official text)
- RBI storage of payment system data (6 April 2018) — Circular and June 2019 FAQs (official text)
- DPDP Rules, 2025 full text ↗
- MeitY data protection framework ↗
- Reserve Bank of India ↗
- Gazette of India ↗
This guide explains the law for engineering and business teams. It is not legal advice; confirm how it applies to your organisation with qualified counsel, and check the Gazette for later notifications or amendments.
About the author

Suhas Bhairav
Systems architect and applied AI practitioner who designs production AI systems for Indian and global companies, with a focus on privacy-by-design under the DPDP Act and the EU AI Act.
Related guides
- DPDP Rules 2025Significant Data Fiduciary Obligations Under DPDP Rule 13Once notified, a Significant Data Fiduciary must run an annual DPIA and audit, report significant observations to the Board, vet its algorithms, and keep Government-specified data in India.
- DPDP Rules 2025DPDP Rule 23: Government Calls for Information and the Seventh ScheduleRule 23 lets the Central Government require Data Fiduciaries and intermediaries to furnish information for three Seventh Schedule purposes, sometimes with a gag on telling users.
- DPDP Act 2023DPDP Act vs GDPR: Side-by-Side Comparison for Tech TeamsA row-by-row comparison of India's DPDP Act 2023 and Rules 2025 with the EU GDPR: scope, lawful bases, children, rights, breach timelines, DPOs, transfers and penalties.
- DPDP Rules 2025DPDP Reasonable Security Safeguards Under Rule 6Rule 6 lists the minimum security safeguards every Data Fiduciary must take from 13 May 2027. Failure can attract a penalty of up to ₹250 crore, the highest in the DPDP Act.
- DPDP Act 2023Data Fiduciary vs Data Processor Under the DPDP ActWhoever decides why and how personal data is processed is the Data Fiduciary and carries the liability; the Data Processor acts on its behalf under contract.
- DPDP Rules 2025Algorithmic Due Diligence for Significant Data FiduciariesRule 13(3) requires Significant Data Fiduciaries to verify that technical measures, including algorithmic software, are not likely to pose a risk to Data Principals' rights. Here is what that means in practice.