On 5 October 2026, MeitY used its power under Section 43 of the DPDP Act to add one word to Section 9(1). The Removal of Difficulties Order inserted "of", so the clause now covers personal data "of a child or of a person with disability". It creates no new duty. It does show that children's data is on the government's desk as 13 May 2027 approaches.
In July, MediaNama reported that data from at least 41 distinct 2026 examination and institute databases was listed for sale online. One listing claimed over 15.5 lakh records from CUET-UG 2026. Students and parents MediaNama called confirmed their details were accurate.
Schools, universities and edtech platforms will meet Section 9 with data estates built over decades. Parental consent, the ban on tracking and erasure on exit all depend on one prior step. You have to know where each child's data sits. This piece maps where student, parent and staff data lives in a typical institution. It also shows how to find it in the six months that remain.
Why education carries more risk than most sectors
Section 2(f) defines a child as an individual who has not completed 18 years. In a school, that covers nearly every student. The UDISE+ 2025-26 report counts 24.72 crore students and 1.03 crore teachers across 14.67 lakh schools.
Section 2(j) adds a second layer. Where the Data Principal is a child, the term includes her parents or lawful guardian. So a parent holds rights over the child's records. The same parent is also a Data Principal for her own phone number, income certificate and fee payments.
Section 9 then sets three rules. Section 9(1) requires verifiable parental consent before processing any personal data of a child. Section 9(2) bars processing likely to harm a child's well-being. Section 9(3) bars tracking, behavioural monitoring and targeted advertising directed at children.
The penalties match that weight. The Schedule to the Act allows up to ₹200 crore for breaching the Section 9 duties. Failing to take reasonable security safeguards can attract up to ₹250 crore.
Large edtech platforms carry one more exposure. Section 10 lets the Central Government notify a Significant Data Fiduciary after weighing factors such as the volume and sensitivity of data. A platform holding crores of children's records fits that description. Designation would add a Data Protection Officer, an independent data auditor and periodic impact assessments.
The core duties start on 13 May 2027. In January 2026, MeitY asked industry for views on cutting the 18-month window to 12 months, Storyboard18 reported. As of early November 2026, legal commentary still treats May 2027 as the date for core obligations. Our plan for working back from 13 May 2027 sets out the sequence.
The systems everyone lists first
Every inventory starts with the systems the IT team already runs. That list is the easy half.
- ERP or student information system. Admission number, date of birth, address, parents' names and numbers, siblings and photographs.
- Admissions portal. Applications from children who never joined, often kept for years after the cycle closed.
- Fee and payment systems. Parent bank details, UPI references, concession and fee-waiver files.
- Learning management system. Assignments, submissions, discussion posts and activity logs.
- Exam and results databases. Marks, answer scripts, hall tickets and re-evaluation requests.
Each of these has a known owner and a schema. Discovery here is about completeness. Does the ERP still hold students who left ten years ago? Do test and staging environments hold real children's records? Are Excel exports sitting in a shared drive? Data discovery and classification should scan for those copies as well as the production tables.
Where student data actually hides
The harder half is the data no system owner would put in an asset register.
Scanned admission files. Section 3(a)(ii) applies the Act to data collected on paper and digitised later. A scanned admission form, birth certificate or transfer certificate on a file server is in scope. So is the Aadhaar card or income certificate attached to a scholarship application.
Class WhatsApp groups. Many class teachers run a parent group from a personal phone. It holds names, numbers, photos and messages about individual children. The teacher runs it for school work, so the school should treat it as its own processing.
CCTV. In July 2025, CBSE added clause 4.7.10 to its Affiliation Bye-Laws, SCC Online reported. Affiliated schools must record audio and video in classrooms, corridors, labs and common areas, excluding toilets. Footage must be kept for at least 15 days. That recorder in the server room holds personal data of every child and teacher on camera.
Biometric attendance and bus GPS. Fingerprint or face templates sit on the attendance device and often in the vendor's cloud. The transport operator's app holds the live location of each child on a route.
Counselling and medical-room notes. These often live in a register or on one person's laptop. They are among the most sensitive records a school holds. Limit access to the counsellor, the nurse and whoever must act on a concern.
Event photos and videos. Annual-day albums on cloud drives, the school's Instagram account and the hired photographer's hard disk all count.
Alumni lists. Spreadsheets kept by a teacher or the alumni cell rarely carry an expiry date or a stated purpose.
You find these stores by asking people as well as by scanning. Interview admissions, transport, the front office and class teachers about what they keep. Then scan file shares and cloud drives for Aadhaar numbers, dates of birth and admission-number formats.
Data that sits with vendors and government platforms
Section 8(1) makes the Data Fiduciary responsible for processing its Data Processors carry out on its behalf. Section 8(7)(b) requires it to make the processor erase data once the purpose ends. You can't instruct a vendor to delete data you don't know it holds.
A typical processor list includes:
- edtech and LMS vendors
- online proctoring tools that capture webcam video and screen activity
- transport operators and their tracking apps
- payment gateways and fee-collection partners
- cloud hosting and backup providers
- the agency that built and maintains the parent app
Government platforms add another flow. Schools key student records into UDISE+. The APAAR portal says each APAAR ID is generated in UDISE+ against the student's Permanent Education Number. Its mandatory fields include Aadhaar number, date of birth, mobile number and both parents' names. Parental consent is taken for minors. On 5 November 2026 the portal showed 33.74 crore APAAR IDs registered.
Map what you upload, from which system, and who holds the login. Section 11(1)(b) gives the Data Principal a right to know every other Data Fiduciary and Data Processor that received her data. A data map that records these flows lets you answer without a week of emails.
Classification that changes what you must do
Finding the data is half the job. Each record also needs labels that tell you which duty applies.
| Label | What it decides | Example |
|---|---|---|
| Child or adult | Section 9 applies only below 18 | Date of birth in the ERP |
| Student, parent or staff | Parents are Data Principals twice. Staff data often rests on Section 7(i) | Fee payer's bank details |
| Exempt tracking or not | The Fourth Schedule covers only tracking and monitoring for education or safety | Bus GPS vs an ad pixel |
| Retention required by law | Section 8(7) allows retention needed to comply with law | Admission and withdrawal register |
The age label needs care. Students turn 18 during Class 12 or the first year of college. A static "minor" flag set at admission will be wrong for many records within a year. Compute age from date of birth each time a process runs. Universities face the reverse problem. Most of their students are adults, but any first-year student under 18 is still a child under Section 2(f).
The retention label needs a named rule behind it. CBSE Examination Bye-law 69.2 covers date-of-birth corrections. For any correction, the school must forward the admission application, the admission and withdrawal register entry and the previous school's leaving certificate. In Jigya Yadav v. CBSE, the Supreme Court held that the board's bye-laws have the force of law. The Delhi High Court applied that ruling in June 2025 to a 1999 Class X certificate and a correction sought in 2021.
The CBSE is a record keeper of considerable importance
— Justice Harish Vaidyanathan Shankar, Delhi High Court, CBSE v. Prema Evelyn D'Cruz, 4 June 2025
In our reading, records like these sit within the Section 8(7) exception. The annual-day photo album does not. Map each record type to the specific board, university or regulator rule that requires it. Keep only what that rule names, for the period it sets.
Finding the tracking that Section 9(3) prohibits
Part A of the Fourth Schedule to the DPDP Rules gives educational institutions a narrow exemption from Sections 9(1) and 9(3). It applies where processing is restricted to tracking and behavioural monitoring for the institution's educational activities. It also applies to monitoring for the safety of enrolled children. Separately, a transport provider engaged by the school is exempt for tracking children's location on the way to and from school.
The exemption also stops at the institution's own purposes. Attendance analytics that help a teacher spot absences may qualify. The same data in a vendor's product-improvement pipeline serves a different purpose.
So discovery has to cover data in motion as well as data at rest. Check these places:
- admissions pages and parent portals, for advertising pixels and third-party analytics tags
- parent and student apps, for advertising and attribution SDKs
- LMS and proctoring contracts, for clauses that let the vendor reuse engagement data
- marketing lists built from enquiry forms filled in by under-18 applicants
Edtech companies face a prior question. The Schedule defines an educational institution as an institution of learning that imparts education, including vocational education. Whether a consumer learning app counts is unsettled. Get legal advice before you build a product on that exemption.
How discovery feeds every later duty
Notice and consent. Rule 10 requires due diligence that the person consenting is an identifiable adult. The school can rely on identity and age details it already holds. It can also accept details the parent provides, including tokens verified through a Digital Locker service provider. Discovery tells you which records already carry a verified parent. That is where consent management starts.
Rights requests. A parent may ask for a summary of the child's data, a correction or erasure. Under Rule 14, grievances need a response within a reasonable period not exceeding 90 days. That clock is hard to meet if the answer depends on finding the teacher who ran the 2023 class group. A rights request portal works only when it sits on a complete inventory.
Retention and erasure. When a student leaves, Section 8(7) requires erasure once the purpose is no longer served, unless a law requires retention. Discovery tells you where every copy sits, including the vendor's.
Breach reporting. Rule 7 requires intimation without delay to each affected Data Principal and to the Board. A detailed report must reach the Board within 72 hours of becoming aware of the breach. For a child, the person you notify is the parent. Every child record therefore needs a current parent contact, in your systems and your vendors'. Rule 6 requires logs to be kept for one year, so you can establish what was touched.
Discovery has to run every admission cycle
A one-time audit goes stale fast in education. Each admission cycle adds a batch of forms, scans and enquiry leads. Each new app a teacher adopts adds a store. Each vendor renewal can change where data goes.
Run discovery as a standing control with these triggers:
- a scheduled scan of file shares, cloud drives and databases after each admission cycle and exam season
- a check before any new vendor, app or integration goes live
- an exit routine when a student leaves or a staff member moves on
Give every store a named owner. The admissions head owns admission scans. The transport manager owns GPS data. The IT head owns the scanning tools and the inventory itself. The Data Protection Officer, or the contact named under Rule 9, reviews the results each term.
Start with admissions and transport. Both touch every child and every parent, and both run on the most informal tools. If you want an outside view of where the gaps sit, a DPDP gap assessment can scope the work.
If a parent asked for every record you hold on their child
Imagine the request arrives on 14 May 2027. How many systems, drives and phones would you need to search? Use these questions to find out now.
| Question | Where to look |
|---|---|
| Which systems hold this child's admission number? | ERP, LMS, exam, fee and library systems |
| Which scans carry the birth certificate or Aadhaar? | Admissions drives, scholarship folders, file servers |
| Which phones hold class groups with this child? | Class teachers and coordinators |
| Which footage shows the child, and for how long? | CCTV recorders and backups |
| Which vendors received the child's data? | Contracts, API logs, file transfers |
| What did we upload to UDISE+ and APAAR? | The UDISE+ login holder |
| Where are counselling or medical notes? | Counsellor, nurse and their devices |
| Which photos of the child are public? | Social media accounts, event drives |
| Which records must we keep, and under which rule? | Your retention register |
Any row answered with "we'd have to ask around" is your first discovery task.
The record nobody listed
Section 9 follows the child wherever her data goes. It reaches the scanned birth certificate, the teacher's phone and the vendor's analytics pipeline. A parent's complaint won't care which systems made it onto your asset register.
Every answer you will owe that parent starts with knowing where the data is. Six months is enough time to find it, if the search starts this term.
Sources
- Legislative Department, Ministry of Law and Justice (India Code), "The Digital Personal Data Protection Act, 2023 (Act No. 22 of 2023)", as on 19 November 2025. Link
- DPDP Wiki (Gazette text of G.S.R. 846(E)), "Fourth Schedule: Exemptions from section 9(1) and 9(3) for processing children's data", updated 9 September 2026. Link
- DPDP Wiki (Gazette text of G.S.R. 846(E)), "Rule 10: Verifiable consent for processing of personal data of child", updated 9 September 2026. Link
- DPDP Wiki, "The DPDP Rules, 2025 explained: what each rule does", 9 September 2026. Link
- Legal 500 (S.S. Rana & Co.), "DPDP (Removal Of Difficulties) Order, 2026: What Has Been Changed For Children's Data And SDF Audits", 2 November 2026. Link
- India Briefing, "DPDP (Removal of Difficulties) Order 2026 Clarifies Consent and Data Audit Requirements in India", 7 October 2026. Link
- Storyboard18, "MeitY seeks industry views on fast-tracking DPDP Act rollout, proposes 12-month compliance timeline", January 2026. Link
- MediaNama, "Leaked data of Indian students from government exams and private coaching institutes is sold online", 8 July 2026. Link
- Press Information Bureau, "Beyond the Numbers: Decoding India's School Education Progress, UDISE+ 2025-26 Report", 17 August 2026. Link
- Ministry of Education, "APAAR: Automated Permanent Academic Account Registry", accessed 5 November 2026. Link
- SCC Online, "CBSE introduces Real-Time CCTV Guidelines for safer school environments", 22 July 2025. Link
- Delhi High Court, "Central Board of Secondary Education v. Prema Evelyn D'Cruz, LPA 171/2023", 4 June 2025. Link