Skip to content
TrustOS

DPDP Act guide

Children's personal data under the DPDP Act

The DPDP Act treats anyone under 18 as a child. Before you process a child's personal data, you need the verifiable consent of a parent or lawful guardian, and some kinds of processing aimed at children are off limits. For an edtech platform or a gaming app, this changes sign-up, analytics and marketing at once.

The law as of October 2026.

In shortAs of October 2026

  1. Under the DPDP Act, a child is anyone under 18.
  2. Get verifiable consent of a parent or lawful guardian before processing.
  3. No tracking, behavioural monitoring or targeted advertising directed at children, subject to the exemptions in the Rules.
  4. The penalty for breaching these duties can reach 200 crore rupees.

Who is a child

A child is an individual who has not completed 18 years. That is older than many app age gates, which often stop at 13. A Class 11 student signing up for coaching classes is a child under the Act, and so is a 17 year old customer of a fashion brand.

What you must not do

You must not undertake tracking or behavioural monitoring of children, or targeted advertising directed at children. You also must not process a child's data in a way likely to cause a detrimental effect on their well-being.

For an edtech platform, that means looking hard at engagement analytics, "students like you also bought" offers and retargeting ads. Some of it may need to stop for under 18 users. Disclosing it in the notice does not make it allowed.

Exemptions in the Rules

The Rules list certain classes of Data Fiduciaries and purposes that are exempt from some of these duties, subject to conditions. Whether an exemption covers your service is a narrow legal question, and the conditions matter. Confirm it with counsel before you rely on it.

Timing and penalties

The children's data duties apply in Phase 3, around 13 May 2027 as notified, unless amended. A breach of the additional duties for children's data can attract a penalty of up to 200 crore rupees.

Putting it into practice with TrustOS

TrustOS lets you flag purposes and data sets that involve children, record the parental consent method used for each, and keep that consent with the notice version shown. Marketing and analytics purposes can be marked as not permitted for child users, so the restriction shows up in your inventory and processor reviews. It does not verify identity itself; that depends on the method you choose and the systems you connect. Nor does it replace legal advice on exemptions.

Free toolPenalty exposure and readiness scoreSee which heads of the Schedule apply to you, their ceilings, and the controls to close first.

Official sources

This guide explains the law in plain words as of October 2026. It is not legal advice. Dates that depend on notifications can change, so check the official text before you rely on them.

Watch a withdrawal travel

One switch in the Privacy Centre, every system that used it

A customer turns off WhatsApp offers. The consent record changes, and the withdrawal goes to each system and processor that relied on it, until every one has confirmed. Sample data.

PRIVACY CENTRERitika ShahLoan account PL-88213Offers on WhatsAppWithdrawn · 09:14ConsentrecordCON-2026-2291tamper evidentWhatsApp senderConnector · number suppressedCRMConnector · consent flag updatedEmail platformProcessor · removed from listsSMS vendorProcessor · confirmed in writingData warehouseConnector · record taggedAd audiencesTask · marketing ops, done6 of 6 systems confirmed by 10:44 · kept with the consent record

Questions

Common questions

We are a school. Do these rules apply to us?

Schools process a great deal of children's data, so the duties are relevant. The Rules exempt certain classes and purposes subject to conditions. Check with counsel which apply to your activities before you rely on them.

Can we show any ads to users under 18?

The Act bars targeted advertising directed at children. Whether a particular ad format counts as targeted depends on how it is chosen. If it uses the child's behaviour or profile, assume it is caught unless an exemption clearly applies.

How do we know a user is a child?

You need a reasonable way to tell, such as an age question at sign-up with checks proportionate to the risk. Then route children through the parental consent flow.

See it with your data

Show us where your personal data lives. We will show you TrustOS running on it.

A 30 minute walkthrough on Google Meet with someone who knows the Act and the product. You leave with a view of your first phase, the owners and the effort.

Or get a rollout proposal in two minutes
  1. Step 1A 30 minute demo on Google MeetWith someone who knows the Act and the product.
  2. Step 2Your systems and purposesWe walk one product's personal data through TrustOS.
  3. Step 3A first phase you can planModules, owners and effort, written down for you to keep.