Short answer: build a parent check that runs before you process any personal data of a child, and make it prove that the adult is identifiable. The DPDP Act treats everyone under 18 as a child. Section 9(1) says you must get verifiable parental consent before processing, and Rule 10 says how to check the parent: use reliable identity and age details you already hold, or details the parent gives you, directly or through a virtual token from an authorised entity such as DigiLocker. The Rules name no single method, so edtech teams pick from a few designs: a verified existing parent account, a DigiLocker or other token, or a parent-supplied ID check. Then log the outcome as proof. The duty starts on 13 May 2027.
This post covers the engineering: the options, the flow, the consent record and what changes for AI tutors. It is not legal advice. Whether a particular method satisfies Rule 10, and whether a Fourth Schedule exemption covers your product, are questions for counsel. Our edtech DPDP page puts these checks in the context of a full programme.
What does verifiable parental consent mean under the DPDP Act?
Three provisions do the work:
- Section 2(f): a child is an individual who has not completed 18 years. There is no lower tier, so a 17-year-old needs the same parental consent as a 6-year-old.
- Section 9(1): before processing any personal data of a child, the Data Fiduciary must obtain verifiable consent of the parent, in the manner prescribed. The consent must come first. Collecting the child's details first and asking the parent later is the wrong order.
- Section 9(3): no tracking or behavioural monitoring of children, and no targeted advertising directed at children. A breach of the Section 9 duties carries a penalty of up to ₹200 crore under the Schedule to the Act.
Rule 10 of the DPDP Rules, 2025 sets the manner. Rules 10 to 12 come into force 18 months after the Rules were published, so your child-data duties start on 13 May 2027. The Removal of Difficulties Order, 2026 (S.O. 5458(E), 5 October 2026) made only a wording fix to Section 9(1), adding the missing word "of" in the phrase "or of a person with disability". As of November 2026 we have found no Section 9(5) notification setting an age above which a fiduciary is exempt for "verifiably safe" processing. Plan for 18 as the line.
What does Rule 10 require you to check?
Rule 10(1) asks for appropriate technical and organisational measures, plus due diligence, to check that the person identifying herself as the parent is an adult who is identifiable. An adult is someone who has completed 18 years. You make the check by reference to either:
- (a) reliable details of identity and age of that individual that you already hold, or
- (b) details of identity and age that the individual voluntarily provides, either directly, or through a virtual token mapped to those details and issued by an authorised entity.
An authorised entity is one entrusted by law or by the Central or a State Government to issue identity and age details or such a token, or a person it appoints or permits. The definition also covers details or tokens made available and verified by a Digital Locker service provider.
The Rule's illustration walks through the cases. It applies whether the child tells you about the parent or the parent opens the account for the child.
| Situation | What the illustration says you do before processing the child's data |
|---|---|
| Parent is already a registered user on your platform and gave identity and age details earlier | What the illustration says you do before processing the child's data: Check that you hold reliable identity and age details for the parent and that the parent is an identifiable adult |
| Parent is not a registered user | What the illustration says you do before processing the child's data: Check that the parent is an identifiable adult, by reference to details issued by an entity entrusted by law or Government, or a virtual token mapped to them. The parent may make the details available through a Digital Locker service provider |
Two points are easy to miss. First, the Rule asks you to check the adult. It does not describe a check on the family relationship, so ask counsel whether your product needs more. Second, "reliable" matters. A date of birth a parent typed at sign-up and you never verified is hard to call reliable.
What are the implementation options for edtech?

No method is named in the Rules, so the table lists ways to meet Rule 10, not approved methods. Each maps to part (a) or (b) of the Rule.
| Option | How it maps to Rule 10 | Data you end up holding | Watch-outs |
|---|---|---|---|
| Verified existing parent account | How it maps to Rule 10: 10(1)(a): reliable details you already hold | Data you end up holding: Nothing new, if the parent was verified earlier | Watch-outs: Only counts if the earlier verification gave identity and age details you can call reliable. Link each child to the parent record, and handle several children per parent |
| DigiLocker or another authorised-entity token | How it maps to Rule 10: 10(1)(b)(ii): virtual token mapped to identity and age details | Data you end up holding: A token or a result such as "adult, identity matched", plus a reference. Not the document | Watch-outs: Confirm the provider qualifies as an authorised entity or notified Digital Locker service provider. Plan a fallback for parents who cannot use it |
| Parent provides ID details directly | How it maps to Rule 10: 10(1)(b)(i): details voluntarily provided by the individual | Data you end up holding: ID images or numbers, unless you discard them after the check | Watch-outs: Heavy on data and a breach target. Keep the result, delete the image, and protect it meanwhile under your Section 8(5) safeguards |
| School-led onboarding | How it maps to Rule 10: Depends on who is the Data Fiduciary | Data you end up holding: Depends on the contract | Watch-outs: If the school decides the purposes and you act for it, you may be a processor. Write into the contract who runs the Rule 10 check and keeps the evidence |
| Tick-box, typed birth year, email or phone OTP, card payment alone | How it maps to Rule 10: None of these, on its face, gives you identity and age details to check against | Data you end up holding: Low | Watch-outs: Can be useful signals. We would not rely on any of them alone for Rule 10. Counsel decides |
Offer two routes where you can, for example a token first and an ID check as the fallback, so a parent without one route is not locked out.
How should the parental consent flow work, step by step?
- Age gate, with the least data. Rule 12 and Part B of the Fourth Schedule exempt processing needed to confirm that a user is not a child. Ask for an age band or a yes or no on being 18, and store the result, not a birth date, unless you need it elsewhere.
- Hold the child's data back. For anyone under 18, create nothing beyond a pending record. No profile, no analytics events, no third-party SDK calls, no content personalisation until the parent has consented.
- Identify the parent. Collect the parent's contact details and send a link. The parent then goes through your chosen Rule 10 route.
- Check, then notify. Confirm the parent is an identifiable adult. Show a notice with or before the consent request (Section 5). It must say what data is processed, why, how to exercise rights and how to complain to the Board, in English or an Eighth Schedule language.
- Take the consent. Section 6 asks for consent that is free, specific, informed, unconditional and unambiguous, by a clear affirmative action, limited to necessary data. Do not bundle optional purposes such as marketing or model training into the same tick.
- Activate and log. Release the child's account only after the consent event is written. If the parent never completes, expire the pending record on a set date and delete it.
Rule 3 adds that the notice must be standalone, with an itemised description of the data, the purposes and the services. Write it for the parent, not the child.
What should you record as proof of parental consent?
Section 6(10) puts the burden on you: in any proceeding, the fiduciary must prove that notice was given and consent obtained. A consent log is your evidence. Keep the event, not the identity document.
| Field | Why it is there |
|---|---|
| Child record ID and parent record ID | Why it is there: Links consent to the right child without storing extra identity data in the log |
| Rule 10 route used and its outcome | Why it is there: Shows which check ran and that it passed, for example "token verified, adult" |
| Token or verification reference and timestamp | Why it is there: Lets you show when and how the check ran |
| Notice version and language shown | Why it is there: Proves what the parent was told |
| Purposes consented to, one flag per purpose | Why it is there: Lets you stop one purpose without stopping all |
| Consent timestamp, device or session ID | Why it is there: Ties the action to a clear affirmative act |
| Withdrawal timestamp and the systems that acted on it | Why it is there: Evidence that processing stopped, including at processors |
The Rules set no fixed retention period for a fiduciary's consent records. The seven-year minimum applies to Consent Managers. For your own log, keep records long enough to prove consent under Section 6(10), and at least the one-year Rule 8(3) minimum for logs. Ask counsel for the period. Our consent management service builds this log, and our consent log post goes into the schema.
How do withdrawal, correction and a child turning 18 work?
- Withdrawal. It must be as easy as giving consent (Section 6(4)). Offer it in the parent's account and in the app. After withdrawal, you and your processors must stop within a reasonable time (Section 6(6)). Deletion jobs should run from your erasure workflow and reach every vendor.
- Rights requests. The parent acts for the child. Route access, correction and erasure requests through your rights-request workflow with the parent's identity checked.
- Turning 18. The child stops being a child on the 18th birthday. Plan to ask the person for their own consent at that point. Whether the parent's consent carries over is a question for counsel, so build the trigger first and settle the rule later.
Which edtech products are exempt from the parental consent rule?
Rule 12 and the Fourth Schedule lift Section 9(1) and 9(3) for some fiduciaries and purposes, subject to conditions. They do not lift the rest of the Act: notice, security, erasure and Section 9(2), which bars processing likely to harm a child's well-being, still apply.
| Part A class | Condition (summary) |
|---|---|
| Clinical establishments, mental health establishments, healthcare professionals, allied healthcare professionals | Condition (summary): Health services or treatment support, only as far as needed to protect the child's health |
| Educational institutions | Condition (summary): Tracking and behavioural monitoring only for the institution's educational activities, or for the safety of enrolled children |
| Crèches and child day care | Condition (summary): Tracking and behavioural monitoring only for safety |
| Transport providers engaged by schools or crèches | Condition (summary): Tracking location during travel to and from the institution, for safety |
Part B lists purposes, each limited to what is necessary. They include functions in the child's interest under a law, State benefits under Section 7(b), creating an email-only account, tracking real-time location for the child's safety, blocking information or advertising likely to harm the child, and confirming that the user is not a child.
The Schedule defines an educational institution as "an institution of learning that imparts education, including vocational education". We have found nothing that says whether an edtech platform counts. Edtech firms should not assume the exemption applies. An app sold directly to parents is the weakest case. A tool used inside a school, run for the school's educational activities, is a stronger one. Get counsel's written view before you rely on it, and keep the exemption narrow even then.
What changes for AI tutors and children's data?

The Act does not define "tracking" or "behavioural monitoring". A tutor that records how a child answers, then adapts the next lesson, may count as behavioural monitoring. We would not call AI tutors banned. We would treat personalisation as a design choice that needs parental consent and, if you claim an exemption, a documented basis. These are the product changes that reduce the exposure:
- Separate in-session adaptation from stored profiles. Adapting a lesson inside one session is different from building a long-term record of a child's behaviour. Keep the stored profile to what the learning purpose needs.
- No advertising, no ad SDKs in child-facing apps. Section 9(3) bars targeted advertising directed at children. Audit every SDK. Firebase and GA4 create an app-instance ID automatically and collect the advertising ID by default where available. The Meta SDK logs installs, launches and purchases automatically unless you set `AutoLogAppEventsEnabled` to false. Our mobile SDK audit covers the checks.
- Treat model training as its own purpose. Do not train on a child's chats or recordings unless the notice names it, the parent consents to it separately, and the model vendor's terms agree.
- Minimise what reaches the model. Strip names, school, contact details and location from prompts before they reach any provider. See our post on PII redaction for LLMs, and check each vendor's retention, training and processing region against our DPDP-compliant AI architecture guide.
- Set short retention for chat logs. Keep transcripts only as long as the learning purpose and your proof duties need, and delete them on withdrawal.
- Guard against harm. Section 9(2) bars processing likely to harm a child's well-being. Add content filters, escalation for distress and a human review route, and keep the evidence.
What about guardians of a person with a disability?
Section 9(1) also covers a person with a disability who has a lawful guardian. Rule 11 asks you to observe due diligence to verify that the guardian was appointed by a court, a designated authority or a local level committee under the applicable guardianship law. That is a different check from Rule 10. If your product serves such users, a manual review queue with a record of what the reviewer checked is a practical start.
How does this compare with GDPR Article 8?
GDPR Article 8 sets the age of digital consent at 16, and member states may lower it to 13. Below that age, the controller must make reasonable efforts to verify parental authorisation, taking available technology into account. India sets one threshold at 18 and a more prescriptive check on the adult. Your Article 8 flow will need a separate path for Indian users.
What should an edtech team build before 13 May 2027?
- Pick the Rule 10 routes and get counsel's written view on each.
- Build the age gate, the pending state, the parent notice, the consent screen and the consent log.
- Wire withdrawal to every system and processor, and test it.
- Audit SDKs, ad IDs and AI vendor flows in child-facing products.
- Plan for existing child users. Section 5(2) requires a notice for earlier consents as soon as reasonably practicable, and counsel should say whether they also need a fresh parent check.
- Write down your exemption position, if any, with the counsel opinion attached.
If you want a second pair of engineering eyes first, a gap assessment maps these items against your actual systems. Mono is not a law firm and does not certify compliance. Legal sign-off goes to counsel.
Sources: Digital Personal Data Protection Act, 2023, Sections 2(f), 5, 6, 8, 9 and the Schedule (meity.gov.in). Digital Personal Data Protection Rules, 2025, Rules 3, 8, 10, 11 and 12 and the Fourth Schedule (dpbi.gov.in). The Removal of Difficulties Order, 2026, S.O. 5458(E), 5 October 2026 (dpbi.gov.in). GDPR Article 8 (gdpr-info.eu). Apple, Google and Meta developer documentation on SDK data collection. Last reviewed 20 November 2026.
FAQ
What is verifiable parental consent under the DPDP Act?
It is the consent of a child's parent, obtained before any processing of the child's personal data, with a check that the person giving it is an identifiable adult. Section 9(1) of the DPDP Act sets the duty and Rule 10 of the DPDP Rules, 2025 sets the manner. A child is anyone under 18. The duty starts on 13 May 2027.
How can an app verify a parent under Rule 10?
Rule 10 lets you check by reference to reliable identity and age details you already hold, or details the parent provides voluntarily, directly or through a virtual token from an authorised entity such as DigiLocker. The Rules name no single method. Common designs are a verified existing parent account, a DigiLocker or other token, and a parent-supplied ID check, with the result logged and the document discarded.
Is a tick-box saying 'I am over 18' enough for DPDP?
We would not rely on it alone. Rule 10 asks the fiduciary to check that the parent is an identifiable adult using identity and age details, and a tick-box gives you none to check. It can work as a signal inside a stronger flow. Counsel should confirm what is enough for your product.
Are edtech platforms exempt from parental consent under the DPDP Rules?
Not automatically. The Fourth Schedule exempts educational institutions from Section 9(1) and 9(3) only for tracking and behavioural monitoring for their educational activities or children's safety. It defines an educational institution as an institution of learning that imparts education, including vocational. Whether an edtech platform counts is unconfirmed, so edtech firms should not assume the exemption applies.
Can an AI tutor personalise lessons for children under DPDP?
Possibly, with parental consent and care. Section 9(3) bars tracking and behavioural monitoring of children, and the Act does not define those terms, so personalisation may count as behavioural monitoring. Keep adaptation inside the session where you can, limit stored profiles, avoid advertising and ad SDKs, and take legal advice before relying on an exemption.
