All resources Compliance

The DPDP Act and your school: what changes for student data

India's Digital Personal Data Protection Act applies to the records every school keeps — and most of them belong to children. A plain-language guide to what it means and where to start.

The Takshova team · 12 October 2026 · 4 min read

Schools hold more personal data than almost any other organisation of their size: names, dates of birth, addresses, photographs, health conditions, marks, fee records, parents’ phone numbers and jobs — for every child, every year. India’s Digital Personal Data Protection Act, 2023 (the DPDP Act) sets out how that data must be handled.

This article is a plain-language introduction, not legal advice. For decisions about your own school, read the Act and its Rules and speak to a qualified adviser.

Who’s who under the Act

  • The school is a Data Fiduciary. It decides why and how personal data is processed, so it carries the responsibility.
  • Students, parents and staff are Data Principals — the people the data is about. For a child, the parent or lawful guardian acts on the child’s behalf.
  • Your software and service providers are Data Processors. They process data on the school’s instructions, but the school remains accountable.

Children’s data needs extra care

The Act treats anyone under 18 as a child. For children’s data, it requires:

  • Verifiable consent of a parent or lawful guardian before processing, where consent is the basis for processing.
  • No processing that is likely to harm a child’s well-being.
  • No tracking or behavioural monitoring of children, and no targeted advertising directed at them.

The Rules made under the Act describe how verifiable consent works in practice and set out limited exemptions, so check them for your school’s situation.

What the Act asks of schools

Tell people clearly

Give a clear notice of what personal data you collect and why, in plain language. The Act allows the notice to be made available in English or any of the languages in the Eighth Schedule of the Constitution — useful when many families are more comfortable in Telugu, Hindi or another language.

Collect what you need, for a clear purpose

Running a school needs certain data. Optional uses — a child’s photo on the website, a story in the newsletter, marketing messages — are different, and should be asked for separately and recorded.

Keep it safe

The Act expects reasonable security safeguards to prevent breaches. In practice: staff see only what their role needs, sign-ins are protected, changes are logged, and backups exist.

Report breaches

If personal data is breached, the school must inform the Data Protection Board of India and each affected person, in the manner the Rules set out. That’s much easier if you already keep a breach register and a response plan.

Don’t keep data forever

Personal data should be erased once its purpose is served and the law no longer requires it to be kept. Schools have genuine reasons to keep some records for a long time — admission registers and transfer certificates, for example — so write down a retention rule for each kind of record.

Respect people’s rights

Parents, students and staff can ask what data you hold about them, ask for corrections, and raise grievances. You’ll need a named contact and a way to track each request to completion.

The penalties are serious

The Act provides for heavy financial penalties: up to ₹250 crore for failing to take reasonable security safeguards, and up to ₹200 crore each for failing to notify a breach or to meet the obligations for children’s data. The amount in any case depends on the circumstances, but the message is clear.

Where to start: a checklist for this term

  1. Map your data. List every place personal data lives: the office software, the fee app, spreadsheets, WhatsApp groups, paper files, the transport vendor.
  2. Name an owner for data protection and grievances, and publish how to reach them.
  3. Review your notices and forms, starting with the admission form.
  4. Separate “needed to run the school” from “optional”, and record consent for the optional uses.
  5. Tighten access. Does every teacher really need to see every student’s health record and fee balance?
  6. Check your vendors. Ask each one where data is stored, who can access it, and how they would tell you about a breach.
  7. Write retention rules, and remove data you no longer need.
  8. Prepare for a breach before one happens: who decides, who informs whom, and how.

How Campus Flow helps

Campus Flow was built with these obligations in mind. Families manage their own consents — for example, for photographs — from the parent app. Each role sees only what it needs, every change is recorded in an audit log, and the school can track data requests, keep a breach register and set retention rules for each kind of record.

Software doesn’t make a school compliant on its own. But it can make the right way the easy way. If you’d like to see how, talk to us.