Security and data protection

Children's names, family contacts and payment records stay with each centre, seen only by the people who need them.

The audit log: every change, with who, when and where. Sample data.

Each person sees their part

Owners see every branch, staff their own branches, teachers their classes and parents only their own children.

Who sees what: each role and the branches it covers. Sample data.

Voids need a reason, unlocking attendance needs permission, and the log cannot be edited afterwards.

A day in the audit log, voids with their reasons. Sample data.

Kept apart from every other centre
Your records are separated from every other centre's by the database itself, not just by the app.
Row-level security in PostgreSQL
Access by role and branch
Staff see and change only what their role allows, in the branches they work in.
Role permissions, scoped per branch
Every change on record
Who changed what and when is kept, including voids with their reasons, sign-ins and password changes.
An audit trail that cannot be edited
Passwords nobody can read
Passwords are stored one-way, and repeated failed sign-ins are blocked for a while.
bcrypt hashing, limited sign-in attempts
Encrypted connections
The console, the apps and this website are served over HTTPS only.
HTTPS with modern security headers
Backups you can restore
The database is backed up continuously and can be restored to a chosen moment.
Point-in-time recovery, rehearsed restores

We are happy to go through how TuitionSync handles your data in detail.