Guide
Keeping student records safe: a school's duty
What student data a school holds, who should see what, the habits that leak it, and the questions to put to any software vendor.
A school is a custodian of other people's information: children's identities, families' finances, home addresses and daily routines. Keeping that safe is mostly not a technology problem. It is five habits, each of which a school can adopt in a term, and a short list of hard questions to put to whoever supplies the software.
What does a school hold, and why does it matter?
Take one student file and list what accumulates around it in a year: admission form with the guardian's CNIC, address and workplace; fee ledger showing what the family pays and when they struggled; attendance showing when the child is home alone; marks; a photograph; sometimes medical notes. None of it is secret state material, and all of it together is exactly what a bad actor, an angry ex-employee or a custody dispute would want. The school that treats this as routine paperwork is trusting luck.
The five habits that do most of the work
- One person, one login. A shared office password makes every mistake anonymous and every audit meaningless. This is the first thing to fix, and it costs nothing.
- Access follows the role. Teachers see their classes, accounts sees fees, parents see their own children. On paper this is impossible; in software it is a settings page. In EDUTIG you create the roles and decide which areas each one opens, as described on the security page.
- Sensitive lists stay out of open chats. A fee-defaulter list in a staff WhatsApp group is a leak that has already happened. The substance belongs behind logins; the chat gets the nudge. Our portal versus WhatsApp guide covers the working split.
- Leavers lose access the same day, staff and students both. An account that outlives its owner is the classic quiet breach.
- Backups someone has actually restored. A backup nobody has ever restored from is a hope, not a backup. Ask for the arrangement in writing and ask when restore was last tested.
What should you demand from the software?
| Question | A good answer looks like |
|---|---|
| Does everyone get their own login? | Yes, per person, and the vendor pushes back on sharing. |
| Can roles limit what each person sees? | Shown on screen: a teacher login and an accounts login, side by side. |
| Is the connection encrypted? | Served over HTTPS, stated plainly. |
| What are the backup arrangements? | Specifics for your deployment, in writing, not generalities. |
| Can we export everything if we leave? | Yes, and they tell you how before you sign. |
One design choice worth asking about, because it quietly removes a whole category of risk: whether the system needs to hold children's personal contact details at all. EDUTIG stores no student email address or phone number; students receive messages in their portal inbox, and the school's messaging reaches guardians, not children. However you answer these questions, answer them before the records move: it is the one part of choosing a system that cannot be fixed afterwards by switching.