Quick answer
A DPA (data processing agreement) is the GDPR Article 28 contract between an EU controller and its processor. SCCs are the Commission's model transfer clauses (Implementing Decision (EU) 2021/914) that make transfers to countries without adequacy, such as India, lawful. Most Indian vendors sign Module 2 (controller to processor) inside the DPA and support a transfer impact assessment.
- A DPA sets processor obligations under GDPR Article 28; SCCs legitimise the transfer of EU personal data to India under Chapter V.
- The 2021 SCCs have four modules; Indian vendors usually sign Module 2 with EU customers and Module 3 with EU processors.
- SCC clauses cannot be modified; negotiation happens in the annexes and the surrounding commercial agreement.
- After Schrems II, a transfer impact assessment is expected, so Indian vendors should prepare a standard input on Indian law and safeguards.
- From 13 May 2027, DPDP Rule 6(1)(f) also requires security clauses in contracts between Indian fiduciaries and processors.
Who this is for: Indian SaaS and IT services vendors, Sales and contract managers, In-house counsel, Privacy and security leads, Founders preparing for EU enterprise deals
DPA vs SCCs: what is the difference?
EU buyers usually send two documents, often merged into one. They do different jobs.
| DPA | SCCs | |
|---|---|---|
| Legal source | GDPR Article 28 | GDPR Article 46 via Commission Implementing Decision (EU) 2021/914 |
| Purpose | Governs how a processor processes personal data for a controller | Makes a transfer to a third country lawful |
| When needed | Any controller–processor relationship, even inside the EU | When EU personal data goes to, or is accessed from, a country without adequacy |
| Editable? | Yes, within Article 28 minimums | Clauses must not be changed; annexes are completed |
| For Indian vendors | Almost always | Almost always, because India has no adequacy decision |
A good way to think about it: the DPA answers "what may the vendor do with the data?", while the SCCs answer "is it lawful for the data to leave the EU to go to this vendor?"
Many vendors maintain a single document: a DPA that incorporates the SCCs by reference and contains the SCC annexes. That is fine, as long as the SCC text itself is not altered and prevails in case of conflict.
For the wider EU sales context, see selling AI SaaS to Europe from India.
Which SCC module does an Indian vendor sign?
The 2021 SCCs are modular. Pick by the roles of exporter (in the EU or otherwise subject to GDPR) and importer (in India).
| Module | Exporter | Importer | Indian vendor example |
|---|---|---|---|
| 1 — C2C | Controller | Controller | Indian partner receiving leads it will use for its own purposes |
| 2 — C2P | Controller | Processor | EU customer using Indian SaaS or IT services (most common) |
| 3 — P2P | Processor | Processor (sub-processor) | EU vendor or EU subsidiary engaging the Indian entity as sub-processor |
| 4 — P2C | Processor | Controller | EU processor returning data to a controller outside the EU |
Typical structures
- Direct contract: Indian company contracts with EU customer → Module 2.
- EU subsidiary model: EU entity contracts with customers; Indian parent or affiliate does the work → EU entity and customer sign a DPA; EU entity and Indian entity sign Module 3.
- Both roles: if you also use customer data for your own purposes (analytics on your platform, model improvement), consider whether Module 1 elements are needed — and whether the customer has agreed.
Onward transfers
If you use sub-processors outside the EU (for example, a US model API), the SCCs require that onward transfers are protected by equivalent terms. List them and flow down obligations.
Filling in the SCC annexes
The SCC clauses are fixed. The work is in the annexes, which customers will review closely.
Annex I — list of parties and description of transfer
- Parties: legal names, addresses, contact persons, roles.
- Categories of data subjects: for example, the customer's employees, end customers, website visitors.
- Categories of personal data: identifiers, contact data, content uploaded, usage logs.
- Sensitive data: if any, and the safeguards applied.
- Frequency: continuous or one-off.
- Nature and purpose: hosting, support, AI inference, analytics on the customer's behalf.
- Retention: how long, and when deleted.
- Competent supervisory authority: determined by the exporter's situation.
Annex II — technical and organisational measures
Be specific. Generic statements ("industry-standard security") invite follow-up questions. List encryption at rest and in transit, access control and MFA, logging and monitoring, backup and recovery, vulnerability management, personnel security and incident response. For AI products, add model-specific controls: whether prompts are logged, retention, no training on customer data by default, and isolation between tenants.
Annex III — sub-processors
Names, locations and the processing each performs. Keep it in sync with your public sub-processor list.
The same control descriptions can support DPDP Rule 6 evidence for Indian data; see DPDP data processing agreement clauses.
The transfer impact assessment
After the CJEU's Schrems II judgment (C-311/18, July 2020), signing SCCs is not enough on its own. The exporter must assess whether the importer's country's law and practice could prevent compliance with the SCCs, and add supplementary measures if needed. Clause 14 of the SCCs reflects this: both parties warrant they have no reason to believe local laws prevent compliance.
What EU customers will ask Indian vendors
- Which Indian laws allow authorities to request access to data?
- Has the vendor received such requests, and how does it handle them?
- What technical measures limit what could be disclosed?
- Will the vendor notify the customer of requests where legally permitted?
A standard TIA input pack
Prepare a short document covering:
- relevant Indian law, described neutrally — for example, DPDP Rule 23 and the Seventh Schedule allow the Central Government to call for information from Data Fiduciaries and intermediaries for specified purposes; the IT Act and CERT-In directions contain other powers;
- your policy for reviewing, narrowing and challenging requests;
- encryption, key management, pseudonymisation and access controls;
- data minimisation and EU-hosting options.
Avoid overstating either way. Describe the law accurately and let the exporter reach its conclusion. See does India have GDPR adequacy?.
Negotiation points that matter
Because the SCC clauses cannot change, negotiation shifts to the DPA and commercial terms.
| Topic | Customer typically asks | Vendor-reasonable position |
|---|---|---|
| Breach notice | A fixed short window | A defined window you can meet operationally, with updates as facts emerge |
| Audits | On-site audits on demand | Reliance on third-party reports first; on-site with notice and limits |
| Sub-processors | Approval for each change | General authorisation with advance notice and right to object |
| Liability | Uncapped for data breaches | A separate, higher cap for data protection |
| Data location | EU-only | EU hosting where offered; access from India covered by SCCs |
| AI training | Prohibited | No training on customer data by default; opt-in only |
| Deletion | Immediate on termination | Within a defined period, with certificate; backups age out |
Keep a playbook
Record standard fallback positions approved by leadership, so sales can close quickly without reinventing answers.
Common mistakes
- Editing SCC clause text in redlines (it invalidates them as SCCs).
- Leaving Annex II generic.
- Forgetting to list AI model API providers as sub-processors.
- Signing a DPA that forbids any access from outside the EU when the delivery team is in India.
How this connects to DPDP processor contracts
The DPDP Act has its own processor contract rules, which apply to Indian personal data:
- Section 8(2): a Data Fiduciary may engage a Data Processor only under a valid contract.
- Section 8(1): the fiduciary remains responsible for processing by its processors.
- Rule 6(1)(f): contracts between fiduciaries and processors must contain appropriate provisions for reasonable security safeguards (from 13 May 2027).
- Rule 8(3): the fiduciary must ensure processors retain personal data and logs for at least one year (the cloud provider illustration).
- Section 8(7): processors must be caused to erase data when the fiduciary must erase.
For EU customers' data processed in India under contract, section 17(1)(d) disapplies most DPDP duties other than sections 8(1) and 8(5). So an Indian vendor's EU DPA is driven by GDPR, while its contracts covering Indian data are driven by DPDP.
One template family
Maintain two schedules on a common base: a GDPR schedule with SCCs for EU data, and a DPDP schedule for Indian data. Shared security annexes reduce effort and contradictions. See DPDP vs GDPR.
Further reading on suhasbhairav.com
- BlogCross-Border Data Compliance for Agentic AI Systems
- BlogLocal AI and GDPR: data transfer risk explained
- BlogAgent-based vendor risk auditing for sub-processors
- AI SkillsCursor Rules Template: GDPR Risk Assessment Tools from Website Forms and Data Flows
- AI Use CasesAI Agent Use Case: Gdpr Consultants Using Website Forms and Data Flows to Identify Privacy Risks
Before 13 May 2027
Compliance checklist
Map your roles per customer
Decide controller or processor for each data flow, including model improvement.
GDPR Art. 28
Pick the right SCC module
Use Module 2 for EU customers and Module 3 for EU processors or affiliates.
Decision (EU) 2021/914
Complete Annex I accurately
Describe data subjects, data categories, purposes, frequency and retention.
SCCs Annex I
Write a specific Annex II
List concrete technical and organisational measures, including AI-specific controls.
SCCs Annex II
Keep Annex III current
Maintain sub-processor names, locations and purposes, including AI API providers.
SCCs Annex III
Prepare a TIA input pack
Describe Indian access laws, request handling and supplementary measures.
SCCs Clause 14
Build a negotiation playbook
Pre-approve fallback positions on breach notice, audits, liability and deletion.
GDPR Art. 28
Align DPDP processor contracts
Add Rule 6(1)(f) security and Rule 8(3) retention terms for Indian data.
DPDP Rule 6(1)(f), Rule 8(3)
Key dates
DPDP Rule 6(1)(f) processor contract and Rule 8(3) retention requirements apply
Answers
Frequently asked questions
What is the difference between a DPA and SCCs?
What is the difference between a DPA and SCCs?
A DPA is the GDPR Article 28 contract setting out how a processor handles personal data for a controller. SCCs are the European Commission's model clauses that make a transfer to a non-adequate country lawful. Indian vendors usually need both, often combined in one document.
Which SCC module should an Indian SaaS company sign?
Which SCC module should an Indian SaaS company sign?
Module 2 (controller to processor) when an EU customer engages the Indian company directly to process its data. Module 3 (processor to processor) if the Indian company is a sub-processor to an EU processor, including its own EU subsidiary.
Can I change the wording of the SCCs?
Can I change the wording of the SCCs?
No. The SCC clauses must be used without modification to function as SCCs. You may add clauses or commercial terms that do not contradict them, and you must complete the annexes. If you edit the clauses, they may no longer count as an Article 46 safeguard.
What is a transfer impact assessment?
What is a transfer impact assessment?
It is an assessment, expected since Schrems II, of whether the laws and practices of the importer's country could stop the importer complying with the SCCs, and of what supplementary measures are needed. The exporter is responsible, but Indian vendors should supply a clear input on Indian law and safeguards.
Do I need SCCs if my data is hosted in the EU?
Do I need SCCs if my data is hosted in the EU?
If anyone in India can access the EU-hosted personal data, yes. Remote access is treated as a transfer. If the data is strictly EU-hosted and no one outside the EU can access it, SCCs may not be needed for that flow, but sub-processors elsewhere may still trigger them.
Does DPDP require a DPA with Indian processors?
Does DPDP require a DPA with Indian processors?
Yes. Section 8(2) of the DPDP Act requires a valid contract with any Data Processor, and from 13 May 2027 Rule 6(1)(f) requires it to include reasonable security safeguard provisions. Rule 8(3) also makes the fiduciary ensure processors retain data and logs for at least one year.
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)
- Digital Personal Data Protection Rules, 2025 — Rule 6(1)(f) (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
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-borderGDPR for Indian IT Services Firms: Practical ChecklistA practical GDPR checklist for Indian IT services, BPO and engineering firms handling EU client data: processor duties, SCC modules, sub-processors, breach support, AI tooling and DPDP s.17(1)(d).
- 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.
- Templates & playbooksDPDP Data Processing Agreement Clauses TemplateCopy-ready data processing agreement clauses for India, mapped to DPDP section 8(2), Rule 6(1)(f), Rule 7 breach timelines and Rule 8(3) one-year retention.
- EU & cross-borderSelling AI SaaS to Europe From India: Complete Compliance GuideThe full compliance stack for an Indian AI SaaS company selling into the EU: GDPR scope and roles, DPAs and SCCs, EU AI Act roles and dates, and how it fits with DPDP at home.
- 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.
- DPDP Act 2023Data Fiduciary vs Data Processor Under the DPDP ActWhoever decides why and how personal data is processed is the Data Fiduciary and carries the liability; the Data Processor acts on its behalf under contract.