Chanki

Impact assessment: Your games

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

The full field list is in Your data and the deletion schedule in Retention.

Why we assess it

FactorHere
ProfilingYes: 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 peopleYes: opponents' moves and ratings, collected without asking them (see Opponents' data)
ScaleUp to 1,000 games per player; few players while sign-in is limited to invited testers
Sensitive dataNone
ChildrenPlayers must be 16 or older; opponents on lichess may be younger
New technologyNo: 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:

The legal basis is therefore our agreement with the player (GDPR Art. 6(1)(b)).

Necessity and proportionality

Risks and measures

RiskMeasuresWhat remains
The lichess token leaks and someone reads the player's lichess dataNo 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 logLow
An opponent is identified from our copyNo 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 inLow: the games are public on lichess already
Opponents don't know their moves are analysedPublished 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 phoneThe app needs a signed-in account; each account's data is in its own database, deleted at sign-outLow
Data kept too longDaily 24-month deletion; deletion at disconnect and erasureLow
A player shares a game that isn't theirsThe 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 storedLow
Shares add games beyond the import's limitsAt most 20 a day per player, only games of the last 24 months, deleted on the same schedule as imported gamesLow
The report discourages or shames the playerCalm statements only; no scores that shame; "not enough games yet" below 20 gamesLow
Access from outside the EUGoogle LLC may access data for support or security; Data Privacy Framework certification and standard contractual clausesLow

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.