PRIVACY
POLICY.
1. Controller
The controller for personal data processed through this site and the game is [FULL NAME / COMPANY], based at [ADDRESS]. Privacy contact: [PRIVACY EMAIL].
2. Two possible configurations
The game ships in one of two states, and which one applies changes this policy substantially:
- Local only (default). No backend is configured. Callsign, identifier and scores are stored solely in your browser's local storage. Nothing is transmitted to us, and no leaderboard is shared with other players.
- Online leaderboard. A backend is configured. The data listed in section 3 is transmitted to and stored on that server so that scores can be ranked against other players.
The currently published configuration is: [LOCAL ONLY / ONLINE LEADERBOARD]. When the online leaderboard is active, the database provider is [PROVIDER, e.g. Supabase — hosting region], acting as a processor.
3. What data is processed
| Data | Why | Where it lives |
|---|---|---|
| Guardian callsign, chosen by you | To identify your scores on the leaderboard | Browser, and server if online |
| Random identifier (UUID) generated on first visit | To keep your scores attached to you if you rename yourself | Browser, and server if online |
| Score, wave reached, run duration, sector, difficulty, game version, timestamp | To rank runs and to reject implausible results | Browser, and server if online |
| Aggregates: personal best, number of runs, average score, last seen | To build the player profile and the boards | Server, if online |
| Rejected submissions and the reason for rejection | Anti-cheat and abuse prevention | Server, if online |
| Technical connection data (IP address, request logs) | Delivery and security of the service | Hosting and database providers |
Please choose a callsign that is not your real name and does not identify you: nothing in the game requires it, and a nickname keeps the leaderboard public without making you public.
No account, password, email address or payment data is ever requested. There is no advertising, no profiling and no social tracking.
One third-party connection exists on both the site and the game: typefaces are loaded from Google Fonts, which discloses your IP address and browser details to Google as an unavoidable part of any HTTP request. See the Cookie Policy for the detail and for how to remove it by self-hosting the fonts.
4. Purposes and legal bases
Storing the callsign, identifier and scores serves to deliver the competitive feature you asked for by entering a callsign and finishing a run: the legal basis is performance of the service requested by you (Art. 6(1)(b) GDPR), or your consent where that is the more appropriate basis in your jurisdiction.
Anti-cheat validation, rate limiting and the anomaly log rest on the controller's legitimate interest in keeping the leaderboard meaningful and the service available (Art. 6(1)(f) GDPR). Technical logs kept by hosting providers rest on the same basis, together with Art. 32 GDPR on security of processing.
5. Retention
Data held in your browser stays until you clear your browser storage; you can do this at any time from your browser settings, and it removes your local identity completely.
Where the online leaderboard is active, scores and profiles are retained for [RETENTION PERIOD], or until deletion is requested. Anomaly records are retained for [RETENTION PERIOD]. Provider-side technical logs follow the provider's own configuration and legal obligations.
6. Recipients and transfers
Data may be processed by technical suppliers acting as processors: the site host, and — in the online configuration — the database provider named in section 2. Where any provider stores data outside the European Economic Area, the transfer must be assessed and documented under Chapter V GDPR, and the relevant safeguards recorded here: [SAFEGUARD, e.g. EU hosting region / standard contractual clauses].
7. Your rights
Under Arts. 15–22 GDPR you may request access, rectification, erasure, restriction, objection and portability, and withdraw any consent given, without affecting the lawfulness of processing carried out before withdrawal.
Because the leaderboard identity is a callsign plus a random identifier, please include your callsign in any request so the record can be located. Requests go to [PRIVACY EMAIL]. You may also lodge a complaint with your supervisory authority; in Italy this is the Garante per la protezione dei dati personali.
8. Children
The game is not directed at children and asks for no data beyond a chosen callsign. If you believe a child has entered identifying information as a callsign, write to [PRIVACY EMAIL] and it will be removed.
9. Security
Where the online leaderboard is active, the client cannot write to the database directly: all writes pass through validated server-side functions, and row-level security denies direct insertion and modification. Appropriate technical and organisational measures are applied in proportion to the risk, under Art. 32 GDPR.
10. Changes
This policy will be updated if the site, the game or the services behind them change. The published version always carries the date of its last update.
← BACK TO THE LANDING