Quick answer
Under section 9 of the DPDP Act, a Data Fiduciary processing personal data of a child (anyone under 18) must obtain verifiable parental consent, must not process data in a way likely to harm the child's well-being, and must not track, behaviourally monitor or target advertising at children. Rule 10 sets verification steps, Rule 12 lists exemptions, and penalties reach ₹200 crore from 13 May 2027.
- A child under the DPDP Act is anyone who has not completed 18 years of age.
- Section 9(1) requires verifiable parental consent before processing a child's personal data; Rule 10 explains how.
- Section 9(3) bans tracking, behavioural monitoring and targeted advertising directed at children.
- Section 9(2), no detrimental processing, has no exemption in the Fourth Schedule.
- Breach of children's obligations can attract a penalty of up to ₹200 crore per instance.
- Platforms must design for both known child users and adults who claim to be parents.
Who this is for: Edtech and gaming platforms, Social media and content apps, Ad-tech and marketing teams, Schools and child-focused services, Trust & safety teams
What does section 9 require for children's data?
Section 9 of the DPDP Act creates three separate obligations for any Data Fiduciary processing the personal data of a child, defined as an individual who has not completed eighteen years:
- Verifiable parental consent — s.9(1). Before processing a child's personal data, obtain the verifiable consent of the parent (or lawful guardian). Rule 10 sets out how.
- No detrimental processing — s.9(2). Do not undertake processing likely to cause any detrimental effect on the well-being of a child.
- No tracking or targeting — s.9(3). Do not undertake tracking or behavioural monitoring of children, or targeted advertising directed at children.
Each duty stands on its own. A parent's consent under 9(1) does not permit targeted advertising under 9(3) or harmful processing under 9(2).
Two further points shape compliance:
- Exemptions. Rule 12 and the Fourth Schedule switch off 9(1) and 9(3) — never 9(2) — for specified classes of fiduciaries and purposes.
- Lower age threshold. Section 9(5) allows the Government to notify a lower age above which a fiduciary may be exempt from some obligations, if it processes children's data in a manner that is verifiably safe. No such notification should be assumed.
The penalty for breaching additional obligations in relation to children is up to ₹200 crore per instance.
Verifiable parental consent under Rule 10
Rule 10(1) requires appropriate technical and organisational measures to ensure verifiable parental consent is obtained before processing any personal data of a child. The fiduciary must do due diligence that the person identifying as the parent is an adult (completed 18 years) who is identifiable if required by law, by reference to:
- (a) reliable identity and age details already available with the fiduciary; or
- (b) identity and age details voluntarily provided by the individual, or via a virtual token mapped to those details issued by an authorised entity — including details or tokens made available and verified by a Digital Locker service provider.
Rule 10's illustration covers four cases:
| Case | Who starts | Parent already a registered user? | Check |
|---|---|---|---|
| 1 | Child declares parent | Yes | Confirm you hold reliable identity and age details of the parent |
| 2 | Child declares parent | No | Verify against details issued by an entity entrusted by law/Government, or a virtual token; DigiLocker may be used |
| 3 | Parent opens account for child | Yes | Confirm reliable details held |
| 4 | Parent opens account for child | No | Verify via authorised entity details or token |
Under Rule 2(1)(d), "verifiable consent" means consent as specified in Rule 10 (or Rule 11 for lawful guardians of persons with disability). For implementation detail see verifiable parental consent and DigiLocker age verification.
The ban on tracking, monitoring and targeted ads
Section 9(3) is where most consumer platforms will need product changes. For users known or reasonably likely to be children, switch off:
- Behavioural advertising — interest-based ad targeting, retargeting, lookalike audiences seeded with child users.
- Cross-site or cross-app tracking — third-party pixels, SDK-based device graphs, advertising identifiers.
- Behavioural monitoring used to profile children, such as engagement-optimised feeds driven by inferred interests.
Engineering pattern
- Maintain an
age_bandattribute (child,adult,unknown) on every account. - For
child, enforce a policy flag that disables ad SDKs, pixels and personalisation services at the edge, not just in the UI. - Default
unknownto the safer path until age is established, where risk is material. - Keep contextual advertising separate — ads chosen by page content rather than the child's profile — and review it under 9(2) and Part B item 5 of the Fourth Schedule.
- Log every ad and tracking decision path for child accounts, to evidence compliance.
The Fourth Schedule does permit specific tracking — for example, by educational institutions for educational activities or safety, by crèches for safety, by transport providers for location during travel, and real-time location for a child's safety. These are narrow; read the conditions in children's data exemptions.
Detrimental effect: the duty with no exemption
Section 9(2) prohibits processing likely to cause any detrimental effect on the well-being of a child. Rule 12 exempts 9(1) and 9(3) for specified classes and purposes but leaves 9(2) intact, so it applies to every fiduciary, including schools and healthcare providers.
The Act does not define "detrimental effect", so treat it as a risk assessment rather than a checklist. Questions worth recording for any child-facing feature:
- Could the design encourage compulsive use, such as streaks, infinite scroll or loot-box style rewards?
- Could it expose the child to harmful content, contact from strangers or financial loss?
- Does an AI feature — chatbot, tutor, companion — generate content unsuitable for the child's age? See AI and children's safety.
- Are inferences (mood, ability, risk scores) used in ways that could disadvantage the child?
- Is location or contact data exposed to other users?
Part B item 5 of the Fourth Schedule lets you process a child's data to the extent necessary to ensure that information, services or advertisements likely to cause detrimental effect are not accessible to the child. Safety filtering is therefore supported, but must stay within that purpose.
Which platforms are in scope?
Any Data Fiduciary that processes children's personal data is in scope — not just services aimed at children. That includes:
- Edtech and test-prep apps whose users are largely school students.
- Games and online gaming intermediaries with teenage players.
- Social media and messaging where users under 18 sign up.
- E-commerce and fintech where minors may hold accounts or be beneficiaries.
- Health apps for paediatric care (with Fourth Schedule Part A relief for clinical establishments and healthcare professionals, limited to health services).
- General platforms that do not ask age at all.
The last category is the hardest. If a service is used by children, a Data Fiduciary cannot rely on ignorance. Part B item 6 of the Fourth Schedule lets you process data to the extent necessary to confirm that a Data Principal is not a child and to observe Rule 10 due diligence, without parental consent for that step. Use that to build age assurance into onboarding.
Sector-specific guides: edtech, online gaming, social media, schools and colleges.
What to build before 13 May 2027
- Age assurance at signup — a declared date of birth plus risk-based verification, using the Part B item 6 purpose.
- Parent verification flows for all four Rule 10 cases, including a DigiLocker or token-based option for parents who are not existing users.
- Consent records linking child account, parent identity check result, timestamp, notice version and consent scope.
- A child policy layer that turns off ad SDKs, tracking and profile-based personalisation for child accounts.
- A detrimental-effect review in your product development process, signed off for each child-facing feature.
- Exemption mapping where you rely on the Fourth Schedule, with the exact class or purpose and its condition.
- Rights handling for parents — access, correction, erasure and withdrawal on the child's behalf.
- Data minimisation and retention — keep only what the child's service needs, subject to the Rule 8(3) one-year minimum for logs.
Further reading on suhasbhairav.com
- BlogAgentic RAG in EdTech: Personal learning paths
- BlogAI in Media vs Gaming: Production-Scale Content and Interactivity
- BlogGDPR for AI Agents: Consent, Minimization, Auditability
- AI TemplatesNext.js AI Chatbot Templates and ChatGPT Clone Starters
- AI SkillsCursor Rules Template: GDPR Risk Assessment Tools from Website Forms and Data Flows
Key dates
DPDP Rules, including Rules 10 and 12, notified
Section 9 duties and Rules 10–12 apply
Answers
Frequently asked questions
What age is a child under the DPDP Act?
What age is a child under the DPDP Act?
A child under the DPDP Act is an individual who has not completed eighteen years of age. Section 9(5) allows the Government to notify a lower age for fiduciaries that process children's data in a verifiably safe manner, but no such notification should be assumed.
What is verifiable parental consent under the DPDP Rules?
What is verifiable parental consent under the DPDP Rules?
It is consent from a parent whose status as an identifiable adult the platform has checked under Rule 10, using reliable identity and age details it already holds, or details voluntarily provided by the parent or through a virtual token from an authorised entity, such as a DigiLocker service provider.
Can platforms show targeted ads to children in India?
Can platforms show targeted ads to children in India?
No. Section 9(3) of the DPDP Act prohibits tracking, behavioural monitoring and targeted advertising directed at children, even with parental consent. The Fourth Schedule exemptions cover narrow cases such as safety and education, not commercial ad targeting.
What is the penalty for violating children's data rules?
What is the penalty for violating children's data rules?
Breach of the additional obligations relating to children under section 9 can attract a penalty of up to ₹200 crore per instance under the Schedule to the DPDP Act. The Board decides the amount after inquiry, considering gravity, duration, type of data and mitigation.
Do schools need parental consent under the DPDP Act?
Do schools need parental consent under the DPDP Act?
Educational institutions are exempt from sections 9(1) and 9(3) only for tracking and behavioural monitoring for their educational activities or children's safety, under Part A of the Fourth Schedule. Other processing still needs verifiable parental consent, and the section 9(2) ban on detrimental processing always applies.
Do general apps need to check if users are children?
Do general apps need to check if users are children?
In practice, yes. A Data Fiduciary that processes children's data has section 9 duties even if it does not target children. Part B item 6 of the Fourth Schedule allows processing needed to confirm a user is not a child, without parental consent for that step.
Legal references and sources
- Digital Personal Data Protection Act, 2023 — Section 9 (official text)
- Digital Personal Data Protection Rules, 2025 — Rule 10 (official text)
- Digital Personal Data Protection Rules, 2025 — Rule 12 and Fourth Schedule (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 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.
- Templates & playbooksAge Verification and DigiLocker Tokens Under DPDPHow Rule 10 verification of parents works under DPDP, what 'virtual token' and 'authorised entity' mean, where DigiLocker fits, and how to design age assurance flows.
- 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.
- AI & personal dataAI Products for Children: DPDP Tracking and Profiling LimitsWhat section 9 and Rules 10 and 12 mean for AI tutors, companion chatbots, kids' apps and any AI product that may be used by someone under 18 in India.
- 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.