Quick answer
Rule 2(1) of the DPDP Rules, 2025 defines four terms: "Act" (the DPDP Act, 2023), "techno-legal measures" (as used in Rules 20 and 22), "user account" (the online account, including profiles, pages, handles, email address and mobile number) and "verifiable consent" (consent under Rule 10 or 11). Rule 2(2) imports every other definition from the Act. Rule 2 has applied since 13 November 2025.
- Rule 2 has been in force since 13 November 2025, so its definitions already govern how the rest of the Rules will be read.
- "User account" is broad: it includes profiles, pages, handles, email addresses, mobile numbers and similar presences used to access a service.
- "Verifiable consent" means only parental consent under Rule 10 or lawful guardian consent under Rule 11, not ordinary user consent.
- "Techno-legal measures" is tied to the Board and Appellate Tribunal running proceedings digitally under Rules 20 and 22.
- Many operational definitions sit outside Rule 2, in Rules 6(2), 10(2), 11(2), 13(5), 14(5), 23(3) and the schedule notes.
Who this is for: Product managers writing DPDP requirements, Legal teams drafting contracts and policies, Engineers designing account and identity systems, Data Protection Officers, Trust and safety teams
What does Rule 2 of the DPDP Rules define?
Rule 2 is the definitions clause. It is short and it has been in force since publication on 13 November 2025, under Rule 1(2).
Rule 2(1) defines four terms:
| Clause | Term | Definition (paraphrased closely) |
|---|---|---|
| 2(1)(a) | Act | The Digital Personal Data Protection Act, 2023 (22 of 2023) |
| 2(1)(b) | Techno-legal measures | As referred to under Rules 20 and 22 |
| 2(1)(c) | User account | The online account registered by the Data Principal with the Data Fiduciary, including any profiles, pages, handles, email address, mobile number and other similar presences through which she accesses the fiduciary's services |
| 2(1)(d) | Verifiable consent | Consent as specified in Rule 10 or Rule 11 |
Rule 2(2) is the catch-all: any word used in the Rules but not defined there, and defined in the Act, carries the Act's meaning. That imports the core vocabulary of section 2 of the Act: Data Principal, Data Fiduciary, Data Processor, Consent Manager, personal data, personal data breach, processing, child and so on. The DPDP glossary collects those terms.
The opening words "unless the context otherwise requires" leave some interpretive room, but the safe engineering assumption is that the definitions apply as written.
Why the "user account" definition matters for engineers
"User account" appears in three places that drive real product work:
- Rule 7(1): breach intimation to a Data Principal goes "through her user account or any mode of communication registered by her".
- Rule 8(2): the 48-hour pre-erasure warning tells the user her data will be erased unless she "logs into her user account" or otherwise makes contact.
- Third Schedule: large platforms may keep data needed to let a user access her user account even after the three-year erasure period.
Because the definition includes "profiles, pages, handles, email address, mobile number and other similar presences", a user account is not just a row in your users table. For a marketplace, a seller storefront page is a presence. For a social app, a handle is. For a login-less service that identifies people only by mobile number and OTP, the mobile number itself is a user account.
Engineering consequences:
- Your breach notification system must be able to reach a person through any of these presences, not only the primary email.
- "Last activity" for Rule 8 erasure should consider logins and interactions across all of a person's linked presences.
- Account-merge and identity-resolution logic matters: if one person holds three handles, the dormancy clock should reflect her most recent use of any of them.
Document which identifiers your platform treats as part of one user account, and keep that mapping in your data inventory.
What "verifiable consent" means and does not mean
Rule 2(1)(d) defines verifiable consent as "a consent as specified in rule 10 or 11". That is narrower than many readers expect.
- Rule 10 covers consent of a parent before processing a child's personal data. The fiduciary must check that the person identifying as parent is an identifiable adult, using reliable identity and age details it already holds, or details voluntarily provided by the individual or through a virtual token from an authorised entity, including a Digital Locker service provider.
- Rule 11 covers consent from a lawful guardian of a person with disability. The fiduciary must verify 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.
Ordinary adult consent under section 6 of the Act is not "verifiable consent" in this sense. It must still be free, specific, informed, unconditional and unambiguous, but the Rules do not demand identity checks for it.
The practical rule: reserve the term "verifiable consent" in your product and legal documents for the parent and guardian flows. Using it loosely for all consent creates confusion in audits. See verifiable parental consent and guardian consent.
Techno-legal measures: the Board and Tribunal as digital offices
Rule 2(1)(b) does not define techno-legal measures in substance. It points to the two places the phrase is used.
- Rule 20 makes the Data Protection Board function as a digital office. Without prejudice to its power to summon and enforce attendance and examine on oath, it may adopt techno-legal measures to conduct proceedings without requiring anyone's physical presence.
- Rule 22(3)(b) gives the Appellate Tribunal the same digital-office character for appeals.
Read together, the term describes a combination of technology (online filing, video hearings, digital authentication of orders) and legal procedure (summons, examination on oath, natural justice) that lets proceedings run end to end without a physical courtroom.
For companies, the practical effect is that interaction with the Board will be digital by default. Plan for:
- A designated person who can receive and respond to Board communications quickly.
- Evidence prepared in digital form: logs, timelines, screenshots and reports exported in formats that can be uploaded.
- Digital payment of appeal fees, which Rule 22(2) says is via UPI or another RBI-authorised payment system.
See the Board inquiry process for how this plays out.
Other definitions scattered through the Rules
Several definitions with day-to-day impact sit outside Rule 2.
| Where | Term | Meaning |
|---|---|---|
| Rule 6(2) | Computer resource | As in the IT Act, 2000 |
| Rule 10(2)(a) | Adult | An individual who has completed 18 years |
| Rule 10(2)(b) | Authorised entity | An entity entrusted by law or Government with issuing identity and age details or tokens, or a person it appoints, including details or tokens verified by a Digital Locker service provider |
| Rule 10(2)(c) | Digital Locker service provider | An intermediary notified by the Central Government under IT Act rules |
| Rule 11(2) | Designated authority; local level committee; person with disability | Tied to the RPwD Act, 2016 and the National Trust Act, 1999 |
| Rule 13(5) | Committee | Central Government committee, including MeitY officials, that recommends data to be kept in India |
| Rule 14(5) | Identifier | Any character sequence issued by the fiduciary to identify the Data Principal, such as customer ID, application reference, enrolment ID, email, mobile or licence number |
| Rule 23(3) | Intermediary | As in the IT Act, 2000 |
| First Schedule note | Net worth | Total assets minus liabilities as in the Consent Manager's books |
| Third Schedule note | E-commerce entity; online gaming intermediary; social media intermediary; user | Linked to the Consumer Protection Act, 2019 and IT Rules, 2021 |
| Fourth Schedule note | Clinical establishment; healthcare professional; educational institution | Linked to sector statutes |
Common misreadings of the definitions
Three errors recur in compliance documents.
Treating a child as under 13 or 16. The Rules do not define "child"; Rule 2(2) imports the Act's definition, which is an individual who has not completed 18 years. Rule 10(2)(a) mirrors this by defining an adult as someone who has completed 18. The Act allows the Government to lower the age threshold for fiduciaries that process in a verifiably safe manner, but no such notification is reflected in the Rules.
Assuming "sensitive personal data" is defined. It is not. Neither the Act nor the Rules create a sensitive category. Sensitivity matters for Significant Data Fiduciary designation and for penalty assessment, but your classification scheme is your own design choice.
Reading "identifier" as a security concept. Under Rule 14(5), an identifier is simply what you issue to recognise someone, so that she can make rights requests. Publishing which identifiers you need, under Rule 14(1)(b), is a transparency obligation. It does not mean exposing internal database keys.
A good habit is to keep a definitions annex in your internal DPDP policy that quotes the Rules and Act verbatim, with a column showing how each term maps to your systems.
Further reading on suhasbhairav.com
- BlogGDPR for AI Agents: Consent, Minimization, Auditability
- BlogData privacy by design for AI features and products
- BlogAudit Logs for AI Agents: Traceable Actions in Production
- AI SkillsAGENTS.md Template for Privacy and Data Governance Agents
- AI AutomationAI Automation for Privacy and GDPR Requests: Uses + Example
Key dates
Rule 2 definitions in force with Rules 1 and 17–21
Rules that rely on these definitions (Rules 7, 8, 10, 11, 14) take effect
Answers
Frequently asked questions
What is a user account under the DPDP Rules?
What is a user account under the DPDP Rules?
Under Rule 2(1)(c), a user account is the online account a Data Principal registers with a Data Fiduciary, and it includes any profiles, pages, handles, email address, mobile number and other similar presences through which she accesses the fiduciary's services. It matters for breach intimation, pre-erasure notices and Third Schedule exceptions.
What does verifiable consent mean in the DPDP Rules?
What does verifiable consent mean in the DPDP Rules?
Rule 2(1)(d) defines verifiable consent as consent specified in Rule 10 or Rule 11. That means consent from a parent before processing a child's data, with checks that the parent is an identifiable adult, or consent from a lawful guardian of a person with disability whose appointment has been verified.
What are techno-legal measures under the DPDP Rules?
What are techno-legal measures under the DPDP Rules?
Rule 2(1)(b) refers to techno-legal measures as used in Rules 20 and 22. They are the combination of technology and legal procedure that lets the Data Protection Board and the Appellate Tribunal function as digital offices, running proceedings without requiring physical presence while keeping powers to summon and examine on oath.
Who is a child under the DPDP Rules?
Who is a child under the DPDP Rules?
The Rules do not define child themselves. Rule 2(2) imports the DPDP Act's definition: an individual who has not completed 18 years of age. Rule 10(2)(a) correspondingly defines an adult as an individual who has completed 18 years.
Are the DPDP Rules definitions in force?
Are the DPDP Rules definitions in force?
Yes. Rule 2 came into force on 13 November 2025, the date of publication, under Rule 1(2). Most rules that use these definitions, such as Rules 7, 8, 10, 11 and 14, start on 13 May 2027, but the definitions themselves are already settled law.
What is an identifier under DPDP Rule 14?
What is an identifier under DPDP Rule 14?
Rule 14(5) defines an identifier as any sequence of characters a Data Fiduciary issues to identify a Data Principal, such as a customer identification file number, customer acquisition form number, application reference number, enrolment ID, email address, mobile number or licence number. Fiduciaries must publish which identifiers they need for rights requests.
Legal references and sources
- Digital Personal Data Protection Rules, 2025 — Rule 2 (official text)
- Digital Personal Data Protection Rules, 2025 — Rules 10(2), 11(2), 14(5) (official text)
- Digital Personal Data Protection Act, 2023 — Section 2 (definitions) (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 2023DPDP Glossary: 40 Terms Every Tech Team Should KnowPlain-English definitions of 40 terms from the DPDP Act 2023 and DPDP Rules 2025, with the section or rule each comes from, grouped for engineering and product teams.
- DPDP Rules 2025DPDP Rules 2025 Explained: The Complete Guide for Indian CompaniesA rule-by-rule guide to all 23 rules and seven schedules of the DPDP Rules, 2025: what each requires, when it applies, and what to build before 13 May 2027.
- DPDP Rules 2025Verifiable Parental Consent Under DPDP Rule 10Rule 10 requires verifiable consent from a parent before processing any child's personal data, with due diligence that the parent is an identifiable adult. The four illustrated cases explained.
- DPDP Rules 2025Data Principal Rights Under DPDP Rule 14The DPDP Act grants access, correction, erasure, grievance and nomination rights. Rule 14 sets how fiduciaries publish request channels, identifiers and a grievance period of up to 90 days.
- DPDP Rules 2025How a Data Protection Board Inquiry Works (Rules 19–20)A step-by-step guide to Data Protection Board inquiries: what triggers them, the six-month deadline in Rule 19(9), digital hearings under Rule 20, outcomes and how to prepare.
- DPDP Rules 2025Algorithmic Due Diligence for Significant Data FiduciariesRule 13(3) requires Significant Data Fiduciaries to verify that technical measures, including algorithmic software, are not likely to pose a risk to Data Principals' rights. Here is what that means in practice.