Security and Privacy
Socrait is human-centered AI that was engineered from day one for privacy, security, and data protection. We were built to comply with FERPA and state-level student data protections in the U.S., and we design every feature with those guardrails in mind. We purposely do not collect data directly from students, so COPPA does not apply.
Socrait Uses AI to Empower Teachers and Improve Schools
We understand the skepticism about using voice technologies and AI in classrooms.
Our commitment is simple:
We are Teacher-first.
When values conflict, we put ourselves in the teacher’s shoes.
Safety-first.
We use best practices to protect the student and teacher data.
Transparency-first.
You should always know what we collect, why, and how it’s protected.
Privacy and Safety Overview
No classroom audio recordings.
Socrait streams audio in real time, converts the waveforms to text, and extracts classroom events. We do not save classroom audio.
Teachers control when Socrait listens.
Socrait only listens when a teacher taps “Start.” Teachers can stop at any time.
Teachers control whether Socrait saves the data.
If a teacher would like to remove the data for a class, they can press a button in the Class Dashboard to delete it.
We never sell data.
We do not sell student or teacher data ever.
Built for FERPA, COPPA, and state student privacy laws.
We sign data protection agreements (DPAs) and state student privacy addenda with schools and districts, and we operate as a school official under FERPA.
ISO-27001 certification
We are actively pursuing ISO-27001 certification and can provide a letter of engagement upon request.
Student names are removed before AI processing.
When we send requests to an AI or LLM, we replace actual student names with placeholders like person_1. When we receive the results, we replace person_1 with the student name so that you see it correctly.
US-based, encrypted storage.
All data is stored in Google Cloud data centers located in the U.S., encrypted in transit (SSL/TLS) and at rest (AES-256).
Admin views are aggregated.
Teachers see their own class data first; school leaders view aggregate patterns, not a live “surveillance feed” into classrooms.
Teacher’s choice.
As we add more functionality, teachers will make the choice to allow other school staff to have access to class data directly. For example, a teacher may choose to share class data for a particular student with that student’s Special Education Case Manager.
How Socrait Uses AI in The Classroom
Streaming, Not Recording
- The Socrait mobile app streams the teacher’s voice to our secure cloud using a real-time conferencing tool over encrypted channels.
- We do not create or store audio recordings on the teacher’s phone or in the cloud. Voice processing happens in real time.
Names Removed Before AI is Used
- An automatic speech service converts the audio stream into short text “utterances.” Voice waveforms are not saved.
- Socrait’s own models then identify classroom events (e.g. attendance, praises, warnings, participation, reminders, and “to-do” moments) from those utterances.
Voice → Text → Classroom Events
- Before any text is sent to an AI model (for a summary, draft email, or reminder), Socrait removes student names and other direct identifiers inside our own infrastructure.
- AI tools see students as person_1, person_2, etc. They do not know which school or class the events came from.
AI Suggestions, Human Control
- AI generates artifacts like class summaries, parent email drafts, and to-do lists, which are displayed in a dashboard.
- Teachers decide which artifacts to use, edit, or share. The teacher is always in control.
Socrait isn’t critiquing, scoring, or judging teachers. Socrait is simply remembering and organizing what teachers already say aloud so they don’t have to write it all down.
What Data We Collect and Why
Updated: December 12th, 2025
We focus on collecting only the data needed to support teachers, students, and school leaders. We update this regularly as the product evolves. See latest privacy policy here
Teacher Account Data
Examples
- Name and email address (from Google SSO)
- Name the teacher uses in class (e.g. Mrs. Brown)
- Class name and period
- School name (for some users)
- Login and usage metadata (e.g., last login time, device type)
Why we collect it
- To securely authenticate teachers (we don’t store passwords; sign-in uses Google SSO).
Socrait Data Privacy and Securi… - To associate recordings and class events with the right teacher and classes
- To help us provide support, troubleshoot issues, and improve the experience
Student Roster Data
Examples
- Student first names or nicknames as entered by the teacher
- Future: Optional student IDs or roster information provided by the school (depending on the integration)
Why we collect it:
- So teachers can use natural speech (“Cameron, great job!”) and still get accurate logs of participation, praises, warnings, and attendance
- To personalize teacher-facing dashboards, summaries, and draft communications
On the mobile app, only student first names or nicknames are visible while the teacher is logged in. Behavior data is not stored on the device. This is to allow teachers to quickly glance at a roster if they are trying to take attendance.
Classroom Events and Derived Data
From teacher speech we derive structured classroom data, such as:
- Praises, warnings, and other behavior notes
- Classroom activities
- Attendance status
- Teacher-spoken reminders (“Remind me to email Jordan’s parents.”)
- AI-generated class summaries and draft communications
- Future: Classroom participation
Why we collect it
- To save teachers time on follow-up and documentation
- To provide teachers with a private, reflective view of their own practice
- To give schools aggregate insight into patterns (e.g., praise vs. warnings) so they can be smarter in the PD sessions they offer and the students they work with
Logs and Diagnostics
Examples
- Basic device and browser information
- Error logs and performance metrics
- Limited actions taken in the web app (e.g., when a teacher views a summary)
Why we collect it
- To keep the service reliable and secure
- To detect misuse or suspicious activity
- To understand which features are useful and where to improve