AMLEGALS
Children's Data Protection Under the DPDPA — AMLEGALS DPDPA Advisory
Vulnerable Data Principals

Children's Data Protection Under the DPDPA

How Section 9 and Rules 10 to 12 create a heightened compliance obligation for organisations processing data of individuals below 18 years.

Section 9
Primary Children's Provision
< 18 Years
Age Threshold
Rule 10-12
Operational Rules
₹200 Cr
Maximum Penalty (Schedule)
Executive Summary

The DPDPA establishes children as a protected category, imposing obligations that go beyond standard Data Fiduciary duties.

Section 9 of the DPDPA creates a separate compliance layer for processing personal data of children, defined as individuals below 18 years. Before processing a child's data, the Data Fiduciary must obtain verifiable consent from the parent or lawful guardian. The Act prohibits tracking, behavioural monitoring, and targeted advertising directed at children. Rules 10 to 12 operationalise these provisions by prescribing the mechanics of age verification and parental consent, while also providing exemptions for prescribed categories of Data Fiduciaries.

Section 9
Primary Children's Provision
< 18 Years
Age Threshold
Rule 10-12
Operational Rules
₹200 Cr
Maximum Penalty (Schedule)
Why Children's Data Requires a Separate Compliance Architecture — AMLEGALS analysis
01

Why Children's Data Requires a Separate Compliance Architecture

The prohibitions on tracking, behavioural monitoring, and targeted advertising fundamentally change how platforms must operate when children are among their users.

The DPDPA's children's data provisions affect a wide range of organisations: educational technology platforms, gaming companies, social media services, healthcare providers treating minors, and any consumer-facing business whose user base includes individuals under 18. The requirement for verifiable parental consent means that standard consent mechanisms, such as click-through agreements, are insufficient.

The prohibition on tracking and behavioural monitoring under Section 9(3) has architectural implications. Platforms that serve both adults and children must implement age-gating mechanisms and ensure that their analytics, recommendation, and advertising systems can exclude users identified as children. This is not a policy change. It is a systems engineering requirement. Rule 12 provides specific exemptions for prescribed categories of Data Fiduciaries, but the burden of demonstrating eligibility for these exemptions rests with the organisation.

02

Children's Data Compliance Framework

Six core requirements that organisations processing children's data must operationalise under Section 9 and Rules 10 to 12.

Verifiable Parental Consent

Section 9(1) | Rule 10

Consent for processing a child's data must be obtained from the parent or lawful guardian, verified through mechanisms that provide reasonable assurance of the consenting individual's identity and parental authority.

Tracking and Monitoring Prohibition

Section 9(3)

Data Fiduciaries must not track, conduct behavioural monitoring of, or direct targeted advertising at children. This prohibition applies subject to Rule 12 exemptions for prescribed categories of Data Fiduciaries.

Age Verification

Rule 10

Organisations must implement mechanisms to determine whether a Data Principal is a child. Age verification must be proportionate and effective, balancing accuracy with the privacy of the verification process itself.

Detrimental Processing Prohibition

Section 9(2)

No processing of a child's personal data may be undertaken if it is likely to cause any detrimental effect on the well-being of the child. This requires proactive risk assessment of processing activities.

Ed-Tech and Gaming Compliance

Section 9 | Rule 12

Educational technology platforms and gaming companies must redesign their data collection, analytics, and advertising systems to comply with children's data restrictions or demonstrate eligibility for Rule 12 exemptions.

Exemption Documentation

Rule 12

Organisations claiming exemptions under Rule 12 must maintain documentary evidence of their eligibility, including the basis for their classification as a prescribed category of Data Fiduciary.

03

The Architecture of Age-Gating and Consent Verification

Age verification and parental consent verification are not solved problems. Every mechanism involves trade-offs between accuracy, user experience, and the privacy of the verification process itself. Organisations must design systems that are proportionate to the risk, effective at identifying children, and capable of demonstrating compliance under audit. The DPDPA does not prescribe specific technical methods, which means organisations bear the responsibility of selecting and defending their chosen approach.

Age-Gating Implementation
Deploy age verification at registration or first data collection, with fallback mechanisms for edge cases
Parental Consent Workflow
Build a verified parental consent flow that provides reasonable assurance of identity and authority
Analytics Exclusion Architecture
Ensure tracking, behavioural monitoring, and ad targeting systems exclude identified child users
Rule 12 Exemption Audit
Document and maintain evidence supporting eligibility for prescribed category exemptions
"The DPDPA treats children as India's most vulnerable data principals. Organisations that fail to build compliance infrastructure for this category face both regulatory penalties and reputational consequences that extend beyond the statutory framework."
04

Frequently Asked Questions

Concise, statutory-referenced answers to the most common compliance questions on this topic.

What is the age threshold for children under the DPDPA?

Under the DPDPA, a child is defined as an individual who has not completed 18 years of age. This applies uniformly across all sectors and types of data processing. Organisations must implement mechanisms to verify age and obtain verifiable parental consent before processing a child's personal data.

Can ed-tech platforms continue to collect student data under the DPDPA?

Yes, but with significant restrictions. Ed-tech platforms must obtain verifiable parental consent before processing student data. They are prohibited from tracking, behavioural monitoring, and targeted advertising directed at child users. Rule 12 provides exemptions for prescribed categories of Data Fiduciaries, and eligible ed-tech platforms must document their basis for claiming these exemptions.

What constitutes verifiable parental consent?

The DPDPA requires that consent from a parent or lawful guardian be verifiable, meaning the Data Fiduciary must have reasonable assurance that the individual providing consent is indeed the child's parent or guardian. The Act does not prescribe specific verification methods, allowing organisations to implement mechanisms proportionate to the risk and context of their processing activities.

Are there exemptions to the children's data restrictions?

Rule 12 of the DPDP Rules, 2025 provides exemptions for prescribed categories of Data Fiduciaries from certain children's data restrictions, including the prohibition on tracking and behavioural monitoring. However, the exemptions are narrow, and organisations must maintain documentation supporting their eligibility for these categories.

Request the Brief

Get the Children's Data Compliance Brief

This brief provides a structured framework for operationalising children's data protections across technology platforms, educational services, and consumer-facing businesses.

Age verification implementation options and trade-off analysis
Parental consent workflow architecture for digital platforms
Analytics and advertising exclusion system requirements
Rule 12 exemption eligibility assessment and documentation guide
Next Steps

From Awareness to Implementation

Understanding the requirement is the first step. Building the operational infrastructure to meet it, under scrutiny, is the work that follows.