Privacy · Data · Transparency
Privacy by design
A project that teaches data governance should be exemplary about its own. This page explains in detail what NO AI ACT collects, what it does not collect, and how to verify it.
01What the game does NOT do
- No accounts: you play without registration, email or identifiers.
- Aggregate usage statistics: starts, completions and screens are counted automatically, with a disable control in the game bar. Decisions, scores and reports stay local.
- No player database: the backend stores marginal counters only, without player accounts or identifiers.
- No student data: teacher mode and its debrief export are local and anonymous.
- No persistent identifiers created by the game, no cookies added by the game.
02Where your progress lives
Progress (completed cases, unlocked norms, audio/language preferences) is stored exclusively in your browser's localStorage, on your device. Clear the site data and the progress is gone: it exists nowhere else.
03What is measured on public pages
Public pages use cookie-free Cloudflare Web Analytics. During gameplay, a separate first-party system sends only aggregate counters and closed categories of usage and game-generated assessment, without names, free text, cookies or persistent identifiers. Counters can be disabled and respect DNT/GPC.
This page is about NO AI ACT's own data. For how the two laws relate — when the GDPR applies, when the AI Act does, when both — see the AI Act and the GDPR.
04No external forms
This version embeds no external forms (feedback, surveys or questionnaires): no third-party form script is loaded and no data is transmitted to form providers. The game remains complete and fully playable when aggregate counters are disabled.
05At a glance: measured vs never measured
Aggregate statistics
Public-page visits via Cloudflare Web Analytics and aggregate first-party game counters. They do not count identified people or demonstrate learning; small cells are suppressed.
Answers, scores and reports
Decisions, classifications, scores, reports and outcomes stay local. The game automatically sends aggregate usage counters only, without analytics cookies or player identifiers. Disable them in the game bar; DNT and GPC are respected.
06How to verify it
The project is open source: the code is public on GitHub, including the minimal aggregate collector, opt-out controls and automated tests. Browser developer tools can be used to inspect the bounded counter batches; answers and outcomes are excluded.
The educational reasoning behind these choices is on privacy-conscious learning, with the questions to ask of any classroom tool; the broader context is in the education hub and the glossary (privacy by design, data governance).
07Limitations and contact
- This page describes the software's behaviour; it is not legal advice on data protection.
- Questions, reports or collaborations: open an issue on the GitHub repository.
08Privacy FAQ
Do I need to register to play?
No. No registration, no account, no email: open the link and play. Progress stays in the browser's localStorage.
Does the game use cookies?
The game sets no cookies. The public pages use Cloudflare Web Analytics, which by design uses no cookies and no client-side state for visit counting.
Are my answers sent anywhere?
No. Decisions, scores and reports stay in your browser. Only aggregate usage counters are sent automatically and can be disabled in the game bar. See the statistics notice for retention, infrastructure and controls.
Is there an external feedback form?
No. This version embeds no external forms: there is nothing to fill in and the game sends nothing to third-party form providers.