DPDP Rules 2025Updated 22 November 202610 min read

Verifiable Parental Consent Under DPDP Rule 10

Rule 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.

By Suhas Bhairav · Reviewed against the DPDP Rules, 2025 (G.S.R. 846(E), 13 Nov 2025)

Provision
Rule 10(1)–(2) with four illustrations; Act section 9(1)
In force from
13 May 2027
Child
Under 18 years
Adult
Has completed 18 years (Rule 10(2)(a))
Verification sources
Details held; details provided; virtual token from authorised entity
Named token source
Digital Locker service provider
Penalty
Up to ₹200 crore for children's obligations

Quick answer

Under Rule 10 of the DPDP Rules, 2025, a Data Fiduciary must obtain verifiable parental consent before processing any child's (under-18) personal data, checking that the parent is an identifiable adult through reliable identity and age details it already holds, or details provided voluntarily, directly or via a virtual token from an authorised entity such as a DigiLocker provider. It applies from 13 May 2027.

  • A child under the DPDP Act is anyone under 18, so Rule 10 applies to teenagers as well as young children.
  • The fiduciary must check that the person giving consent as parent is an adult (18+) who is identifiable if required under Indian law.
  • Verification can rely on reliable identity and age details already held, or details voluntarily provided directly or via a virtual token.
  • Tokens from authorised entities, including Digital Locker service providers, are expressly recognised for age and identity verification.
  • Breach of children's data obligations can attract a penalty of up to ₹200 crore; Rule 12 and the Fourth Schedule exempt certain cases.

Who this is for: EdTech and learning platforms, Gaming and social apps with under-18 users, Consumer apps with sign-up flows, Identity and age-assurance engineers, Trust and safety teams

What does DPDP Rule 10 require for children's data?

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. A child is an individual who has not completed 18 years. Rule 10 sets how that consent is made verifiable.

Rule 10(1) has two parts:

  1. Technical and organisational measures to ensure verifiable parental consent is obtained before processing any personal data of a child.
  2. 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, by reference to:
    • (a) reliable details of identity and age of the individual 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 10(2) defines an adult as someone who has completed 18 years, and an authorised entity as an entity entrusted by law or by the Central or a State Government with issuing identity and age details or tokens, or a person it appoints or permits. It expressly includes details or tokens made available and verified by a Digital Locker service provider.

Rule 10 applies from 13 May 2027.

The four illustrated cases

Rule 10 includes four illustrations. In each, C is a child, P a parent and DF the Data Fiduciary, and C's account is to be created by processing her personal data.

CaseWho startsIs P a registered user of DF?What DF must do before processing C's data
1C declares she is a child and names PYes, and P previously gave identity and age detailsLet P identify herself; confirm DF holds reliable identity and age details of P and that P is an identifiable adult
2C declares she is a child and names PNoLet P identify herself; check P is an identifiable adult by reference to identity and age details from an entity entrusted by law or Government, or a virtual token; P may use a Digital Locker service provider
3P opens the account for CYes, with details previously givenConfirm DF holds reliable identity and age details of P and that P is an identifiable adult
4P opens the account for CNoCheck against identity and age details from an entrusted entity or a token; P may use a Digital Locker service provider

The pattern reduces to two branches:

  • Known parent: rely on reliable identity and age data you already hold.
  • Unknown parent: rely on data issued by an authorised entity, provided voluntarily, for example via a DigiLocker-based token.

In every case, verification happens before processing the child's data to create the account. Collect the minimum needed to start the parent flow, then pause.

Verification methods that fit the Rule

The Rule is technology-neutral but sets a standard: details must be reliable (if already held) or issued by an authorised entity (if provided via token). Self-declaration alone is not enough for an unknown parent.

MethodFits which branchNotes
Existing verified account data (KYC done for another purpose)Known parent (Cases 1, 3)Must be "reliable"; a self-entered birth year is weak
DigiLocker-based age or identity tokenUnknown parent (Cases 2, 4)Named in Rule 10(2)(b); data minimised if only an age-over-18 attribute is shared
Token from another Government-entrusted issuerUnknown parentMust be issued by an entity entrusted by law or Government, or its appointee
Details voluntarily provided by the individualEitherNeeds checking against a reliable source to satisfy due diligence

Design principles:

  • Ask for the minimum. If an "adult: yes" attribute is enough, do not collect full identity documents.
  • Do not retain more than needed. Store the verification result, method, timestamp and token reference, not document images, unless law requires it.
  • Keep it voluntary. The Rule speaks of details "voluntarily provided". Offer more than one route where practical.
  • Log consent events against the parent's verified identity and the child's account for audit.

See age verification and DigiLocker tokens.

How do you know a user is a child?

Rule 10 is triggered by processing "any personal data of a child". The illustrations start with the child declaring she is a child, or the parent opening the account. They do not prescribe a universal age-gate.

Practical approaches:

  • Age declaration at sign-up, neutral in design, followed by the parent flow if the user indicates she is under 18.
  • Contextual signals. If your service is directed at children (school apps, learning platforms, children's games), assume users may be children and design the parent flow as the default.
  • Confirming adulthood. Item 6 of Part B of the Fourth Schedule exempts processing to confirm that a Data Principal is not a child, and to observe due diligence under Rule 10, from section 9(1) and 9(3), restricted to the extent necessary. That gives a legal basis to run an age check without parental consent.

What not to do:

  • Build a flow where under-18 users are silently allowed through after a self-declaration and their data processed before the parent is verified.
  • Use behavioural profiling to guess age and then use that profile for other purposes. Section 9(3) bars tracking, behavioural monitoring and targeted advertising directed at children.

Section 9(5) allows the Government to lower the age threshold for fiduciaries that process in a verifiably safe manner. No such notification is reflected in the Rules; plan for 18.

Verifiable parental consent is one of three section 9 duties. The others still apply after consent is obtained.

  1. Section 9(2): a fiduciary shall not undertake processing likely to cause any detrimental effect on the well-being of a child.
  2. Section 9(3): a fiduciary shall not undertake tracking or behavioural monitoring of children, or targeted advertising directed at children.

Parental consent does not unlock targeted advertising or behavioural monitoring of a child. A parent can consent to account creation and service use; she cannot consent away section 9(3).

Rule 12 and the Fourth Schedule exempt specific classes and purposes from section 9(1) and 9(3), including healthcare, educational institutions' tracking for educational activities or safety, crèches, school transport location tracking, email-only accounts and real-time location for safety. Section 9(2) is never exempted. See children's data exemptions.

The Act's penalty Schedule provides for up to ₹200 crore per instance for breach of the additional obligations in relation to children. For a product team, the risk is less about the consent screen and more about what happens afterwards: recommendation engines, ad SDKs, analytics and AI features applied to under-18 users.

Implementation plan for a consumer product

A six-step plan to be ready by 13 May 2027:

  1. Decide scope. Do you knowingly serve under-18 users? Is the service directed at children? Document the answer and evidence.
  2. Design the age signal. Add a neutral age question or other signal at sign-up; route under-18 users to the parent flow before any further processing.
  3. Build both branches. Known parent: match to an existing account with reliable verified age. Unknown parent: integrate an authorised-entity token flow, such as DigiLocker-based verification.
  4. Lock down the child account. Disable ad SDKs, behavioural analytics, personalised recommendations based on tracking, and targeted advertising for child accounts, unless a Fourth Schedule exemption applies.
  5. Record evidence. Log the parent's verification method, result, timestamp, consent scope and child account link. Keep the record alongside your consent logs.
  6. Support withdrawal and rights. Give the parent a dashboard to review, withdraw consent and exercise the child's rights. The Act defines Data Principal, for a child, to include the parent or lawful guardian.

Test with real users. Parental flows have high drop-off; good UX matters both commercially and for compliance, because a confusing flow pushes children to lie about their age. See EdTech and children's data.

Further reading on suhasbhairav.com

Before 13 May 2027

Compliance checklist

  1. Determine whether you process children's data

    Assess whether the service is used by or directed at individuals under 18.

    Act section 9(1)

  2. Add an age signal before processing

    Route under-18 users to a parent flow before creating an account or processing further data.

    Rule 10(1)

  3. Verify known parents against reliable data

    Confirm the parent is an identifiable adult using reliable identity and age details already held.

    Rule 10(1)(a)

  4. Integrate an authorised-entity token flow

    Accept virtual tokens from authorised entities, including Digital Locker service providers, for unknown parents.

    Rule 10(1)(b)(ii)

  5. Disable tracking and targeted ads for child accounts

    Switch off behavioural monitoring and targeted advertising unless a Fourth Schedule exemption applies.

    Act section 9(3)

  6. Log verification and consent evidence

    Record method, result, timestamp and consent scope without retaining unnecessary documents.

    Rule 10

  7. Give parents a control dashboard

    Let parents review, withdraw consent and exercise rights on behalf of the child.

    Act sections 6, 11–14

Key dates

  1. Rule 10 verifiable parental consent applies

Answers

Frequently asked questions

What is verifiable parental consent under DPDP?

It is consent from a child's parent that the Data Fiduciary has verified under Rule 10. The fiduciary must check that the person claiming to be the parent is an identifiable adult, using reliable identity and age details it already holds, or details voluntarily provided directly or through a virtual token from an authorised entity.

What age is a child under the DPDP Act?

Anyone who has not completed 18 years. Rule 10(2)(a) correspondingly defines an adult as someone who has completed 18. Section 9(5) lets the Government lower the age threshold for fiduciaries that process data in a verifiably safe manner, but no such notification is reflected in the Rules.

Can DigiLocker be used for DPDP age verification?

Yes. Rule 10(2)(b) includes identity and age details or tokens made available and verified by a Digital Locker service provider within the meaning of authorised entity. Illustrations 2 and 4 say a parent may voluntarily make her details available using a Digital Locker service provider.

Is a checkbox saying I am the parent enough under DPDP?

Not for an unknown parent. Rule 10 requires due diligence that the person is an identifiable adult, by reference to reliable details already held or details from an authorised entity or token. A self-declaration checkbox alone does not meet that standard.

Can parents consent to targeted advertising for their children?

No. Section 9(3) of the DPDP Act prohibits tracking, behavioural monitoring and targeted advertising directed at children regardless of parental consent. Only the specific classes and purposes in the Fourth Schedule are exempt, and they do not include advertising.

What is the penalty for violating DPDP children's data rules?

Up to ₹200 crore per instance for breach of the additional obligations in relation to children under the DPDP Act's Schedule. The Board sets the amount after an inquiry, considering gravity, duration, the type of data and mitigation.

When does DPDP Rule 10 apply?

From 13 May 2027, eighteen months after the Rules were published. Products with under-18 users should build parent verification flows before then, because they affect sign-up, identity and support processes and usually take longer than notice changes.

Legal references and sources

  • Digital Personal Data Protection Rules, 2025 — Rule 10 (official text)
  • Digital Personal Data Protection Act, 2023 — Section 9(1)–(3), 9(5) (official text)
  • Digital Personal Data Protection Rules, 2025 — Rule 12 and Fourth Schedule (official text)
  • DigiLocker — Digital Locker service provider (Rule 10(2)(c)) (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

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.