GCC AI Governance: Cross-Border Compliance for India
There are more than 1,800 Global Capability Centers operating in India right now. They employ over 2 million professionals and generated $64.6 billion in revenue in FY24. Zinnov/NASSCOM Eighty percent of newly established GCCs are prioritizing AI and machine learning capabilities. Gratuityconsulting And as of 2026, every one of them faces the same problem.
What GCCs Actually Face: The Three-Framework Challenge
Most GCCs in India serve parent companies headquartered in the US, UK, or EU. Their AI systems process data from Indian users, European data subjects, and often North American customers. That means a single AI deployment can trigger obligations under Indian law, EU regulation, and the parent company's home jurisdiction at the same time.
The challenge is not just volume. It is contradiction. India's DPDPA permits cross-border data transfers by default, with government power to restrict specific countries by notification (a blocklist approach). The GDPR requires Standard Contractual Clauses or adequacy decisions for transfers outside the EU. The EU AI Act adds a layer of AI-specific obligations that neither data protection law covers.
The 3-Framework Compliance Challenge
Where DPDPA, GDPR, and the EU AI Act overlap for GCCs operating in India
DPDPA: India's Data Protection Backbone
The Digital Personal Data Protection Act received Presidential assent on 11 August 2023 as Act No. 22 of 2023. MeitY The DPDP Rules were notified on 14 November 2025, PIB establishing the implementation timeline.
Key obligations for GCCs
- Consent management. Every AI system processing personal data of Indian citizens must obtain clear, informed consent. Purpose limitation applies: data collected for one purpose cannot be reused for AI training without fresh consent.
- Data fiduciary duties. GCCs acting as data fiduciaries must implement reasonable security safeguards, ensure data accuracy, and delete data once the purpose is fulfilled.
- Cross-border transfers. The DPDPA allows transfers to countries not blacklisted by the central government, but the rules remain pending on which countries qualify. GCCs cannot assume blanket permission.
- Breach notification. Data fiduciaries must notify the Data Protection Board and affected individuals. Timelines are defined in the rules.
- Children's data. Processing personal data of children (under 18) requires verifiable parental consent. AI systems that profile minors face additional scrutiny.
Penalties: Up to INR 250 crore (approximately $30 million) per violation. DPDPA Full Text
Timeline:
- November 2026 (Phase 1): Data Protection Board operational, Consent Manager registration opens, core fiduciary obligations begin. PIB 2025
- May 2027 (Full compliance): All provisions enforceable for every entity processing Indian personal data. PIB 2025
EU AI Act: Risk-Based Obligations for AI Systems
The EU AI Act applies to any organization that places AI systems on the EU market or whose AI system outputs are used within the EU. For GCCs building AI systems that serve European operations of their parent companies, compliance is not optional.
Risk tiers and timelines
| Tier | What It Covers | Effective Date |
|---|---|---|
| Prohibited | Social scoring, real-time biometric surveillance (limited exceptions), subliminal manipulation | 2 February 2025 |
| GPAI | General-purpose AI models (transparency, technical documentation) | 2 August 2025 |
| High-risk | AI in employment, credit scoring, education, law enforcement, critical infrastructure | 2 August 2026 |
| Limited risk | Chatbots, deepfakes (transparency obligations only) | 2 August 2026 |
Key obligations for GCCs
- Conformity assessments for high-risk AI systems before market placement. SecurePrivacy
- Risk management systems that identify, analyze, and mitigate risks throughout the AI lifecycle.
- Technical documentation covering system design, training data, performance metrics, and known limitations.
- Human oversight mechanisms built into high-risk systems.
- Transparency requirements for AI systems that interact with people (users must know they are interacting with AI).
Penalties: Up to 35 million EUR or 7% of global annual turnover, whichever is higher. SecurePrivacy
Explore the full EU AI Act breakdownGDPR: The Ongoing Baseline
For GCCs processing personal data of EU residents, GDPR has been the compliance baseline since 2018. But in the context of AI governance, several GDPR requirements take on new weight.
AI-specific GDPR obligations
- Data Protection Impact Assessments (DPIAs) are mandatory for AI systems that involve systematic profiling, automated decision-making, or large-scale processing of sensitive data. EDPB
- Automated decision-making (Article 22) gives individuals the right not to be subject to decisions based solely on automated processing that produce legal or significant effects. GCCs running AI-driven HR screening, credit scoring, or insurance underwriting must provide human review mechanisms.
- Cross-border transfer mechanisms. Standard Contractual Clauses (SCCs) remain the primary tool for transferring EU personal data to India. Transfer Impact Assessments are required.
- 72-hour breach notification to the supervisory authority, plus notification to affected individuals if the breach poses high risk. EDPB
- Right to explanation. Data subjects can request meaningful information about the logic involved in automated decisions.
Penalties: Up to 20 million EUR or 4% of global annual turnover.
Where the Frameworks Conflict
The three frameworks do not simply stack. They actively contradict each other in several areas.
| Dimension | DPDPA | GDPR | EU AI Act |
|---|---|---|---|
| Data localization | Transfers permitted by default; government can restrict specific countries by notification (blocklist) | SCCs/adequacy required for third-country transfers | No data localization requirement, but training data documentation required |
| Breach timeline | Immediate notification to Board and individuals without delay; detailed report to Board within 72 hours (DPDP Rules) | 72 hours to supervisory authority | No separate breach timeline (defers to existing law) |
| Incident reporting | CERT-In: 6 hours for covered entities CERT-In | 72 hours to DPA EDPB | Serious incident reporting for high-risk AI (timeline TBD) |
| Consent model | Explicit consent with purpose limitation | Consent or legitimate interest (6 legal bases) | No separate consent regime (defers to GDPR/national law) |
| Risk classification | No AI-specific risk tiers | No AI-specific risk tiers | 4 risk tiers: prohibited, high, limited, minimal |
| Children's data | Under 18, verifiable parental consent | Under 16 (member states can lower to 13), parental consent | Prohibited systems include those targeting children with manipulation |
| Right to explanation | Not explicitly in DPDPA | Article 22: right not to be subject to automated decisions | Transparency obligations for all AI systems interacting with people |
Data localization vs. cross-border flows. GCCs sit at the exact intersection of this tension. They need to move data between India and the EU to function. India's DPDPA permits outbound transfers by default but gives the government power to restrict transfers to specific countries by notification (the restricted country list has not yet been issued). GDPR restricts inbound transfers to the EU through SCCs and adequacy decisions. India does not have an EU adequacy decision, and there is no indication one is forthcoming. Hogan Lovells
This means GCCs must maintain dual transfer mechanisms: GDPR-compliant SCCs for EU-to-India flows, and DPDPA-compliant safeguards for India-to-EU flows.
Incident reporting timeline conflict. CERT-In requires 6-hour incident reporting. CERT-In Directions GDPR allows 72 hours. If a GCC experiences a breach affecting both Indian and EU data subjects, it must report to CERT-In within 6 hours and to the EU supervisory authority within 72 hours. The 6-hour window effectively becomes the binding constraint.
ISO 42001: The Unifying Governance Backbone
Here is the practical answer to the three-framework problem.
ISO 42001 is a certifiable AI management system standard. It does not replace any of the three frameworks. Instead, it provides a structured management system that maps controls to multiple jurisdictional requirements simultaneously. The Bureau of Indian Standards (BIS) has adopted it as IS/ISO/IEC 42001:2023, making it an Indian national standard. KPMG India received ISO 42001 certification from SGS in December 2025, PRNewswire demonstrating that certification is achievable in the Indian context.
Why ISO 42001 works for GCCs
- Single control framework. Instead of maintaining three separate compliance programs, GCCs map DPDPA, GDPR, and EU AI Act requirements to ISO 42001's control set. Gaps become visible. Overlaps get consolidated. ISO
- Risk-based approach. ISO 42001 requires organizations to define their own risk criteria, which accommodates the different risk classification approaches of the EU AI Act (four tiers) and MeitY guidelines (six context-specific categories). ISO
- Compatible with ISO 27001. Most GCCs already hold ISO 27001 certification for information security. ISO 42001 shares the same management system structure, so integration is incremental rather than greenfield. See the IT certifications hub for a full comparison of governance credentials.
- Audit-ready documentation. The standard requires documented policies, risk assessments, and control implementations that satisfy regulatory inquiries from any jurisdiction.
- Third-party credibility. Certification by an accredited body (like SGS) provides evidence of compliance that regulators and parent companies recognize.
MeitY Voluntary Compliance: What GCCs Should Adopt Now
India's MeitY AI governance guidelines are voluntary. They carry no legal penalties. But GCCs that ignore them are making a strategic mistake.
MeitY's guidelines signal the direction Indian AI regulation is heading. The seven sutras (Trust is the Foundation, People First, Innovation over Restraint, Fairness & Equity, Accountability, Understandable by Design, and Safety, Resilience & Sustainability) align closely with principles embedded in both GDPR and the EU AI Act. MeitY 2025 Organizations that operationalize these principles now will have less work to do when binding regulation arrives.
Specific MeitY recommendations GCCs should implement
- Transparency reports. MeitY encourages organizations deploying AI to publish transparency reports covering system capabilities, limitations, and risk mitigation measures. This aligns with EU AI Act transparency obligations and builds public trust. MeitY 2025
- Grievance mechanisms. The guidelines recommend accessible grievance redressal for individuals affected by AI decisions. This maps directly to GDPR's right to contest automated decisions and the EU AI Act's human oversight requirements.
- AI impact assessments. MeitY recommends assessments before deploying high-impact AI systems. Combined with GDPR DPIAs and EU AI Act conformity assessments, this creates a single assessment process that satisfies all three frameworks.
The 5-Step Compliance Roadmap for GCCs
Theory is useful. Execution is what matters. Here is a practical five-step roadmap for GCCs building a multi-jurisdiction AI governance compliance program.
Implementation Roadmap
Framework Overlap Analysis
INR 250Cr max
No legitimate interest
EUR 20M / 4%
DPO required
CE marking
7% revenue penalty
bias testing
documentation
breach notification
- Does it process personal data of Indian citizens? DPDPA applies.
- Does it process personal data of EU residents? GDPR applies.
- Is its output used in the EU market? EU AI Act applies.
- Does it run on cloud infrastructure covered by CERT-In? 6-hour incident reporting applies.
- DPDPA: Consent mechanisms, cross-border transfer documentation, deletion capability, children's data protections
- GDPR: DPIAs for high-risk AI, SCCs for EU-to-India transfers, human review for automated decisions, 72-hour breach notification process
- EU AI Act: Risk tier classification, conformity documentation for high-risk systems, technical documentation for training data and performance metrics
Prioritize by enforcement timeline: DPDPA Phase 1 (November 2026), EU AI Act high-risk (August 2026), GDPR (already enforceable).
- Adopt ISO 42001's risk assessment methodology as your primary approach
- Map DPDPA, GDPR, and EU AI Act requirements to ISO 42001 controls
- Identify controls that satisfy multiple frameworks simultaneously (efficiency gains)
- Fill gaps with framework-specific controls where ISO 42001 does not cover a requirement
- If your GCC holds ISO 27001, use the shared Annex SL structure to integrate
Practical tip: Run tabletop exercises quarterly. Simulate a breach that affects both Indian and EU data subjects. Time your team from detection to CERT-In notification. If they cannot hit 6 hours consistently, the process needs work.
- AI engineers: Technical documentation requirements (EU AI Act), data minimization principles (DPDPA/GDPR), bias testing methodologies
- Data teams: Consent management, cross-border transfer mechanisms, purpose limitation, data governance lifecycle principles, and data retention policies
- Legal and compliance teams: Jurisdictional mapping, regulatory change monitoring, audit preparation across all three frameworks
- Leadership: Penalty exposure, resource allocation for compliance programs, and the business case for ISO 42001 certification
Update training materials whenever a framework changes. The DPDPA rules are still being phased in. The EU AI Act is rolling out through 2027. This is not a one-time effort.
- Does it process personal data of Indian citizens? DPDPA applies.
- Does it process personal data of EU residents? GDPR applies.
- Is its output used in the EU market? EU AI Act applies.
- Does it run on cloud infrastructure covered by CERT-In? 6-hour incident reporting applies.
- DPDPA: Consent mechanisms, cross-border transfer documentation, deletion capability, children's data protections
- GDPR: DPIAs for high-risk AI, SCCs for EU-to-India transfers, human review for automated decisions, 72-hour breach notification process
- EU AI Act: Risk tier classification, conformity documentation for high-risk systems, technical documentation for training data and performance metrics
Prioritize by enforcement timeline: DPDPA Phase 1 (November 2026), EU AI Act high-risk (August 2026), GDPR (already enforceable).
- Adopt ISO 42001's risk assessment methodology as your primary approach
- Map DPDPA, GDPR, and EU AI Act requirements to ISO 42001 controls
- Identify controls that satisfy multiple frameworks simultaneously (efficiency gains)
- Fill gaps with framework-specific controls where ISO 42001 does not cover a requirement
- If your GCC holds ISO 27001, use the shared Annex SL structure to integrate
- Tier 1 (0-6 hrs): CERT-In reporting for cloud services, data centers, or managed services. CERT-In
- Tier 2 (6-72 hrs): GDPR supervisory authority notification. Assess the scope of EU personal data affected and determine whether individual notification is required. EDPB
- Tier 3 (72+ hrs): EU AI Act serious incident reporting timelines are still being finalized, but the requirement exists for high-risk systems. Compile thorough documentation for all applicable regulators.
Practical tip: Run tabletop exercises quarterly. Simulate a breach that affects both Indian and EU data subjects. Time your team from detection to CERT-In notification. If they cannot hit 6 hours consistently, the process needs work.
- AI engineers: Technical documentation requirements (EU AI Act), data minimization principles (DPDPA/GDPR), bias testing methodologies
- Data teams: Consent management, cross-border transfer mechanisms, purpose limitation, data governance lifecycle principles, and data retention policies
- Legal and compliance teams: Jurisdictional mapping, regulatory change monitoring, audit preparation across all three frameworks
- Leadership: Penalty exposure, resource allocation for compliance programs, and the business case for ISO 42001 certification
Update training materials whenever a framework changes. The DPDPA rules are still being phased in. The EU AI Act is rolling out through 2027. This is not a one-time effort.
The GCC Landscape: Why Compliance Is a Competitive Advantage
India's GCC ecosystem is massive and growing.
These numbers matter for compliance because they represent scale. A single GCC compliance failure does not just affect one company. It signals to regulators, parent companies, and clients that the India GCC model carries governance risk. GCCs that demonstrate strong multi-jurisdiction compliance become more attractive to parent companies evaluating where to locate their next AI capability center.
New Roles Emerging in GCC AI Governance
The three-framework challenge is creating demand for roles that did not exist two years ago.
Both roles command salary premiums in the Indian market. AI governance professionals with cross-jurisdiction experience are scarce, and GCCs are competing for them with consulting firms and regulatory bodies. The AI governance careers hub breaks down salary ranges and credential requirements for these emerging positions, and the AIGP certification is becoming a baseline expectation for governance architects.
Explore AI governance career paths and salary dataWhat Comes Next
The compliance landscape for GCCs in India will not simplify in 2026 and 2027. The DPDPA rules are phasing in. The EU AI Act's high-risk obligations take effect in August 2026. IAPP GDPR enforcement continues to intensify. India's MeitY guidelines may evolve toward binding regulation.
GCCs that build a structured, multi-jurisdiction compliance program now (anchored on ISO 42001 and informed by the practical steps above) will spend less time reacting to regulatory changes and more time building AI systems that drive business value. Start with free governance templates for gap analysis checklists and framework mapping tools.
The three-framework challenge is real. But it is solvable. The organizations that solve it first will define the standard for GCC AI governance in India.
Track DPDPA, GDPR, and EU AI Act requirements in one framework.
Download Free TemplateExplore More
Sources & References (14 citations · 7 primary)
- Primary Zinnov/NASSCOM, "India GCC Landscape Report: The 5-Year Journey" (2025). zinnov.com
- Secondary Gratuityconsulting, "India GCC Growth 2026: Talent, AI & Strategy" (2026). gratuityconsulting.com
- Primary MeitY, "DPDPA 2023 Full Text (Act No. 22 of 2023)" (Aug 2023). meity.gov.in
- Primary Press Information Bureau, "DPDP Rules 2025 Notification" (Nov 2025). pib.gov.in
- Secondary EU Artificial Intelligence Act, "Up-to-date developments and analyses of the EU AI Act" (2025). artificialintelligenceact.eu
- Secondary SecurePrivacy, "EU AI Act Compliance: Key Steps and Penalties" (2025). secureprivacy.ai
- Secondary ISO, "ISO/IEC 42001:2023 -- AI Management Systems" (2023). iso.org
- Primary MeitY / IndiaAI Mission, "India AI Governance Guidelines" (Nov 2025). pib.gov.in
- Primary CERT-In / MeitY, "Mandatory Incident Reporting Directions" (Apr 2022). cert-in.org.in
- Secondary European Data Protection Board, "International Data Transfers Guide" (2025). edpb.europa.eu
- Secondary Hogan Lovells, "India Data Localization and Cross-Border Transfer Requirements" (Jul 2024). hoganlovells.com
- Primary NASSCOM, "Strategic Review 2026: Technology Sector in India" (Feb 2026). nasscom.in
- Secondary IAPP, "Guide to EU AI Act Compliance Timelines" (2025). iapp.org
- Primary PRNewswire / SGS, "KPMG India Receives ISO 42001 Certification" (Dec 2025). prnewswire.com
GCC Multi-Jurisdiction Checklist
Track DPDPA, GDPR, and EU AI Act requirements in one framework. Built for GCC compliance teams.