Skip to main content

The 3rd and main DPDP commencement date is computed as 13 May 2027, which is interpretation until officially confirmed.

Sources last verified on 28 October 2026. Methodology

Does the DPDP Act have a sensitive personal data category? No

Definitions

By · Primary sources verified by dpdprules.orgPublished · Last reviewed 8 min read

Jump to sources

Does the DPDP Act classify sensitive personal data separately?

The short answer

No. The DPDP Act creates no separate sensitive personal data category. Section 2(t) defines personal data as any data about an individual who is identifiable by or in relation to that data. The exact word sensitive does not appear in the Act. Sensitivity appears in section 10(1)(a), but only as one factor the Central Government may assess when deciding whether to notify a Data Fiduciary or class as a Significant Data Fiduciary. Section 3 contains clauses (a), (b) and (c), so section 3(d) does not exist. Additional obligations can arise from notified Significant Data Fiduciary status under section 10, from processing personal data of children or persons with disability who have a lawful guardian under section 9, and from Rule 8 read with the Third Schedule for specified classes and user thresholds. Those mechanisms do not create a sensitive data tier. Sections 9 and 10 are in the Act's 18 month group. Rule 8 is in the Rules' 18 month group, and the Third Schedule operates through Rule 8. The common date is computed as 13 May 2027, interpretation until officially confirmed. Section 2 is already in force.

More answered questions →

Diagram: No sensitive personal data tier in the DPDP Act. The same diagram appears further down this article, where it is described in full.

Open the DPDP sensitive data comparison at full size

The DPDP Act gives personal data 1 definition and creates no sensitive data tier. Section 3(d) does not exist. The precise answer is not that every record has identical duties. Sections 9 and 10 add duties for different triggers, Rule 8 creates retention rules tied to class and purpose, and section 17 can disapply provisions. None of those mechanisms classifies health, biometric or financial data as sensitive personal data under the DPDP Act. Those sections and Rule 8 are in 18 month groups, computed as 13 May 2027, interpretation until officially confirmed.

DPDP comparison: GDPR Article 9 has special categories. The DPDP Act has 1 definition in section 2(t) and no sensitivity tier. Section 3 ends at clause (c), so section 3(d) does not exist. Section 9, section 10, section 17 and Rule 8 can change duties or scope without creating a data tier. Their 18 month groups are computed to start 13 May 2027, interpretation until officially confirmed. Section 2 is in force.

The exact word sensitive is not in the Act

A case insensitive whole word search of the English Gazette text of the Digital Personal Data Protection Act 2023 returns 0 matches for sensitive. The related word sensitivity appears once, in section 10(1)(a).

Personal data is defined a single time:

DPDP Act 2023, s. 2(t) · Definitions · verbatim

"“personal data” means any data about an individual who is identifiable by or in relation to such data"

That definition names no data type or sensitivity tier. A blood group and a shipping address can both satisfy the same definition. What follows can still differ because of the Data Principal, the Data Fiduciary's status, the purpose and context of processing, and the routes in section 17. Applying the definition to 2 fields almost every business holds is worked through in is a name or an email address personal data.

There is no section 3(d)

Section 3 is the application provision. It has 3 clauses:

ClauseWhat it does
3(a)Applies the Act to processing of digital personal data within India, whether collected in digital form or digitised later
3(b)Extends it to processing outside India in connection with any activity related to offering of goods or services to Data Principals within India
3(c)Excludes personal data processed by an individual for any personal or domestic purpose, and personal data made publicly available either by the Data Principal herself or by any other person who is under an obligation in Indian law to make it public

After clause (c)(ii)(B) and its illustration, the Gazette moves straight into Chapter II and section 4. There is no clause (d), so any article that cites section 3(d) for a sensitive data category is citing a provision that does not exist. That is a useful test to apply to a DPDP source: check the number, not just the claim.

Where sensitivity really appears

Section 10(1) lets the Central Government notify a Data Fiduciary, or a class of them, as a Significant Data Fiduciary after assessing relevant factors. The first listed factor is:

DPDP Act 2023, s. 10(1) · Additional obligations of Significant Data Fiduciary · verbatim

"the volume and sensitivity of personal data processed"

Sensitivity is a factor in assessing a Data Fiduciary for notification. It does not create a class of data and attaches no duty by itself. Section 10 duties require a Central Government notification of a Data Fiduciary or class as Significant Data Fiduciary.

No such notification was located in this site's source registry or timeline, or in MeitY's published document library when that library was enumerated on 26 October 2026. The live enumeration held 1,605 records and the same 19 DPDP records as the archived capture, with none titled as a notification under section 10(1). That is a bounded search result, not a certified negative. The eGazette portal was not checked. Section 10 itself has not commenced, and on this site's reading a notification under that power could not take effect before section 10 does. G.S.R. 843(E) places section 10 in the 18 month group, computed as 13 May 2027, interpretation until officially confirmed.

Even after commencement, section 17 remains relevant. Section 17(3) allows the Central Government to notify certain Data Fiduciaries or classes, including startups, so that section 10 and the other listed provisions do not apply. Section 17(5) creates a separate, time limited notification power that can disapply any provision for a Data Fiduciary or class. Those are exemption routes, not sensitive data categories.

Processing health records can enter the sensitivity factor in a Government assessment under section 10(1). The section states no threshold and no automatic result. It does not put health records into a statutory category. What can apply to a hospital or health app is set out in the DPDP Act for hospitals, clinics and health apps.

What changes the result without creating a data tier

The framework changes duties and scope through several mechanisms. None asks whether the data belongs to a statutory sensitive category.

MechanismWhat changesBoundary
Section 9Section 9(1) requires verifiable consent before processing personal data of a child or a person with disability who has a lawful guardian. Section 9(2) bars processing likely to cause a detrimental effect on a child's well being. Section 9(3) bars tracking or behavioural monitoring of children and targeted advertising directed at children.Section 9(4), implemented by Rule 12 and the Fourth Schedule, disapplies sections 9(1) and 9(3) for stated classes, purposes and conditions. Section 9(5) creates a separate notification route for sections 9(1) and 9(3). Neither route reaches section 9(2). Applicable parts of section 17 can reach section 9 more broadly.
Section 10A Government notification can make a Data Fiduciary or class a Significant Data Fiduciary after assessment of relevant factors, including volume and sensitivity. Section 10 then adds a Data Protection Officer with 4 stated features, an independent data auditor, a Data Protection Impact Assessment, audit and other measures.Notification is required. Sections 17(3) and 17(5) provide separate notification routes that can disapply section 10.
Rule 8Rule 8(1) and the Third Schedule create a 3 year inactivity period for 3 named classes at stated user thresholds and for stated purposes. Rule 8(2) requires a warning at least 48 hours before the Rule 8 period completes. Rule 8(3) creates a separate minimum 1 year retention period for the purposes in the Seventh Schedule.The Third Schedule does not govern all Data Fiduciaries or all purposes. The Rule 8(3) floor turns on Seventh Schedule purposes, not data sensitivity.
Section 17Section 17 can disapply Chapter II provisions subject to its stated carveouts, the Act as a whole, or named provisions in the processing contexts and notification routes it states.Its routes turn on processing context, purpose, actor or notification. They do not create a sensitive data category.

The timing is common but the legal routes are not. G.S.R. 843(E) places sections 3, 9, 10 and 17 in the Act's 18 month group. Rule 1(4), as corrected by G.S.R. 892(E), places Rule 8 and Rule 12 in the Rules' 18 month group. Computed from the printed publication dates, the common calendar date is 13 May 2027, interpretation until officially confirmed. Section 2 is already in force. The full status is set out in what is in force in 2026.

Why the myth is so persistent

2 reasons, both understandable.

The GDPR does have special categories. Article 9(1) of Regulation (EU) 2016/679 names personal data revealing racial or ethnic origin, political opinions, religious or philosophical beliefs or trade union membership, plus genetic data, biometric data for uniquely identifying a natural person, health data, and data concerning sex life or sexual orientation. It states a prohibition on processing that data. Article 9(2) lists routes under which paragraph 1 does not apply, Article 9(3) adds a professional secrecy condition to the paragraph 2(h) route, and Article 9(4) permits Member States to add conditions for genetic, biometric or health data.

That comparison was read on 26 October 2026 from the official OJ text, CELEX 32016R0679, served by the Publications Office Cellar resource for the English expression. It is an orientation comparison. That GDPR classification does not create a DPDP duty under Indian law.

India's own pre DPDP privacy vocabulary is the other source of the habit. Rule 3 of the Information Technology (Reasonable security practices and procedures and sensitive personal data or information) Rules, 2011 creates a sensitive personal data or information category for those Rules in 8 clauses and a proviso. The official Gazette print is on file and is read in full in the SPDI Rules 2011 and the DPDP Act.

Section 44(2)(a) of the DPDP Act directs the omission of section 43A of the Information Technology Act 2000, and section 44(2)(c) directs the omission of the rule making power in section 87(2)(ob). Those changes have not commenced. Section 44(2) is in the Act's 18 month group, computed as 13 May 2027, interpretation until officially confirmed. Section 43A and its current remedy are worked through in can I sue under the DPDP Act.

Neither the GDPR comparison nor the older Indian vocabulary changes the DPDP text. Carrying a sensitive data tier across without a separate DPDP map can overemphasise data type and miss the rules tied to scope, role, the Data Principal, Significant Data Fiduciary notification, purpose and exemptions.

What this means in practice

A sensitivity tier can help manage risk, but it is not a DPDP legal classification and cannot replace a provision by provision map. Start with section 3 scope and section 17. Identify whether the organisation is a Data Fiduciary or Data Processor for each activity. Then map the applicable basis, notice, section 8 duties, rights, section 9 duties, any section 10 notification, and the Rule 8 route.

Sensitivity is still worth recording as an internal risk input. Section 10(1)(a) expressly names it as 1 assessment factor. Section 8(5) requires reasonable security safeguards, but it does not prescribe a sensitivity tier or a safeguard matrix. Treating the classification as risk practice rather than statutory text keeps the 2 ideas separate.

What to do

Work out what applies to your organisation with the applicability checker and your position for a given activity with the role and actor checker. The official text is at Section 3, Section 9, Section 10 and Section 17, and the definition itself at Section 2. For the GDPR mapping, see DPDP vs GDPR; for the notification factors and the invented thresholds that circulate alongside them, see Significant Data Fiduciary explained.

Section 3, application of the Act →Is a name or email address personal data? →Significant Data Fiduciary: factors, not thresholds →DPDP vs GDPR: the differences that matter →Children's data: the section 9 duties and the Rule 12 exemptions →DPDP for healthcare →

Personal dataDefinitionsCorrectionsHealthcare

Share this: