EdTech privacy · Trust
Privacy-conscious learning
A tool that teaches students to question data collection should survive its own questioning. This page explains why privacy matters in educational technology and documents how this project answers — based strictly on what the code does.
This page explains why privacy matters in educational tools and exactly what NO AI ACT does and does not collect, based strictly on its implementation: no account, no registration, no player profiling, and gameplay data that stays in the browser. It complements the privacy-by-design page. Nothing here is legal advice.
01Why privacy matters in educational tools
Classrooms are captive environments: students rarely choose their tools and cannot meaningfully refuse them. That makes edtech data collection a power issue, not a preferences issue — and it makes "we only collect a little" an answer that deserves scrutiny. The AI Act itself treats education as a sensitive, high-stakes domain.
02What this project does — and does not do
- No registration: the game runs in the browser; no accounts, emails or identifiers.
- No player profiling and no gameplay telemetry: decisions, scores and reports never leave the device; progress lives in localStorage only.
- Aggregate page statistics only on the public site (cookie-free Cloudflare Web Analytics), never inside gameplay.
- No external forms embedded: this version includes no third-party feedback forms.
The complete implementation-level description lives on privacy by design; the code is open source and verifiable.
03Questions to ask any classroom tool
- Does it require student accounts? Why?
- What leaves the device, exactly — and can the vendor show you?
- Is there a dashboard profiling individual students? Who sees it?
- Could the tool work without that data? (If yes, why is it collected?)
- What happens to the data when the class ends?
These questions double as teaching material: they are the same ones the game trains players to ask of any automated system — see AI literacy.
04Using this page in class
Pair one game case with an audit of a real tool the class uses, applying the questions above. The contrast between "what we can verify here" and "what we cannot verify there" is usually the liveliest discussion of the session. A structured version is in the classroom activities.