Quick answer
Under the DPDP Act, personal data is any data about an individual who is identifiable by or in relation to that data. The Act regulates digital personal data, meaning data collected digitally or digitised later. Names, phone numbers, device IDs linked to accounts, IP logs, photos and voice recordings all qualify. India has no separate sensitive personal data category.
- Personal data is any data about an individual who is identifiable by or in relation to that data; identifiability is the test.
- Only digital personal data is regulated, including paper data once it is digitised.
- Indirect identifiers such as device IDs, account-linked IP logs and hashed emails usually count as personal data.
- There is no sensitive personal data category, though data type affects SDF designation and penalties.
- Data about companies is not personal data, but data about individuals inside company records is.
Who this is for: Data engineers and architects, Product managers designing data collection, Privacy and compliance teams building data inventories, AI and ML teams handling training data, Security teams classifying data
How does the DPDP Act define personal data?
Section 2 of the Digital Personal Data Protection Act, 2023 defines personal data as any data about an individual who is identifiable by or in relation to such data. Digital personal data is personal data in digital form.
Read together with section 3, the Act regulates digital personal data, whether collected digitally or collected on paper and digitised later.
The two-part test
- Is it about an individual? The Act protects natural persons, called Data Principals. Data about a company, partnership or government body is not personal data in itself.
- Is the individual identifiable by or in relation to the data? The individual need not be named. It is enough that the data, alone or combined with other data available to the fiduciary, can single her out.
What is "data"?
Section 2 defines data broadly: a representation of information, facts, concepts, opinions or instructions suitable for communication, interpretation or processing by humans or by automated means. That includes:
- structured fields, free text and chat transcripts;
- images, video, voice recordings and biometric templates;
- logs, events and telemetry;
- inferences and scores, such as a credit score or a churn prediction attached to a user.
Opinions about a person count too. A support agent's note saying a customer "seems financially stressed" is personal data about that customer.
Personal data examples: common identifiers and grey areas
| Data | Personal data? | Notes |
|---|---|---|
| Name, email, mobile number, address | Yes | Direct identifiers |
| Aadhaar, PAN, passport or licence number | Yes | Also subject to their own laws, such as the Aadhaar Act; check the sector rules |
| Customer ID, enrolment ID, application reference number | Yes | Rule 14(5) lists these as identifiers that identify the Data Principal |
| Device ID or advertising ID linked to an account | Yes | Identifiable in relation to account data |
| IP address in server logs tied to sessions or accounts | Usually | Identifiable when it can be linked to a user |
| Hashed or tokenised email | Usually | Pseudonymised data is still identifiable if you hold or can obtain the key |
| Photos, CCTV footage, voice notes | Yes, if a person can be recognised | Covered once digital |
| Location trails | Yes | Often uniquely identifying even without a name |
| Aggregated counts, such as "1,240 users in Pune" | No, if truly aggregated | Watch for small cells that single people out |
| Company CIN, GSTIN, revenue | No | Not about an individual, though a sole proprietor's details may be |
| Model weights trained on user data | Depends | In scope if the model can output identifiable information; assess per model |
Rule 2(1)(c) defines user account broadly. It covers profiles, pages, handles, email addresses, mobile numbers and other presences through which the Data Principal accesses a service. Those handles are themselves personal data and are the channel for Rule 7 breach intimations and Rule 8 erasure notices.
Is there a sensitive personal data category in DPDP?
No. The DPDP Act treats all personal data under one regime. There is no list of special categories like the GDPR's, and no "sensitive personal data or information" list like the SPDI Rules made under section 43A of the IT Act.
The SPDI Rules transition
Section 44(2) of the DPDP Act omits section 43A of the IT Act, the legal basis of the SPDI Rules 2011. That omission operates from 13 May 2027. Until then, the SPDI Rules continue to apply to bodies corporate handling sensitive personal data, such as passwords, financial information, health data and biometrics. Run both regimes in parallel until commencement.
Where sensitivity still matters
- SDF designation (section 10): the Central Government weighs the volume and sensitivity of data processed when notifying Significant Data Fiduciaries.
- Penalties (section 33(2)): the Board considers the type and nature of the personal data affected.
- Children (section 9): children's data carries its own obligations and a separate penalty entry of up to ₹200 crore.
- Sector law: health, payments, insurance and telecom regulators impose their own controls.
Practical approach
Keep a sensitivity tier in your data classification even though the Act does not require one. It drives encryption scope under Rule 6, access controls, breach severity triage and penalty mitigation.
Identifiability in real systems: logs, analytics and pseudonymisation
Engineers often assume data is "not personal" because it has no name in it. Under DPDP the question is whether the individual is identifiable by or in relation to the data. Context matters.
Logs and telemetry
Request logs with user IDs, IPs, user agents and timestamps are personal data. Rule 6(1)(c) requires such logs for security visibility. Rule 8(3) requires personal data, associated traffic data and processing logs to be retained for at least one year. So your logs are both a compliance obligation and a store of personal data that needs protection. See one-year log retention.
Pseudonymisation
Tokenising or hashing identifiers is a recognised safeguard. Rule 6(1)(a) names encryption, obfuscation, masking and virtual tokens mapped to personal data. It reduces risk, but tokenised data remains personal data where the mapping exists.
Anonymisation
The Act does not define anonymisation. Data from which no individual can be identified falls outside "personal data". Be strict about this:
- remove direct and indirect identifiers;
- suppress small groups and rare attribute combinations;
- check linkability against other datasets you hold;
- document the method and re-test when datasets change.
Analytics and AI
Event streams keyed to user or device IDs, embeddings derived from user content, and fine-tuning datasets built from support tickets are all typically personal data. Model outputs that reproduce identifiable details are processing of personal data too.
Whose data is it? Data Principals, children and representatives
The Data Principal is the individual the personal data relates to. Section 2 extends the term in two cases:
- Children. For a child (under 18), the Data Principal includes the parents or lawful guardian. Rule 10 governs how their verifiable consent is obtained.
- Persons with disability with a lawful guardian. The Data Principal includes the guardian acting on her behalf. Rule 11 requires due diligence that the guardian was appointed by a court, a designated authority under section 15 of the RPwD Act 2016, or a local level committee under section 13 of the National Trust Act 1999.
Deceased persons and nominees
Section 14 lets a Data Principal nominate another individual to exercise her rights in the event of death or incapacity. Rule 14(4) operationalises this through the fiduciary's terms of service. See right to nominate.
Employees, customers, prospects
All are Data Principals. Their data is personal data whether it sits in an HRMS, a CRM or a marketing list. The lawful ground may differ: employment purposes under section 7, or consent for marketing. The definition does not change.
Business contacts
The work email and phone number of an individual at a client company are personal data about that individual. B2B companies cannot treat their CRM as outside the Act.
How to classify personal data before 13 May 2027
A personal data inventory is the foundation for Rule 3 notices, Rule 6 safeguards, Rule 7 breach scoping and Rule 14 access requests.
- Discover. Scan databases, object stores, warehouses, logs, SaaS tools and backups for identifiers: emails, phone numbers, Aadhaar and PAN patterns, names, addresses and device IDs.
- Classify each field into three groups: direct identifiers, indirect identifiers, and derived data (scores, inferences, embeddings).
- Link to a Data Principal type: customer, child, employee, vendor contact or other.
- Record the purpose and lawful ground (consent or a section 7 legitimate use), and the itemised description for the Rule 3 notice.
- Tier by sensitivity for internal controls: financial, health, children's, identity documents and precise location at the top.
- Note location and processors, for cross-border and processor contract obligations.
- Set retention that respects both the purpose-based erasure duty in section 8(7) and the Rule 8(3) one-year minimum.
Keep the inventory machine-readable, for example as a YAML or JSON schema registry in the repo, so that new fields cannot ship without a classification.
Further reading on suhasbhairav.com
Before 13 May 2027
Compliance checklist
Scan for identifiers across all stores
Include logs, backups, analytics and AI datasets, not just primary databases.
DPDP Act s.2, s.3
Classify direct, indirect and derived data
Treat pseudonymised and inferred data as personal data unless it is truly anonymised.
Rule 6(1)(a)
Map Data Principal types
Flag children and guardian-represented persons, because they trigger Rule 10 and Rule 11 flows.
Rules 10–11
Keep SPDI controls until commencement
Continue section 43A and SPDI Rules compliance for sensitive data until 13 May 2027.
DPDP Act s.44(2)
Document your anonymisation method
Record the techniques and re-identification tests used before treating a dataset as outside the Act.
DPDP Act s.2
Gate new fields through classification
Require a data classification entry in code review before new personal data fields reach production.
Rule 6(1)(g)
Key dates
Act definitions (s.2) and Rule 2 in force
Core obligations apply; IT Act s.43A and the SPDI Rules basis omitted
Answers
Frequently asked questions
What is personal data under the DPDP Act?
What is personal data under the DPDP Act?
Personal data is any data about an individual who is identifiable by or in relation to that data. The Act regulates the digital form of such data, including paper data that is later digitised. Names, contact details, identifiers, photos, location and account-linked logs all count.
Is an IP address personal data under DPDP?
Is an IP address personal data under DPDP?
Usually, yes. An IP address in logs that can be linked to a session, account or device identifies an individual in relation to that data. IP logs are also part of the traffic data and processing logs that Rule 8(3) requires fiduciaries to retain for at least one year, so protect them accordingly.
Does the DPDP Act have a category of sensitive personal data?
Does the DPDP Act have a category of sensitive personal data?
No. Unlike the GDPR and the SPDI Rules, the DPDP Act has no separate sensitive data category. Sensitivity still matters: it influences Significant Data Fiduciary designation and penalty amounts. The SPDI Rules continue until section 43A of the IT Act is omitted from 13 May 2027.
Is anonymised data covered by DPDP?
Is anonymised data covered by DPDP?
Data from which no individual can be identified is not personal data, so it falls outside the Act. The Act does not define anonymisation, so document your method and test re-identification risk. Pseudonymised data, such as tokenised or hashed identifiers you can link back, generally remains personal data.
Is business contact information personal data in India?
Is business contact information personal data in India?
Yes. A work email, direct phone number or LinkedIn profile of an individual at another company is data about an identifiable individual. B2B CRMs and sales prospecting lists therefore fall under the DPDP Act, even though company-level data such as a CIN or revenue does not.
Is data about a deceased person covered by DPDP?
Is data about a deceased person covered by DPDP?
The Act protects identifiable individuals and gives a Data Principal the right under section 14 to nominate someone to exercise her rights in the event of her death or incapacity. Fiduciaries should honour valid nominations made under their terms of service, as Rule 14(4) describes.
Legal references and sources
- Digital Personal Data Protection Act, 2023 — Section 2 (definitions) and section 3 (official text)
- Digital Personal Data Protection Act, 2023 — Section 44(2) (omission of IT Act s.43A) (official text)
- Digital Personal Data Protection Rules, 2025 — Rule 2 (user account, verifiable consent) (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
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.
Related guides
- DPDP Act 2023Who Does the DPDP Act Apply To? Territorial Scope ExplainedSection 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.
- DPDP Act 2023DPDP and Publicly Available Data: What Scrapers and AI Teams Must KnowSection 3(c)(ii) excludes personal data made public by the Data Principal herself or under a legal obligation. What that means for web scraping, AI training and data enrichment.
- DPDP Act 2023DPDP Act 2023 Explained in Plain EnglishA plain-English guide to India's Digital Personal Data Protection Act, 2023: who it covers, what it requires, penalties up to ₹250 crore, and what applies from 13 May 2027.
- DPDP Rules 2025DPDP Reasonable Security Safeguards Under Rule 6Rule 6 lists the minimum security safeguards every Data Fiduciary must take from 13 May 2027. Failure can attract a penalty of up to ₹250 crore, the highest in the DPDP Act.
- DPDP Rules 2025DPDP One-Year Log Retention: What to Keep and for How LongTwo DPDP rules require one year of retention: Rule 6(1)(e) for security logs and Rule 8(3) for personal data, traffic data and processing logs. What to keep, where, and how to protect it.
- DPDP Act 2023Data Fiduciary vs Data Processor Under the DPDP ActWhoever decides why and how personal data is processed is the Data Fiduciary and carries the liability; the Data Processor acts on its behalf under contract.