DPDPA for schools, platforms and learning apps
Learning products collect data about children, often through a school or a parent. The Act asks for verifiable parental consent and limits how you can track and target children.
Customer journey
- 1Sign-upCONSENT
- 2LearningPURPOSE
- 3AssessmentsSECURITY
- 4Parent requestsRIGHTS
- 5Leaving the platformRETENTION
Where EdTech gets hard
Parental consent
You need a way to confirm that the adult is a parent or guardian.
Tracking and ads
Analytics and advertising on products used by children need a careful look.
School and platform roles
Who decides why data is used, the school or you, shapes your duties.
Old accounts
Learners leave. Their data should not stay forever.
How the three stages apply
Consulting
Map data across the app, school systems and analytics.
See consultingImplementation
Parental consent at sign-up, deletion when learners leave.
See implementationGovernance
Vendor reviews and breach drills on a schedule.
See governance
EdTech questions
For children, the Act asks for verifiable consent from a parent or guardian, with limited exceptions set by the Rules. We map which of your uses fall under it.
Be careful. The Act limits tracking and targeted advertising aimed at children. We review each tool you use.
It depends on who decides why and how the data is used. Contracts should say so plainly.
With a map of what data you hold about learners, then consent at sign-up.
Get the EdTech checklist
One page: the duties that matter most for learning products, in order.