Zero student data — by design
A one-page statement for school leaders, operators and data protection officers
What the student side is
Free, browser-based daily practice games for color, pitch and rhythm perception, served as static web pages in nine languages. Students open a link; no account exists, nothing is installed.
What we do not collect from students
- No accounts — none exist, so none can be created, breached or subpoenaed
- No names, email addresses, class lists, birth dates, photos or location data
- No student results on our servers — results are stored in the student's own browser, on their device
- No cross-site tracking or profiling of students, and no sale or sharing of student data — there is none to sell
How an assignment works, technically
A teacher creates an assignment in the teacher builder. The settings are encoded in the part of the link after the # character (the URL fragment). Browsers do not send the fragment to any server: it is read and decoded inside the student's browser. The game then runs locally, and results are written to the browser's local storage on the student's device. If a teacher wants to see progress, the student shows their progress card — physically, at the student's choice.
What runs where
| Layer | What it does |
|---|---|
| Our server / CDN | Serves the game pages as static files — like any website, the hosting layer transiently processes standard technical request data (such as IP addresses) to deliver and protect the service. We do not use it to identify or profile students. |
| The student's browser | Everything else: assignment decoding, gameplay, results, the progress card. |
Analytics and advertising
- Public game pages: an optional, consent-based analytics feature exists for general visitors and runs only after explicit consent.
- While an assignment is active: no analytics events are sent and no ads are shown.
- The /teach and /education pages are always ad-free.
What this typically means for your paperwork
Because the tool does not process student personal data, in our understanding there is typically no student-data processing relationship to put under a contract (no Article 28 GDPR data-processing agreement for student data) and no parental consent to collect for the use of our tool. The license record holds the buyer's name (teacher or institution) for licensing and invoicing — that is the customer's business data, not student data.
Verify it yourself
The student flow can be inspected end to end: open an assignment link, open the browser's developer tools, and watch the network activity. We invite you to.
This document is a factual description of the product as designed and shipped on the date above. It is not legal advice; your institution makes its own determination. Questions: hello@huekle.com.