DPDP Act 2023Updated 22 November 20269 min read

Who Does the DPDP Act Apply To? Territorial Scope Explained

Section 3 of the DPDP Act decides who is in scope: anyone processing digital personal data in India, and offshore businesses offering goods or services to people in India.

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

Scope provision
Section 3, DPDP Act 2023
Covers
Digital personal data, and non-digital data digitised later
Extra-territorial trigger
Offering goods or services to Data Principals in India
Size threshold
None
Excluded
Personal/domestic purposes; data made public by the Data Principal or under legal obligation
Core obligations apply from
13 May 2027

Quick answer

Under section 3, the DPDP Act applies to anyone processing digital personal data within India, including non-digital data later digitised. It also applies outside India when processing is connected to offering goods or services to Data Principals in India. There is no size or turnover threshold. Personal or domestic use and data made public by the person herself are excluded.

  • Any organisation processing digital personal data in India is in scope, whatever its size, sector or turnover.
  • Foreign companies are covered when processing is connected to offering goods or services to Data Principals in India.
  • Unlike GDPR, DPDP has no standalone monitoring or profiling trigger for offshore processing.
  • Paper records stay outside the Act until they are digitised; once digitised, they are covered.
  • Indian outsourcing firms processing foreign individuals' data under contract get a partial exemption under section 17(1)(d).

Who this is for: Foreign SaaS and consumer apps with Indian users, Indian startups and SMEs, IT services and BPO companies, Legal and compliance teams scoping DPDP programmes, Cloud and infrastructure providers

What does section 3 of the DPDP Act cover?

Section 3 sets the Act's reach through three tests.

1. Processing within India

The Act applies to processing of digital personal data within the territory of India where the data is:

  • collected in digital form, for example through app sign-ups, web forms, API calls, IoT devices or call-centre systems; or
  • collected in non-digital form and digitised subsequently, for example scanned KYC forms, digitised patient files or OCR'd paper applications.

2. Processing outside India

The Act also applies to processing of digital personal data outside India if it is in connection with any activity related to offering goods or services to Data Principals within the territory of India.

3. What is excluded

The Act does not apply to:

  • personal data processed by an individual for any personal or domestic purpose; and
  • personal data made or caused to be made publicly available by the Data Principal herself, or by any other person under a legal obligation in India to publish it.

There is no exemption based on headcount, revenue or number of users. A two-person startup and a listed bank face the same baseline obligations. The heavier duties are reserved for Significant Data Fiduciaries and for the Third Schedule platforms with large user bases.

When does the DPDP Act apply to a foreign company?

A company with no Indian entity, servers or staff is still covered if its processing is connected to offering goods or services to Data Principals in India.

Signals that you are offering to people in India

The Act gives no checklist. These practical indicators make the connection hard to deny:

  • pricing in rupees, or accepting UPI and Indian cards;
  • an India-specific app store listing, website or language version, such as Hindi or another Indian language;
  • marketing campaigns targeted at India;
  • shipping to Indian addresses, or Indian phone number sign-up flows;
  • a material Indian user base that you actively serve.

What is different from GDPR

GDPR Article 3(2) covers non-EU organisations that offer goods or services to people in the EU or monitor their behaviour. DPDP has only the offering limb. An offshore analytics vendor that tracks Indian visitors on behalf of a non-Indian client is not caught by section 3 just because it monitors them. But if the client is itself offering services to people in India, that client is in scope.

No local representative

DPDP does not require an India representative, unlike GDPR Article 27. You must still publish a contact person under Rule 9 and accept rights requests and grievances under Rule 14. Board proceedings run digitally (Rule 20), so offshore fiduciaries should expect to engage with the Board remotely.

Scope scenarios: who is in and who is out

ScenarioIn scope?Why
Indian D2C brand collecting customer data on its websiteYesDigital processing in India
US SaaS company selling subscriptions to Indian businesses, with users' data hosted in the USYesOffering services to Data Principals in India
Hospital in India scanning paper patient files into an EMRYes, from digitisationNon-digital data digitised later
A paper visitor register that is never digitisedNoNot digital personal data
An individual keeping friends' numbers in a personal phoneNoPersonal or domestic purpose
Indian BPO processing UK customers' data for a UK bank under contractPartlySection 17(1)(d) exempts most obligations, but security safeguards still apply
European app with no Indian users whose data is hosted by an Indian vendorPartlyProcessing in India is covered, but the vendor's processing under a foreign contract fits section 17(1)(d)
An Indian employer processing employee HR dataYesSection 7 allows employment purposes without consent, but other obligations apply

The outsourcing rows surprise people. Section 3(a) applies to processing within India whoever the Data Principals are. That is why section 17(1)(d) exists. It carves out processing in India of non-Indian principals' data under a contract with a foreign person. Even then, section 8(1) (overall responsibility) and section 8(5) (reasonable security safeguards) continue to apply.

The outsourcing exemption under section 17(1)(d)

India's IT services and BPO industry processes large volumes of foreign individuals' data. Section 17(1)(d) addresses this directly.

What it covers

Processing of personal data of Data Principals not within the territory of India, by a person in India, under a contract with any person outside India.

What still applies

For such processing, Chapter II (obligations of Data Fiduciaries) does not apply, except section 8(1) and section 8(5). Chapter III (rights of Data Principals) and section 16 (cross-border transfer) also do not apply. In practice that means:

  • the Indian provider must still take reasonable security safeguards, so Rule 6 controls are relevant from 13 May 2027;
  • it remains responsible for compliance in respect of the processing it carries out.

Engineering consequences

  • Tag tenants or datasets by Data Principal location and contract counterparty. The exemption depends on both.
  • Do not assume the exemption covers mixed datasets. A global CRM holding Indian and foreign customers needs separate treatment for the Indian records.
  • Keep the client contract on file showing the foreign counterparty. That is your evidence for the exemption.

Section 17(3) separately lets the Government exempt notified classes of fiduciaries, including startups, from certain provisions. Do not rely on it until a notification covers you. See section 17 exemptions.

Digital, digitised and public data: the material scope

Section 3 only reaches digital personal data, meaning data about an identifiable individual in digital form. Three boundary cases come up repeatedly.

Paper first, digital later

A form filled on paper is outside the Act. Once it is scanned, keyed into a system or photographed into a workflow, it becomes digitised personal data and is covered. Ops teams that photograph documents on phones are digitising them.

Anonymised and aggregated data

The Act covers data about an individual who is identifiable by or in relation to that data. Truly anonymised aggregates fall outside it. Pseudonymised data, such as hashed emails or device IDs linked to accounts, generally remains identifiable and in scope. See what counts as personal data.

Publicly available data

The exclusion covers only data the Data Principal herself made public, or data published under a legal obligation. Data someone else posted about her, leaked datasets and scraped profiles are not automatically excluded. The publicly available data guide covers scraping and AI training.

Not personal data at all

Company data, such as a firm's name, CIN or financials, is not personal data. Individuals' details inside it, such as directors' phone numbers, are.

How to scope your DPDP programme before 13 May 2027

Core obligations under the Act and Rules 3, 5–16, 22 and 23 apply from 13 May 2027. Scope first, because every later control depends on it.

  1. Inventory systems holding data about individuals: production databases, data warehouses, logs, support tools, CRMs, HR systems, backups and AI training sets.
  2. Tag each dataset with four attributes:
    • Is the data digital or digitised?
    • Is it processed in India, or offshore?
    • Do the Data Principals include people in India?
    • Is there a contract with a foreign counterparty, relevant to section 17(1)(d)?
  3. Classify your role per dataset: Data Fiduciary (you decide purpose and means) or Data Processor (on behalf of a client). See fiduciary vs processor.
  4. Flag special regimes: children's data (section 9), and platforms meeting the Third Schedule thresholds (2 crore e-commerce or social media users, or 50 lakh gaming users in India).
  5. Record exclusions and exemptions with written reasoning, such as public data or 17(1)(d). These are your evidence if the Board asks.
  6. Re-scope on change: new markets, a payment method launch or an India language version can bring a foreign product into scope.

Further reading on suhasbhairav.com

Before 13 May 2027

Compliance checklist

  1. Inventory digital personal data

    List every system, including logs, backups and analytics, that stores data about identifiable individuals.

    DPDP Act s.3

  2. Test the offering limb for offshore products

    Document whether pricing, payments, marketing or app listings target people in India.

    s.3(b)

  3. Identify digitisation points

    Find where paper records are scanned or keyed in, since data becomes in scope at that moment.

    s.3(a)

  4. Segregate outsourced foreign data

    Tag datasets processed under contracts with foreign persons for non-Indian principals, and keep Rule 6 security controls on them.

    s.17(1)(d)

  5. Document public data reliance

    Record evidence that the Data Principal herself made the data public before relying on the exclusion.

    s.3(c)(ii)

  6. Assign a scope owner

    Give one person responsibility for re-running scoping when markets, products or vendors change.

    Rule 9

Key dates

  1. DPDP Act receives assent

  2. Rules notified; definitions and Board provisions in force

  3. Section 3 scope and core obligations become enforceable

Answers

Frequently asked questions

Does the DPDP Act apply to companies outside India?

Yes, if their processing is connected to any activity related to offering goods or services to Data Principals in India. A foreign SaaS or e-commerce business selling to Indian users is covered even if it has no Indian entity or servers. Section 3 has no separate monitoring trigger like GDPR's.

Is there a minimum size or turnover for DPDP applicability?

No. The DPDP Act applies to every Data Fiduciary processing digital personal data within its scope, regardless of headcount, revenue or user numbers. Only certain duties scale: Significant Data Fiduciary obligations once notified, and Third Schedule erasure rules for very large e-commerce, gaming and social media platforms.

Does DPDP apply to paper records?

Not while they stay on paper. Section 3 covers digital personal data and personal data collected in non-digital form that is later digitised. Once a paper form is scanned, photographed into a workflow or keyed into a system, the digitised data is covered by the Act.

Does DPDP apply to an Indian company processing data of foreign customers?

Yes, processing within India is covered regardless of where the individuals live. Section 17(1)(d) relaxes this for processing of non-Indian principals' data under a contract with a foreign person. Most obligations and rights are switched off, but sections 8(1) and 8(5), including reasonable security safeguards, still apply.

Is employee data covered by the DPDP Act?

Yes. Employee data is digital personal data, so the Act applies. Section 7 lets employers process it without consent for employment purposes, such as protecting trade secrets or providing benefits. Security, breach notification, retention and other fiduciary obligations still apply.

Does the DPDP Act apply to anonymised data?

The Act covers data about an individual who is identifiable by or in relation to it. Properly anonymised data that cannot identify anyone falls outside it. Pseudonymised data, such as hashed identifiers that can be linked back to an account, is generally still personal data and remains in scope.

Legal references and sources

  • Digital Personal Data Protection Act, 2023 — Section 3 (official text)
  • Digital Personal Data Protection Act, 2023 — Section 17(1)(d) and 17(3) (official text)
  • Digital Personal Data Protection Rules, 2025 — Rule 1 (commencement) (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.