Sector guidesUpdated 22 November 20269 min read

Children's Data & Verifiable Parental Consent for EdTech AI

How EdTech companies using AI tutors, proctoring and learning analytics must handle under-18 learners' data under DPDP section 9, Rule 10 and the Fourth Schedule.

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

Child threshold
Under 18 years
Parental consent
Rule 10 verifiable consent
Institution exemption
Fourth Schedule Part A item 3
Exempt scope
Tracking/monitoring for educational activities or safety
Penalty, children's obligations
Up to ₹200 crore
Applies from
13 May 2027

Quick answer

EdTech platforms serving learners under 18 must obtain verifiable parental consent under Rule 10 and must not track, behaviourally monitor or target ads at children under section 9(3), from 13 May 2027. The Fourth Schedule exempts educational institutions only for tracking and monitoring for educational activities or safety, so a direct-to-consumer EdTech app should not assume the exemption covers it.

  • Most K-12 and many test-prep learners are children under DPDP because the threshold is 18, not 13.
  • Rule 10 requires verifiable consent from a parent confirmed to be an identifiable adult, for example through a DigiLocker token.
  • The Fourth Schedule Part A exemption covers 'educational institutions' and is limited to educational activities and safety.
  • AI tutors that profile learning behaviour across sessions sit close to section 9(3)'s ban on behavioural monitoring.
  • Section 9(2) — no detrimental processing — applies to every EdTech provider without exception.

Who this is for: EdTech founders and product heads, AI tutor and adaptive learning teams, Online test-prep platforms, Learning management system vendors, Data Protection Officers in education

Who counts as a child for EdTech under DPDP?

The DPDP Act defines a child as an individual who has not completed eighteen years, and for a child "Data Principal" includes the parents or lawful guardian. For EdTech that means:

  • Every school-age learner on a K-12 platform is a child.
  • Most JEE, NEET and board-exam test-prep users are children for at least part of their time on the platform.
  • Coding, language and skilling apps marketed to teenagers process children's data.
  • College and adult upskilling platforms may still have under-18 users and need age assurance.

Section 9 imposes three duties for children's data: verifiable parental consent before processing (s. 9(1)), no processing likely to cause a detrimental effect on the child's well-being (s. 9(2)), and no tracking, behavioural monitoring or targeted advertising directed at children (s. 9(3)).

These apply from 13 May 2027, along with Rule 10 (how to get parental consent) and Rule 12 with the Fourth Schedule (exemptions). Non-fulfilment of children's obligations carries a penalty of up to ₹200 crore per instance.

Many EdTech platforms built for the 13+ assumptions common in foreign app-store policies need to re-architect sign-up for an 18 threshold.

Does the educational institution exemption cover EdTech?

Fourth Schedule Part A item 3 disapplies sections 9(1) and 9(3) for "a Data Fiduciary who is an educational institution", subject to the condition that processing is restricted to tracking and behavioural monitoring (a) for the educational activities of the institution, or (b) in the interests of safety of children enrolled with it. The Schedule's note defines "educational institution" as an institution of learning that imparts education, including vocational education.

How that maps to EdTech models:

ModelExemption position
School or college using an LMS or AI tutor for its own studentsInstitution is the fiduciary; exemption can apply within its conditions
EdTech vendor providing that LMS to the schoolTypically a processor for the school; works within the school's exemption and instructions
Direct-to-consumer learning appWhether it is an "institution of learning" is untested; do not assume the exemption
Coaching centre with online classesArguable as an institution imparting education; take advice

Even where the exemption applies, it is narrow. It covers tracking and behavioural monitoring for educational activities or safety — not targeted advertising, not selling leads, not marketing upsells. And section 9(2) still applies.

The safest D2C design assumes no exemption: obtain parental consent and avoid behavioural profiling outside what a parent has clearly consented to and the law allows. See Fourth Schedule exemptions and DPDP for schools and colleges.

Rule 10 requires technical and organisational measures to obtain verifiable parental consent before processing any child's personal data, and due diligence that the person identifying as parent is an identifiable adult (18+), using:

  • reliable identity and age details the platform already holds; or
  • details voluntarily provided by the individual; or
  • a virtual token mapped to identity and age details, issued by an authorised entity, including through a Digital Locker service provider.

The Rule's illustrations cover both EdTech patterns: the child signs up and names a parent (Cases 1–2), or the parent opens the account for the child (Cases 3–4). Parents already registered with reliable details can be checked against what you hold; new parents verify through government-issued details or a token.

EdTech-specific design points:

  1. Parent-first onboarding for K-12 — parents usually pay, so make the parent account primary and add child profiles beneath it.
  2. Minimal pre-consent collection. Before consent, collect only the child's age declaration and parent contact.
  3. Per-child consent record with notice version, verification method and timestamp.
  4. Free trials. A free trial that collects a child's data needs consent first; there is no trial exemption.
  5. School-issued accounts. Where the school is the fiduciary, follow the school's consent process instead.

See age verification and DigiLocker tokens.

AI tutors, proctoring and learning analytics

EdTech AI features need a section 9(3) review, because much of what makes adaptive learning work is behavioural monitoring.

  • AI tutors. Within-session adaptation to the current question is low risk. Cross-session learner models that track mistakes, pace and engagement are behavioural monitoring. For an exempt institution, that is permissible for educational activities; for a D2C app, rely on clear parental consent and keep the profile strictly educational.
  • Proctoring. Webcam, screen and keystroke monitoring during exams is intensive tracking. Within an institution's assessments, it may fit "educational activities"; outside, scope it narrowly to the exam session and delete recordings on schedule.
  • Engagement nudges. Streaks, notifications and recommendations optimised for time-on-app are hard to justify as educational and raise section 9(2) concerns.
  • Chat safety. Safety classifiers that keep harmful content away from children are covered by Fourth Schedule Part B item 5.
  • Marketing. Targeted ads to children, and using learners' performance data to target upsell campaigns at them, fall within section 9(3)'s prohibition.

Mask learner identifiers before LLM calls, and keep children's prompts out of vendor training. More in AI products for children.

Retention, security and breach for learner data

Learner records are long-lived by nature — transcripts, certificates, assessment history — and the Act lets you keep data needed for the purpose or required by law. Separate what is needed from what is merely accumulated:

  • Keep: enrolment, results and certificates for as long as the learning relationship and any applicable education laws require.
  • Expire: raw proctoring video, chat transcripts with tutors, clickstream and engagement telemetry, on defined schedules.
  • Rule 8(3): processing logs and associated personal data must be kept for at least one year from processing, then erased unless another law requires longer.

Security under Rule 6 should reflect that a children's data breach is high-impact: encryption of recordings and assessment data, strict access control for tutors and support staff, and monitoring.

Under Rule 7, every breach must be notified to affected Data Principals — for a child, that is the parent — without delay, and to the Board with a detailed report within 72 hours. Notices should go to the parent's registered contact and be written for parents.

Publish a contact person (Rule 9) and a grievance channel with a response period of not more than 90 days (Rule 14(3)) that parents can use.

EdTech readiness plan to 13 May 2027

  1. Age reality check (December). Estimate how many users are under 18 and where they enter the funnel.
  2. Role mapping (December). For B2B school deployments, confirm you are a processor and update contracts; for D2C, you are the fiduciary.
  3. Parent-first onboarding (January–March). Build Rule 10 verification with token-based options for parents not already verified.
  4. Feature review (February). Classify every AI and analytics feature against section 9(3); turn off targeted ads and engagement profiling for child accounts.
  5. SDK and marketing audit (March). Remove ad-tech and lead-sharing that touches children's data.
  6. Retention schedules (March–April). Set expiry for proctoring video, tutor chats and telemetry; configure Rule 8(3) one-year logs.
  7. Re-notice existing families (April–May). Send Rule 3-compliant notices to parents of existing child users, and seek parental consent where you hold none.

Schools buying EdTech will also ask for this evidence in procurement from 2027, so the work doubles as sales enablement.

Further reading on suhasbhairav.com

Before 13 May 2027

Compliance checklist

  1. Raise the age threshold to 18

    Treat every user under 18 as a child for consent, profiling and advertising purposes.

    DPDP Act s. 2; s. 9

  2. Implement verifiable parental consent

    Verify the parent is an identifiable adult using held data, provided details or a virtual token before processing the child's data.

    Rule 10(1)

  3. Offer DigiLocker-based parent verification

    Accept identity and age tokens from a Digital Locker service provider for parents not already verified.

    Rule 10(2)(b)

  4. Confirm whether the institution exemption applies

    Rely on Fourth Schedule Part A item 3 only as or for an educational institution and only for educational activities or safety.

    Rule 12; Fourth Schedule

  5. Turn off targeted advertising for learners

    Remove personalised ads and upsell targeting based on children's behaviour or performance.

    DPDP Act s. 9(3)

  6. Scope AI tutor memory

    Limit learner models to educational purposes and prefer within-session adaptation for D2C products.

    DPDP Act s. 9(3)

  7. Set retention for proctoring and chats

    Define expiry for recordings, tutor transcripts and telemetry, subject to the one-year log minimum.

    Rule 8(3)

  8. Write breach notices for parents

    Prepare plain-language Rule 7 notices addressed to parents' registered contacts.

    Rule 7(1)

  9. Update school contracts

    Act as processor on the school's instructions, with security, retention and breach terms.

    DPDP Act s. 8(2); Rule 6(1)(f)

Key dates

  1. DPDP Rules notified

  2. Section 9, Rules 10 and 12 apply to EdTech platforms

Answers

Frequently asked questions

Do EdTech apps need parental consent under DPDP?

Yes, for any learner under 18, unless a Fourth Schedule exemption applies. From 13 May 2027, Rule 10 requires verifiable consent from a parent who is confirmed to be an identifiable adult, using details the platform holds, details provided by the parent, or a virtual token such as one made available through DigiLocker.

Is an EdTech company an 'educational institution' under the Fourth Schedule?

The Schedule defines an educational institution as an institution of learning that imparts education, including vocational education. A school using an EdTech platform clearly qualifies; a direct-to-consumer app's position is untested. Even where it applies, the exemption covers only tracking and behavioural monitoring for educational activities or safety.

Can an AI tutor track a student's progress under DPDP?

An educational institution may track and monitor enrolled children for educational activities under Fourth Schedule Part A item 3. Outside that, cross-session learner profiling is behavioural monitoring under section 9(3). D2C platforms should keep adaptation within sessions or limit profiles strictly to educational use and take advice.

Can EdTech platforms show ads to students under 18?

Targeted advertising directed at children is prohibited by section 9(3), and the educational institution exemption does not extend to advertising. Using a learner's behaviour, performance or profile to target ads or upsell offers at the child should be switched off for under-18 accounts.

Who gets the breach notice when a child's data is leaked?

For a child, the Data Principal includes the parent or lawful guardian, so Rule 7 notices should go to the parent's registered contact, without delay, describing the breach, likely consequences, mitigation and safety steps, with a contact person. The Board must receive a detailed report within 72 hours.

Are online proctoring recordings allowed under DPDP?

Proctoring is intensive monitoring. Within an educational institution's assessments, it may fall under the Fourth Schedule exemption for educational activities. Otherwise, rely on clear parental consent for children, limit monitoring to the exam session, secure recordings under Rule 6 and delete them on a defined schedule.

Legal references and sources

  • Digital Personal Data Protection Act, 2023 — Section 9 (official text)
  • Digital Personal Data Protection Rules, 2025 — Rule 10 (official text)
  • Digital Personal Data Protection Rules, 2025 — Rule 12; Fourth Schedule Part A item 3 (official text)
  • DigiLocker — Digital Locker service provider (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.