EU & cross-borderUpdated 22 November 20268 min read

Does India Have GDPR Adequacy? What It Means for Data Transfers

India has no EU adequacy decision. What that means for transfers of EU personal data to India, the tools that fill the gap, whether DPDP changes the picture, and how to design around it.

By Suhas Bhairav · Reviewed against the DPDP Rules, 2025 (G.S.R. 846(E), 13 Nov 2025)

EU adequacy for India
None
Adequacy legal basis
GDPR Article 45
Main alternative
SCCs, Decision (EU) 2021/914 (Art. 46)
Assessment expected
Transfer impact assessment after Schrems II (C-311/18, July 2020)
Derogations
GDPR Article 49 (limited use)
DPDP core obligations
From 13 May 2027
GDPR max fine
€20m or 4% of worldwide turnover

Quick answer

No. India does not have an EU adequacy decision under GDPR Article 45, so transfers of EU personal data to India — including remote access from India — need another Chapter V mechanism, usually Standard Contractual Clauses under Decision (EU) 2021/914 plus a transfer impact assessment. The DPDP Act, with core duties from 13 May 2027, does not by itself confer adequacy.

  • India has no EU adequacy decision, so EU-to-India transfers are restricted transfers under GDPR Chapter V.
  • SCCs under Decision (EU) 2021/914, with a transfer impact assessment, are the usual tool; binding corporate rules suit some groups.
  • Article 49 derogations such as explicit consent are for occasional, specific transfers, not routine outsourcing.
  • The DPDP Act creates a national data protection framework, but adequacy requires a European Commission decision; none has been adopted.
  • Remote access from India to EU-hosted data still counts as a transfer, so EU hosting alone does not solve the problem.

Who this is for: Indian companies receiving EU personal data, EU companies outsourcing to India, Privacy and legal teams, CTOs designing cross-border architectures, Policy and public affairs teams

Does India have GDPR adequacy?

No. The European Commission has not adopted an adequacy decision for India under GDPR Article 45. An adequacy decision is the Commission's formal finding that a country ensures an essentially equivalent level of protection; with one, personal data can flow from the EU without further safeguards.

Without it, every transfer of EU personal data to India is a restricted transfer under Chapter V (Articles 44–49). That includes:

  • sending EU customer data to servers in India;
  • Indian staff viewing EU personal data hosted anywhere;
  • Indian sub-processors receiving data from EU processors.

Restricted does not mean prohibited. It means the exporter must use one of the other Chapter V routes.

RouteArticleTypical use for India
Adequacy decision45Not available for India
Standard Contractual Clauses46Default for vendors, outsourcing, SaaS
Binding corporate rules46–47Multinational groups with approved BCRs
Other Art. 46 safeguards (codes, certifications)46Rare in practice
Derogations (e.g., explicit consent, contract necessity)49Occasional, specific transfers only

Check the Commission's adequacy list on official EU sources for any change; adequacy decisions are published in the Official Journal and available via EUR-Lex.

Does the DPDP Act change the position?

The DPDP Act, 2023 and the DPDP Rules, 2025 give India a comprehensive data protection framework: a Data Protection Board, penalties up to ₹250 crore, breach notification, rights and security obligations. Core fiduciary duties apply from 13 May 2027.

That is relevant to adequacy, but it is not adequacy. An adequacy decision requires:

  1. a Commission assessment of the country's law and practice, including rules on government access to data, oversight and redress;
  2. an opinion from the European Data Protection Board;
  3. a formal decision adopted through EU procedures.

Features any assessment would look at

  • Scope and exemptions. DPDP section 17 contains broad exemptions, including for notified State instrumentalities (s.17(2)(a)) and, notably, section 17(1)(d), which disapplies most DPDP duties for foreign individuals' data processed in India under contract with a foreign person. For EU data, that means DPDP protections are narrower than for Indian data.
  • Government access. Rule 23 and the Seventh Schedule allow the Central Government to call for information for specified purposes, including sovereignty and security of the State.
  • Independence and redress. The Board's structure (Rules 17–21) and appeals to TDSAT.
  • Onward transfers. Section 16's negative-list approach.

Whether, when or how India might seek or obtain adequacy is a policy question. Do not plan on it. Plan on SCCs.

SCCs in practice for India

Standard Contractual Clauses are in Commission Implementing Decision (EU) 2021/914. Four modules cover controller and processor combinations; most Indian vendors sign Module 2 (controller to processor).

What makes SCCs work for India

  1. Correct module and annexes. Annex I describes the transfer; Annex II lists technical and organisational measures; Annex III lists sub-processors.
  2. Transfer impact assessment (TIA). Since Schrems II (CJEU C-311/18, July 2020), the exporter must assess whether the destination's law and practice undermine the clauses.
  3. Supplementary measures where the TIA identifies risk: encryption with keys held outside India, pseudonymisation, minimisation, access controls, and contractual commitments on handling government requests.

What a TIA for India typically covers

  • the categories and sensitivity of data and who in India can access it;
  • Indian legal powers enabling government access (DPDP Rule 23, IT Act provisions, CERT-In directions) and their conditions;
  • the importer's experience of requests and policies for responding;
  • technical measures that limit what could be disclosed.

Indian vendors can make deals faster by preparing a standard TIA input. See DPA and SCCs explained.

Derogations and binding corporate rules

Article 49 derogations

GDPR Article 49 allows transfers without adequacy or Article 46 safeguards in specific situations, including the data subject's explicit consent after being informed of the risks, transfers necessary for a contract with the data subject, and transfers necessary for legal claims.

They are interpreted narrowly and are meant for occasional transfers. They are not a basis for routine outsourcing, hosting or continuous support from India. For example:

  • An EU traveller booking an Indian hotel: contract necessity can cover sending her booking details.
  • An EU bank outsourcing customer service to India: derogations do not fit; use SCCs.

Binding corporate rules

BCRs are internal codes approved by EU supervisory authorities that allow intra-group transfers. Large multinationals with Indian GCCs or delivery centres sometimes rely on them. They take time to obtain and maintain, and must cover the specific entities and processing. If your group has BCRs, check that the Indian entity and its AI activities are in scope.

For GCC-specific design, see sovereign AI for Indian GCCs.

Designing around the lack of adequacy

Many Indian companies combine contracts with architecture to reduce transfer risk.

ApproachEffect on transfersTrade-off
EU hosting, India access via controlsData at rest in EU; access still a transferStrong TIA position; access friction for engineers
Encryption with EU-held keysIndian staff see ciphertext unless authorisedHarder for support and debugging
Pseudonymise before transferData in India less identifyingRe-identification keys must stay in EU
Synthetic data for developmentNo personal data in India for most workSynthetic data quality
EU subsidiary as contracting partyClear EU controller/processor chainCorporate overhead; still Module 3 to India

Key principle

Remote access counts. An EU-only storage claim does not remove Chapter V if staff in India can read the data. Design the access model first. See EU data residency on Hetzner from India.

Do not forget Indian data going the other way

Indian personal data sent to the EU is governed by DPDP section 16 (a negative list, with no restriction notified as of this writing) and Rule 15 from 13 May 2027, plus sectoral localisation such as RBI's payment data rule. See DPDP cross-border data transfer.

Common mistakes

  • Assuming DPDP gives adequacy. It does not; only a Commission decision does.
  • Relying on consent for bulk outsourcing. Article 49 explicit consent is for occasional transfers and is withdrawable.
  • Skipping the TIA. Signing SCCs without assessing Indian law leaves the exporter exposed.
  • Ignoring remote access. Support, DevOps and data science access from India is a transfer.
  • Overstating Indian protections for EU data. Section 17(1)(d) means most DPDP duties do not apply to foreign clients' data processed in India; only sections 8(1) and 8(5) do. Be accurate in TIA inputs.
  • Forgetting sub-processors. A US model API used by your Indian team is another transfer chain.

What to do now

  1. Inventory EU data flows to India, including access.
  2. Put SCCs in place with the right modules.
  3. Prepare a TIA input describing Indian law accurately.
  4. Implement supplementary measures, starting with access control and encryption.
  5. Re-check periodically for any adequacy developments, without planning on them.

For a full EU sales view, see selling AI SaaS to Europe from India.

Further reading on suhasbhairav.com

Before 13 May 2027

Compliance checklist

  1. Map EU-to-India data flows

    Include storage, processing and every form of remote access from India.

    GDPR Art. 44

  2. Sign SCCs

    Use the correct module of Decision (EU) 2021/914 with complete annexes.

    GDPR Art. 46

  3. Complete a TIA

    Assess Indian law and practice on government access and document conclusions.

    GDPR Ch. V; Schrems II

  4. Add supplementary measures

    Apply encryption with EU-held keys, pseudonymisation and access controls.

    GDPR Art. 32, 46

  5. Limit Article 49 use

    Reserve derogations for occasional, specific transfers.

    GDPR Art. 49

  6. Describe DPDP accurately

    Note s.17(1)(d) limits for foreign data in TIA inputs.

    DPDP s.17(1)(d)

  7. Check BCR coverage

    If relying on BCRs, confirm the Indian entity and AI processing are in scope.

    GDPR Art. 47

Key dates

  1. DPDP core obligations apply in India (no effect on EU adequacy status by itself)

Answers

Frequently asked questions

Does India have an adequacy decision under GDPR?

No. The European Commission has not adopted an adequacy decision for India under GDPR Article 45. Transfers of EU personal data to India need another Chapter V mechanism, usually Standard Contractual Clauses with a transfer impact assessment, or binding corporate rules for groups.

Will the DPDP Act make India GDPR adequate?

Not automatically. Adequacy requires a European Commission decision after assessing India's law and practice, including government access and redress, and an EDPB opinion. The DPDP Act is a relevant development, but no adequacy decision has been adopted. Plan on SCCs.

How do companies transfer EU data to India without adequacy?

Mostly with Standard Contractual Clauses under Decision (EU) 2021/914, completed annexes and a transfer impact assessment, plus supplementary measures such as encryption and access control. Multinationals may use binding corporate rules. Article 49 derogations cover only occasional transfers.

Is remote access from India a transfer without adequacy?

Yes. Making EU personal data accessible to people in India is treated as a transfer, even if the data stays on EU servers. It needs SCCs or another Chapter V tool and should be addressed in the transfer impact assessment.

Can EU users consent to their data going to India?

Explicit consent under Article 49 can justify occasional, specific transfers after the person is informed of the risks. It is not suitable for routine or large-scale outsourcing, and consent can be withdrawn. SCCs are the standard route for ongoing processing.

Does DPDP protect EU data processed in India?

Only partly. Section 17(1)(d) disapplies most DPDP provisions for personal data of individuals not within India processed under a contract with a foreign person. Sections 8(1) and 8(5) still apply, so security safeguards and accountability remain.

Legal references and sources

  • GDPR, Regulation (EU) 2016/679 — Articles 44–49 (Chapter V) (official text)
  • Commission Implementing Decision (EU) 2021/914 — Standard Contractual Clauses (official text)
  • Digital Personal Data Protection Act, 2023 — Sections 16 and 17(1)(d) (official text)

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

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.