EU & cross-borderUpdated 22 November 20269 min read

How Indian GCCs Can Deploy Sovereign AI for European Parents

How Indian global capability centres can build and run AI for European parent companies while respecting GDPR transfers, EU AI Act roles, DPDP s.17(1)(d) and Indian security directions.

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

Typical GDPR role of GCC
Processor or sub-processor to the parent
Transfer tool
Intra-group SCCs, Decision (EU) 2021/914
India adequacy
None
DPDP carve-out
s.17(1)(d) for non-Indian individuals' data
AI Act high-risk start
2 August 2026 (as adopted; Omnibus proposal pending)
CERT-In incident window
6 hours

Quick answer

An Indian GCC can build and operate AI for its European parent by keeping EU personal data and models in EU infrastructure the parent controls, accessing it from India only under intra-group SCCs, a transfer impact assessment and tight access controls. The parent is usually the AI Act provider or deployer. DPDP s.17(1)(d) limits Indian duties on EU data to security and accountability.

  • For a GCC, sovereign AI means EU data, models and keys stay under the European parent's control, with Indian teams working through governed access.
  • Access from India to EU personal data is a GDPR transfer; intra-group SCCs (often Module 3) and a transfer impact assessment are needed.
  • Define AI Act roles early: the parent typically provides or deploys the system, the GCC builds and operates it.
  • DPDP s.17(1)(d) limits Indian obligations on EU data to sections 8(1) and 8(5), but the GCC's own employee data needs full DPDP compliance from 13 May 2027.
  • CERT-In directions apply to the GCC's Indian systems, including 6-hour incident reporting and 180-day logs in India.

Who this is for: Heads of Indian GCCs, Group CIOs and CDOs in European companies, Enterprise architects, Group DPOs and privacy teams, AI platform teams in GCCs

What does sovereign AI mean for an Indian GCC?

"Sovereign AI" is a commercial term, not a legal one. For a European group with an Indian global capability centre (GCC), it usually means three things:

  1. Data sovereignty — EU personal and confidential data stays in EU infrastructure the group controls.
  2. Model sovereignty — the models (open-weight or fine-tuned) and their weights run in environments the group controls, not only behind a third-party API.
  3. Operational control — the group decides who can access data, models and keys, and can prove it to regulators and works councils.

The Indian GCC's role in this setup is to build, operate and improve the AI platform and applications, while the parent keeps legal control. Done well, this lets the group use Indian engineering capacity without moving the data estate to India.

The legal frame

LawWhat it governs
GDPREU personal data, transfers to and access from India
EU AI ActAI systems placed on the EU market or whose output is used in the EU
DPDP ActPersonal data processed in India, with s.17(1)(d) carve-out for foreign individuals' data
CERT-In directionsCyber incidents and logs for the GCC's Indian systems

The rest of this guide shows how to design for all four.

A reference architecture

EU side (parent-controlled)

  • Data plane in EU regions: source systems, data lake, vector stores, feature stores.
  • Model hosting in EU: self-hosted open-weight models or EU-region managed endpoints with contractual EU processing.
  • Key management in EU under the parent's control.
  • LLM gateway in EU enforcing policy: routing, redaction, logging, rate limits.

India side (GCC)

  • Engineering environment with code, pipelines and synthetic or masked datasets.
  • Access to EU production only via an EU-hosted bastion or virtual desktop, with session recording.
  • Observability limited to metrics and redacted traces by default.

Access patterns

TaskDefault access from India
Building pipelines and appsSynthetic or masked data in India; no production personal data
Model evaluationEvaluation sets curated and pseudonymised in EU
Production supportJust-in-time access, ticket-linked, recorded
Incident responseBreak-glass with group DPO notification
Fine-tuning on EU dataJobs run in EU; GCC submits code, not data

This keeps the volume and sensitivity of transfers low, which strengthens the group's transfer impact assessment. Hosting options such as an EU provider are discussed in EU data residency on Hetzner from India.

GDPR: intra-group transfers and contracts

India has no EU adequacy decision, so any access by GCC staff to EU personal data is a restricted transfer under Chapter V.

Contract set-up

  • Parent (controller) → GCC (processor): Article 28 DPA plus SCC Module 2.
  • EU group processor entity → GCC (sub-processor): Module 3, where an EU IT subsidiary sits between business units and the GCC.
  • Some groups use binding corporate rules; if yours does, check that the GCC and its AI activities are covered.

Transfer impact assessment

The group exporter assesses Indian law and practice. Inputs from the GCC:

  • the access model above, showing what personal data is actually visible in India;
  • encryption and EU-held keys;
  • Indian government access powers, such as DPDP Rule 23 and the Seventh Schedule, IT Act powers and CERT-In directions, described accurately;
  • the GCC's process for handling any government request.

Other GDPR duties the GCC supports

  • Article 30 records of processing for the parent;
  • Article 32 security;
  • Article 35 DPIAs for high-risk processing such as employee monitoring or profiling;
  • Breach support so the controller can notify within 72 hours under Article 33.

See GDPR for Indian IT services firms for the processor checklist.

EU AI Act: who is provider and deployer?

AI Act obligations follow roles, and GCC set-ups can blur them.

ScenarioLikely providerLikely deployer
GCC builds an internal HR screening tool used by the parent's EU HR teamParent (system developed for it and put into service under its name)Parent's EU HR function
GCC builds a customer-facing chatbot the parent launches in the EUParentParent
GCC licenses its own AI product to third parties in the EUGCC entityThe third parties
GCC uses an AI system to process EU operations (e.g., invoice triage) whose outputs are used in the EUVendor of the systemGCC and/or parent

Write roles into intra-group agreements. Then allocate the work: even when the parent is provider, the GCC will produce much of the technical documentation, logging and testing.

Watch the high-risk categories

Annex III includes employment uses (recruitment, selection, promotion, termination, task allocation, monitoring) and credit scoring of individuals. GCCs often build exactly these tools for HR and finance. High-risk obligations apply from 2 August 2026 under the Regulation as adopted; the November 2025 Digital Omnibus proposal would delay some high-risk deadlines — check its adoption status. See high-risk rules for HR-tech and credit scoring.

Transparency

Customer-facing chatbots and generated content need Article 50 measures from 2 August 2026.

Indian law on the GCC's side

DPDP Act

  • EU individuals' data processed by the GCC under contract with the foreign parent: section 17(1)(d) disapplies most of Chapter II (except sections 8(1) and 8(5)), Chapter III and section 16. Reasonable security safeguards remain mandatory.
  • Indian individuals' data — above all the GCC's own employees — needs full DPDP compliance from 13 May 2027: Rule 3 notice, Rule 6 security, Rule 7 breach intimation, Rule 8(3) one-year retention, Rule 14 rights. Employment purposes are a section 7 legitimate use, but they do not remove security, breach or retention duties. See DPDP for HR and employee data.
  • Employee monitoring by AI (productivity analytics, copilots reading mail) needs careful scoping; see enterprise AI copilots and employee data.

CERT-In

The GCC's Indian systems are subject to CERT-In's April 2022 directions: report specified incidents within 6 hours, keep ICT logs for a rolling 180 days within India, synchronise clocks. Logs from the India-side bastion and engineering systems need Indian retention; EU-side logs stay in the EU.

India AI governance

MeitY's AI governance guidelines (November 2025) are principle-based and do not add binding obligations, but they are useful framing for GCC AI policies. See India AI governance guidelines explained.

Operating model and common mistakes

Governance

  • A group AI council with the GCC represented, approving use cases and risk tiers.
  • A single AI inventory shared across the group, recording role (provider/deployer), risk tier, data categories and hosting.
  • Group DPO sign-off for any use case that moves personal data access to India.

Engineering standards

  • Synthetic and masked data by default in India.
  • Infrastructure as code that pins EU regions and blocks non-EU replication.
  • Gateway-enforced redaction on any prompt leaving the EU boundary.
  • Evaluation harnesses that run in the EU and return only aggregate metrics.

Common mistakes

  • Copying production EU data to Indian development environments "temporarily".
  • Using a third-party model API with data processing outside the EU while claiming sovereignty.
  • Leaving AI Act roles undefined in intra-group agreements.
  • Applying the s.17(1)(d) carve-out to Indian employees' data — it covers only individuals not within India.
  • Keeping CERT-In logs only in the EU for Indian systems.

First 90 days

Inventory AI use cases, fix the access model, sign or refresh intra-group SCCs, produce the TIA input, assign AI Act roles, and confirm DPDP readiness for the GCC's own employees before 13 May 2027.

Further reading on suhasbhairav.com

Before 13 May 2027

Compliance checklist

  1. Define sovereignty requirements

    Agree with the parent which data, models and keys must remain in EU control.

    GDPR Ch. V

  2. Sign intra-group DPAs and SCCs

    Use Module 2 or Module 3 depending on the group structure.

    Decision (EU) 2021/914

  3. Minimise access from India

    Use synthetic data, masked views and just-in-time access to EU production.

    GDPR Art. 32

  4. Contribute to the TIA

    Provide access model, encryption, Indian law and request-handling details.

    GDPR Ch. V; Schrems II

  5. Assign AI Act roles

    Record provider and deployer for each AI system in intra-group agreements.

    AI Act Art. 2

  6. Screen for Annex III uses

    Flag HR and credit scoring tools as potential high-risk systems.

    AI Act Annex III

  7. Keep Indian logs in India

    Retain India-side ICT logs for 180 days within Indian jurisdiction.

    CERT-In Directions, 28 Apr 2022

  8. Comply with DPDP for employees

    Prepare notices, security, breach and retention controls for Indian staff data.

    DPDP Rules 3, 6, 7, 8(3)

  9. Maintain a group AI inventory

    Track every AI use case with hosting, role, risk tier and data categories.

    Group AI governance

Key dates

  1. EU AI Act Article 50 and Annex III high-risk rules apply (as adopted)

  2. DPDP core obligations apply to GCC employee and Indian data

Answers

Frequently asked questions

Can an Indian GCC access EU personal data for AI projects?

Yes, with safeguards. Access from India is a GDPR transfer, so the group needs SCCs or another Chapter V mechanism, a transfer impact assessment and supplementary measures such as encryption, masking and just-in-time access. Minimise what is visible in India.

Who is the AI Act provider when a GCC builds AI for its parent?

Usually the parent, if the system is developed for it and placed on the market or put into service under its name. The GCC is then a builder and operator within the group. If the GCC markets the system under its own name to others, it becomes a provider.

Does DPDP apply to EU data handled by an Indian GCC?

Only partly. Section 17(1)(d) disapplies most DPDP duties for data of individuals not within India processed under a contract with a foreign person. Sections 8(1) and 8(5) still apply, so the GCC must keep reasonable security safeguards and remains accountable.

What is sovereign AI for a European company with an Indian GCC?

Keeping EU data, model weights and encryption keys under the group's control in EU infrastructure, while Indian teams build and operate the platform through governed access. It reduces transfer exposure and supports regulatory and works council expectations.

Do CERT-In rules apply to a GCC?

Yes, to its Indian ICT systems. CERT-In's April 2022 directions require reporting specified cyber incidents within 6 hours, keeping logs for a rolling 180 days within Indian jurisdiction and synchronising clocks. Plan incident response to cover CERT-In, GDPR and DPDP together.

Can a GCC fine-tune models on EU data in India?

It is better to run fine-tuning jobs in EU infrastructure and have the GCC submit code and configuration rather than move training data to India. If data must be accessed from India, it is a transfer requiring SCCs, a TIA and strong safeguards.

Legal references and sources

  • GDPR, Regulation (EU) 2016/679 — Article 28; Chapter V (official text)
  • Commission Implementing Decision (EU) 2021/914 — Standard Contractual Clauses (official text)
  • EU AI Act, Regulation (EU) 2024/1689 — Articles 2 and 50; Annex III (official text)
  • Digital Personal Data Protection Act, 2023 — Section 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.