Last updated: April 2026
Saya is deployed inside live K–12 classrooms. We take student data protection seriously and operate in accordance with FERPA (Family Educational Rights and Privacy Act) and COPPA (Children's Online Privacy Protection Act). This policy explains what data we collect, why, and how it is protected.
Teacher account data: Name, email, school name, and hashed password at registration.
Session configuration: Grade level, subject, topic, persona, language, and class size settings created by the teacher.
Session transcripts: All messages typed or spoken during a classroom session, including teacher narration, student contributions (attributed by name if provided), and Saya's responses.
Usage metrics: Token counts, provider latency, and cost estimates for internal monitoring. No personally identifiable information is included in these metrics.
Every session, message, and analytics record is linked to the teacher's account ID. No teacher can access another teacher's sessions or student data. School administrators do not have access to individual session transcripts unless the teacher shares them.
Session data is retained for as long as the teacher's account is active. Teachers can delete individual sessions from their dashboard at any time. Account deletion removes all associated sessions, messages, and analytics permanently. Deletion requests can also be submitted to waqas.shah88@gmail.com and will be processed within 30 days.
Saya operates as a "school official" under FERPA when contracted by a school or district — we process education records only for legitimate educational purposes and under the direction of the institution. We do not disclose education records to third parties without appropriate consent or a valid FERPA exception.
Saya accounts are created by teachers, not students. No child under 13 is asked to create an account or provide personal information directly to Saya. Student contributions visible in the classroom feed are entered by their teacher and are not collected from students directly.
Passwords are hashed using bcrypt (cost factor 12). All data in transit is encrypted via TLS 1.2+. Database access is restricted to authenticated application servers. We conduct periodic security reviews and will notify affected users within 72 hours of a confirmed data breach.
Privacy questions or deletion requests: waqas.shah88@gmail.com