One key per student, and why that's the whole point
Envelope encryption with a per-record data key turns "we deleted it" from a policy statement into a fact you can verify — and turns key loss into a permanent, irreversible cost.
Classline blog
Engineering and education, argued separately
Two tracks under one roof, kept structurally apart: how the system is actually built, for the people who have to trust it — and what a school should ask before any of it goes in.
Track
Engineering
Field-level encryption, self-hosting, Go and htmx — what a hundred passing tests failed to catch. For the people evaluating this product.
Track
For educators
Why behaviour-data persistence matters, and what to ask a vendor before it goes in. For teachers and school leaders.
Recent posts
What to ask a vendor about your students' data
Ten practical questions for a school evaluating any behaviour-tracking or communication platform, with plain-language explanations of why each one matters and what a good answer sounds like.
What a hundred passing tests didn't catch
The core loop passed every test in the suite and was completely inert in a browser, because no test ever fetched what a template referenced.