Data & Security

Every record carries the school it belongs to, and database-level access rules check that school on every read and write. A user signed in to one school cannot query another school's students, fees or messages, even by manipulating requests from the browser.

Access is granted by role — school admin, class teacher, subject teacher, accountant, admission manager, librarian, transport head, driver, health officer and parent. Roles are stored separately from user profiles and checked on the server, so a user cannot raise their own permissions from the client. Parents see only their own children.

Traffic between devices and the platform uses HTTPS/TLS. Stored data and file uploads are encrypted at rest by our cloud provider. Passwords are never stored in readable form; only salted hashes are kept.

Student documents and photos live in access-controlled storage. File paths are scoped to the owning school and student, and download links are checked against the requester's role rather than being publicly guessable.

Sensitive actions — role changes, fee payments, promotions, student termination, document deletion — are recorded with the acting user and timestamp so a school can review what happened.

The managed database is backed up on an automated schedule with point-in-time recovery, so a school's data can be restored to an earlier moment after an accidental bulk change. Schools can also export their own records at any time for an independent copy.

The app is a progressive web app. Attendance taken while a device is offline is queued locally and synced when connectivity returns, so a weak network does not cause lost records.

If you believe you have found a security issue, tell us before disclosing it publicly. Reach us through the contact page with steps to reproduce. Please do not access, modify or download data belonging to other users while testing. We will acknowledge reports and keep you updated on the fix.