This is the full list of personal data Chanki processes. Last updated 19 November 2026 (version 1.26).
Each table says what is kept, why, on which legal basis (GDPR article; the Swiss FADP applies throughout), where, and when it is deleted. "Pseudonymous code" means a short hash of your Google account id: it names no one by itself, but we treat it as personal data. How to see or delete your data: Data requests. How long each item is kept: Retention.
Your account and sign-in
Kept by Google Cloud Firestore in the EU (eur3: Belgium and the Netherlands).
| Data | Why | Basis | Deleted when |
|---|---|---|---|
| Google account id, email address, whether Google verified it | Sign you in; show which account is signed in; check data requests | Contract, 6(1)(b) | Account erasure, or 36 months without use |
| Your email address, to ask you now and then how the app works for you (a short personal email, at most a few times a year, never advertising) | Improve the app from what players tell us | Legitimate interests, 6(1)(f); reply "stop" | Account erasure, or 36 months without use; after a "stop" we don't ask again |
| Your answers to those emails, and a "stop" if you send one — kept in our Gmail mailbox, not in Firestore | Improve the app; never ask again after a "stop" | Legitimate interests, 6(1)(f) | Answers: once they no longer help improve the app, and at erasure; a "stop": at erasure |
| Sign-in sessions: a hash of the session token, a hash of its CSRF token, the account id, times | Keep you signed in safely | Contract, 6(1)(b) | Sign-out, erasure, or 60 days after you last opened the app |
| Practice reminder by email, only if you ask for it (at sign-up or in Settings): on or off and where you chose it, your phone's time zone, the hour they come, when the next is looked at and the last was sent, how many weekly ones went since you last practised, the provider's reference for the last one, who switched it off (you, the email's link, a bounce, or us after a database restore), and a random code for the unsubscribe link. Deciding uses only when your phone last sent practice | Send the reminders you asked for, on the days and at the hour they promise; stop them with one click | Contract, 6(1)(b) | Account erasure, or 36 months without use |
| Erasure record: a hash of the account id, the date, a ticket reference | Prove an erasure happened and stop the account coming back by accident | Legal obligation and legitimate interests, 6(1)(c)/(f) | Kept |
The ticket reference never holds personal data.
Your practice
Kept by Google Cloud Firestore in the EU (eur3).
| Data | Why | Basis | Deleted when |
|---|---|---|---|
| Practice events: the moves you play, thinking time, the app's grades, positions from your games past your book (your first move there that went clearly wrong in a game, kept so the position comes back in your practice), the level your tactics and endgames started at (from your lichess puzzle rating, your games' ratings or your tactics level, rounded to 50), sessions, settings changes, an anonymous device id, times | Run the trainer, including planning your reviews from how you remember (worked out on your phone); keep your devices in step. Also counted together with other players' to improve the app, unless "Help improve Chanki" is off | Contract, 6(1)(b); the counting: legitimate interests, 6(1)(f) | Account erasure, or 36 months without use |
| Positions where a move of yours went wrong in practice: the position, the move you played, the moves judged right and good too there, and where the right move sits against the opening's rule of thumb; in Play on also your answer, right or wrong, where the opponent's move before it was a common mistake at your level, with how much that move lost (past the games at your level a model that runs on your phone picks that mistake; it sends nothing anywhere); from your games, past your book, a chance an opponent's mistake gave you that you missed — from older games too — with how much their move lost | Show you the positions where you went wrong in practice; count how often you punish the opponent's common mistakes | Contract, 6(1)(b) | With your practice |
| Notes you report as wrong, with the text you write (up to 280 characters) | Correct the notes | Contract, 6(1)(b) | With your practice. The correction work uses only the note and your text, never your account. |
| Drills you report as wrong, with the text you write (up to 280 characters) | Correct the drills from your games | Contract, 6(1)(b) | With your practice. The check uses the report, your text and whether the game is yours, never your account; its working copy is deleted within 30 days. |
How you use the app ("Help improve Chanki")
Kept by Google Cloud Firestore in the EU (eur3), only while the switch is on (it is on by default; Settings › Help improve Chanki).
| Data | Why | Basis | Deleted when |
|---|---|---|---|
| Usage records: each screen you open and each control you tap (named by a fixed code, never its text), the time since you opened the app, an id for that visit, the app version, the practice-rules version, your rating band, whether it was your first start, the code of the ad campaign or shared position that brought a new account, if any, and in practice the kind of exercise and the moves you play; the pseudonymous code (never your email or Google account id). No notes, reports or anything you type | Improve the app: we only look at totals across at least 5 players | Legitimate interests, 6(1)(f); switch it off in Settings | 13 months after they reach us; switching "Help improve Chanki" off; erasure |
Practice reminders by email (if you ask for them)
Sent for us by Scaleway SAS in France (Paris, fr-par), only while your reminder is on.
| Data | Why | Basis | Deleted when |
|---|---|---|---|
| Each reminder email: your email address, the email (its subject, its few lines, the unsubscribe link), when it was sent and whether it was delivered or bounced (Scaleway's delivery record) | Deliver the reminders; notice an address that bounces and stop | Contract, 6(1)(b) | Kept by Scaleway under its terms, for as long as its service keeps such records; deleting the account doesn't shorten it |
Logs and running the service
Kept by Google Cloud Logging in Belgium (europe-west1), except where stated.
| Data | Why | Basis | Deleted when |
|---|---|---|---|
| Server request logs: IP address, browser, address requested (including any ad campaign and click codes, or a shared position's code, in it), time | Security and fault finding | Legitimate interests, 6(1)(f) | After 30 days |
| App request lines: route, result, timing, the pseudonymous code | Security and fault finding | Legitimate interests, 6(1)(f) | After 30 days |
| IP addresses for the request limits on sign-in, error reports, the public page's counts, the pictures of shared positions and the reminder emails' stop page (server memory only; an IPv6 address by its first half) | Stop repeated sign-in attempts and floods of error reports, counts, picture or stop-page requests | Legitimate interests, 6(1)(f) | After 1 minute; never written down |
| Error-screen counts: which screen, app version, rating band (no account, no IP kept with them) | Find problems | Legitimate interests, 6(1)(f) | After 30 days |
| Cost counters per account: the pseudonymous code, the day's estimated analysis cost and task count (Firestore, eur3) | Cost control and abuse prevention | Legitimate interests, 6(1)(f) | After 35 days |
| Administrator audit logs (operator and service identities only) | Security of the systems | Legitimate interests, 6(1)(f) | After 400 days (set by Google) |
Visiting our public page
The public page is chanki.app/start/, the pages shared positions open at chanki.app/c/, and chanki.app for visitors who aren't signed in, once we turn it on there. Nothing here applies once you are signed in, except that your first start counts the sign-up.
| Data | Why | Basis | Deleted when |
|---|---|---|---|
Counts by day and ad campaign or shared position of visits, tried exercises, sign-ups, in-app-browser notices and shared results: the step, the source, the campaign and ad codes, for a shared position the source share and the kind of position as the campaign (Firestore, eur3; no cookie, no account, no IP) | See which ads and shared positions bring players | Legitimate interests, 6(1)(f) | After 13 months |
Your lichess games (if you connect lichess)
Kept by Google Cloud Firestore in the EU (eur3). Lichess is the source of this data, not a recipient.
| Data | Why | Basis | Deleted when |
|---|---|---|---|
| Your lichess id and username; your lichess puzzle rating (one number, read when you connect; none while lichess calls it provisional); the access token, encrypted with Google Cloud KMS | Import your games; start your tactics and puzzles at your level | Contract, 6(1)(b) | Disconnect or erasure |
| Your games: lichess game id, date, time control, rated or casual, colour, result, both ratings, opening name, moves, clock times, lichess evaluations; our analysis (position evaluations, move classes, "find a better move" positions — among them chances an opponent's mistake gave you that you missed — the threat your opponent had where your move did not meet it, endgame positions where a win or draw slipped, and the tactical themes of those moves, e.g. "fork") | Show where your openings drift and which mistakes come back; set how much of the daily practice your openings take and which lines come back first | Contract, 6(1)(b) | 24 months after the game was played, disconnect, or erasure |
| Your opponents' moves, ratings and clock times in those games; for each opponent only a keyed code: a hash of their lichess id under a secret key only the server holds, never sent to a phone (never their name or id) | Analyse your games; find an opponent's games if they ask | Legitimate interests, 6(1)(f): see Opponents' data | As your games; also on the opponent's request |
| Import progress and connect attempts | Run the import safely | Contract, 6(1)(b) | Connect attempts after 10 minutes; the rest at disconnect or erasure |
| Monthly practice counts, linked to your account: for each month of your games, how many slips you fixed, played wrong again, and met in practice (numbers only) | Check that practice from your games helps | Legitimate interests, 6(1)(f); switch it off in Settings | Switching "Share monthly practice counts" off, disconnect or erasure; only the last 13 months are kept |
| Markers of deleted games: game id and date | Remove a deleted game from your devices | Contract, 6(1)(b) | After 90 days |
| Shared games: the same fields as your imported games, plus when you shared them and a reference code that links the share to our logs (no game id is logged) | Look at a game you share right away | Contract, 6(1)(b) | As your games |
| Your share counts per day: how many games you shared and how many times we asked lichess (numbers only) | The limit of 20 shares a day | Contract, 6(1)(b) | After 2 days; erasure |
| Opponents' deletion requests: a keyed code, the scope, a one-time code | Honour the request on every later import | Legal obligation, 6(1)(c) | Opt-outs are kept; one-time codes after 7 days |
On your phone
Kept in your browser's storage, on your device only. The names in brackets are the storage keys, for anyone who wants to check; "…" stands for the account's pseudonymous code.
| Data | Why | Deleted when |
|---|---|---|
Your practice database (events, sync state, your lichess puzzle rating, a copy of your analysed games without the opponents' keyed codes, usage records waiting to be sent, your coordinate sprints: the colour, the squares found and the wrong taps of each 30-second sprint, and the coordinates goal you set; your course record: for each course position you finish, its unit, the result and the day, with how it was asked and the pack's version, and the course's units you opened; kept on this phone only) (cot-u-…) | Practise offline; show your games report | Sign-out, switching account, or erasure; a game deleted on the server leaves at the next download; disconnecting lichess removes all games and the puzzle rating |
The signed-in account's code and email address (cot.activeUser) | Open your practice without a connection | Sign-out or erasure |
A small backup of practice when the phone is low on space (cot.journal.…) | Keep practice that couldn't be saved yet | Sign-out or erasure |
Your rating-band choice, whether "How this works" still needs showing, and which colour the Lines screen shows (cot.band.…, cot.onboarding.…, cot.linesColour.…) | Start the app the way you left it | Sign-out or erasure |
The screen you were on when you last left the app, such as Your games or the lichess game you were looking at (cot.resume.…) | Open the app where you left it when you come back within 30 minutes | Sign-out or erasure; otherwise it is replaced by the next screen you open |
Whether the service has practice from your games and its themes switched on, as last seen (cot.gamePractice.…, cot.gameThemes.…) | Honour those switches when the app starts offline | Sign-out or erasure |
The monthly practice counts last sent and the day they were sent, or that sharing them is off (cot.outcomes.…; numbers only) | Send the counts at most once a day, and only when they changed | Sign-out or erasure |
The id of a lichess game you shared before you could look at it (cot.pendingShare; the game id only, never the shared text) | Show you the game after signing in or connecting lichess | When you look at it or choose Not now, at sign-out, or when another account signs in; once 30 minutes have passed, the next time the app opens |
The token of a sign-out still waiting to reach the server (cot.pendingRevoke) | Finish signing you out on the server | Once the server confirms, or at the next sign-in |
The level you picked on our public page and, if an ad or a shared position brought you, its campaign code, with its source and ad code (cot.arrival, this tab's session storage) | Start you at that level; count which ads and shared positions bring players who stay | At your first start, or when the tab closes |
Your cookie choices, with their date and version (cookie __Host-cot_consent) | Remember them on the public page | After 6 months, or when you change them; it stays after sign-out |
A new account's sign-in, for a moment (cookie __Host-cot_pending) | Finish signing up before your account opens in this browser | When sign-in finishes, or after 2 minutes |
Your "Email me when today's practice is ready" tick and your phone's time zone, for a moment (cookie __Host-cot_remind) | Bring that choice to our server when Google's sign-in leaves the page | When sign-in finishes, when you untick it, or after 10 minutes |
Error-screen counts waiting to be sent; which openings are downloaded, and the openings themselves (cot.errorReports, cot.packs, the cot-packs-v1 cache; no account data) | Report problems; practise offline | After sending; openings when replaced by a newer version |