What are the exemptions under the DPDP Act?
DPDP Act exemptions are set out in Section 17 of the 2023 Act. Section 17(1) switches off most duties for six purposes, such as legal claims, crime prevention and approved mergers, but security safeguards still apply. Section 17(2) takes notified State security processing and standard-compliant research outside the Act. Startups are exempt only if notified under Section 17(3).
Section 17 has five sub-sections, and they work in different ways. Two apply by themselves when the facts fit (Sections 17(1) and 17(4)); the rest need the Central Government to issue a notification first (Sections 17(2)(a), 17(3) and 17(5)), or need you to meet prescribed standards (Section 17(2)(b) with Rule 16). Section 17 comes into force with the main duties on 13 May 2027 (G.S.R. 843(E)). For the whole Act on one page, see the DPDP Act, 2023 explained.
When does the DPDP Act not apply at all?
Before any exemption, check scope. Under Section 3, the Act covers digital personal data processed in India, whether it was collected digitally or collected on paper and digitised later, and processing outside India that is connected to offering goods or services to people in India. Section 3(c) then leaves out two kinds of data entirely:
- personal data processed by an individual for a personal or domestic purpose (Section 3(c)(i));
- personal data made publicly available by the person it relates to, or by someone under a legal duty to publish it (Section 3(c)(ii)). The Act's own illustration is a blogger who shares her own personal data on social media.
Paper records that are never digitised also fall outside the Act, because Section 3(a) covers only digital personal data. These are limits on scope, not exemptions, so nothing needs to be notified for them to apply.
What does Section 17(1) exempt, and what still applies?
Section 17(1) switches off Chapter II (the Data Fiduciary's obligations, Sections 4 to 10) except Sections 8(1) and 8(5), all of Chapter III (the Data Principal's rights and duties, Sections 11 to 15) and Section 16 on transfers outside India, where processing falls under one of six clauses:
| Clause | Processing that is exempt | Everyday example |
|---|---|---|
| 17(1)(a) | Necessary to enforce a legal right or claim | Using a customer's records to recover an unpaid invoice in court |
| 17(1)(b) | By a court, tribunal or other body for judicial, quasi-judicial, regulatory or supervisory functions | A regulator reviewing records in an inspection |
| 17(1)(c) | To prevent, detect, investigate or prosecute an offence or a contravention of any law in India | Analysing account data to investigate payment fraud |
| 17(1)(d) | By a person in India, of people outside India, under a contract with a person outside India | An Indian support centre handling a US client's US customers |
| 17(1)(e) | Necessary for a merger, amalgamation, demerger, arrangement or similar scheme approved by a court, tribunal or competent authority | Moving customer data in an NCLT-approved merger |
| 17(1)(f) | To ascertain the finances, assets and liabilities of a person who has defaulted on a loan from a financial institution, within other disclosure laws | A bank checking a defaulting borrower's assets (the Act's own illustration) |
Two duties survive every Section 17(1) exemption. Under Section 8(1), the Data Fiduciary stays responsible for compliance, including for processing done by its Data Processor. Under Section 8(5), it must still take reasonable security safeguards to prevent a personal data breach, and failing that duty carries a penalty of up to ₹250 crore (Schedule, item 1). Other laws also keep applying, because the Act is in addition to them (Section 38(1)). For what reasonable safeguards look like, see Rule 6 security safeguards.
Which processing is fully outside the DPDP Act under Section 17(2)?
Section 17(2) is the only place where the whole Act stops applying, and it covers two cases. First, processing by an instrumentality of the State that the Central Government notifies, in the interests of the sovereignty and integrity of India, the security of the State, friendly relations with foreign States, public order, or preventing incitement to a cognizable offence about any of these, along with the Central Government's processing of data that instrumentality gives it (Section 17(2)(a)).
Second, processing necessary for research, archiving or statistical purposes, if the data is not used to take any decision specific to a Data Principal and the processing meets prescribed standards (Section 17(2)(b)). Rule 16 of the DPDP Rules 2025 sets those standards in the Second Schedule. In short, the processing must be lawful, limited to the data needed for the purpose, reasonably accurate, kept only as long as needed or required by law, protected by reasonable security safeguards (including at Data Processors), and accountable to whoever decides its purpose and means.
The research route is narrow. Product analytics that feeds a recommendation, a credit score or any decision about one person is not covered, because the condition on decisions specific to a Data Principal fails.
Are startups exempt from the DPDP Act?
No, not unless the government notifies them. Section 17(3) lets the Central Government, having regard to the volume and nature of personal data processed, notify Data Fiduciaries or classes of them, including startups, to whom these provisions will not apply:
- Section 5: the privacy notice given with a request for consent;
- Section 8(3): keeping data complete, accurate and consistent when it is used for a decision or shared with another Data Fiduciary;
- Section 8(7): erasing data once consent is withdrawn or the purpose is served;
- Section 10: the extra duties of a Significant Data Fiduciary;
- Section 11: the right to a summary of the data processed and who it was shared with.
For this sub-section, a "startup" is a private limited company, partnership firm or LLP incorporated in India that is eligible for, and recognised under, the criteria of the government department that handles startups. Even a notified startup would still need valid consent (Section 6), security safeguards (Section 8(5)), breach reporting (Section 8(6)) and a contact for questions (Section 8(9)). The DPDP Rules 2025 do not mention startups, and as of 17 November 2026 we found no notification under Section 17(3).
How is the government treated under the DPDP Act?
Government bodies are Data Fiduciaries like anyone else, with three kinds of relief. Notified instrumentalities fall outside the Act for security and public-order purposes (Section 17(2)(a)). For any other processing by the State, Section 17(4) removes the erasure duty in Section 8(7) and the erasure right in Section 12(3), and also the correction right in Section 12(2) where the processing does not involve a decision that affects the person. And before five years from the Act's commencement, the Central Government may notify that any provision will not apply to specified Data Fiduciaries for a set period (Section 17(5)).
When the State processes data to give a subsidy, benefit, service, certificate, licence or permit, it can use the legitimate use in Section 7(b) and must follow the Second Schedule standards (Rule 5). See legitimate uses under Section 7.
Are there exemptions for children's data?
Yes, but they sit in Section 9 and Rule 12, not Section 17. Rule 12 lifts verifiable parental consent (Section 9(1)) and the ban on tracking, behavioural monitoring and targeted advertising (Section 9(3)) for the classes and purposes in the Fourth Schedule, within the conditions it sets. Part A names five classes: clinical and mental health establishments and healthcare professionals, allied healthcare professionals, educational institutions, crèches and child day care centres, and transport providers engaged by schools or crèches. Part B lists six purposes, including real-time location tracking for a child's safety, creating an email-only account, and confirming that a user is not a child under Rule 10. Section 9(2), the duty not to cause a detrimental effect on a child's well-being, is not lifted. Details are in children's data under the DPDP Act.
Which DPDP exemption applies to you? All routes in one table
Every route out of some or all DPDP duties, what it switches off, what still applies and whether it needs a government notification:
| Route | What it switches off | What still applies | Automatic? |
|---|---|---|---|
| Personal or domestic use, Section 3(c)(i) | The whole Act | Nothing under the Act | Yes |
| Data made public by the person or under law, Section 3(c)(ii) | The whole Act, for that data | Nothing under the Act | Yes |
| Six purposes, Section 17(1)(a) to (f) | Chapter II, Chapter III and Section 16 | Sections 8(1) and 8(5), and other laws | Yes, if the facts fit |
| State security and public order, Section 17(2)(a) | The whole Act | Nothing under the Act | No: the instrumentality must be notified |
| Research, archiving, statistics, Section 17(2)(b), Rule 16 | The whole Act | The Second Schedule standards | Yes, if the standards are met |
| Startups and other notified Data Fiduciaries, Section 17(3) | Sections 5, 8(3), 8(7), 10 and 11 | Everything else | No: needs a notification |
| Any State processing, Section 17(4) | Sections 8(7), 12(3), and 12(2) where no decision is made | Everything else | Yes |
| Any provision, Section 17(5) | Whatever the notification names | Everything else | No: needs a notification, within five years |
| Children's data, Section 9(4), Rule 12, Fourth Schedule | Sections 9(1) and 9(3) for listed classes and purposes | Section 9(2) and the rest of the Act | Yes, within the Schedule's conditions |
A simple decision rule follows from the table:
- Is it digital personal data processed in India, or processed abroad in connection with offering goods or services to people in India? If not, the Act does not apply.
- Is it personal or domestic use, or data the person made public themselves? If yes, it is outside the Act.
- Does the processing fit one of the six Section 17(1) clauses exactly? If yes, keep accountability and security safeguards, and drop the rest for that processing only.
- Is it research or statistics with no decision about any one person? If yes, meet the Second Schedule standards and record that you do.
- Otherwise, assume every duty applies unless an official notification names you.
What does this look like for a real business?
This is a made-up example. "LedgerLeaf" is a fictional Bengaluru SaaS startup, recognised as a startup and with 40 staff, that sells invoicing software to Indian shops and also runs customer support for one US client.
| Processing | Exemption? | Why |
|---|---|---|
| Indian shop owners' accounts and invoices | No | Startup recognition alone exempts nothing; no Section 17(3) notification covers it |
| Support tickets from the US client's US customers | Partly, Section 17(1)(d) | A person in India, data of people outside India, under a contract with a person outside India; Sections 8(1) and 8(5) still apply |
| A court case to recover fees from a shop that stopped paying | Partly, Section 17(1)(a) | Only the data necessary to enforce the claim; security safeguards still apply |
| Monthly usage statistics shared at an industry event | Possibly, Section 17(2)(b) | Only if no decision about any user is taken from it and the Second Schedule standards are met |
| The same usage data used to target upgrade offers at each user | No | A decision specific to each person, so the research route fails |
LedgerLeaf still needs consent and a notice for its Indian users, a breach plan and reasonable security safeguards across all of it. The exemptions narrow the work for two data sets; they do not remove the programme.
How do you check and record a DPDP exemption?
- List each processing activity separately in your record of processing; exemptions apply to processing, not to a whole company.
- For each one, name the exact clause you rely on, such as Section 17(1)(d), and write one line on why the facts fit.
- For a notification-based route (Section 17(2)(a), 17(3) or 17(5)), keep the Gazette reference; without one, do not rely on it.
- Keep reasonable security safeguards and named accountability for every exempt activity (Sections 8(1) and 8(5)).
- For research or statistics, record how each Second Schedule standard is met and confirm the output is never used for decisions about one person.
- Review the list when your processing changes, and before Section 17 applies on 13 May 2027.
What are the common myths about DPDP exemptions?
- Myth: "Small businesses are exempt." The Act has no size threshold; only notified Data Fiduciaries can be relieved under Section 17(3).
- Myth: "A recognised startup is automatically exempt." Recognition only makes a company eligible to be notified; the relief needs a notification and covers five provisions, not the whole Act.
- Myth: "Public data is free to use." Section 3(c)(ii) excludes only data made public by the person or under a legal duty, not data someone else posted.
- Myth: "Exempt processing needs no security." Section 8(5) survives every Section 17(1) exemption, with a penalty of up to ₹250 crore. See DPDP Act penalties.
- Myth: "Calling it research makes analytics exempt." The data must not be used for a decision specific to a person, and the Second Schedule standards apply.
- Mistake: one exemption for the whole company. The clauses cover particular processing; the rest of your data keeps every duty. Our DPDP compliance checklist covers what that means.
GRC-Flow's AI GRC Analyst answers DPDP questions, such as whether a Section 17 exemption fits a processing activity, with the provision it relies on, and a person on your team decides. To see where your website stands on DPDP today, run the free DPDP website check. No tool can guarantee compliance.
This guide is general information about the DPDP Act and Rules, not legal advice.
Frequently asked questions
Who is exempted from the DPDP Act?
No type of business is exempt by default. Section 17 exempts certain kinds of processing: six purposes in Section 17(1), such as legal claims, crime prevention and approved mergers; State security processing that the government notifies and qualifying research under Section 17(2); and any Data Fiduciaries the government later notifies under Section 17(3) or 17(5).
Is the DPDP Act applicable to startups and small businesses?
Yes. The Act has no turnover or headcount threshold, so any business processing digital personal data in India is covered (Section 3). Section 17(3) lets the government exempt notified startups from Sections 5, 8(3), 8(7), 10 and 11, but the DPDP Rules 2025 contain no such notification, and we found none as of 17 November 2026.
Does the DPDP Act apply to publicly available personal data?
Only some public data is outside the Act. Section 3(c)(ii) excludes personal data made public by the person it relates to, or by someone legally required to publish it. Data that a third party has posted, or data you scraped from a site, is not excluded on that ground alone.
Does the DPDP Act apply to research and statistics?
Not when the processing is necessary for research, archiving or statistical purposes, the data is not used to take a decision specific to a person, and the processing meets the Second Schedule standards (Section 17(2)(b), Rule 16). Those standards include lawful processing, data minimisation, reasonable accuracy, limited retention, security safeguards and accountability.
Does the DPDP Act apply to the government?
Yes, with carve-outs. A State instrumentality the Central Government notifies for sovereignty, security, public order and related interests is outside the Act (Section 17(2)(a)). For other State processing, Section 17(4) removes only the erasure duties in Sections 8(7) and 12(3), and the correction right in Section 12(2) where no decision about the person is made.
Sources
- The Digital Personal Data Protection Act, 2023 (India Code)
- Digital Personal Data Protection Rules, 2025 (G.S.R. 846(E), Gazette text)
- PIB: Digital Personal Data Protection Rules, 2025
- Taxmann: Exemptions under the DPDP Act
This guide explains the law in general terms and is not legal advice. Check specific situations with a qualified lawyer.