In short. Before processing the data of anyone under 18, you need the verifiable consent of a parent or lawful guardian, and Rule 10 requires you to check that the parent is an identifiable adult. Tracking, behavioural monitoring and targeted advertising aimed at children are banned outright. A short list of institutions and purposes in the Fourth Schedule is exempt from consent and the tracking ban, but never from the duty not to harm a child's well-being. The penalty goes up to Rs. 200 crore. These rules apply from 13 May 2027.

Who counts as a child

Section 2(f) defines a child as an individual who has not completed eighteen years. There is no separate digital age of consent. A seventeen-year-old college student signing up for a coding course is a child for the purposes of the Act, in the same way as an eight-year-old on a learning app.

Section 9(5) allows the Central Government to notify a lower age above which a particular Data Fiduciary is exempt, if it is satisfied that the processing is verifiably safe. Until such a notification names your business, plan on eighteen.

The three duties in Section 9

  • Verifiable parental consent, Section 9(1). Before processing any personal data of a child, you must obtain the verifiable consent of the parent or lawful guardian, in the manner prescribed by the Rules.
  • No harm to well-being, Section 9(2). You must not process a child's personal data in a way likely to cause any detrimental effect on the child's well-being.
  • No tracking or targeted ads, Section 9(3). You must not track or behaviourally monitor children, or direct targeted advertising at them.

The third duty is the one that cuts deepest into ordinary product practice. Most analytics, recommendation and ad stacks track behaviour by design. For users under eighteen, those systems have to be switched off or brought within an exemption.

Verifying the parent under Rule 10

Rule 10 asks the Data Fiduciary to adopt appropriate technical and organisational measures so that verifiable parental consent is obtained, and to use due diligence to check that the person identifying as the parent is an adult who can be identified if needed. The check can be done by reference to:

  • Reliable details of identity and age the business already holds, for example where the parent is an existing verified user of the same platform; or
  • Details provided voluntarily by the person, either directly or through a virtual token mapped to those details and issued by an authorised entity.

Rule 10(2) says an authorised entity includes a body entrusted by law or the government with issuing such details, and expressly includes details or tokens made available and verified by a Digital Locker service provider. The Rules carry four illustrations covering existing and new users and whether the child or the parent starts the sign-up.

The practical reading is that a checkbox saying "I am the parent" will not do. The parent's adulthood has to be checked against something reliable. A token-based route is the most privacy-friendly option, because the platform learns that the person is an adult without collecting a copy of an identity document.

Persons with disability

Section 9(1) extends the consent requirement to a person with disability who has a lawful guardian. Rule 11 requires the Data Fiduciary to verify that the guardian was appointed by a court, by a designated authority under Section 15 of the Rights of Persons with Disabilities Act, 2016, or by a local level committee under Section 13 of the National Trust Act, 1999. A family member's say-so is not enough. Ask for the appointment order.

The wording of Section 9(1) was corrected by the Digital Personal Data Protection (Removal of Difficulties) Order, 2026 (S.O. 5458(E)), in force from 6 October 2026. It inserted the word "of" before "a person with disability", so the provision now plainly covers the personal data of a child and the personal data of a person with disability who has a lawful guardian. The government described the change as textual and editorial. The obligations themselves did not change.

The Fourth Schedule exemptions

Rule 12 and the Fourth Schedule exempt certain Data Fiduciaries and purposes from parental consent and from the ban on tracking and targeted advertising. They do not exempt anyone from Section 9(2). Each exemption is tied to a condition, so read it narrowly.

Part A, classes of Data Fiduciary:

  • Clinical establishments, mental health establishments and healthcare professionals, for providing health services to the child.
  • Allied healthcare professionals, for carrying out a treatment or referral plan.
  • Educational institutions, for tracking and behavioural monitoring in the course of educational activities or for the safety of enrolled children.
  • Crèches and child day care centres, for the safety of children in their care.
  • Transport engaged by an educational institution, crèche or day care centre, for tracking the location of children while they travel.

Part B, purposes:

  • Exercising a legal power, function or duty in the interests of the child.
  • Providing a State subsidy, benefit, service, certificate, licence or permit.
  • Creating a user account limited to communication by email.
  • Real-time location tracking for the child's safety.
  • Making sure that information, services or advertisements likely to harm the child are not accessible to them.
  • Confirming that a user is not a child, and the due diligence under Rule 10 itself.

Note what is missing. There is no exemption for a commercial edtech platform as such. The educational institution exemption covers the institution, and a vendor processing data on the institution's behalf may be able to rely on the institution's position. An app selling directly to parents and students is in a different position and should plan for full compliance.

What this means for product teams

  1. Find out who your users are. If your audience may include anyone under eighteen, you need an age gate at sign-up. Age confirmation itself is an exempt purpose under Part B.
  2. Build a parental consent flow that verifies the parent through one of the Rule 10 routes, and keep a record of how each consent was verified.
  3. Split the analytics and ad stack by age. For child accounts, switch off behavioural tracking, personalised recommendations driven by behaviour, and any targeted advertising.
  4. Review features for harm. Section 9(2) applies even where an exemption covers consent and tracking. Public profiles, open messaging with strangers and engagement mechanics aimed at children deserve a written review.
  5. Check your vendors. Ad networks and analytics SDKs embedded in your app process data on your behalf, and under Section 8(1) their processing is your responsibility.

Penalty

Item 3 of the Schedule sets a penalty of up to Rs. 200 crore for breach of the additional obligations relating to children under Section 9. This is separate from the penalties for failing to protect data or to report a breach.

Common mistakes

  • Assuming the age of consent is thirteen or sixteen, as in some foreign laws.
  • Accepting an unverified "I am the parent" checkbox.
  • Running the same analytics and ad SDKs on child accounts as on adult accounts.
  • Treating the educational institution exemption as covering every edtech product.
  • Collecting a scan of the parent's identity document when a token would do, and then having to secure that document.
  • Forgetting that exemptions never cover the duty not to harm a child's well-being.

Frequently asked questions

Anyone who has not completed eighteen years, under Section 2(f). There is no lower digital age of consent.

Rule 10 allows reliance on reliable identity and age details you already hold, or on details given voluntarily, including through a virtual token issued by an authorised entity such as a Digital Locker service provider.

Only within the Fourth Schedule exemption for educational institutions, which covers tracking for educational activities or the safety of enrolled children. A private app selling directly to families is not automatically covered.

Up to Rs. 200 crore under item 3 of the Schedule.

No. They cover parental consent and the tracking and advertising ban only. The duty in Section 9(2) not to harm a child's well-being always applies.


Related reading

Enrolment: Bar Council of Punjab & Haryana  |  No.: PH/9616/2023
This page is informational and does not constitute legal advice. References are to the Digital Personal Data Protection Act, 2023 and the Digital Personal Data Protection Rules, 2025 (G.S.R. 846(E), 13 November 2025). How these apply depends on the data and operations of each organisation.