India's DPDP Act sets one of the strictest regimes in the world for children's data. A child is anyone under 18, a higher age than most comparable laws. Before processing a child's personal data, a business needs verifiable consent from a parent or lawful guardian. Breaching the children's obligations can draw a penalty of up to ₹200 crore.

The three core rules

  1. Verifiable parental consent before processing any personal data of a child.
  2. No processing likely to harm a child's well-being.
  3. No tracking, behavioural monitoring or targeted advertising directed at children.

What "verifiable" means in the Rules

Rule 10 says a business must take appropriate technical and organisational measures to make sure the person giving consent is the parent and is an identifiable adult. It can rely on:

  • details it already holds. If the parent is already a registered, verified user, their existing identity and age details can be used.
  • details provided voluntarily by the parent, or
  • a virtual token issued by an entity authorised by law or the government that maps to the parent's identity and age details. A token from a digital locker service is the example given.

The aim is to confirm adulthood and identity without the business having to collect and store copies of ID documents.

Exemptions

The Rules exempt some fiduciaries and purposes, wholly or partly, from the parental-consent and tracking rules. Examples include:

  • clinical establishments and healthcare professionals, to the extent needed to protect a child's health;
  • educational institutions and childcare or crèche providers, for educational activities, safety and tracking;
  • transport arranged for children by an educational institution, for tracking location during travel;
  • creating a user account limited to email communication;
  • determining a child's real-time location, restricted to the child's safety, protection or security;
  • confirming that a user is not a child.

Read the exact wording in the schedule to the Rules: each exemption is tied to a purpose and only goes "to the extent necessary".

Design patterns

Age assurance at sign-up. Ask for date of birth neutrally, without hinting at the "right" answer. Where the risk is higher, use stronger age assurance.

Parent-linked accounts. Let a verified adult create and manage child profiles. This fits the "details already held" route.

Separate data paths. Once a user is identified as a child, route their data through a pipeline with no ad-tech, no behavioural profiling and minimal analytics. A flag that the whole stack respects works better than relying on each team to remember.

Defaults. Private profiles, no public location, no direct messages from strangers and no personalised recommendations based on tracking.

Withdrawal. A parent must be able to withdraw consent easily, and processing must stop.

Common traps

  • Assuming 13 is the line. Many global apps use 13 because of US law. Under the DPDP Act, 13 to 17-year-olds are children too.
  • Contextual ads that quietly use profiles. Targeted advertising directed at children is prohibited. Check what your ad partners actually do.
  • Analytics SDKs. Third-party SDKs can amount to tracking. Review every SDK that runs in screens children use.

Learn more

Our free Data Protection & Privacy Fundamentals course covers consent, children's data and privacy by design in a law-neutral way. See also privacy by design patterns for engineering teams.

Written and reviewed by the DigiTrust Asia editorial team. How we research, review and correct articles.

General information, not legal advice. Laws and official guidance change; check the current text before acting.

Learn privacy properly

Data Protection & Privacy Fundamentals is a free, law-neutral course with a final exam and certificate.

Create a free account