Built for environments where data, access and accountability matter.
Student and financial records are locked down by role — not by luck. Before you sign anything, we walk your IT lead through exactly how it works.
The foundations.
Role-based access
A teacher sees their classes, a parent their child, finance the fees. Access follows the role.
Encrypted at rest
Student and financial data is encrypted where it is stored.
Regular backups
Backed up regularly — not a single laptop or shared drive.
Data residency, your way
Hosting configured to match your institution's or board's data-residency requirements.
What we'll walk your IT team through.
Final security architecture is confirmed with your IT team before go-live. These are the areas we cover together.
- Permissions model
- Authentication
- Activity visibility
- Data ownership
- Backups & recovery
- Data export
- Secure integrations
- Privacy practices
Regulatory and compliance requirements differ by country and board. We review yours with your IT and legal teams during discovery rather than displaying badges.
Questions your IT team will ask
How is our data handled?
Student and financial data is encrypted at rest and backed up regularly, access is role-based, and hosting is configured to match the data-residency requirements of your institution or board. Final security architecture is confirmed with your IT team before go-live.
Can different users get different permissions?
Yes. Access is role-based: a teacher sees their classes, a parent sees their child, finance sees fees, and leadership sees across campuses.
Where is our data hosted?
Hosting is configured to match the data-residency requirements of your institution or board, and confirmed with your IT team before go-live.
Can we see the security setup before signing?
Yes. We walk your IT lead through access control, encryption, backups and hosting before you commit.