Sector guidesUpdated 22 November 20269 min read

DPDP for IT Services, BPO and Outsourcing Firms

What the DPDP Act's section 17(1)(d) outsourcing exemption covers, what still applies to Indian IT services and BPO firms, and how to treat domestic and employee data.

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

Exemption
Section 17(1)(d), DPDP Act 2023
Still applies
Sections 8(1) and 8(5)
Does not apply
Rest of Chapter II, Chapter III, section 16
Security benchmark
Rule 6, DPDP Rules 2025
Max security penalty
Up to ₹250 crore
Core rules in force
13 May 2027

Quick answer

Section 17(1)(d) of the DPDP Act exempts a person based in India who processes personal data of people outside India under a contract with a person outside India. Most of Chapter II, all of Chapter III (rights) and section 16 do not apply, but sections 8(1) and 8(5) still do: the firm stays responsible for compliance and must maintain reasonable security safeguards, with penalties up to ₹250 crore.

  • The section 17(1)(d) carve-out only covers foreign Data Principals' data processed under a contract with a foreign person.
  • Sections 8(1) and 8(5) survive the exemption, so accountability and reasonable security safeguards still apply.
  • Failure to take reasonable security safeguards carries the highest DPDP penalty: up to ₹250 crore per instance.
  • Indian employees' data, Indian customers' data and domestic client work get no benefit from the exemption.
  • Client contracts under GDPR or other foreign laws impose their own duties, which the exemption does not displace.

Who this is for: IT services and consulting firms, BPO, KPO and contact-centre operators, Global capability centres in India, Delivery heads and CISOs, Contract and legal teams at Indian vendors

What does section 17(1)(d) exempt?

Section 17(1)(d) addresses the classic offshore delivery model. It applies where a person based in India processes personal data of Data Principals not within the territory of India, pursuant to a contract entered into with a person outside the territory of India.

All three conditions must be met for a given processing activity:

  • The processor is based in India (an Indian entity, branch or capability centre).
  • The individuals whose data is processed are outside India.
  • The processing happens under a contract with a foreign person, typically the overseas client.

When those conditions hold, the Act switches off most of its obligations: Chapter II except sections 8(1) and 8(5), the whole of Chapter III, and section 16 on cross-border transfers do not apply.

What that removes

Switched offEffect for the vendor
Sections 4–7 (grounds, notice, consent, legitimate uses)No DPDP notice or consent duty for foreign end users
Rest of section 8 (breach intimation, erasure, contact details, grievance)DPDP breach intimation under s.8(6) and Rule 7 does not apply to that data
Sections 9 and 10 (children, SDF duties)Not applicable to that data
Chapter III (rights of Data Principals)Foreign users cannot invoke DPDP access or erasure rights
Section 16No DPDP restriction on sending the data back or onward abroad

What still applies: sections 8(1) and 8(5)

Two obligations survive, and they are not trivial.

Section 8(1): accountability

The Data Fiduciary is responsible for complying with the Act and the rules in respect of any processing undertaken by it or on its behalf by a Data Processor, irrespective of any agreement to the contrary. In outsourcing terms: you cannot contract out of responsibility, and processing done by your own sub-contractors is attributed to you.

Section 8(5): reasonable security safeguards

The Data Fiduciary must protect personal data in its possession or under its control, including processing by its processors, by taking reasonable security safeguards to prevent a personal data breach.

Rule 6 of the DPDP Rules, 2025, in force from 13 May 2027, sets out what reasonable safeguards include at the minimum. Because it elaborates section 8(5), treat it as the benchmark for exempt work too:

  • encryption, obfuscation, masking or virtual tokens (Rule 6(1)(a));
  • access control over computer resources (Rule 6(1)(b));
  • logging, monitoring and review to detect unauthorised access (Rule 6(1)(c));
  • continuity measures such as backups (Rule 6(1)(d));
  • one-year retention of logs and personal data for detection and remediation (Rule 6(1)(e));
  • security provisions in processor contracts (Rule 6(1)(f));
  • technical and organisational measures (Rule 6(1)(g)).

Enforcement survives too

Section 17(1)(d) does not disapply the Board's powers or the penalty Schedule. Failure to take reasonable security safeguards can attract a penalty of up to ₹250 crore per instance, after an inquiry by the Data Protection Board.

Which data in an IT services firm is not exempt?

The exemption is activity-specific. Most Indian IT and BPO firms run several processing activities that fall fully inside the Act.

  1. Employee and contractor data. Payroll, HR records, attendance, background checks, device monitoring and badge logs for staff in India are processed for the firm's own purposes. The legitimate use for employment purposes in section 7 helps, but notice-free processing is limited to that use, and all security, breach, retention and rights obligations apply. See DPDP for HR and employee data.
  2. Indian clients' customers. Work for an Indian bank, telecom or retailer involves Indian Data Principals, so the exemption does not apply. The vendor is usually a Data Processor and the client's DPDP obligations flow down through the contract.
  3. Mixed datasets. A global client's CRM often contains Indian customers. Those records are not within the exemption even if the contract is with a foreign entity.
  4. Recruitment and marketing. Candidate databases, website analytics and sales outreach to Indian prospects are fully in scope.
  5. The firm's own products. A SaaS product sold to Indian users is outside the outsourcing model entirely.

Tag every engagement and dataset by data-subject geography in the inventory so the exemption is claimed only where it genuinely applies.

Are you a Data Fiduciary or a Data Processor?

Under the Act, a Data Fiduciary determines the purpose and means of processing; a Data Processor processes on its behalf. In most delivery contracts the Indian firm is a processor and its client is the fiduciary.

That distinction shapes what you must do:

ScenarioYour roleWhat drives your obligations
Offshore support for a US retailer's US customersProcessorClient contract, foreign law, s.8(1)/8(5) via s.17(1)(d)
Managed services for an Indian insurerProcessorClient's DPDP duties flowed down by contract; Rule 6(1)(f) clauses
Your own HR and payrollFiduciaryFull DPDP Act and Rules
Analytics you run on client data for your own benchmarkingLikely fiduciary for that purposeFull Act, plus contractual restrictions

The last row is the one that catches vendors out. Reusing client data to train an internal model or build a benchmark turns you into a decision-maker about purpose. Get written permission from the client, and assess whether the exemption still applies. More: Data Fiduciary vs Data Processor.

How do client contracts and GDPR interact with the exemption?

The exemption narrows what the DPDP Act demands. It does not change what your client's law or your contract demands.

A European client will usually require an Article 28 GDPR processor agreement and, because India has no EU adequacy decision, Standard Contractual Clauses under Commission Implementing Decision (EU) 2021/914 with a transfer impact assessment. Those terms impose breach notification to the client, assistance with data subject requests, audit rights and sub-processor approval. None of that is displaced by section 17(1)(d).

A workable compliance stance

  • Run a single security baseline that satisfies Rule 6 and the strictest client contract, rather than two standards.
  • Report incidents to clients on contractual timelines, even where DPDP Rule 7 does not apply to that data.
  • Apply CERT-In's 28 April 2022 Directions separately: specified cyber incidents must be reported to CERT-In within 6 hours of noticing, irrespective of the DPDP exemption.

See GDPR for Indian IT services firms and DPAs and SCCs explained.

How should a delivery organisation implement this?

Treat the exemption as a scoping decision that must be documented per engagement.

Engagement scoping record

For each statement of work, record: client entity and country; Data Principal geographies; whether any Indian residents' data is present; your role (fiduciary or processor); the governing data protection terms; and whether s.17(1)(d) is claimed.

Security controls mapped to Rule 6

  • Client-segregated environments, with access granted per project and revoked on roll-off.
  • Virtual desktop infrastructure for agents handling personal data, with copy, print and USB controls.
  • Centralised logs of access to client data, reviewed for anomalies and retained for at least one year.
  • Encryption in transit and at rest, and masking of payment or identity fields in agent screens.
  • Tested backup and recovery for client systems you operate.

Governance

Name an accountable owner for DPDP at the firm level, publish a contact for Data Principals of the firm's own data (Rule 9), and train delivery managers to escalate any scope change that introduces Indian Data Principals.

Further reading on suhasbhairav.com

Before 13 May 2027

Compliance checklist

  1. Classify every engagement by data-subject geography

    Flag any engagement that includes Indian residents' data, because the exemption cannot apply to it.

    Section 17(1)(d)

  2. Document the exemption decision

    Record why all three section 17(1)(d) conditions are met for each exempt engagement.

    Section 17(1)(d)

  3. Apply Rule 6 safeguards to exempt work

    Use encryption, access control, logging, backups and contract clauses as the security baseline.

    Section 8(5); Rule 6

  4. Bring employee data fully into scope

    Prepare notices, retention schedules and breach procedures for HR, payroll and monitoring data.

    Section 7; Rule 7

  5. Retain access logs for one year

    Keep logs of access to client personal data for at least one year for detection and investigation.

    Rule 6(1)(e)

  6. Control reuse of client data

    Prohibit internal reuse of client personal data without written client approval and a fresh scope assessment.

    Section 8(1)

  7. Flow down security terms to sub-contractors

    Include security, breach reporting and audit clauses in every sub-processor agreement.

    Rule 6(1)(f)

  8. Keep CERT-In reporting separate

    Report specified cyber incidents to CERT-In within 6 hours regardless of the DPDP exemption.

    CERT-In Directions, 28 April 2022

Answers

Frequently asked questions

Does the DPDP Act apply to Indian BPOs serving foreign clients?

Partly. Under section 17(1)(d), where an India-based firm processes data of people outside India under a contract with a foreign person, most obligations do not apply. Sections 8(1) and 8(5) still do, so the firm remains accountable and must take reasonable security safeguards, and the Board can impose penalties of up to ₹250 crore for security failures.

Do foreign customers get DPDP rights against an Indian vendor?

No, not for data covered by section 17(1)(d). Chapter III, which contains the rights to access, correction, erasure, grievance redressal and nomination, does not apply to that processing. Those individuals may still have rights under their own country's law, which the client contract will usually require you to support.

Must an Indian IT firm notify the Board of a breach of exempt data?

The DPDP breach intimation duty in section 8(6) and Rule 7 is outside the surviving provisions, so it does not apply to exempt processing. However, contractual and foreign-law notification duties still apply, and CERT-In's directions require reporting of specified cyber incidents within 6 hours of noticing them.

Does the exemption cover our Indian employees' data?

No. Employee data is processed for the firm's own purposes about people in India, so the full Act applies. Section 7 allows processing for employment purposes without consent, but security safeguards, breach intimation, retention limits and Data Principal rights all apply to that data from 13 May 2027.

What if a foreign client's dataset includes Indian customers?

The exemption covers data of Data Principals not within the territory of India. Records of people in India fall outside it, so the client, as Data Fiduciary, owes DPDP duties for those records and you, as processor, must support them under the contract. Segment such data and document how each part is treated.

Is Rule 6 binding on exempt processing?

Rule 6 sets out what reasonable security safeguards include under section 8(5), which survives the exemption. The safest reading is to treat Rule 6's minimum measures as the benchmark for exempt work as well. Where the interpretation matters for a specific engagement, involve counsel, because the point has not yet been tested before the Board.

Legal references and sources

  • Digital Personal Data Protection Act, 2023 — Section 17(1)(d) (official text)
  • Digital Personal Data Protection Act, 2023 — Sections 8(1) and 8(5) (official text)
  • Digital Personal Data Protection Rules, 2025 — Rule 6 (official text)
  • Digital Personal Data Protection Act, 2023 — Schedule (penalties) (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.