Schools hold some of the most sensitive information in any community: children’s names and photographs, marks and attendance, health notes, family contacts. Most schools already guard it carefully. India’s Digital Personal Data Protection Act, 2023, and the Rules that bring it into force, turn that care into specific legal duties. There is still time to prepare, and much of what’s required is good practice your school may already follow.
This article is general information, not legal advice. For decisions about your school, speak to a lawyer.
The timeline: what applies, and when
- August 2023: the DPDP Act becomes law.
- 13 November 2025: the government notifies the DPDP Rules, 2025.
- 13 November 2026: registration of Consent Managers opens.
- 13 May 2027: the main obligations take effect — notices, security safeguards, breach reporting, retention limits, children’s data and individuals’ rights.
That makes the 2026–27 academic year your preparation window.
Why every school is in scope
Under the Act, an organisation that decides why and how personal data is used is a Data Fiduciary — and every student under 18 is a child in law. So nearly every school, whether CBSE, ICSE or State Board, private or aided, processes children’s personal data every day, on paper and in software.
The core rule for children’s data
Section 9 of the Act sets two headline duties for anyone processing children’s data:
- obtain verifiable consent from a parent or lawful guardian before processing a child’s personal data; and
- do not carry out tracking, behavioural monitoring or targeted advertising directed at children.
Read on their own, those duties would make everyday school life — marking attendance, tracking progress — legally awkward. That’s why the Rules include a specific carve-out for schools.
The school exemption, and its limits
The Fourth Schedule of the Rules exempts educational institutions from both duties, but only to the extent that processing is tracking and behavioural monitoring for the institution’s educational activities, or in the interests of the safety of enrolled children. A separate entry covers tracking a child’s location during travel to and from school, for their safety.
Two things stay true even inside the exemption. The Act still prohibits processing that is likely to harm a child’s well-being. And anything else a school does with children’s data still needs a parent’s verifiable consent. In practice, the line tends to fall like this:
| Likely within the school exemption | Likely needs a parent’s consent |
|---|---|
| Attendance records and absence alerts | Student photos or videos on social media, the website or brochures |
| Assessments, marks and progress reports | Sharing student data with vendors for anything beyond educational purposes |
| Locating the school bus during travel to and from school | Using student data for marketing or promotions while students are minors |
Exactly where a specific activity falls is a legal question, so treat this table as a starting point for a conversation with counsel, not the final word.
What every school must still do
The exemption is narrow. These duties apply in full from May 2027:
- Tell parents clearly what data you collect, why, and how they can raise questions or complaints.
- Protect it with reasonable security safeguards: access limited by role, encryption, and logs of who accessed what.
- Report breaches to the Data Protection Board and to affected families without delay, with a detailed report to the Board within 72 hours.
- Keep data only as long as it is needed, then erase it.
- Honour parents’ rights to access, correct and erase their child’s data, through a named contact.
- Hold your vendors to the same standard — more on that below.
The penalties are designed to be taken seriously: the Act allows fines of up to ₹200 crore for breaching the duties on children’s data, and up to ₹250 crore for failing to protect personal data with reasonable safeguards.
Your software vendors are part of your compliance
When an ERP, LMS or app stores student data for you, that vendor is your Data Processor: it may only use the data on your instructions, and your school remains responsible for it. Before May 2027, ask each vendor:
- Where is our data stored, and who on your side can access it?
- Is access limited by role, and is data encrypted in transit?
- What happens, and how quickly, if there is a breach?
- Will you delete our data when we leave — and confirm it in writing?
- Is student data ever used for advertising, or sold?
A starting checklist for 2026–27
- Map what student data you collect, where it lives and who can see it.
- Review photo and media consent forms before the next admissions cycle.
- Rewrite your parent privacy notice in plain language.
- List every vendor that touches student data, and review the contracts.
- Agree a breach response plan: who decides, who informs parents, who informs the Board.
- Name one person responsible for data protection, and train staff on the basics.
Built to be your data processor
TedQu processes student data on the school’s instructions, with role-based access isolated to each school and encrypted connections. Student data is never used for advertising and never sold. Pulse Card scanning happens on the teacher’s phone: the camera reads each card’s printed code, and no photos are stored.
Read the TedQu privacy policy →May 2027 can feel far away in the middle of a school year. The schools that start mapping their data and talking to their vendors now will find the deadline arrives as a formality, not a scramble.
