District & IT
Built for districts. Student privacy in mind.
Built with student privacy and classroom controls in mind. COPPA-aware design; for school deployments, data handling is designed to align with FERPA expectations for education records. We design to SOC 2 Trust Services Criteria (Type II certification in progress). DPA, SLA, and School Services Agreement available on request.
COPPA-aware
Classroom controls
Agreements on request
Privacy & Compliance
Data Privacy & Compliance
Built with student privacy and classroom controls in mind. COPPA-aware design; for school deployments, data handling is designed to align with FERPA expectations for education records. We design to SOC 2 Trust Services Criteria (Type II certification in progress).
COPPA-aware
COPPA-aware design. Built with student privacy and classroom controls in mind.
FERPA expectations
For school deployments, data handling is designed to align with FERPA expectations for education records.
SOC 2
We design to SOC 2 Trust Services Criteria (Type II certification in progress).
Agreements on request
DPA, SLA, and School Services Agreement available on request.
Data minimization
We collect only what's needed to operate the platform and support safety features — not for advertising, not for sale, not for third-party marketing. HeyOtto does not sell student data or use it to train models on identifiable information.
Retention & deletion
A deletion request or a closed account starts a 24-hour clock. Student data is removed on that timeline — not held in a backlog, not parked for later.
Subprocessors
A current subprocessor list is available on request as part of the Data Processing Agreement.
Safety
Real-Time Safety Monitoring
- 01
Real-time conversation scoring
Every conversation is scored as it happens — flags for self-harm, sexual content, grooming, violence, and bullying as they happen, not after the fact.
- 02
Ongoing behavioral tracking
HeyOtto builds a running safety profile per student across conversations, so patterns get caught, not just single messages.
- 03
Four-tier Real-time alerts
Low, Medium, High, and Critical — so staff know what needs attention now vs. what’s just a flag.
Admin
Admin Dashboard
District and school admins get visibility without needing to read every conversation:
User management across schools and classrooms
District- and school-level administration from one account
Reporting and usage analytics
Role-based access (district admin, school admin, teacher, student)
Data handling designed to align with FERPA expectations across every role
Rollout
A Simple Path to District-Wide Use
- 1
Start with a pilot
One school, one grade band, one advisor or coordinator.
- 2
Review the paperwork
DPA, SLA, and School Services Agreement available on request.
- 3
Roll out district-wide
Scale from pilot to full deployment once approved.
IT
Integration & Technical Requirements
Single sign-on
SSO is available for school-wide and district-wide deployments.
Rostering
HeyOtto doesn't require full roster sync to get started — schools can onboard through invite-based signup for pilots, with SSO-based rostering available for full district deployment.
LMS compatibility
Google Classroom integration.
System requirements
Browser-based, no software install. Works on Chromebooks, the standard 1:1 device in most K–12 districts.
Deployment models
- 01
Classroom pilot
A single teacher or grade level, invite-based, no district IT lift required.
- 02
School-wide rollout
School-level admin account, teacher and student roles provisioned through SSO.
- 03
District-wide deployment
District admin account with visibility across schools, centralized provisioning, and a named implementation contact.
FAQ
Common Questions from IT & Compliance
Straight answers for district technology, privacy, and legal review.
Next step
Ready for Your District?
Talk to our team about a pilot, or review our Trust Center for full technical and compliance detail.