A data-protection impact assessment for "Your games" (Swiss FADP Art. 22, GDPR Art. 35). Last updated 9 November 2026 (version 1.7).
What the processing is
- A player who chooses to connect their lichess account signs in on lichess.org. The app asks lichess for no permissions beyond knowing which account it is.
- Our server then imports that player's finished rapid, blitz and classical games from the last 24 months, up to 1,000 games, and later their new games. The player can also share one of their own games with the app (at most 20 a day, no older than 24 months): it is fetched from lichess at their request, stored like an imported game and analysed straight away.
- Each game is analysed with a chess engine on our servers: an evaluation of every position, a class for each of the player's moves (inaccuracy, mistake, blunder), a few "find a better move" positions (among them positions where the opponent's mistake gave the player a chance they missed), the opponent's threat where the player's move did not meet it, and endgame positions where a win or draw slipped.
- The player's phone downloads that analysis and works out, on the phone, where the player leaves their opening lines, which mistakes come back, how each game was decided, how often a few habits come up in their recent games compared with earlier ones, and a short report. Nothing worked out on the phone is stored on our server.
- The phone also builds practice from it: drills from the player's own positions (where the opponent had a threat the player's move did not meet, the drill first asks for that threat), "Is it safe?" checks from positions in the player's games and fix cards for the moves where they left their lines, inside the part of the daily practice their games set (switched off in Settings); with games in, how much of the day openings take is set from the games and lines the games never reach come back less often, which changes only what is practised, and tactics, endgame and threat exercises from some of those positions, inside their own part of the daily practice (switched off in Settings). Reports of a wrong drill or check are kept with the player's practice.
- While "Share monthly practice counts" is on (on by default), the phone sends per month how many slips the player fixed or repeated: numbers only, linked to the account, deleted when it is switched off, at disconnect and at erasure; the operator looks only at totals across players.
- The data: the player's lichess id and username; their lichess puzzle rating, read when they connect, which sets where their tactics and puzzles start; the lichess access token, encrypted with Google Cloud KMS; the games (date, time control, colour, result, both ratings, opening name, moves, clock times) and their analysis. From the opponents: their moves, their rating and their clock times in those games, and one keyed code per opponent: a hash of their lichess id under a secret key that only our server holds. Nobody can turn the code back into a name; it never leaves the server and is used only to find an opponent's games when they ask to see or delete them. Never an opponent's name or lichess id.
- Where: Google Cloud in the EU (Firestore in eur3, Belgium and the Netherlands; the service in Belgium), and a copy of the analysed games on the player's phone.
- How long: each game for 24 months after it was played; everything imported is deleted when the player disconnects or their account is erased. The level the player's tactics and endgames started at (from the puzzle rating, the games' ratings or the tactics level, rounded to 50) is part of their practice and stays with it.
The full field list is in Your data and the deletion schedule in Retention.
Why we assess it
| Factor | Here |
|---|---|
| Profiling | Yes: the analysis describes how the player plays (where they leave their lines, which mistakes come back, how they use their clock), at their request |
| Data about other people | Yes: opponents' moves and ratings, collected without asking them (see Opponents' data) |
| Scale | Up to 1,000 games per player; few players while sign-in is limited to invited testers |
| Sensitive data | None |
| Children | Players must be 16 or older; opponents on lichess may be younger |
| New technology | No: a chess engine and an ordinary database |
The processing may not strictly require an assessment, but profiling plus other people's data makes one prudent.
Is it high-risk profiling?
The FADP treats profiling as high-risk when it combines data in a way that allows an assessment of essential aspects of a person's personality; it then needs express consent. Our assessment is that this is profiling, but not high-risk:
- It looks only at chess: moves and clock times in one kind of online game, and the player's lichess puzzle rating. It says nothing about health, money, work, beliefs, relationships or behaviour outside chess.
- It serves only the player's own training, at their request, and is shown only to them.
- It is not combined with other data, not shared, and no decision is taken about the player.
- The player can disconnect at any time, and everything imported is then deleted.
The legal basis is therefore our agreement with the player (GDPR Art. 6(1)(b)).
Necessity and proportionality
- Only what the analysis needs. No opponent names or ids, no chat, no bullet or variant games, nothing beyond 24 months or 1,000 imported games plus the player's own shares (at most 20 a day), and no lichess permissions.
- One purpose. The player's own analysis and practice. Never advertising, never sold, never used to train anything.
- Limited storage. A daily job deletes games older than 24 months. Disconnecting deletes the link, the token and every imported game and its analysis. The phone's copy follows: deletions reach it on its next download, and disconnecting or signing out removes it at once.
- Open about it. A notice before connecting, the Privacy notice, this assessment and the opponents' assessment are published in the app.
Risks and measures
| Risk | Measures | What remains |
|---|---|---|
| The lichess token leaks and someone reads the player's lichess data | No lichess permissions are requested; the token is encrypted with a key only the importing service may use, decryptions are logged, and the token never reaches a phone or a log | Low |
| An opponent is identified from our copy | No names or ids are stored; the keyed code stays on the server and is never shown; the app links only to the public game the player took part in | Low: the games are public on lichess already |
| Opponents don't know their moves are analysed | Published notice and assessment; any opponent can see or delete their data and keep it out of later imports (Data requests) | Low to medium, accepted under GDPR Art. 14(5)(b) |
| Someone else sees a player's report on a shared phone | The app needs a signed-in account; each account's data is in its own database, deleted at sign-out | Low |
| Data kept too long | Daily 24-month deletion; deletion at disconnect and erasure | Low |
| A player shares a game that isn't theirs | The server fetches only the game id, from lichess, and keeps it only if lichess lists the player's connected account as White or Black; otherwise nothing is stored | Low |
| Shares add games beyond the import's limits | At most 20 a day per player, only games of the last 24 months, deleted on the same schedule as imported games | Low |
| The report discourages or shames the player | Calm statements only; no scores that shame; "not enough games yet" below 20 games | Low |
| Access from outside the EU | Google LLC may access data for support or security; Data Privacy Framework certification and standard contractual clauses | Low |
Outcome
The remaining risk is low. No prior consultation with the Swiss Federal Data Protection and Information Commissioner (FDPIC) is needed. The operator confirmed this outcome on 4 October 2026, including that the analysis is not high-risk profiling under the FADP, that opponents are informed under GDPR Art. 14(5)(b), and that the monthly practice counts rest on legitimate interests with a switch in Settings, on by default. The assessment is reviewed again whenever the processing changes; it was reviewed on 18 October 2026 for chances and threats from opponents' moves (version 1.2), with the same outcome; on 22 October 2026 for the player's lichess puzzle rating (version 1.3), with the same outcome; on 27 October 2026 for drills that first ask for the opponent's threat (version 1.4), with the same outcome; on 29 October 2026 for how each game was decided and a few habits compared with earlier games, worked out on the phone (version 1.5), with the same outcome; on 31 October 2026 for "Is it safe?" checks from positions in the player's games (version 1.6), with the same outcome; and on 9 November 2026 for how much of the daily practice openings take and how often lines the player's games never reach come back, worked out on the phone (version 1.7), with the same outcome: still not high-risk profiling under the FADP, because it changes only what is practised and the player can set the openings' share and switch practice from games off.