Skip to content
DPDP
Edtech·sector risk profile

Built for Learners, Governed for Children

If your users are under eighteen, the Act changes the rules entirely — verifiable parental consent, no behavioural advertising, and no tracking that could harm a child.

Max penalty on children's data
₹200 crMax penalty on children's data
Sector capabilities
8Sector capabilities
Recommended plan
StarterRecommended plan

Where Edtech programmes usually break

  • Verifiable parental consent

    A checkbox is not verification. You need a defensible method and a record of it.

  • No behavioural targeting

    Advertising and tracking aimed at children are prohibited, not merely discouraged.

  • Age assurance

    You must know which accounts are children's before you can apply the right rules.

  • Alumni data

    Learners leave, records stay. Retention windows must survive the account being abandoned.

How it works inside a edtech stack

  1. 1Day 1

    Add age assurance

    Identify which accounts belong to children before any other rule can be applied correctly.

  2. 2Week 1

    Switch on parental consent

    Verifiable consent flow for under-eighteen accounts, with the verification method recorded.

  3. 3Week 1

    Strip child-facing tracking

    Behavioural tags blocked on child accounts, enforced at the tag layer rather than by policy.

  4. 4Week 2

    Set alumni retention

    Windows that keep working after a learner stops logging in.

Built for edtech compliance requirements

  • Age assurance and account classification
  • Verifiable parental consent capture
  • Behavioural tracking blocks for minors
  • Alumni and dormant account retention
  • Institution and school DPA tracking
  • Guardian rights request handling
  • Classroom analytics without identifiers
  • Consent transition at eighteen

What changes for a edtech team

Without the platform

  • Self-declared age treated as verification
  • Behavioural ad tags firing on child accounts
  • Alumni records kept indefinitely because nobody owns them
  • Guardians with no route to exercise rights

With the platform

  • Child accounts identified and governed differently
  • Parental consent captured with a defensible method
  • Tracking blocked at the tag layer for minors
  • Retention that runs on dormant accounts too

Modules that close these gaps

Recommended plan

Starter

Most edtech platforms start below 10,000 data principals per institution, and Starter covers consent, rights and notices. Move to Growth when discovery and DPIA become the constraint.

See plan details

Common questions

A method you can evidence — not a checkbox. The Rules point to reliable identity or virtual token based verification; the record of which method was used matters as much as the consent.

Get the DPDP readiness checklist, free

42 questions covering every operative section of the Act. No account needed — tell us where to send it.

Send me the checklist
30 minutes·one real data flow

Ready to Simplify DPDP Compliance?

Most vendors open a deck. We open the product, map one of your real data flows, and tell you honestly how far you are from compliant.

  • No slides
  • No obligation
  • Data stays in India

What the 30 minutes looks like

  1. 0–5Your stack, in your wordsWhere data lands today, and who already owns it.
  2. 5–15One real flow, mapped liveWe connect a sample source and build the map on the call.
  3. 15–25Where you are exposedThe gaps we can see, ranked — including the ones you already knew.
  4. 25–30Effort and costWhat closing them takes, and whether we are the right answer.

If we are not the right fit, we will say so on the call rather than three follow-ups later.