Learner evidence is private by default.

Teacher and learner application areas require authenticated access. Server routes verify the signed-in account and the teacher-student relationship before returning private records.

Private tables use row-level security or server-only access patterns. Browser clients are not given unrestricted database access to teacher, learner, recording or AI-conversation data.

Lesson recordings and student photos are stored in private storage buckets. They are not published through permanent public URLs; authorised workflows use controlled or short-lived access.

Service credentials and AI provider keys are kept in server-side environment variables rather than public browser configuration.

Student code and PIN login attempts are rate-limited using privacy-minimised identifiers, reducing repeated guessing without storing the attempted credentials as plain tracking data.

AI can help interpret lesson evidence, but teacher review remains part of the workflow before learner-facing review content is approved or shared.