DPDP Rules 2025Updated 22 November 202610 min read

DPDP Children's Data Exemptions: Fourth Schedule Explained

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

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

Provision
Rule 12(1)–(2); Fourth Schedule, Parts A and B
In force from
13 May 2027
Exempted provisions
Act section 9(1) and 9(3)
Never exempted
Section 9(2): no detrimental processing
Part A
5 classes of Data Fiduciary
Part B
6 purposes
Common condition
Restricted to the extent necessary

Quick answer

Rule 12 and the Fourth Schedule of the DPDP Rules exempt specified processing of children's data from section 9(1) (verifiable parental consent) and section 9(3) (no tracking, behavioural monitoring or targeted advertising). Part A covers five classes: health providers, allied healthcare professionals, educational institutions, crèches and their transport providers. Part B covers six purposes. Section 9(2), the ban on detrimental processing, is never exempted. It applies from 13 May 2027.

  • Rule 12(1) exempts classes of fiduciary in Part A; Rule 12(2) exempts purposes in Part B, each subject to the conditions stated.
  • Only section 9(1) and 9(3) are exempted; the section 9(2) ban on processing detrimental to a child's well-being always applies.
  • Part A covers health providers, allied healthcare professionals, educational institutions, crèches and transport providers they engage.
  • Part B covers legal functions, State benefits, email-only accounts, real-time location for safety, blocking harmful content and confirming a user is not a child.
  • Every exemption is restricted to the extent necessary for the stated purpose, so scope creep, such as using school tracking data for ads, is outside it.

Who this is for: Schools, colleges and EdTech providers, Hospitals, clinics and health-tech, Crèches and child day care centres, School transport operators, Child safety and parental control apps, Platforms running age assurance

What does the DPDP Fourth Schedule exempt?

Section 9 of the DPDP Act imposes three duties for children's data:

Sub-sectionDutyExemptible under Rule 12?
9(1)Obtain verifiable parental consent before processingYes
9(2)Do not process in a way likely to cause a detrimental effect on the child's well-beingNo
9(3)Do not track, behaviourally monitor or target advertising at childrenYes

Rule 12 uses the Act's power to exempt in two ways:

  • Rule 12(1): section 9(1) and 9(3) do not apply to processing of a child's data by the classes of Data Fiduciary in Part A of the Fourth Schedule, subject to the conditions in that Part.
  • Rule 12(2): section 9(1) and 9(3) do not apply to processing for the purposes in Part B, subject to the conditions in that Part.

Every entry pairs a class or purpose with a condition, almost always "processing is restricted to" a defined scope or "to the extent necessary". The exemption covers only what fits inside that condition. Anything outside it falls back under the full section 9 regime.

The rest of the Act still applies: notice where consent is used, security safeguards, breach intimation, retention, rights. Rule 12 is a narrow carve-out, not a general licence. It applies from 13 May 2027.

Part A: five classes of Data Fiduciary

ItemClassCondition
1Clinical establishment, mental health establishment or healthcare professionalRestricted to provision of health services to the child, to the extent necessary for the protection of her health
2Allied healthcare professionalRestricted to supporting implementation of a healthcare treatment and referral plan recommended by such professional, to the extent necessary for the protection of her health
3Educational institutionRestricted to tracking and behavioural monitoring (a) for its educational activities, or (b) in the interests of safety of children enrolled with it
4An individual to whose care infants and children in a crèche or child day care centre are entrustedRestricted to tracking and behavioural monitoring in the interests of safety of children entrusted to its care
5A person engaged by an educational institution, crèche or child care centre to transport enrolled childrenRestricted to tracking the location of the children, in the interests of their safety, during travel to and from the institution, crèche or centre

Definitions come from sector statutes, per the Schedule note: clinical establishment from the Clinical Establishments (Registration and Regulation) Act, 2010; mental health establishment from the Mental Healthcare Act, 2017; healthcare professional, allied healthcare professional and health services from the National Commission for Allied and Healthcare Professions Act, 2021. "Educational institution" means an institution of learning that imparts education, including vocational education.

Note that an EdTech company is not automatically an "educational institution". Whether it qualifies depends on whether it is itself an institution of learning imparting education; take advice on your specific model.

Part B: six exempt purposes

Part B exempts purposes regardless of who the fiduciary is.

ItemPurposeCondition
1Exercise of a power, performance of a function or discharge of a duty in the interests of a child under any law in IndiaTo the extent necessary
2Providing or issuing a subsidy, benefit, service, certificate, licence or permit under law, policy or public funds, in the interests of a child, under section 7(b)To the extent necessary
3Creating a user account for communicating by emailTo the extent necessary to create the account, whose use is limited to email communication
4Determining the real-time location of a childRestricted to tracking real-time location in the interest of her safety and protection or security
5Ensuring that information, a service or an advertisement likely to cause a detrimental effect on the child's well-being is not accessible to herTo the extent necessary to ensure it is not accessible
6Confirming that the Data Principal is not a child, and observing due diligence under Rule 10To the extent necessary for that confirmation or observance

Items 5 and 6 are the ones most product teams will rely on. Item 6 means you can run age assurance without first getting parental consent, which solves the chicken-and-egg problem in Rule 10. Item 5 means you can process a child's data to filter harmful content and ads away from her.

"Advertisement" takes its Consumer Protection Act, 2019 meaning.

Why section 9(2) still applies to everything

Neither Rule 12(1) nor Rule 12(2) mentions section 9(2). The prohibition on processing "likely to cause any detrimental effect on the well-being of a child" therefore applies to every exempt class and purpose.

Practical meaning:

  • A school's behavioural monitoring for safety, exempt from 9(3) under Part A item 3, still must not be done in a way likely to harm the child, for example by publicly ranking pupils or exposing sensitive observations.
  • A location-tracking app relying on Part B item 4 still must not expose a child's real-time location to people who could harm her. Access control and sharing limits are essential.
  • A health provider under Part A item 1 still must not process the child's data in ways that harm her well-being.

Section 9(2) is a standard, not a checklist, so document a well-being assessment for each exempt use: what data, who sees it, what could go wrong for the child, and what controls prevent it. A short structured assessment per use case is enough for most organisations and gives evidence if the Board asks.

The Act's Schedule provides for penalties of up to ₹200 crore for breach of the additional obligations in relation to children, which includes section 9(2).

Applying the exemptions in real products

Three worked examples show how the conditions bite.

School safety app (Part A item 3, item 5). A school uses an app to record attendance and monitor bus location. Attendance and in-school behavioural notes for educational activities and safety fit item 3. Bus location tracking during travel by the school's transport provider fits item 5. Using the same data to build a profile for marketing courses to parents does not fit either and needs consent and section 9(3) compliance, which bars targeted advertising directed at children.

Family location app (Part B item 4). A parental app showing a child's real-time location fits item 4 when restricted to tracking for her safety and protection or security. Storing years of location history for analytics, or using location to serve ads, falls outside the condition.

Social platform age assurance (Part B items 5 and 6). Processing to estimate or confirm whether a user is an adult fits item 6. Processing to keep harmful content and ads away from a likely child fits item 5. Once a user is confirmed as a child, creating her full account and processing beyond these purposes requires Rule 10 parental consent and full section 9(3) compliance.

For each exempt use, record the Fourth Schedule item relied on, the condition, the data elements, and technical controls that enforce the boundary.

Common errors with the Fourth Schedule

  • Treating an exemption as a category, not a condition. Being a school does not exempt everything a school does; only tracking and behavioural monitoring for educational activities or safety.
  • Assuming EdTech equals educational institution. An app that supplies content to learners may not be an institution of learning. Check before relying on Part A item 3.
  • Forgetting that only 9(1) and 9(3) are lifted. Notice, security, breach, retention and rights duties still apply, and so does section 9(2).
  • Letting data flow beyond the exempt purpose. Location collected for safety must not feed advertising, analytics products or model training that targets children.
  • Over-retaining. "To the extent necessary" implies retention limits too. Keep safety location data only as long as safety requires, subject to the one-year floor in Rule 8(3) for processing logs.
  • No documentation. If the Board asks which exemption you relied on, you need a record that names the item and shows the controls.

A short register of exempt uses, reviewed each time a feature changes, prevents most of these. See verifiable parental consent for the default regime and schools and colleges for sector detail.

Further reading on suhasbhairav.com

Before 13 May 2027

Compliance checklist

  1. List every use of children's data

    Inventory each feature or process that touches personal data of users under 18.

    Act section 9

  2. Map each use to a Fourth Schedule item or to consent

    Record whether a Part A class or Part B purpose applies, or whether Rule 10 consent is needed.

    Rule 12; Fourth Schedule

  3. Enforce the condition technically

    Use purpose tags, access controls and data flow restrictions so exempt data cannot reach other uses.

    Fourth Schedule, column 3

  4. Run a well-being assessment

    Assess each exempt use against the section 9(2) ban on detrimental processing.

    Act section 9(2)

  5. Use item 6 for age assurance

    Rely on Part B item 6 to confirm a user is not a child before seeking parental consent.

    Fourth Schedule, Part B, item 6

  6. Limit retention of exempt data

    Keep exempt data only as long as necessary, subject to the Rule 8(3) one-year floor for logs.

    Fourth Schedule; Rule 8(3)

Key dates

  1. Rule 12 and the Fourth Schedule apply

Answers

Frequently asked questions

Which organisations are exempt from DPDP parental consent?

Under Part A of the Fourth Schedule: clinical and mental health establishments and healthcare professionals, allied healthcare professionals, educational institutions, crèches and child day care centres, and transport providers they engage. Each exemption is limited to a stated purpose such as health services, education or child safety.

Can schools track students under the DPDP Act?

Yes, within limits. Part A item 3 of the Fourth Schedule exempts educational institutions from section 9(1) and 9(3) for tracking and behavioural monitoring for their educational activities or in the interests of the safety of enrolled children. Other uses, and anything detrimental to the child, remain prohibited.

Does the Fourth Schedule allow targeted advertising to children?

No. No class or purpose in the Fourth Schedule permits targeted advertising directed at children. Part B item 5 allows processing only to ensure harmful information, services or advertisements are not accessible to a child.

Can I verify age without parental consent under DPDP?

Yes. Part B item 6 of the Fourth Schedule exempts processing for confirming that a Data Principal is not a child, and for observing due diligence under Rule 10, from section 9(1) and 9(3), to the extent necessary. This lets age assurance run before parental consent.

Is section 9(2) of the DPDP Act ever exempted?

No. Rule 12 exempts only section 9(1) and 9(3). The prohibition in section 9(2) on processing likely to cause a detrimental effect on a child's well-being applies to every exempt class and purpose.

Are location tracking apps for children allowed under DPDP?

Yes, for safety. Part B item 4 exempts determining a child's real-time location, restricted to tracking for her safety and protection or security. Using that location data for advertising, analytics products or unrelated purposes falls outside the exemption.

When do the DPDP children's data exemptions apply?

From 13 May 2027, together with Rule 10 parental consent and the rest of the core rules. Organisations relying on an exemption should document the Fourth Schedule item and the controls that keep processing within its condition before then.

Legal references and sources

  • Digital Personal Data Protection Rules, 2025 — Rule 12 (official text)
  • Digital Personal Data Protection Rules, 2025 — Fourth Schedule (official text)
  • Digital Personal Data Protection Act, 2023 — Section 9(1)–(3) (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.