Education
DPDP compliance for schools, colleges and EdTech
Last reviewed 15 November 2026
Schools hold data on students, parents, teachers and staff: admission records, attendance, grades, health notes, photographs, biometric attendance and school-bus locations. Most of those students are children in the eyes of the Digital Personal Data Protection Act, 2023. This page explains the obligations that matter most to schools, colleges, coaching centres and EdTech platforms.
Children are anyone under 18
The Act defines a child as an individual who has not completed eighteen years. That covers every school pupil and many first-year college students. Before processing a child’s personal data, a Data Fiduciary must obtain verifiable consent of the parent or lawful guardian. It must not process data in a way likely to harm a child’s well-being, and it must not track or behaviourally monitor children or direct targeted advertising at them. Breaching these duties carries a penalty of up to ₹200 crore.
What verifiable parental consent means
Rule 10 requires you to adopt technical and organisational measures to ensure verifiable consent is obtained, and to check that the person claiming to be the parent is an identifiable adult. You can do that by reference to reliable identity and age details you already hold, such as a parent registered with the school, or to details the parent voluntarily provides or provides through a virtual token issued by an authorised entity, including through a Digital Locker service provider. A tick box that a child can click is not enough.
The education exemption, read carefully
The Rules recognise that schools need to monitor and track some things. They exempt educational institutions from the parental-consent and tracking restrictions, but only where processing is restricted to tracking and behavioural monitoring for the institution’s educational activities or for the safety of enrolled children. Transport providers engaged by a school or crèche have a similar, narrow exemption for tracking in the interest of children’s safety.
The exemption is narrow by design. Using student data for marketing, sharing it with a coaching partner, building profiles for advertisements or running an app that tracks children for commercial purposes falls outside it. Schools should list what they track, why, and which exemption they rely on.
EdTech platforms: no tracking, no targeted ads
EdTech companies are not schools and do not automatically benefit from the school exemption. A learning app used by children generally needs verifiable parental consent, must avoid behavioural monitoring beyond what the Rules permit, and must not serve targeted advertising to children. Product analytics that follow individual children across sessions deserve particular scrutiny. Revisit your analytics, recommendation engines and attribution tools for children’s accounts.
Staff, alumni and parents
Teachers’ and staff data can be processed for employment purposes under the Act’s legitimate use for employment and safeguarding the employer from loss or liability, but you should still be transparent about what you hold. Alumni databases and fundraising or event marketing need consent for those purposes. Parents’ contact details used for fee reminders and notices are covered by the purposes for which they were provided, but newsletters from third parties are not.
Vendors and everyday tools
- School management and ERP systems, which hold admissions, attendance and grades.
- Learning platforms, video-conferencing and online assessment tools.
- Biometric attendance, CCTV and school-bus tracking providers.
- Payment gateways for fees, and SMS or WhatsApp providers for notices.
- Cloud storage and email providers.
Security and breach duties
Schools are not exempt from the security safeguards in Rule 6: encryption or masking, access controls, logging and monitoring with logs retained for a year, backups and security terms in vendor contracts. If student data is breached, Rule 7 requires prompt notice to each affected person, here usually the parent, and to the Data Protection Board, with a detailed report within 72 hours. A school without an incident plan will struggle to meet these timelines.
How Complisarthi helps education providers
- Compliance Audit shows your readiness and the gaps with children’s data.
- Policy Generator drafts a clear privacy notice for parents, with a children’s data section.
- Consent Manager records and withdraws consent, and tracks access, correction and erasure requests.
- Vendor Risk Tracker and DPA Generator cover your ERP, learning and transport vendors.
- Data Classification flags children’s data, helping you restrict who can see it.
- Breach Response gives you a countdown, templates and a log.
Check your school’s DPDP readiness
Start with the free compliance audit: about 10 minutes, no credit card, and a ranked list of what to fix first.
Check Your Compliance Score — Free