Each school, separated
Every record belongs to one school, and the school comes from the signed-in account—never from what a browser sends. Row-level security in the database adds a second wall on 73 tables.
SECURITY & PRIVACY
Schools trust us with children’s records, family contacts and fee details. Here is how Nirva keeps each school’s information inside that school—and inside the school, with the people responsible for it.
We sign in as every role in one school and try to read and change another school’s students, invoices, enquiries, timetables and messages through hundreds of API routes. Every read came back empty and every write was refused, with the other school’s data unchanged byte for byte.
HOW IT WORKS
No single check is relied on alone. Each layer below works on its own, and together.
Every record belongs to one school, and the school comes from the signed-in account—never from what a browser sends. Row-level security in the database adds a second wall on 73 tables.
A subject teacher sees the classes and subjects they teach. A parent sees only their own children. Accounts, transport and front office see only what their work needs.
Screens that just pick a student receive a name, admission number and section—not addresses or phone numbers. Sensitive identity numbers are masked.
Passwords are hashed with Argon2 and must be at least 12 characters. Sessions use short-lived tokens with refresh-token rotation, and repeated sign-in attempts are rate-limited by account and network.
Production runs on HTTPS only, with strict security headers, protection against being framed by other sites, and checked origins on session requests.
CSV uploads are size-limited and validated column by column, so malformed files are rejected with a clear message instead of reaching your records.
Nirva AI drafts syllabi, question papers and suggested marks. A teacher reviews, edits and approves every one before anything reaches students or families.
Important actions, such as fee and result changes, are written to an audit log that stays within your school.
Administrators decide which features each role can use, including chat, internal email, channels, helpdesk and question papers.
HOSTING & COMPLIANCE
The commitments we make to every school, written into your agreement with us.
Nirva runs on Cloudflare’s network with a managed PostgreSQL database. Data is encrypted in transit with HTTPS and encrypted at rest.
Your school’s data is backed up automatically every day and kept for 30 days, so a bad day never becomes lost data.
We act as your data processor under the Digital Personal Data Protection Act, 2023: we collect only what school work needs, use it only for that purpose, and support consent, correction and deletion requests.
Ask for an export of your school’s records at any time. If you leave Nirva, we hand over your data and delete it from our systems within 30 days.
Student and family data is never sold, never shared with advertisers and never used to train public AI models.
Found a security issue? Write to admin@nirva.digital. We acknowledge every report within one working day.
LET’S TALK
Tell us about your classes, curricula and the routines you want to bring together. We’ll walk you through the product with your school in mind.