EU & cross-borderUpdated 22 November 20269 min read

DPA & SCCs Explained for Indian Vendors Selling to EU Clients

What 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.

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

DPA legal basis
GDPR Article 28
SCC instrument
Commission Implementing Decision (EU) 2021/914
SCC modules
C2C, C2P, P2P, P2C
Typical Indian vendor module
Module 2 (controller to processor)
India adequacy
None
Key case
Schrems II, CJEU C-311/18 (July 2020)
DPDP processor contract rule
Rule 6(1)(f), from 13 May 2027

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.

DPASCCs
Legal sourceGDPR Article 28GDPR Article 46 via Commission Implementing Decision (EU) 2021/914
PurposeGoverns how a processor processes personal data for a controllerMakes a transfer to a third country lawful
When neededAny controller–processor relationship, even inside the EUWhen EU personal data goes to, or is accessed from, a country without adequacy
Editable?Yes, within Article 28 minimumsClauses must not be changed; annexes are completed
For Indian vendorsAlmost alwaysAlmost 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).

ModuleExporterImporterIndian vendor example
1 — C2CControllerControllerIndian partner receiving leads it will use for its own purposes
2 — C2PControllerProcessorEU customer using Indian SaaS or IT services (most common)
3 — P2PProcessorProcessor (sub-processor)EU vendor or EU subsidiary engaging the Indian entity as sub-processor
4 — P2CProcessorControllerEU 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

  1. Which Indian laws allow authorities to request access to data?
  2. Has the vendor received such requests, and how does it handle them?
  3. What technical measures limit what could be disclosed?
  4. 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.

TopicCustomer typically asksVendor-reasonable position
Breach noticeA fixed short windowA defined window you can meet operationally, with updates as facts emerge
AuditsOn-site audits on demandReliance on third-party reports first; on-site with notice and limits
Sub-processorsApproval for each changeGeneral authorisation with advance notice and right to object
LiabilityUncapped for data breachesA separate, higher cap for data protection
Data locationEU-onlyEU hosting where offered; access from India covered by SCCs
AI trainingProhibitedNo training on customer data by default; opt-in only
DeletionImmediate on terminationWithin 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

Before 13 May 2027

Compliance checklist

  1. Map your roles per customer

    Decide controller or processor for each data flow, including model improvement.

    GDPR Art. 28

  2. Pick the right SCC module

    Use Module 2 for EU customers and Module 3 for EU processors or affiliates.

    Decision (EU) 2021/914

  3. Complete Annex I accurately

    Describe data subjects, data categories, purposes, frequency and retention.

    SCCs Annex I

  4. Write a specific Annex II

    List concrete technical and organisational measures, including AI-specific controls.

    SCCs Annex II

  5. Keep Annex III current

    Maintain sub-processor names, locations and purposes, including AI API providers.

    SCCs Annex III

  6. Prepare a TIA input pack

    Describe Indian access laws, request handling and supplementary measures.

    SCCs Clause 14

  7. Build a negotiation playbook

    Pre-approve fallback positions on breach notice, audits, liability and deletion.

    GDPR Art. 28

  8. 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

  1. 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?

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?

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?

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?

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?

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?

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

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.