Infrastructure
- ·EU regions only
- ·Age-encrypted backups + WAL
- ·Object-locked, retained offsite
- ·Rate-limited, bot-filtered edge
School data is sensitive — students, staff, choices. Here’s exactly how we protect it, what we comply with, and what we don’t (yet) claim.
We’d rather under-claim than mislead. Here’s the real posture.
Processed under EU 2016/679 + French Loi Informatique et Libertés. Data-subject access, a signed DPA, and full transparency on what we hold and why.
Self-hosted on European infrastructure. Your school’s data never leaves the EU and is never sold or shared.
We run the control frameworks in practice — access control, encryption, backups, audit logs — but we do not claim a formal certification we haven’t completed. See the gap analysis on /Security.
US student-data laws. Relevant for American schools; we align with their principles (records, consent, no ad-tech) without claiming a formal audit.
We collect only what a timetable needs — names, subjects, choices, staff. No behavioural profiling, no ad-tech.
Every school’s data is row-level isolated. One school can never read another’s.
Kept while you’re a customer; deleted on request and on offboarding, backups included on a fixed schedule.
What we hold, where, and why is written plainly in the Privacy Policy and DPA — no dark patterns.
Student and staff data is never used to train models. The solver is a constraint engine, not a learning system.
Every control, including what we don't do yet: Security & compliance
Our Privacy Policy, DPA and sub-processor list are written for humans.