Privacy & student data
The platform is built on data minimalism: no student accounts, no passwords, no emails, no ads, no third-party trackers — and nothing collected that the classroom doesn't need.
For exactly what is stored where, and what is not yet done, see Privacy and data practices in detail.
What is collected
| Data | Why | Who can see it |
|---|---|---|
| First name + class period (student-entered) | So saved work and progress belong to the right student | The student (via their save code) and the teacher |
| Activity state & progress (save codes) | Cross-device, multi-day save/resume | Whoever holds the save code; roster views are teacher-key-gated |
| Learning signals (struggle / misconception / mastery events) | Same-day intervention and standards rollups | Teacher only (key-gated) |
| Accommodation assignments (initials + section) | So assigned supports follow the student into lessons | Full details teacher-only; the student device receives only generic tool switches — never IEP or language-level information |
What is never collected
- No accounts, passwords, or email addresses; no last names required anywhere.
- No advertising, analytics trackers, or data sale — the platform has no third-party trackers.
- No grades of record — the district gradebook remains the system of record.
- No photos, video, audio recordings, or location data.
How it is protected
- All traffic is HTTPS; data is stored in Cloudflare D1 within the platform's own account.
- Every roster, gradebook, and analytics endpoint requires a teacher key — student data is never world-readable.
- Save-code lookups are rate-limited against guessing: failed lookups are throttled per source, while legitimate classroom use is never blocked.
- The one public showcase (student exemplars) is opt-in per work sample by the teacher, shows first name and last initial only, and exposes only whitelisted written excerpts — never scores, codes, or identifiers.
- Student-facing devices receive only generic tool flags — accommodation categories, IEP status, and language levels never leave teacher-gated endpoints.
FERPA & COPPA alignment
- Data collected is limited to what a teacher already maintains in a classroom (first names, class period, classwork) and is used solely for instruction — consistent with FERPA's school-official purpose.
- No accounts are created and no personal information is required from students beyond a first name for labeling work, in keeping with COPPA data-minimization principles for under-13 users.
- Families may request to view or delete their student's saved work at any time through the class's usual channels; deletion is honored promptly.
Policy last reviewed: July 14, 2026.