DPDP + EU AI Act Dual Compliance: Architecture Guide (2026)

Q: Is DPDP compliance enough to satisfy the EU AI Act?

No. DPDP and the EU AI Act protect different things and use different regulatory primitives. DPDP protects personal data of Indian individuals through consent, notice, and erasure rights, with the Data Fiduciary as the central regulated entity. The EU AI Act protects against AI-system harms regardless of whether personal data is processed, classifying systems as prohibited, high-risk, limited, or minimal and imposing obligations on Providers and Deployers including conformity assessment, risk management, technical documentation, human oversight, and post-market monitoring. A system that is fully DPDP-compliant can still be in breach of the AI Act if it lacks an FRIA, a technical file, or the human-oversight controls required for high-risk classification. The two regimes are orthogonal axes that intersect on most production AI systems, and dual compliance requires controls from both sides — not one set repurposed for the other.

Q: Does DPDP require all Indian personal data to stay in India?

DPDP itself does not impose blanket data localisation — it permits cross-border transfer except to countries on a notified restricted list, which as of 2026 remains short. The localisation pressure comes from sectoral regulators: the RBI mandates that all payment system data of Indian users be stored only in India (with limited copies abroad for processing), the IRDAI requires insurance data to remain in India, and CERT-In directives push security telemetry toward Indian retention. So a generic Indian AI workload (e.g., a productivity assistant) is not localised by DPDP, but a financial AI workload (credit scoring, payments fraud) is practically localised by the RBI overlay even though DPDP does not mention localisation. The dual-compliant architecture therefore puts financial and health AI workloads on Indian regions by default and uses the cross-border flexibility for non-sectoral workloads under DPDP-compliant transfer mechanisms.

Q: How do SCCs work for transferring EU data to an Indian AI vendor in 2026?

India does not have an EU adequacy decision and is not on the near-term list, so transfers of EU personal data to an Indian AI vendor must use Standard Contractual Clauses (the 2021 modular SCCs from the European Commission) paired with a Transfer Impact Assessment that addresses Indian government access powers. The TIA must document the Indian legal regime for state access (CrPC, Telegraph Act, IT Act §69, IT Rules 2021), evaluate the risk that those powers undermine the SCC protections (the Schrems II analysis), and document supplementary technical and organisational measures — encryption at rest and in transit with keys held in the EU jurisdiction, contractual commitments to notify the EU controller of any government access request, transparency reporting, and ideally architectural choices that minimise the data crossing the border in the first place. A well-drafted TIA is the difference between a deal closing at the customer's DPO review and stalling indefinitely. Many Indian vendors avoid the SCC issue entirely by deploying EU customer workloads on EU regions and keeping personal data physically pinned to the EU.

Q: What is a DPIA-FRIA combined assessment and how does it work in practice?

A DPIA-FRIA combined assessment is a single workshop and integrated documentation cycle that produces both the Data Protection Impact Assessment required for Significant Data Fiduciaries under DPDP (and required generally under GDPR Art. 35 for high-risk processing) and the Fundamental Rights Impact Assessment required for high-risk AI deployers under the EU AI Act. The integrated approach uses one scoping workshop per significant change with a shared system description and stakeholder map, then runs two parallel assessment tracks — the data-protection track that asks "what could go wrong with this data?" and produces the DPIA, and the fundamental-rights track that asks "what could go wrong with this AI system's decisions?" and produces the FRIA. The two tracks converge on a single combined assessment report that goes to the DPO, the AI Officer, and Legal for joint sign-off, and the outcomes are recorded in one DPIA-FRIA register that is consulted during post-market monitoring. The integrated cycle costs about 30 per cent more than a standalone DPIA but roughly half as much as running the two assessments separately, and it eliminates the risk that two separate assessments produce contradictory findings.

Q: Can the same Indian AI vendor be a Data Fiduciary, Provider, and Deployer at the same time?

Yes — and this is the normal case for an Indian AI vendor with European customers. The same legal entity wears different regulatory hats in different transactions. When the vendor builds and trains a foundation model, it is a Data Fiduciary for any Indian personal data in the training set and a Provider under the AI Act for the model. When it fine-tunes that model for a customer use case, it remains a Data Fiduciary for fine-tune data and is either still a Provider (if the modification is substantial) or a Deployer (if it is just configuring). When it operates the fine-tuned model as a hosted service for a customer's end-users, it is a Data Processor for the customer data (under the customer's instructions) and a Deployer of the platform itself. When it collects telemetry that includes personal data, it becomes a Data Fiduciary again for that telemetry. The regulatory documentation must reflect this layered reality with separate controls and separate evidence per role; teams that try to collapse all of this into "we are an AI vendor" produce documentation that satisfies neither regulator.

Q: How does the right to erasure interact with AI model training?

Both DPDP and GDPR require that a data subject's erasure request be honoured within statutory timelines (typically 30 days under DPDP rules, "without undue delay" under GDPR Art. 17), and both treat failure to honour erasure as a high-severity breach. The architectural implication that AI teams routinely miss is that erasure must reach not only the live database but also the training data lake, the feature store snapshots, and the queue of records pending the next model retraining cycle. A model that has already been trained on a now-erased record cannot itself be untrained without retraining, which is computationally infeasible per request. The accepted compliance position with both regulators is that erasure removes the record from all future training cycles and the next scheduled retraining produces a model that no longer carries the influence of the erased data. This is acceptable provided the erasure is timely, the retraining cadence is documented in the AI system's technical file (typically quarterly or biannually for production models), and the operator can demonstrate the propagation chain with an audit trail. Anonymisation at the point of training-data ingest reduces the surface further: if the training data has been genuinely anonymised, it falls outside the scope of erasure rights entirely.

Q: What is the most common dual-compliance mistake Indian AI vendors make?

The most common and most expensive mistake is treating compliance as documentation that follows the build rather than architecture that precedes it. The pattern is familiar: vendor builds a multi-tenant platform with shared infrastructure, signs a European customer, customer's DPO requests the technical file, vendor discovers it has no jurisdiction-segregated data planes, no consent ledger that captures GDPR lawful basis, no SCC framework, no FRIA, no technical file, no post-market monitoring plan. The remediation costs three to six months of engineering and business-stalling delay; in many cases the deal is lost. The second-most-common mistake is collapsing the role mapping — claiming to be only a Data Processor when the vendor is in fact also a Data Fiduciary for telemetry, or claiming to be only a Provider when the vendor is also a Deployer for its hosted runtime. Both mistakes are cheap to avoid in design and expensive to fix in production. The dual-compliance architecture in this article is the cheapest defensive posture against both.

Q: Do I need a DPO and an AI Officer, or can one person do both roles?

Under DPDP, Significant Data Fiduciaries (notified by category or threshold, including high-volume processors and those with high-risk data) must appoint a Data Protection Officer; smaller Data Fiduciaries are not strictly required to but it is recommended. Under the EU AI Act, there is no mandatory "AI Officer" title, but the obligations on Providers and Deployers (conformity assessment, technical file, post-market monitoring, FRIA, incident reporting) require an accountable function that is in practice a senior role. For small organisations, the same person can hold both roles provided they have the time and the competence breadth — DPOs are typically lawyers or data professionals, AI Officers tend to combine technical and ethical literacy, and few individuals are strong in both. For organisations above roughly 100 staff or with material AI exposure, the practical answer is two distinct individuals with a defined collaboration cadence: the DPO owns DPDP and GDPR compliance, the AI Officer owns AI Act compliance, and they jointly own the DPIA-FRIA register, the audit log, and the incident response playbook.

Q: How long does it take to retrofit an existing AI platform for dual compliance?

Retrofitting an existing single-jurisdiction AI platform to the dual-compliance architecture typically takes four to nine months for a team of four to six engineers plus one DPO and one external counsel, depending on starting state. The longest single workstream is data plane segregation — separating EU and Indian personal data into regionally pinned stores with the supporting access controls — which alone is two to four months for a non-trivial platform. The consent ledger refactor (capturing both DPDP and GDPR semantics in one schema) is typically four to six weeks. The DPIA-FRIA process and template work is two to three weeks of workshop time spread over two months. The technical file authoring per high-risk AI system is two to four weeks per system. The contractual work (DPA, SCC, role allocation) is parallel and lawyer-led, typically three to six weeks. Retrofitting is meaningfully more expensive than greenfield design (perhaps 2.5x), which is the principal argument for adopting the dual-compliance posture from the first European customer rather than waiting for the second or third.

Q: What audit evidence will an Indian Data Protection Board inquiry actually look at?

Based on the rules notified in January 2025 and early enforcement signals through 2025-2026, the Indian Data Protection Board will look at: the consent ledger (proof that notice was provided in the appropriate language and channel, that acknowledgement was captured, that withdrawal was honoured); the data inventory (categories of personal data processed, sources, purposes, retention periods); the breach register (incidents, timelines, notifications to the Board and to affected Data Principals); the DPIA register for Significant Data Fiduciaries (assessments performed, mitigations implemented, sign-offs); the cross-border transfer log (which categories went where, on what basis, with what safeguards); the grievance redressal mechanism (complaints received, responses, escalation handling); and the appointment of a DPO for Significant Data Fiduciaries with documented competence and contact details. The audit log that is tamper-evident and externally anchored is the single most important piece of evidence — it is what allows the Board to verify the operator's claims rather than take them at face value. Operators with clean tamper-evident audit logs are typically through Board inquiries in weeks; operators without them spend months reconstructing evidence.

Satyam Kumar

Retour au blog

ai-architecture

DPDP + EU AI Act: A Dual-Compliance Architecture for India-EU AI Systems (2026)

By Satyam KumarApril 25, 202623 min read

DPDP Act 2023 EU AI Act dual compliance India AI regulation GDPR data fiduciary AI provider deployer DPIA FRIA data residency India cross border data transfer standard contractual clauses transfer impact assessment consent manager ODE Indian Data Protection Board AI conformity assessment India EU AI architecture

DPDP + EU AI Act: A Dual-Compliance Architecture for India-EU AI Systems (2026)

Frequently Asked Questions

Partager l'article

Twitter LinkedIn WhatsApp

Satyam Kumar

Founder & AI Architect, AppScale LLP

Architecte AI & Cloud. J'aide les équipes à construire des systèmes qui scalent pour des millions.

LinkedIn GitHub

DPDP + EU AI Act: A Dual-Compliance Architecture for India-EU AI Systems (2026)

Frequently Asked Questions

Partager l'article

Comments

Leave a comment