Security
How school data is kept separate and protected, described as it is built today. Where something is not confirmed, we say so.
DRAFT - needs legal review. This page is not final and must be reviewed by counsel before launch.
What is built into the platform
These controls are in the code and are being tested with schools. They have not yet been independently tested.
Each school's data is kept separate. The school is taken from your sign-in, never from what a request says.
Students and parents only see their own or linked records. Checks are made on the server, not just on screen.
Role-based access: administrators, teachers, managers, students, parents and aides each see what their role needs. Passwords are stored hashed.
Changes are recorded in an audit log.
To be confirmed before launch
Encryption in transit (HTTPS) for the site, the app and the API. This depends on how the service is hosted and is to be confirmed by the owner.
Hosting region. The hosting region has not yet been published. We will state it once it is confirmed.
Child-data practices
- Student information is treated as sensitive and is limited by role.
- Restricted fields such as health information are visible to approved staff roles only.
- Sample and demonstration data is fake. No real student data is used in the site or demos.
What we do not claim
This site does not state any security certification, penetration-test result, backup schedule or uptime commitment. If that changes, the evidence will be published here first.
To report a security concern, use the contact form and choose Question. A dedicated security address is to be supplied by the owner.
Questions about this page? Use the contact form and mark it as a question. A dedicated contact address is to be supplied by the owner. Contact us