Your students' records, kept like records.
What separates one school from another, what is backed up, who inside your school can see what, and how you get everything out again.
One school cannot see another
Separation is enforced at the data layer, not by remembering to add a filter. A query that cannot be scoped to your institution fails rather than returning someone else's rows.
Backed up every night
The database is backed up nightly and retained, so a mistake on a Tuesday is recoverable on a Wednesday.
Encrypted in transit, on your own certificate
Every school's address carries its own TLS certificate. Traffic between a browser and the school is encrypted end to end.
People see only what they are granted
Access is granted per module and per action, by role group or to an individual. A teacher with no accounts grant cannot reach fees, in the interface or underneath it.
Private documents stay private
Uploaded documents are held in private storage and served through short-lived links, never from a public bucket.
Your data leaves when you do
Records can be exported at any time. Nothing is held hostage to a subscription.
What we do not do
A security page that only lists strengths is a brochure. These are the limits, stated plainly.
We are not a backup of your board's records
Marksheets and certificates generated here are your school's own. Where a board is the issuing authority, its records remain the authority.
There is no offline mode
Registers, marks and receipts need a connection at the moment they are entered. Pages are light, but they are not local.
We can see your data when you ask us to
Support access exists so that we can help when something breaks. It is not used otherwise, and you can ask us to stop.
Still have a question about data?
Ask it before you commit. We would rather answer it now than have you find out later.