Loading…
Loading…
For district IT leads and curriculum directors
The plain-English version of our student-data posture — FERPA, COPPA, residency, and exactly what rostering data flows today. Our actual legal documents (Terms, Privacy Policy, Data Processing Addendum) are canonical at koydo.app/legal and govern in any conflict with this page.
No data leaves your SIS automatically — yet.
Clever, ClassLink, and LTI 1.3/OneRoster automatic rostering sync are in active setup — none is live yet. Until one is connected for your organization, the only student data Koydo receives is what a school admin explicitly types or uploads: a CSV cohort import (name, email, grade band, under-13 flag) or what a student enters redeeming a class code in their browser. Nothing pulls from your SIS in the background. When a live sync is ready for your district, you'll opt in explicitly and we'll tell you exactly which fields it reads.
What counsel usually asks.
US-East AWS via Supabase Postgres by default. EU-only data residency available on request at signup.
Only the assigned instructor, the student, and — for under-13s — the consenting parent. No third-party tracking pixels on student-facing pages.
The built-in COPPA parental-consent flow triggers automatically for any under-13 account. No audio or transcript is stored until a parent completes consent.
CSV gradebook export and a per-cohort JSON progress dump are available at the admin level any time — no data lock-in, cancel or not.
Yes, when contracted with a US K-12 school. Koydo acts as a school official under the FERPA school-official exception, which lets a district share student education records with us for the legitimate educational purpose of running the language program. The full designation and posture live at /policy/ferpa-school-official-agreement and /trust-center/ferpa-program.
Only what a school admin explicitly uploads via a CSV cohort import (name, email, grade band, under-13 flag) or what a student types in redeeming a class code. Clever, ClassLink, and LTI 1.3/OneRoster automatic sync are in active setup and are not live yet — see /educator/school/rostering for the honest per-provider status. No student data flows automatically from a district SIS until one of those integrations is actually connected.
US-East AWS via Supabase Postgres by default. EU-only data residency is available on request at signup for districts and schools with that requirement.
Only the assigned instructor, the student themselves, and — for under-13 students — the parent or guardian who completed the COPPA consent flow. No third-party tracking pixels run on student-facing pages.
CSV gradebook export and a structured JSON progress-record dump per cohort are both available at the admin level, any time, with no data lock-in. Cancelling a plan does not forfeit your ability to export what you built.
Yes, at pilot start. The DPA references the canonical legal terms at koydo.app/legal, and we'll sign a district's preferred template where one exists.