Quick answer
Rule 10 of the DPDP Rules requires verifiable parental consent before processing a child's data, and a check that the person claiming to be the parent is an identifiable adult aged 18 or over. It can rely on reliable identity and age details it already holds, details the individual provides voluntarily, or a virtual token from an authorised entity, expressly including Digital Locker service providers.
- Rule 10 verifies the parent as an identifiable adult; it does not prescribe a single method.
- Three routes exist: details already held, details voluntarily provided, or a virtual token from an authorised entity.
- Tokens made available and verified by a Digital Locker service provider count as an authorised entity source.
- The Rules' four illustrations cover child-initiated and parent-initiated sign-ups, for registered and unregistered parents.
- Confirming a user is not a child is itself an exempt purpose under the Fourth Schedule, Part B, item 6.
- Minimise: verify age and parenthood, then store the outcome, not the underlying documents.
Who this is for: Consumer app and platform teams, Edtech and gaming companies, Trust and safety leads, Identity and KYC engineers, Product designers for sign-up flows
What does Rule 10 require?
Section 9(1) of the DPDP Act requires a Data Fiduciary to obtain the verifiable consent of the parent before processing any personal data of a child. Rule 10, in force from 13 May 2027, explains how.
Rule 10(1) requires the fiduciary to:
- adopt appropriate technical and organisational measures to ensure that verifiable consent of the parent is obtained before processing; and
- observe due diligence to check that the individual identifying herself as the parent is an adult who is identifiable, if required in connection with compliance with any law in India.
The due diligence is done by reference to:
- (a) reliable details of identity and age of the individual already available with the Data Fiduciary; or
- (b) details of identity and age voluntarily provided (i) by the individual, or (ii) through a virtual token mapped to such details, issued by an authorised entity.
Rule 2(1)(d) defines "verifiable consent" as consent specified in Rule 10 or Rule 11, linking these mechanics to the consent standard in section 6.
Note what Rule 10 is not: it is not a mandate to verify the age of every user with documents. It addresses verifying the parent. How you establish that a user is a child in the first place is a separate design question.
What is an 'authorised entity' and where does DigiLocker fit?
Rule 10(2)(b) defines an authorised entity as:
- (i) an entity entrusted by law, or by the Central or a State Government, with issuing details of identity and age, or a virtual token mapped to such details; or
- (ii) a person appointed or permitted by such an entity for that issuance;
and it also includes details of identity and age or a token made available and verified by a Digital Locker service provider.
Rule 10(2)(c) defines a Digital Locker service provider as an intermediary, including a body corporate or a government agency, notified by the Central Government in accordance with rules made under the IT Act, 2000.
What that means for builders
- A token from a Digital Locker service provider is expressly a valid source for Rule 10(1)(b)(ii).
- The parent voluntarily shares the details; the fiduciary should not compel a particular provider if other reliable routes exist.
- A virtual token mapped to identity and age lets you confirm "adult: yes" without collecting the underlying document number.
Check DigiLocker's published integration options and terms at digilocker.gov.in before building, and confirm which attributes can be shared and in what form.
The four illustrated cases in Rule 10
The Rules include an illustration with C (a child), P (a parent) and DF (a Data Fiduciary), where a user account for C is to be created.
| Case | Who initiates | Is P a registered user of DF? | What DF must do before processing C's data |
|---|---|---|---|
| 1 | C declares she is a child and names P | Yes, with identity and age details already given | Enable P to identify herself; confirm DF holds reliable identity and age details showing P is an identifiable adult |
| 2 | C declares she is a child and names P | No | Enable P to identify herself; check P is an identifiable adult using details issued by an entity entrusted by law or Government, or a virtual token; P may use a Digital Locker service provider |
| 3 | P opens an account for C | Yes | Confirm DF holds reliable identity and age details of P showing she is an identifiable adult |
| 4 | P opens an account for C | No | Check P is an identifiable adult by reference to authorised identity and age details or a virtual token; P may use a Digital Locker service provider |
Design implications
- Support both entry points: child-initiated and parent-initiated.
- For existing adult users, reuse the verification you already hold; do not re-collect documents.
- For new parents, offer a token-based route, with DigiLocker as one option.
How do you know the user is a child in the first place?
Rule 10 starts once a fiduciary is dealing with a child. Getting there is a product decision with legal consequences either way: treat adults as children and you add friction; treat children as adults and you breach section 9.
Age assurance options
- Self-declaration of date of birth at sign-up: low friction, easily falsified, but acceptable as a first gate for many services with low risk.
- Inference from account signals: useful for risk flags but should not be the only mechanism for high-risk services.
- Verified age via a token: stronger, but adds friction for every user.
The exempt purpose
Part B, item 6 of the Fourth Schedule, applied through Rule 12(2), says sections 9(1) and 9(3) do not apply to processing for confirmation by the Data Fiduciary that the Data Principal is not a child and observance of due diligence under Rule 10, restricted to the extent necessary. That lets you process data to establish age without first obtaining parental consent.
A risk-based approach
Calibrate to the service. A general-purpose productivity tool might rely on declaration plus signals. A social, gaming or chat product likely to attract teenagers should use stronger assurance. Document the reasoning. See online gaming compliance.
A reference architecture for parental verification
1. Sign-up -> age gate (DOB) [Part B item 6]
2. If age < 18:
a. Child flow: collect parent contact (minimal)
b. Send parent an invitation link
3. Parent flow:
a. Existing adult user with reliable details?
-> confirm, no new documents [Rule 10(1)(a)]
b. New parent:
-> token from authorised entity,
e.g. Digital Locker provider [Rule 10(1)(b)(ii)]
-> or voluntarily provided details [Rule 10(1)(b)(i)]
4. Record outcome: parent_verified = true,
method, timestamp, token reference
5. Show Rule 3 notice to parent; collect
per-purpose consent; actor = parent
6. Create child account with child-safe defaults:
no tracking, behavioural monitoring or
targeted ads [s.9(3)]
Data minimisation
- Store the verification result and a reference, not document images or full identity numbers.
- Delete data collected solely for age gating when it is no longer needed, consistent with Rule 8(3)'s one-year log requirement.
- Separate verification data from behavioural data so it is never reused for profiling.
Security
Treat parent identity data as high risk: encrypt it, restrict access, and log every access under Rule 6.
Exemptions and common pitfalls
When parental consent is not needed
Rule 12 and the Fourth Schedule disapply sections 9(1) and 9(3) in specific cases, such as clinical and mental health establishments providing health services, educational institutions tracking for educational activities or safety, school transport location tracking, creating an email-only user account, real-time location for a child's safety, and keeping harmful content or ads away from children. Section 9(2), which bars processing likely to cause a detrimental effect on a child's well-being, still applies. See children's data exemptions.
Pitfalls
- Treating the parent's click as verification. An unverified "I am the parent" checkbox is not due diligence under Rule 10.
- Over-collection. Asking every parent for a document scan when a token or existing details would do.
- Reusing KYC data for marketing. Identity details collected for verification must not feed other purposes.
- Ignoring 16- and 17-year-olds. The threshold is 18, not 13 or 16 as in some other jurisdictions.
- No path for parents without a Digital Locker account. Offer an alternative reliable route.
- Forgetting withdrawal. The parent must be able to withdraw consent as easily as she gave it.
Further reading on suhasbhairav.com
Before 13 May 2027
Compliance checklist
Implement an age gate
Ask for date of birth neutrally at sign-up and route under-18 users to a parent flow.
Fourth Schedule, Part B, item 6
Support child- and parent-initiated flows
Handle both entry points shown in the Rule 10 illustrations.
Rule 10
Reuse reliable details for existing adults
Verify registered parents from identity and age details already held.
Rule 10(1)(a)
Offer a virtual token route
Accept tokens from authorised entities, including a Digital Locker service provider.
Rule 10(1)(b)(ii)
Provide an alternative route
Give parents without a token a reliable way to provide identity and age details.
Rule 10(1)(b)(i)
Store outcomes, not documents
Keep verification result, method and reference; avoid storing document images.
Rule 6(1)(a)
Apply child-safe defaults
Disable tracking, behavioural monitoring and targeted ads for child accounts.
Section 9(3)
Record the parent as consent actor
Log parent consent events with verification method and notice version.
Rule 10
Answers
Frequently asked questions
Does DPDP require age verification for all users?
Does DPDP require age verification for all users?
No single method is mandated for all users. Section 9 and Rule 10 require verifiable parental consent before processing a child's data, and due diligence that the parent is an identifiable adult. How strongly you establish a user's age should be calibrated to the risk of the service, and processing to confirm a user is not a child is an exempt purpose.
Is DigiLocker mandatory for DPDP parental consent?
Is DigiLocker mandatory for DPDP parental consent?
No. Rule 10 lists three routes: identity and age details the fiduciary already holds, details voluntarily provided by the individual, or a virtual token from an authorised entity. Tokens verified by a Digital Locker service provider are expressly included, but they are one option, and the parent provides them voluntarily.
What is a virtual token under Rule 10?
What is a virtual token under Rule 10?
A virtual token is a token mapped to a person's identity and age details, issued by an authorised entity. It lets a fiduciary confirm that the parent is an identifiable adult without collecting the underlying identity document. Authorised entities include bodies entrusted by law or government and Digital Locker service providers.
Who counts as an adult for parental verification?
Who counts as an adult for parental verification?
Rule 10(2)(a) defines an adult as an individual who has completed the age of eighteen years. The person giving consent on behalf of a child must be verified as an identifiable adult under Rule 10's due diligence, by reference to reliable details already held, details voluntarily provided, or an authorised virtual token.
What if the parent is already my user?
What if the parent is already my user?
Rule 10(1)(a) lets you rely on reliable identity and age details of the parent already available with you. Cases 1 and 3 of the Rules' illustration describe this: confirm you hold reliable details showing she is an identifiable adult before processing the child's data. No fresh document collection is required.
Can I process data to check whether a user is a child?
Can I process data to check whether a user is a child?
Yes. Rule 12(2) and Part B, item 6 of the Fourth Schedule disapply sections 9(1) and 9(3) for processing to confirm that a Data Principal is not a child and to carry out Rule 10 due diligence, restricted to the extent necessary. Use minimal data and do not reuse it for other purposes.
Legal references and sources
- Digital Personal Data Protection Rules, 2025 — Rule 10 (official text)
- Digital Personal Data Protection Act, 2023 — Section 9 (official text)
- Digital Personal Data Protection Rules, 2025 — Rule 12 and Fourth Schedule, Part B, item 6 (official text)
- Digital Personal Data Protection Rules, 2025 — Rule 2(1)(d) (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 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 Act 2023DPDP Children's Data: Section 9 Obligations for PlatformsSection 9 sets three duties for platforms handling data of anyone under 18: verifiable parental consent, no detrimental processing, and no tracking or targeted ads.
- DPDP Rules 2025DPDP Children's Data Exemptions: Fourth Schedule ExplainedRule 12 and the Fourth Schedule exempt five classes of fiduciary and six purposes from DPDP parental consent and the tracking ban, each subject to strict conditions. Section 9(2) still applies.
- Sector guidesDPDP for Online Gaming IntermediariesOnline gaming intermediaries with at least 50 lakh registered users face three-year inactivity erasure, and every gaming platform must handle minors, in-game tokens and logs under DPDP.
- Sector guidesChildren's Data & Verifiable Parental Consent for EdTech AIHow EdTech companies using AI tutors, proctoring and learning analytics must handle under-18 learners' data under DPDP section 9, Rule 10 and the Fourth Schedule.
- Templates & playbooksDesigning Consent and Withdrawal UX for DPDPUX and engineering patterns for DPDP-compliant consent and withdrawal: affirmative action, per-purpose choices, symmetric withdrawal under Rule 3(c)(i), and consent records.