Serious about your data.
Staffing plans contain some of the most sensitive data a school holds. Here is how Curriculum.School treats it.
Access control
Curriculum.School is multi-tenant by organisation. Every user belongs to an organisation, and access within it can be broad or restricted to specific schools, so a school business manager sees their school, and a trust leader sees the roll-up.
Encryption
Staff and financial fields are encrypted at rest in the backend model layer. Data in transit is protected with TLS.
Authentication
Accounts include password management with optional two-factor authentication (2FA). An SSO login path is supported for organisations that prefer to manage access centrally.
Tenancy & separation
Each organisation's data is scoped to that organisation. Users cannot see other organisations' schools, staff or scenarios.
Exports & portability
Your data is yours. Deployment matrices and reporting export to CSV and XLSX at any time, so governance and finance work in the tools they already use.
Questions
Security questionnaires and data-protection questions are welcome:book a demo or raise them with the team and we'll answer them directly.