For schools & districts
ELL support, without the procurement cycle.
Teachers can use Multilinguals with one lesson without waiting for district approval. When you’re ready for a building-wide pilot, we handle setup and give you the data your team needs.
Book a pilot
45-minute conversation · free to try
Compliance, by architecture
What your IT team will ask about, answered up front.
| Student PII | Not collected. First name only. No last names, emails, or roster data. |
|---|---|
| Student accounts | None. Students join with a classroom code and a first name. |
| COPPA | Architecturally compliant — we collect no PII from children. |
| FERPA | No education records stored against student identities. |
| AI vendor contact | Student devices never contact AI vendors. All processing is server-side. |
| Data retention | Lesson content & vocabulary: indefinite (teacher library). Session data: 30 days. |
| Data sale / advertising | Never. No ad networks, no third-party trackers. |
| SSO | Google Workspace for Education and Microsoft Entra supported. |
Pilot structure
Four weeks. Three to eight teachers. Reportable outcomes.
- W1
Setup & training
We handle provisioning, run a 45-minute teacher onboarding, and get your first lessons uploaded.
- W2–3
In-classroom use
Teachers use Multilinguals on their actual lesson plans. We check in once a week, keep the friction low.
- W4
Data & debrief
Usability survey, teacher interviews, and a short report with vocabulary-engagement data you can show your ESOL coordinator or board.