Legal
Privacy statement
In short: your career, progress, profile and settings stay in your own browser. Only when you use a feature that needs a server does anything leave it, and then only what that feature needs. There is no advertising, no tracking and no cookies.
1. Who is responsible
The controller is the company that runs CyberSim (see company details). Send questions and requests through the contact route at the top of this page. Where a school or training organisation uses CyberSim with its students, the school may itself be responsible for the data of its students; that is agreed with the school.
2. What we process, why, on what basis and for how long
| Data | When | Why | Legal basis | Kept |
|---|---|---|---|---|
| Access to the closed playtest (ended 8 November 2026): your access code and the name it was made for | When you were invited | To let only invited testers in | Legitimate interest | No longer collected; a cookie set during the playtest expires in your browser within 30 days |
| Website progress, profile (name, avatar or photo, status, bio), game save and settings | Always | So you can train and play across visits | Not processed by us: it stays in your browser (see cookies and storage) | Until you delete it |
| Practice assessment result: the name you type, score, decisions and comments | When you ask for a verified result | To give you a result that cannot be edited | Still to be completed | 90 days, then deleted automatically |
| Official assessment: the name, cohort and trainee ID your trainer entered, score, decisions and comments | When your trainer invites you | So your trainer can rely on the result | Still to be completed | 365 days; an unused invitation 30 days after it expires |
| Abuse counters on the assessment server | On each request to it | To stop abuse | Legitimate interest | 2 days; your IP address is not stored, only a salted hash that changes daily |
| Shared office floor: your name, rank, look, position, emotes and chat | While you are on a shared floor | To see and talk to colleagues | Still to be completed | Not stored: passed on live only |
| Student account: username, display name, password (hashed), class, progress | When a student joins a class | To keep progress across computers and show it to the student’s own teacher | Still to be completed | Still to be completed |
| Player account: e-mail address, username, display name, password (hashed), that you confirmed being 16 or older, progress | When you create an account | To sign you in, send mail about your account and keep your progress across computers | Still to be completed | Still to be completed |
| Teacher account: e-mail address | When the owner creates it for a school | To sign in and manage classes | Still to be completed | Still to be completed |
| Server logs of our hosting providers: IP address, browser, the address requested | On every visit | To run and secure the service | Legitimate interest | According to the providers’ terms |
A verify link shows one result’s name and score to whoever has the link: that is what it is for. Do not type personal details into the comment fields of an assessment.
3. Who receives it
Our hosting providers, as processors: Vercel (the website) and Supabase (the assessment server, the shared office floor and the accounts) and Resend (sends the account mails: confirming your address, resetting your password). Nothing is sold or used for advertising.
4. Where it is stored
The assessment server runs in London, United Kingdom (AWS eu-west-2); the UK has an adequacy decision of the European Commission. The accounts run in a separate project in Paris, France (EU, AWS eu-west-3).
5. Your rights
You can ask to see your data (access), to correct it (rectification), to delete it (erasure), to restrict its use, to object to it, and to receive it in a usable format (portability).
With an account you can do two of these yourself, on your profile or in the account menu. Download my data saves one file (JSON) with everything your account keeps on our server and your account’s progress in this browser; it holds nothing about other people. Delete my account asks twice, then deletes on our server your account and sign-in details, profile, progress, game career, class places and official results, and signs you out on every device (a device that is still open loses access within minutes, when its sign-in token runs out). You then choose whether your progress also leaves this browser. A school account can be deleted the same way: your school arranged it, your teacher sees that you left the class, and the school’s log notes that a student deleted their account, without saying who. Teacher and staff accounts are closed by the platform administrator on request.
For everything else, or when you cannot sign in (also with a suspended account), write through the contact route at the top of this page; we answer within one month and first check that the request is yours. Data in your own browser you can see and delete yourself. Deleted data stays in the providers’ backups until they expire, and in any report file someone downloaded.
If you think we handle your data wrongly, you can complain to the Dutch Data Protection Authority, the Autoriteit Persoonsgegevens.
6. Children and schools
In the Netherlands a child under 16 needs the permission of a parent or guardian where consent is the legal basis (article 5 of the Dutch GDPR Implementation Act, UAVG). Without an account nothing about a child leaves the browser. Student accounts are made through a school: the student joins a class with a code from their teacher, needs no e-mail address, and only their own teacher sees their progress. The school arranges the agreement and, where needed, the parents’ permission.
7. Changes
When this statement changes we say so on the site and update the date below.
Last updated 8 November 2026.