Oversight shouldn't come at the cost of data protection
RollCall is built around a set of security principles that govern how access, data and operational records are handled.
Our Approach
Principles the platform is built around
Role-based access
Every account is assigned a role — teacher, principal, administrator, owner — and only sees the data appropriate to that role.
Secure authentication
Access to RollCall requires authenticated sign-in, with sessions handled through modern, industry-standard practices.
Controlled permissions
Sensitive actions — approving leave, closing a query, editing a record — are restricted to the roles authorized to perform them.
Audit trails
Compliance-relevant actions are logged, so schools can review who did what, and when.
Tenant isolation
Each school's data is logically isolated from every other school on the platform.
Secure API architecture
The website and future backend communicate over a defined REST API, keeping business logic and data access in one controlled layer.
A note on certifications
RollCall does not claim any compliance certifications or third-party security attestations that have not been independently verified. As the platform matures, this page will be updated to reflect any certifications actually obtained. If your school has specific security or compliance requirements, raise them directly with our team during your demo.