Plain answers about your school's data.
What your board, privacy officer and IT lead usually ask, answered in one place. If your IT team has a security questionnaire, send it to us and we'll complete it.
Where the data is
In Sydney, Australia, on Supabase running in Amazon Web Services' Sydney region (ap-southeast-2). Our database platform doesn't yet offer a New Zealand region. We'll tell schools before any change of location.
Backups and recovery
An encrypted backup is taken every day and kept off the main platform. Every week an automated test restores a backup to prove it works. A warm standby copy of the database is kept in a separate project and refreshed through the day.
Our recovery targets are a recovery point of 4 hours and a recovery time of 8 hours. They are targets, not guarantees.
Who can see what
Access is set by role and limited to your school. Teachers see their checks and reports; the coordinator sees the registers; trustees have a read-only view. Contractors only see their own jobs, and their access ends on the engagement's end date.
Database rules enforce this on every request.
Audit trail
Every change is written to a chained audit log: who, what, when, before and after. The chain makes later tampering detectable. Your school can export the log at any time.
Sign-in
Each person has their own account. Passwords are stored only in hashed form by our sign-in provider. When an admin resets someone's access, that person must choose a new password of their own at the next sign-in. Multi-factor authentication is supported. Single sign-on with Microsoft 365 is in development.
Student information
The platform records places, procedures and staff actions. There is no student register and no connection to your student management system. Where an incident involves a student, your school decides what is recorded and who can see it. EOTC participant details are removed automatically after each trip.
Privacy Act 2020
Your school remains the agency that holds its information. School Guard, and the providers we use to run the service, hold it on your school's behalf and use it only to provide the service. We'll give your school a list of every provider we use and the safeguards we are bound by.
If we become aware of a privacy breach affecting your school's information, we'll tell your school promptly so it can meet its own obligations.
Your records
Your school owns its records. Export everything, including the audit trail, at any time. Retention periods are set by your school. Apart from EOTC participant details, which are removed after each trip, records are not deleted automatically.
Providers we use
Supabase (database, sign-in and file storage; Sydney), Vercel (application hosting), and an email service for notifications. This website uses Cloudflare for hosting and Web3Forms to receive enquiry forms.
School Guard helps your school carry out its health and safety duties and keep evidence that it did. It doesn't make a school compliant and it isn't legal advice. Your board remains responsible for its own obligations.
Have a security questionnaire?
Send it to hello@schoolguard.co.nz and we'll return it completed.