DPDP for schools, colleges and coaching
Most of the people a school serves are children, and the Act treats children’s data with its strictest rules. Anyone under 18 is a child. A school also holds data about parents, teachers and visiting faculty, and runs an ERP, a learning platform, EdTech apps, biometric attendance and CCTV, each of which brings children’s data into another system.
Verifiable parental consent, and what may not be done at all
Before processing a child’s personal data you need verifiable consent from a parent or lawful guardian (s. 9(1)). The Rules describe how to check that the person consenting is an adult who is the parent, for example using details you already hold reliably or an identity token from an authorised source such as DigiLocker.
Separately, you must not track children, monitor their behaviour, or direct targeted advertising at them (s. 9(3)), and must not process their data in a way likely to harm their well-being. This applies to every app and platform you put in front of students, whoever built it.
The Rules exempt educational institutions from some of these requirements for specific purposes: tracking and behavioural monitoring for educational activities and in the interests of children’s safety. The exemption covers those purposes only. A learning app that profiles students to sell them courses is outside it. Under legal review: The scope of the Fourth Schedule exemption for educational institutions, and whether it extends to an EdTech provider acting for the school, should be confirmed.
Students turn 18 during college. From then on the student, not the parent, is the Data Principal who consents and makes requests.
- Needs parental consent
- Admission records, photographs used publicly, learning-app accounts not covered by an exemption.
- Never for children
- Targeted advertising, and tracking or behavioural monitoring outside the exempt purposes.
- At 18
- The student takes over consent and requests from the parent.
The three roles, in a worked case
The Act gives three roles. The Data Principal is the person the data is about. The Data Fiduciary decides why and how it is used, and carries the duties. A Data Processor handles it on the fiduciary’s behalf, under a contract. The same business can be a fiduciary for some data and a processor for other data.
The case
Ananya, aged 11, studies at a private school. The school keeps records in a school ERP, sets homework on a learning platform, uses a third-party EdTech app for maths practice, takes biometric attendance, and runs buses through a transport contractor.
| Role under the Act | In this case |
|---|---|
| Data Principal | Ananya. Because she is a child, her parent or guardian consents on her behalf and exercises her rights. Her teachers are Data Principals for their own staff records and attendance. |
| Data Fiduciary | The school, which decides why her data is collected and used. |
| Data Processor | The ERP and learning-platform providers, the biometric device vendor and, where it acts on the school’s instructions, the transport contractor. |
If the maths app uses Ananya’s activity to recommend paid courses or show adverts, it is deciding its own purpose and becomes a fiduciary, and targeted advertising at a child is prohibited outright. Under legal review: Whether course recommendations amount to targeted advertising under s. 9(3) depends on the facts.
What a school or college holds, and where it goes
| Kind of data | Examples |
|---|---|
| Student records | Name, date of birth, photographs, address, ID numbers such as APAAR or Aadhaar, admission forms |
| Attendance and examinations | Daily attendance, biometric templates, marks, answer scripts, proctoring recordings, report cards |
| Learning activity | LMS submissions, EdTech app activity, online class recordings |
| Sensitive | Health conditions, disabilities, counselling notes, disciplinary records, fee concessions |
| Parents and guardians | Names, phone numbers, occupations, income documents for fee waivers, who may collect the child |
| Faculty and staff | Teacher records, qualifications, salary, ID and police verification, visiting faculty contracts |
| Visual and location | CCTV, bus GPS and cameras, event photographs |
Where it comes in
- Admission and enquiry forms
- School ERP and parent portal
- LMS and EdTech apps
- Biometric attendance devices
- Examinations, online tests and proctoring
- Transport, CCTV and visitor registers
Where it goes
| From | To | What and why |
|---|---|---|
| Parent | School office and ERP | Admission form and documents |
| School ERP | LMS and EdTech apps | Student roster and class lists to create accounts |
| Biometric devices | Attendance system | Templates and attendance marks for students and staff |
| School | Board, university or national portals | Enrolment, examination and academic ID data the rules require |
| School | Transport contractor | Names, addresses and parent numbers for routes; live bus location back to parents |
| Teachers | Parent groups and messaging | Notices, marks and photographs, often with names |
Where schools and colleges are most exposed
| Severity | Risk | Why it matters |
|---|---|---|
| Critical | No verifiable parental consent | Required before processing a child’s data (s. 9(1)), unless an exemption in the Rules applies. |
| Critical | Apps that track or target advertising at students | Prohibited for children regardless of consent (s. 9(3)). |
| High | Marks and ranks published with names | Shared beyond those who need them, often in parent groups or on notice boards. |
| High | Student data on teachers’ personal phones | Data the school cannot control, recover or delete. |
| High | Biometric images stored instead of templates | Raw fingerprints or faces of children kept by a device vendor with no terms. |
| Medium | CCTV and bus cameras with no rules | Footage of children viewable by anyone with the password. |
| Medium | Former students’ and applicants’ records kept indefinitely | Kept long after any record the board requires. |
Who else handles the data
You answer for what your processors do with the data (s. 8(1)), and you need a valid contract with each (s. 8(2)). Some vendors are fiduciaries in their own right; the table says where that is common.
| Vendor | Data they handle | What the contract should cover |
|---|---|---|
| School ERP and parent portal | Admissions, fees, marks, attendance | Access by role; hosting; breach notice; deletion when you leave |
| LMS and EdTech providers | Student accounts, work, activity | No tracking, profiling or advertising; deletion at year end; approved before use |
| Biometric attendance vendors | Templates of students and staff | Templates, not images; stored on the device or by you; an alternative for those who decline |
| Online examination and proctoring | Recordings, ID checks, results | Students told what is recorded; deletion after results and appeals |
| Transport and GPS providers | Addresses, routes, live location, bus camera footage | Location shown only to the route’s parents; short retention |
| Photographers and event vendors | Photographs of children | Use only for the school; no publication without consent |
46 controls written for schools and colleges, on top of 66 common ones
Alongside the common controls, the education assessment asks about children and the systems around them: verifiable parental consent and the institution exemption, EdTech approval and tracking settings, marks and attendance, examinations and proctoring, biometric attendance, CCTV and bus location, teachers’ phones and parent groups, faculty records, and how long student and applicant records are kept.
| Module | What is checked |
|---|---|
| Organisation and role mapping |
|
| Data inventory and purpose |
|
| Notice and transparency |
|
| Consent and lawful basis |
|
| Data Principal rights |
|
| Children and guardians |
|
| Data quality |
|
| Retention and deletion |
|
| Security safeguards |
|
| Breach response |
|
| Processors and vendors |
|
| Data sharing and disclosure |
|
| Transfer and storage location |
|
| Records and evidence |
|
| Access control |
|
| Incident testing |
|
| Policy and training |
|
Six of the questions you will be asked
Questions ask what you actually do, not whether you have a policy. Each answer maps to one control.
-
EDU-01 Critical
At admission, do you take verifiable consent from a parent or guardian before recording a child's details, beyond what any exemption for educational institutions covers?
Why it is asked: A child's data needs verifiable consent from a parent. The exemption for educational institutions covers only tracking and behavioural monitoring for educational activities or safety, not admission records in general.
-
EDU-02 Critical
Have you checked that the learning apps and platforms your students use do not track them, profile their behaviour or show them targeted advertising?
Why it is asked: Tracking, behavioural monitoring and targeted advertising directed at children are prohibited. An institution's own monitoring for educational activities or safety is exempt; targeted advertising never is.
-
EDU-38 Medium
Must an app or website be approved before teachers sign students up to it, with its data use checked first?
Why it is asked: A free app chosen by one teacher can collect a whole class's data with no contract and no check.
-
EDU-47 High
Is biometric data used only for attendance or access, stored as protected templates rather than images, with an alternative available, and deleted when people leave?
Why it is asked: A fingerprint cannot be changed once leaked. Consent to biometrics must be free, which needs an alternative; for staff, where employment is the basis, an alternative remains good practice.
-
EDU-03 High
Do you avoid publishing marks, ranks or attendance with students' names beyond the people who need to see them?
Why it is asked: Publishing marks with names discloses data beyond its purpose. Toppers' results in advertising need consent.
-
EDU-49 High
Before a proctored exam, are students told what is recorded and who reviews it, and are recordings deleted once results and appeals are final?
Why it is asked: Proctoring captures video of students' homes. A notice and a short retention period keep it proportionate.
All 46 questions written for schools and colleges
- EDU-08 For your school ERP, learning platform and EdTech tools, have you agreed in writing who decides how student data is used, and whether the provider may use it for anything of its own?
- EDU-09 Have you identified every group whose data you hold: students, parents and guardians, applicants, alumni, teachers and visiting faculty, drivers and attendants, and visitors?
- EDU-10 Does your admission form leave out details you do not need, such as parents' income, occupation, religion or caste, unless a fee concession, reservation or legal return requires them?
- EDU-11 Do you know where old student data sits: paper admission registers, retired ERP systems, old exam records and personal drives used by teachers?
- EDU-13 At admission, are parents (and adult students) told what data you collect and why, including the ERP, learning apps, transport tracking and photographs you will use?
- EDU-15 Are photographs and videos of students used on your website, social media, prospectus or hoardings only with a separate consent (from a parent where the student is a child), which can be withdrawn?
- EDU-16 Is teachers' and staff data used only for employment, with profiles, photographs or results used in advertising only with each person's consent?
- EDU-17 Are prospective students and parents contacted only when they enquired themselves or agreed, and never from bought or exchanged lead lists?
- EDU-18 Do you know who may make requests about a student: the parent or guardian for a child, the student once 18, and what you do when separated parents disagree?
- EDU-19 Can students and parents have personal details corrected, with changes to marks or certificates made through an approved process that keeps the original visible?
- EDU-01 At admission, do you take verifiable consent from a parent or guardian before recording a child's details, beyond what any exemption for educational institutions covers?
- EDU-02 Have you checked that the learning apps and platforms your students use do not track them, profile their behaviour or show them targeted advertising?
- EDU-20 Where you rely on the exemption for educational institutions, is tracking and behavioural monitoring of children limited to educational activities and their safety?
- EDU-21 Do you avoid uses of children's data likely to harm them, such as displaying disciplinary records, counselling notes, health conditions or "weak student" labels where other students and parents can see them?
- EDU-22 Before marks, attendance or assessment data are used to decide promotion, detention, eligibility or scholarships, are they checked, with a route for the student to challenge errors?
- EDU-23 Is data you upload to boards, universities, scholarship portals and national academic systems checked first, with corrections passed on?
- EDU-07 Do you have a rule for how long records of former students are kept, and delete them when that period ends?
- EDU-24 Is the data of applicants who did not join deleted once the admissions cycle and any appeal period end?
- EDU-25 Are answer scripts, entrance test papers and evaluation records destroyed when the period your board or university sets ends?
- EDU-26 Are lab computers, tablets, teachers' laptops and attendance devices wiped before disposal, return or repair?
- EDU-06 Do teachers avoid keeping student data on personal phones and in personal WhatsApp groups?
- EDU-27 Are student records in the ERP, its backups and exported spreadsheets encrypted, with Aadhaar and other identity numbers masked?
- EDU-28 Are students' health, counselling, disability and special needs records kept separately, open only to the staff who support those students?
- EDU-36 When results, fee details or messages about a child are sent to the wrong parent or posted to the wrong group, is it logged as an incident and notified to the Board and the families affected?
- EDU-05 Are transport operators, fee-collection services and other vendors who receive student data bound by written data terms?
- EDU-37 Do your ERP, LMS and EdTech contracts require immediate breach notice, forbid the provider using student data for its own purposes, and require return and deletion when you leave?
- EDU-38 Must an app or website be approved before teachers sign students up to it, with its data use checked first?
- EDU-03 Do you avoid publishing marks, ranks or attendance with students' names beyond the people who need to see them?
- EDU-39 Is student or parent data shared with partners for their own use (coaching tie-ups, banks, insurers, photographers, sponsors) only with consent and stated in your notice?
- EDU-40 Do you log each release of student records: transfer certificates, records sent to other schools or universities, and data given to scholarship bodies?
- EDU-41 Are requests for student data from police, child welfare bodies and courts checked by a named person, limited to what is required, and logged?
- EDU-42 Do you communicate with parents through a channel that does not show every parent's number to the whole class, and avoid discussing individual children in group messages?
- EDU-43 Do you know where your ERP, learning platform, email and cloud storage keep student data, including backups?
- EDU-44 Where student data goes abroad (foreign university partners, exchange programmes, overseas platforms), have the transfers been checked against any government restriction?
- EDU-45 Do you keep parental consents, publicity consents and release records so you can show, for any student, what was agreed and what was shared?
- EDU-30 In your ERP, can class teachers see only their classes, and are fee, health and disciplinary records limited to the staff who handle them?
- EDU-31 Are accounts of teachers, visiting faculty and interns removed when they leave, and student accounts closed or converted after they graduate?
- EDU-32 Is two-step sign-in required for ERP administrators, the principal, the accounts team and institutional email?
- EDU-33 Does your parent or student portal show each family only its own children, with identity checked before a login or password is reset?
- EDU-34 On shared lab computers and campus Wi-Fi, are students kept out of staff systems, with staff logins never saved on shared devices?
- EDU-35 Do you review who has access to student records at the start of each term, and remove access that is no longer needed?
- EDU-46 Is there a written policy for teachers covering photographing students, parent groups, personal phones and signing students up to apps?
- EDU-04 Is CCTV on campus signposted, with access to footage limited and a set period after which it is deleted?
- EDU-49 Before a proctored exam, are students told what is recorded and who reviews it, and are recordings deleted once results and appeals are final?
- EDU-47 Is biometric data used only for attendance or access, stored as protected templates rather than images, with an alternative available, and deleted when people leave?
- EDU-48 Is live bus location shown only to parents of children on that route, with location history and bus camera footage kept for a set short period?
Evidence that may be asked for
A “yes” is self-declared until something shows it. These are the documents and records that usually do. Your own result lists what each control needs.
- Admission form with the notice and parental consent section
- Method used to verify that the consenting adult is the parent
- List of every app and platform used with students, with the check of tracking and advertising settings
- ERP, LMS and EdTech contracts, with clauses on breach notice and no reuse of student data
- Biometric attendance settings showing templates, not images, and the alternative offered
- Policy on photographs, personal phones and parent groups, with staff acknowledgement
- CCTV signage, named viewers and the overwrite period
- Retention schedule for student, applicant, examination and faculty records
What makes evidence good enough · How the Evidence Room keeps it
First actions, in the order they usually make sense
List every app used with students and switch off tracking and advertising
Stop publishing marks and ranks with names outside the class and parents
Add verifiable parental consent to admission
Require approval before any new EdTech tool is used with students
Move class communication to a school-controlled channel
Sign data terms with ERP, LMS, biometric, transport and fee vendors
Brief teachers each year on children’s data
Your own result orders these by your answers and the law’s dates. How to plan remediation.
The reports a school or college usually needs
In education the result goes to the management committee or trust, and it helps answer parents who ask what happens to their children’s data.
| Report | Who reads it | What it shows |
|---|---|---|
| Executive and Board Summary | The management committee, trust or governing body | Where the institution stands on children’s data in particular, and what must change before 13 May 2027. |
| Remediation Report | The principal, administrator and IT in-charge | Each gap as a task, from the admission form to the EdTech approval rule. |
| DPDP Vendor Readiness Pack | EdTech and ERP providers, read the other way round | Use it as the list of questions to put to every provider before renewing its contract. |
Start the education readiness check
The 46 questions above, plus the common ones, answered in your browser. You see your gaps, their severity and your first actions straight away. It is free and needs no account.
The law behind the education controls
Every section of the Act and rule of the Rules that the education controls rely on. Read them in plain language in the DPDP Act and the DPDP Rules guides, or in the official text linked from those pages.
Digital Personal Data Protection Act, 2023
| Section | About | Parts cited |
|---|---|---|
| s. 2 | Definitions | s. 2(i) s. 2(j) s. 2(k) |
| s. 4 | Grounds for processing | s. 4(1) |
| s. 5 | Notice | s. 5(1) s. 5(1)(i) |
| s. 6 | Consent | s. 6(1) s. 6(4) s. 6(10) |
| s. 7 | Certain legitimate uses | s. 7(d) s. 7(e) s. 7(i) |
| s. 8 | General duties of the Data Fiduciary | s. 8(1) s. 8(2) s. 8(3)(a) s. 8(3)(b) s. 8(4) s. 8(5) s. 8(6) s. 8(7)(a) s. 8(7)(b) |
| s. 9 | Children's data | s. 9(1) s. 9(2) s. 9(3) s. 9(4) |
| s. 11 | Right to information | s. 11(1) s. 11(1)(b) |
| s. 12 | Right to correction and erasure | s. 12(1) s. 12(2) |
| s. 16 | Transfer outside India | s. 16(1) s. 16(2) |
| s. 17 | Exemptions | s. 17(1)(c) |
Digital Personal Data Protection Rules, 2025
| Rule | About | Parts cited |
|---|---|---|
| r. 3 | Notice | r. 3 |
| r. 6 | Reasonable security safeguards | r. 6(1)(a) r. 6(1)(b) r. 6(1)(c) r. 6(1)(f) r. 6(1)(g) |
| r. 7 | Breach intimation | r. 7(1) r. 7(2) r. 7(2)(b) |
| r. 10 | Verifiable consent for children | r. 10(1) |
| r. 12 | Exemptions for children's data | r. 12(1) r. 12(2) |
| r. 14 | Rights of Data Principals | r. 14(1) |
| r. 15 | Transfer outside India | r. 15 |