Human control, restricted access and deliberate deployment.
Appropriate access scope
Schools have separate data. Roles, class assignments and parent relationships determine server-side visibility. Hiding a button alone does not protect data.
The teacher approves
Generated material is a draft. The teacher checks content and the answer key, publishes the task and decides on scoring and feedback.
Student privacy
Parents access authorised child data. A full private tutor conversation does not automatically become a family report.
AI rules at school
The administrator defines available features, limits and configuration. Provider keys stay on the server. Voice and task photos require the appropriate permissions and setup.
A record of important changes
Important operations record an audit history. Version control helps prevent overwriting simultaneous work. Selected roles require a second authentication factor.
Acceptance before using real data
Before working with school data, we agree contracts, processing scope, retention, incident handling and required audits. We do not claim ministry certification or an already completed full audit.
AI is not infallible.
Models can provide incorrect information or fail to follow instructions. The tutor requires educational evaluation and materials require teacher review. Wellbeing reports require action by the appropriate person; the app is not an emergency service.