EU & cross-borderUpdated 22 November 20269 min read

GDPR for Indian IT Services Firms: Practical Checklist

A 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).

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

Typical GDPR role
Processor (Art. 28)
Transfer mechanism
SCCs, Decision (EU) 2021/914 (Module 2 or 3)
India adequacy
None
Controller breach deadline
72 hours to supervisory authority where risk (Art. 33)
GDPR max fine
€20m or 4% of worldwide turnover
DPDP carve-out
s.17(1)(d) for non-Indian Data Principals' data under foreign contract

Quick answer

Indian IT services firms handling EU client data are usually GDPR processors. They need an Article 28 contract, SCCs under Decision (EU) 2021/914 (Module 2 or 3), a transfer impact assessment, Article 30 processor records, Article 32 security, sub-processor controls and fast breach notice so clients can meet the 72-hour Article 33 deadline. DPDP section 17(1)(d) limits Indian duties to security and accountability.

  • Most Indian IT services and BPO firms are GDPR processors for EU client data and are bound through Article 28 contracts.
  • India has no adequacy decision, so SCCs and a transfer impact assessment are needed, including for remote access from Indian delivery centres.
  • Processors must keep Article 30(2) records, apply Article 32 security and notify controllers of breaches without undue delay.
  • Using generative AI tools on client data needs the client's authorisation and sub-processor controls.
  • DPDP section 17(1)(d) disapplies most Indian duties for foreign clients' data, but section 8(5) security still applies.

Who this is for: IT services and engineering firms, BPO and KPO operators, Indian delivery centres of global firms, Delivery managers and account leads, Information security and privacy officers

Is an Indian IT services firm a controller or processor under GDPR?

For client work, almost always a processor. An IT services or BPO firm processes personal data on the client's documented instructions: running a client's CRM, handling its customer support tickets, testing its applications with production data, or operating its payroll.

The firm becomes a controller where it decides purposes and means for its own reasons, for example:

  • its own employee and recruitment data;
  • sales and marketing contacts at client organisations;
  • using client data to build its own reusable tools, accelerators or AI models.

That third case is a common trap. Reusing client data to train an internal AI model or build a product is outside the processor role and needs separate legal analysis and client agreement.

How GDPR reaches the firm

Even where Article 3(2) does not directly apply to the Indian firm (because it is not itself offering services to EU individuals), the EU client is bound to impose GDPR-level obligations through an Article 28 contract, and to use a Chapter V transfer mechanism. Practically, the firm must meet GDPR processor standards to win and keep EU work.

On the Indian side, the firm is also a Data Processor or Data Fiduciary under the DPDP Act. See DPDP for IT services, BPO and outsourcing firms.

What the Article 28 contract requires

GDPR Article 28 lists terms every processor contract must contain. Expect to see them in the client's DPA:

TermWhat it means for delivery teams
Process only on documented instructionsScope of work defines permitted processing; anything else needs client approval
Confidentiality of personnelStaff bound by confidentiality, typically through employment terms and NDAs
Article 32 securityAppropriate technical and organisational measures
Sub-processor conditionsNo sub-processor without prior authorisation; flow down equivalent terms
Assist with data subject rightsHelp the client respond to access, erasure and other requests
Assist with Articles 32–36Security, breach notification, DPIAs and prior consultation
Delete or return at endOn termination, at the client's choice
Audit and informationMake information available and allow audits and inspections
Flag unlawful instructionsInform the client if an instruction appears to infringe GDPR

Delivery implications

  • Keep a processing scope document per engagement, mapped to the SOW.
  • Build rights-request support into runbooks: who searches which systems, within what turnaround.
  • Plan exit: deletion certificates and evidence for every environment, including laptops, test systems and backups.

Transfers: SCCs and transfer impact assessments

India has no EU adequacy decision. Every transfer of EU personal data to India — including remote access by engineers in India to systems hosted in the EU — needs a Chapter V basis.

Which SCC module?

  • Module 2 (controller to processor) — EU client directly engaging the Indian firm.
  • Module 3 (processor to processor) — where the EU client's processor (perhaps the Indian firm's own EU subsidiary) engages the Indian entity as sub-processor.

The SCCs are in Commission Implementing Decision (EU) 2021/914. They must be used without changing their clauses, though they can sit inside a wider contract.

Transfer impact assessment

Since Schrems II (CJEU C-311/18, July 2020), the exporter is expected to assess whether laws in India could prevent the importer from meeting SCC commitments, and to adopt supplementary measures where needed. The Indian firm should provide a structured input covering:

  • applicable Indian laws on government access (for example, DPDP Rule 23 and the Seventh Schedule, IT Act powers, CERT-In directions);
  • its own policy on handling government requests;
  • technical measures: encryption, EU-held keys where feasible, pseudonymisation, access control;
  • how often requests have been received, if any.

For the contract mechanics, see DPA and SCCs explained for Indian vendors.

Security and breach notification

Article 32 security

Processors must implement security appropriate to risk, considering pseudonymisation and encryption, ongoing confidentiality and availability, ability to restore access after incidents, and regular testing. For Indian delivery centres this typically means:

  • client-segregated networks or virtual desktops with copy/paste and download restrictions;
  • multi-factor authentication and privileged access management;
  • endpoint controls, removable media blocking and clean-desk policies for sensitive engagements;
  • logging of access to client systems, retained per contract;
  • background checks consistent with Indian law.

Breach timing

The client, as controller, must notify its supervisory authority within 72 hours of becoming aware where the breach is likely to result in a risk (Article 33), and affected individuals where high risk (Article 34). The processor must notify the controller without undue delay. Many DPAs set a fixed window, often in hours; build to the strictest client commitment.

Indian overlay

A cyber incident at an Indian delivery centre may also need reporting to CERT-In within 6 hours under its April 2022 directions. If Indian individuals' data is also affected, DPDP Rule 7 applies from 13 May 2027. See CERT-In rules for AI systems.

Using AI tools on client data

Delivery teams increasingly use code assistants, LLM chat tools and AI test-data generators. Under GDPR, each is a potential sub-processor or a change in processing.

Rules of thumb

  • No client personal data in unapproved AI tools. An LLM vendor that receives client data is a sub-processor needing the client's prior authorisation under Article 28(2).
  • Check the vendor's terms. Data retention, training use, region and sub-processors must match the client DPA.
  • Prefer client-provided or client-approved AI. Many EU clients now provide sanctioned AI tools inside their own tenancy.
  • Use synthetic or masked data for testing. Copying production personal data to test environments is a common audit finding.
  • Log AI use per engagement. If a client asks which tools touched its data, answer from records.

AI Act angle

If the firm builds an AI system for an EU client, the AI Act roles question arises: who is the provider? Clarify in the contract. If the system falls under Annex III — for example, a recruitment screening tool — high-risk obligations apply. See EU AI Act for Indian companies.

How DPDP applies to EU client work

DPDP section 17(1)(d) is written for exactly this business model. Where personal data of Data Principals not within India is processed by a person in India under a contract with a person outside India:

  • Chapter II except sections 8(1) and 8(5) does not apply;
  • Chapter III (Data Principal rights) does not apply;
  • section 16 (cross-border transfer) does not apply.

So for EU client data, the Indian firm's DPDP duties narrow to responsibility (s.8(1)) and reasonable security safeguards (s.8(5)). Penalties for failing to take reasonable security safeguards can reach ₹250 crore under the Schedule.

What still needs full DPDP compliance

  • the firm's own Indian employees' data (HR, payroll, monitoring);
  • Indian clients' customer data;
  • any Indian individuals in an EU client's dataset, for whom the exemption does not apply.

Those flows need full DPDP compliance from 13 May 2027, including Rule 6 security, Rule 7 breach intimation and Rule 8(3) one-year log retention. See DPDP for HR and employee data.

Further reading on suhasbhairav.com

Before 13 May 2027

Compliance checklist

  1. Confirm processor scope per engagement

    Document permitted processing for each client against the SOW and DPA.

    GDPR Art. 28(3)(a)

  2. Execute SCCs

    Use Module 2 for direct EU clients and Module 3 for sub-processing chains.

    Decision (EU) 2021/914

  3. Prepare a TIA input pack

    Describe Indian government access laws, request handling and technical measures.

    GDPR Ch. V; Schrems II

  4. Maintain Article 30(2) records

    Keep processor records of categories of processing per controller.

    GDPR Art. 30(2)

  5. Control sub-processors

    List all sub-processors, including AI tools, and obtain client authorisation.

    GDPR Art. 28(2), 28(4)

  6. Set breach notification SLAs

    Meet the strictest client DPA window and support Art. 33 72-hour notifications.

    GDPR Art. 33(2)

  7. Block client data in unapproved AI

    Enforce policy and technical controls preventing client data entry into public AI tools.

    GDPR Art. 28, 32

  8. Plan exit and deletion

    Delete or return data at termination with evidence across all environments.

    GDPR Art. 28(3)(g)

  9. Apply DPDP security to EU data

    Meet section 8(5) reasonable safeguards for foreign clients' data.

    DPDP s.17(1)(d), s.8(5)

Key dates

  1. DPDP Rules notified as G.S.R. 846(E)

  2. DPDP core obligations, including s.17 exemptions, apply

Answers

Frequently asked questions

Does GDPR apply to Indian IT companies?

In practice, yes, for EU client work. EU controllers must bind their processors to Article 28 terms and use Chapter V transfer tools, so Indian IT services firms handling EU personal data must meet GDPR processor standards. Some may also be directly in scope under Article 3(2).

Which SCC module does an Indian IT vendor sign?

Module 2 (controller to processor) where the EU client is the controller and engages the Indian firm directly. Module 3 (processor to processor) where the Indian firm is a sub-processor to another processor, such as its EU affiliate. Both are in Decision (EU) 2021/914.

Is remote access from India a data transfer under GDPR?

Yes. Making EU personal data accessible to staff in India, even if the data stays on EU servers, is treated as a transfer to a third country. It needs a Chapter V mechanism such as SCCs and should be covered in the transfer impact assessment.

How fast must an Indian processor report a breach to an EU client?

GDPR requires processors to notify the controller without undue delay after becoming aware. Client DPAs usually set a specific window in hours so the controller can meet its own 72-hour Article 33 deadline. Build incident processes to the strictest contractual commitment.

Can developers use ChatGPT or Copilot on EU client code and data?

Only if the client has authorised the tool as a sub-processor or the tool runs within the client's approved environment, and no client personal data is shared beyond what is permitted. Code without personal data carries less GDPR risk, but confidentiality terms may still restrict it.

Does the DPDP Act apply to EU client data processed in India?

Only partially. Section 17(1)(d) disapplies most of Chapter II, Chapter III and section 16 for non-Indian individuals' data processed under a foreign contract. Sections 8(1) and 8(5) still apply, so the firm must keep reasonable security safeguards and remains accountable.

Legal references and sources

  • GDPR, Regulation (EU) 2016/679 — Articles 28, 30, 32, 33 (official text)
  • GDPR, Regulation (EU) 2016/679 — Chapter V (Articles 44–49) (official text)
  • Commission Implementing Decision (EU) 2021/914 — SCC Modules 2 and 3 (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.