Quick answer
An Indian AI SaaS company selling to EU customers usually faces three regimes: GDPR (Regulation (EU) 2016/679), because it processes EU personal data, typically as a processor needing an Article 28 DPA and SCCs; the EU AI Act (Regulation (EU) 2024/1689), because its system's output is used in the EU; and India's DPDP Act for Indian data, with core duties from 13 May 2027.
- GDPR reaches Indian SaaS firms through Article 3(2) when they offer services to, or monitor, people in the EU, and through processor contracts with EU customers.
- Most B2B AI SaaS vendors act as GDPR processors and must sign an Article 28 DPA and SCCs, because India has no EU adequacy decision.
- The EU AI Act applies to non-EU providers placing AI systems on the EU market or whose output is used in the EU.
- Article 50 transparency and Annex III high-risk rules apply from 2 August 2026 under the Act as adopted; a Digital Omnibus proposal may change some high-risk dates.
- DPDP section 17(1)(d) disapplies most DPDP duties for foreign clients' data processed under contract in India, but security under section 8(5) still applies.
Who this is for: Indian AI SaaS founders, CTOs and heads of security, Sales and legal teams negotiating EU contracts, Data Protection Officers and privacy leads, Product managers for GenAI features
Which laws apply when you sell AI SaaS to Europe?
An Indian AI SaaS company with EU customers usually sits under three legal regimes at once.
| Regime | Why it applies | Core duties |
|---|---|---|
| GDPR (Reg. (EU) 2016/679) | You process personal data of people in the EU, as processor for customers or controller for your own users | Processor contract, security, breach support, transfers, records |
| EU AI Act (Reg. (EU) 2024/1689) | You place an AI system on the EU market, or its output is used in the EU | Depends on role and risk: transparency, high-risk obligations, GPAI duties |
| DPDP Act, 2023 (India) | You process personal data in India | Indian users' data: full duties from 13 May 2027; foreign clients' data under contract: limited duties under s.17(1)(d) |
The commercial reality is that EU enterprise buyers will test all three in procurement. Expect a security questionnaire, a data processing agreement (DPA), Standard Contractual Clauses (SCCs), a sub-processor list and, increasingly, questions about your AI Act role.
This guide walks through each layer and how they connect. For narrower deep dives, see DPA and SCCs for Indian vendors and the EU AI Act for Indian companies.
GDPR: scope, roles and what customers will ask for
Scope
GDPR Article 3(2) applies to organisations outside the EU that offer goods or services to people in the EU or monitor their behaviour in the EU. Separately, when an EU customer uses your SaaS to process its own customers' or employees' data, you are its processor and GDPR obligations reach you through the contract.
Controller or processor?
- Processor for customer data you process on the customer's instructions (documents uploaded, chat transcripts, CRM records).
- Controller for your own account, billing, marketing and product analytics data, and for any use of customer data for your own purposes, such as training your models.
That second point is critical for AI vendors: using customer data to improve your models can make you a controller for that processing, which customers will scrutinise.
What you will need
- Article 28 DPA with mandatory processor terms.
- Article 30 records of processing.
- Article 32 security appropriate to risk.
- Breach support so the customer can notify its supervisory authority within 72 hours where required (Art. 33) and individuals where high risk (Art. 34).
- Article 27 EU representative if you are a controller in scope of Article 3(2) and no exemption applies.
- Chapter V transfer mechanism — usually SCCs.
Getting EU data to India lawfully
India has no EU adequacy decision, so EU personal data processed in or accessed from India is a restricted transfer under GDPR Chapter V (Articles 44–49).
The standard tool: SCCs
The Commission's SCCs (Implementing Decision (EU) 2021/914) have four modules:
| Module | Exporter → Importer | Typical SaaS case |
|---|---|---|
| 1 | Controller → Controller | Exchange of data where both decide purposes |
| 2 | Controller → Processor | EU customer → Indian SaaS vendor (most common) |
| 3 | Processor → Processor | EU-based vendor → Indian sub-processor |
| 4 | Processor → Controller | EU-based processor sending data back to its controller in India |
Transfer impact assessment
After Schrems II (CJEU C-311/18, July 2020), exporters are expected to assess whether the importer's country's laws undermine the SCCs and to add supplementary measures if needed. For India, the assessment typically considers government access powers — DPDP Rule 23 and the Seventh Schedule allow the Central Government to call for information — and documents mitigations such as encryption with keys held in the EU, minimisation and transparency about requests.
Architecture choice
Hosting in an EU region reduces exposure but does not remove Chapter V if engineers in India can access the data. See EU data residency on Hetzner from India.
EU AI Act: your role and your deadlines
Article 2 applies the AI Act to providers placing AI systems or GPAI models on the EU market regardless of where they are established, to deployers in the EU, and to providers and deployers outside the EU where the output is used in the EU. An Indian SaaS vendor selling to EU customers is usually a provider of an AI system.
Key dates (as adopted)
| Date | What applies |
|---|---|
| 2 Feb 2025 | Prohibited practices; AI literacy |
| 2 Aug 2025 | GPAI model obligations |
| 2 Aug 2026 | Most remaining rules, including Article 50 transparency and Annex III high-risk |
| 2 Aug 2027 | High-risk AI embedded in Annex I regulated products |
In November 2025 the Commission proposed a Digital Omnibus that would delay some high-risk deadlines. Check its adoption status on EUR-Lex and the Commission's AI Act page before relying on a changed date.
What typically applies to AI SaaS
- Article 50 if your product chats with users or generates content: AI disclosure and machine-readable marking. See the Article 50 checklist.
- Annex III high-risk if your product is used for recruitment, worker management or credit scoring of individuals. See high-risk rules for HR-tech and credit scoring.
- Authorised representative in the EU if you provide a high-risk system or a GPAI model.
How DPDP applies to your EU business
Your Indian entity is a Data Fiduciary or Data Processor under the DPDP Act for personal data processed in India. For EU customers' data, a specific exemption matters.
Section 17(1)(d) says that for personal data of Data Principals not within India, processed in India under a contract with a person outside India, most of Chapter II (except sections 8(1) and 8(5)), Chapter III and section 16 do not apply. In practice:
- consent, notice, rights and cross-border provisions of DPDP do not apply to that EU data;
- section 8(5) reasonable security safeguards still apply, and so does section 8(1) responsibility;
- your GDPR obligations to the EU customer remain fully in force.
For Indian users and Indian employees, the full DPDP regime applies from 13 May 2027: Rule 3 notice, Rule 6 security, Rule 7 breach intimation, Rule 8(3) one-year log retention and Rule 14 rights.
Practical consequence
Run one security programme that meets the stricter of GDPR Article 32 and DPDP Rule 6, and maintain separate privacy notices and rights workflows for EU and Indian individuals. More: DPDP vs GDPR.
The EU sales compliance pack
Enterprise buyers move faster when you hand them a complete pack. Build these once and maintain them.
- DPA aligned to GDPR Article 28, with SCC Module 2 incorporated (and Module 3 for your own sub-processors where relevant).
- Sub-processor list with locations, purposes and a change-notice mechanism.
- Transfer impact assessment summary covering access from India and supplementary measures.
- Security overview mapping controls to GDPR Article 32 and to recognised frameworks you hold.
- AI Act statement: your role (provider, deployer), the risk category of the product, Article 50 measures, and whether any feature falls under Annex III.
- Model and data use statement: whether customer data trains your models (default should be no), retention periods, and zero-retention options for third-party model APIs.
- Incident response summary: how fast you notify customers, so they can meet the Art. 33 72-hour deadline.
- EU representative details if Article 27 applies.
Common mistakes
- Using customer data for model training under a processor DPA.
- Forgetting that Indian support engineers' access is a transfer.
- Calling a product "not AI" to avoid AI Act questions when it uses ML or LLMs.
- Copying a US-centric DPA without SCCs for India.
Further reading on suhasbhairav.com
- BlogGDPR for GenAI in Enterprise: Compliance by Design
- BlogPMs role in EU AI Act compliance for enterprise AI programs
- BlogSOC 2 for AI startups: practical governance
- AI LabBatuk Audit, GDPR, SOC 2, and ISO 27001 Readiness
- AI SkillsCursor Rules Template: GDPR Risk Assessment Tools from Website Forms and Data Flows
Before 13 May 2027
Compliance checklist
Determine GDPR roles
Map where you are processor and where you are controller, especially for model training.
GDPR Art. 28
Sign Article 28 DPAs
Use a DPA with mandatory processor terms for every EU customer.
GDPR Art. 28
Execute SCCs
Incorporate Module 2 for EU customers and Module 3 for sub-processors where needed.
Decision (EU) 2021/914
Complete a transfer impact assessment
Document access from India, Indian law on government access and supplementary measures.
GDPR Ch. V; Schrems II
Appoint an EU representative if required
Check Article 27 where you are a controller under Article 3(2).
GDPR Art. 27
Classify your AI Act role and risk
Record whether you are a provider, whether Article 50 applies and whether any use is Annex III.
AI Act Art. 2, 50; Annex III
Implement Article 50 measures
Add AI interaction disclosure and machine-readable output marking.
AI Act Art. 50
Track the Digital Omnibus
Check adoption status before relying on any changed AI Act deadline.
AI Act; Digital Omnibus proposal
Apply DPDP security to EU data
Meet section 8(5) safeguards even where s.17(1)(d) disapplies other duties.
DPDP s.17(1)(d), s.8(5)
Key dates
EU AI Act enters into force
AI Act prohibited practices and AI literacy apply
AI Act GPAI model obligations apply
AI Act Article 50 and Annex III high-risk rules apply (as adopted)
DPDP core obligations apply in India
AI Act rules for Annex I product-embedded high-risk AI apply
Answers
Frequently asked questions
Does GDPR apply to an Indian SaaS company?
Does GDPR apply to an Indian SaaS company?
Yes, if it offers services to people in the EU or monitors their behaviour (Article 3(2)), and in practice whenever it processes EU customers' personal data as a processor under contract. Most Indian B2B SaaS firms with EU clients will need an Article 28 DPA and Standard Contractual Clauses.
Do I need SCCs to serve EU customers from India?
Do I need SCCs to serve EU customers from India?
Usually yes. India has no EU adequacy decision, so transferring EU personal data to India, including remote access from India, needs a Chapter V mechanism. SCCs under Decision (EU) 2021/914, with a transfer impact assessment, are the standard tool for SaaS vendors.
Does the EU AI Act apply to Indian startups?
Does the EU AI Act apply to Indian startups?
Yes, if they place AI systems or GPAI models on the EU market, or if their AI system's output is used in the EU. Location of the company does not matter. Obligations depend on role and risk: many AI SaaS products face Article 50 transparency; some HR and credit tools are high-risk.
Do I need an EU representative?
Do I need an EU representative?
Under GDPR Article 27, a non-EU controller covered by Article 3(2) generally needs one unless an exemption applies. Under the AI Act, non-EU providers of high-risk AI systems and GPAI models need an EU authorised representative. Pure processors should still check both.
Can I train my models on EU customer data?
Can I train my models on EU customer data?
Only with a clear legal basis and the customer's agreement. Under a processor DPA you may process only on the customer's instructions; using data to train your own models makes you a controller for that purpose. Most enterprise buyers expect training to be off by default.
Does DPDP apply to EU customer data processed in India?
Does DPDP apply to EU customer data processed in India?
Mostly not. Section 17(1)(d) disapplies most of Chapter II, Chapter III and section 16 for non-Indian individuals' data processed in India under a contract with a foreign person. Section 8(5) reasonable security safeguards and section 8(1) still apply.
When should I involve EU counsel?
When should I involve EU counsel?
When a product may fall under Annex III high-risk categories, when you need to decide on an EU representative, when negotiating non-standard DPAs, and when a breach affects EU personal data. Those decisions carry fines up to €20m or 4% under GDPR and up to €15m or 3% under the AI Act.
Legal references and sources
- GDPR, Regulation (EU) 2016/679 — Articles 3(2), 27, 28, 44–49 (official text)
- EU AI Act, Regulation (EU) 2024/1689 — Articles 2 and 50; Annex III (official text)
- Commission Implementing Decision (EU) 2021/914 — Standard Contractual Clauses (official text)
- Digital Personal Data Protection Act, 2023 — Section 17(1)(d) (official text)
- GDPR on EUR-Lex ↗
- EU AI Act on EUR-Lex ↗
- EU Standard Contractual Clauses ↗
- EU AI Act overview, European Commission ↗
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
- EU & cross-borderEU AI Act for Indian Companies: Does It Apply to You?A scoping guide for Indian companies: when Regulation (EU) 2024/1689 reaches you, which role you play, which obligations and dates apply, and what the Digital Omnibus proposal might change.
- EU & cross-borderDPA & SCCs Explained for Indian Vendors Selling to EU ClientsWhat a DPA and Standard Contractual Clauses are, which SCC module an Indian vendor signs, how the annexes and transfer impact assessment work, and how they fit with DPDP processor contracts.
- EU & cross-borderDoes India Have GDPR Adequacy? What It Means for Data TransfersIndia 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.
- EU & cross-borderAI Act Article 50 Checklist for Indian GenAI StartupsA task-level checklist for Indian GenAI startups to meet EU AI Act Article 50 transparency duties: chatbot disclosure, machine-readable marking, deepfake and public-interest text disclosure.
- 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.
- EU & cross-borderEU Data Residency on a Budget: Hosting AI on Hetzner From IndiaArchitecture guidance for Indian teams hosting AI for EU customers on Hetzner's German and Finnish data centres: region choice, encryption, why access from India is still a transfer, DPA and SCCs.