Security statements are easier to trust when you can check them. Teachers can review conversations, administrators can see an audit log of agent actions and access is based on roles. During the build, we walk your team through these views so you know where to look. Ask to see them on the discovery call or in the blueprint review, before any agent goes live.
Controls only help if people use them. We suggest a named person on your side reviews the audit log and a sample of conversations regularly, especially in the first weeks. Their findings feed back into the agent's rules, which is how a safe setup stays safe as your school and its information change.
Your own policies come first, so use a short checklist to compare providers fairly, including us. Write the questions down before you meet anyone, and ask each provider to show you the answers in a working product, not only in a document. Vague answers to simple questions about data are worth noticing early.
The controls described here show how we build, not a legal opinion about your obligations. Your school, district or company remains responsible for its own policies, and your legal or data protection lead should review the arrangement. Share your requirements on the discovery call and ask for them to be written into the blueprint. If a requirement cannot be met, we will say so plainly instead of promising it.
The tutor gives hints, not answers, and teachers can lock it to hints-only mode for homework and tests.