DPDP for edtech

DPDP compliance for edtech

Most of your learners are under 18, so most of your data is a child’s data. We map it, then build age checks, verifiable parental consent, tracking controls and deletion into the product you already run.

Parental consentNo ad tracking
Edtech

What changes, with evidence

Age gate and parent verificationVerification records and a flow diagram
Notice for parentsVersioned notices in each language
Consent recordsConsent log and withdrawal records
WithdrawalWithdrawal log with each downstream step
Tracking and SDK reviewSDK register and release checks
AI tutors and personalisationFeature register with the decision and its reason
Children are under 18Core duties: 13 May 2027
Law firm review

Where children’s data sits in an edtech company.

Edtech collects from learners, parents and schools, in the app and in the tools behind it. A DPDP gap assessment starts by finding all of it.

Learner sign-up and accounts

Names, ages, phone numbers, emails and the parent or guardian details behind each learner.

Learning app and platform

Progress, scores, quiz history and the behaviour data a recommendation engine reads.

Live classes and recordings

Video, audio, chat and attendance, often stored by a third-party tool.

AI tutors and doubt-solving bots

Questions, answers and personalisation signals sent to a model API.

Analytics and ad SDKs

Firebase, Meta and attribution tools that collect device and advertising identifiers inside the app.

Marketing and messaging

WhatsApp, SMS, email and retargeting lists built from learner and parent data.

Payments and fees

Parent payment details, invoices and loan or EMI partners.

Schools and B2B partners

Rosters and records shared between your platform, schools and other vendors.

What the Act and Rules ask about children.

Section 9 and Rule 10 do the heavy lifting. Our guide to verifiable parental consent goes through them step by step. This page is not legal advice: our partner law firm reviews the grey areas.

A child is anyone under 18

The Act uses one age line, 18 (Section 2(f)). There is no lower tier. GDPR Article 8 differs: it sets 16, which a member state may lower to 13.

Verifiable consent comes first

Before you process a child’s personal data, you need verifiable consent from a parent or lawful guardian (Section 9(1)). Not after sign-up. Before any processing.

No tracking, monitoring or targeted ads

You must not track or monitor a child’s behaviour, or run targeted advertising directed at children (Section 9(3)). The penalty for breaching the duties on children’s data can be up to ₹200 crore (Schedule, item 3).

You must check the parent is an adult

Rule 10 asks you to check, with due diligence, that the person giving consent is an identifiable adult. You can use identity and age details you already hold, or details the person gives you, directly or through a virtual token from an authorised entity such as DigiLocker. The Rules name no single method.

The Fourth Schedule has narrow exemptions

Educational institutions are exempt from Section 9(1) and 9(3) only for tracking and behavioural monitoring done for educational activities or safety, and only on conditions. Whether an edtech company counts as an educational institution is not settled. Do not assume the exemption applies to you.

Age checks are an exempt purpose

The Rules treat confirming that a user is not a child as an exempt purpose, and so is creating an email-only account. Checking age is not itself the problem. Keeping and using what you collect is.

What DPDP changes for edtech.

Core duties start on 13 May 2027. Each one needs a change in the product and evidence that it works. The consent log follows the pattern in our note on DPDP consent log engineering.

Age gate and parent verification

What changesAn age check at sign-up, then a parent verification step that tests for an identifiable adult before any learner data is processed.

EvidenceVerification records and a flow diagram

Notice for parents

What changesA standalone notice with an itemised description of the data, the purposes and the services, with links to withdraw, exercise rights and complain to the Board, in English or an Eighth Schedule language.

EvidenceVersioned notices in each language

Consent records

What changesA log that ties each consent to a child account, the parent, the notice version and the time. You must be able to prove notice and consent in any proceeding (Section 6(10)).

EvidenceConsent log and withdrawal records

Withdrawal

What changesWithdrawing is as easy as giving consent (Section 6(4)). Processing and processors stop within a reasonable time.

EvidenceWithdrawal log with each downstream step

Tracking and SDK review

What changesA list of every SDK and tag in each app. Behavioural tracking and ad identifiers are switched off or removed where children use the product.

EvidenceSDK register and release checks

AI tutors and personalisation

What changesA review of which signals each model or recommendation feature reads. Personalisation may count as behavioural monitoring, which the Act does not define, so each feature gets a documented decision.

EvidenceFeature register with the decision and its reason

Retention and erasure

What changesA retention period for learner data, parent data and recordings, with deletion jobs that reach processors and backups.

EvidenceRetention schedule and deletion logs

Breach notification

What changesOne runbook that tells affected people and the Data Protection Board without delay, with a detailed report to the Board within 72 hours, and CERT-In within 6 hours.

EvidenceTested runbook and incident records

SDKs, AI tutors and the open questions.

Mobile SDKs often collect advertising identifiers by default, so an app for children needs an SDK data audit. Learner questions that go to an AI model are covered in DPDP and AI tools. As of November 2026 no notification has been issued under Section 9(5) for processing that is verifiably safe for children, and the Rules name no method for Rule 10. Where the law is open, we document the choice you made and why.

  1. Step 1

    Map

    Find learner, parent and partner data across apps, tools and vendors, and which of it belongs to children.

  2. Step 2

    Assess

    Compare each flow against Section 9, Rule 10 and the Fourth Schedule, and flag open questions for the law firm.

  3. Step 3

    Build

    Age gate, parent verification, consent log, withdrawal, SDK controls and deletion jobs, in your stack.

  4. Step 4

    Evidence

    Logs and records you can show a school, an investor or the Board.

DPDP for edtech: FAQs.

Who counts as a child under the DPDP Act?

Anyone under 18. The Act has no lower age tier. A 16-year-old learner is a child, and you need verifiable parental or guardian consent before processing their personal data.

Can we still personalise learning for under-18s?

Possibly, but treat it with care. The Act bars tracking and behavioural monitoring of children and does not define behavioural monitoring. Personalisation may count. Review each feature, record the decision and take legal advice on the grey areas.

Does the educational institution exemption cover edtech platforms?

Do not assume it does. The Fourth Schedule exempts educational institutions for tracking and behavioural monitoring done for educational activities or safety, on conditions. Whether a private edtech company is an educational institution is not settled, so plan as if Section 9 applies in full.

How do we verify that a parent is an adult?

Rule 10 asks for due diligence that the person is an identifiable adult. You can use details you already hold, or details given directly or through a virtual token from an authorised entity, such as DigiLocker. The Rules name no method, so we help you choose one and document why it is enough.

How long must we keep parental consent records?

The Act sets no fixed period for a fiduciary’s consent records. Keep them long enough to prove consent if challenged (Section 6(10)), and at least the one-year minimum for logs under Rule 8(3). Consent Managers have a separate seven-year duty.

When do these duties start?

Core duties, including those on children’s data, start on 13 May 2027. We recommend building age checks and parent verification well before then, because they change sign-up flows and need testing.

Find out what DPDP changes for your learners’ data.