Safety and trust
Child safety is not a setting you remember to turn on. It is in how reports are handled, who can see what, and what the system refuses to do.
Child safety
A child, a parent or any staff member can report a concern. It lands on your centre's moderation queue with a deadline by severity, your centre's safety contact is alerted at once for anything serious, and an hourly watchdog emails again if nobody has acted.
Nothing about an incident is emailed to a family automatically. Your safety lead writes what the family sees and shares it from the incident's page, at two-step sign-in, recorded in the audit log.
A document or message thread with a child and a staff member on it also goes to the child's parents. Your compliance staff can read a family's correspondence with staff, and every read is logged first.
A tutor's working with children check is checked when a lesson is booked, when a cover is accepted and when a tutor is changed. Your centre chooses to warn or to block, and a home visit always needs a current, verified check.
Everything a child types to an AI tool, and everything it says back, passes a safety check. A parent can switch AI off for their child, the coach gives hints rather than answers, and names are replaced before anything reaches a model.
Where a centre turns friends on, children far apart in age cannot connect, and a younger child's friendship waits until a parent of each child agrees.
Privacy and security
Every record carries the centre it belongs to and the database enforces the boundary, so one centre's staff can never read another's families.
Hosted in Sydney, Australia: the database, file storage and the application.
Owners, admins and finance staff must use an authenticator, and a centre can require it of every staff member. The database itself refuses money and family records to a session that has not passed it.
A tutor reads only the students they teach. Home addresses and gate codes open to the delivering tutor in a window around the lesson, and are never sent to an AI or written in a log.
Sensitive actions are written to an audit log before they happen, and switching a staff login off takes effect on their next click.
Moderation queue
3 open
Every row is stamped with the centre it belongs to. Nothing crosses.
