How long each kind of data is kept, what deletes it, and whether that deletion is automatic yet. Last updated 19 November 2026 (version 1.6).
| Data | Kept for | Deleted by | Status |
|---|---|---|---|
| Your account and practice | As long as the account exists | Your erasure request (done within 30 days) | In place (operator tool erase-user) |
| An account not used for 36 months | 36 months after its last use | An inactivity sweep | Not built yet. The first account could reach 36 months in 2029; the sweep must exist before then (runbook item) |
| Sign-in sessions | 60 days after you last opened the app | Automatic expiry (Firestore TTL); also sign-out and erasure | In place |
| Your practice reminder choice (only if you ask for reminders) | As long as the account exists; switched off, it stays as "off" | Erasure, with the account | In place |
The sign-up's reminder tick (cookie __Host-cot_remind) | At most 10 minutes | The sign-in's answer; unticking; the cookie expires | In place |
| Scaleway's delivery record of each reminder email | Under Scaleway's terms, for as long as its service keeps such records (the period goes here before reminders are switched on; runbook "Email reminders") | Scaleway, automatically; an account erasure doesn't shorten it | In place once reminders are switched on |
| Server logs (IP address, browser, pseudonymous code) | 30 days | Automatic (log bucket retention) | In place |
| IP addresses for the request limits (sign-in, error reports, the public page's counts, the pictures of shared positions, the reminder emails' stop page) | 1 minute | Never written; held in memory only | In place |
| Cost counters | 35 days | Automatic expiry (Firestore TTL) | In place |
| Administrator audit logs | 400 days | Google, automatically | In place |
| Erasure records | Kept | — | In place; holds a hash, a date and a ticket reference only |
| Lichess link and token | Until you disconnect or are erased | Disconnect; erasure | In place |
| Your games and their analysis | 24 months after the game was played | A daily retention job; disconnect; erasure | In place |
| The copy of your games on your phone | As on the server | The next download removes games deleted on the server; disconnecting lichess, signing out and erasure remove them all | In place |
| Monthly practice counts | Until you switch them off, disconnect lichess or are erased; only the last 13 months | Switching "Share monthly practice counts" off; disconnect; erasure. Each update from your phone replaces them and drops months older than 13 | In place |
| Usage records ("Help improve Chanki") | 13 months after they reach us | Automatic expiry (Firestore TTL); switching "Help improve Chanki" off; erasure | In place |
| Counts by ad campaign | 13 months | Automatic expiry (Firestore TTL) | In place once gcp-bootstrap.sh has run |
| Your cookie choices | 6 months | The cookie expires; you change it | In place |
| Usage records waiting on your phone | Until they are sent | Sending them; switching "Help improve Chanki" off; signing out; erasure. At most 40 batches wait; the oldest goes first | In place |
| Drill reports | With your practice | Erasure, as your practice | In place |
| The operator's working copy of drill reports (no account attached; each names its lichess game, so it is still personal data) | At most 30 days | The operator deletes it after checking the reports, and any copy older than an erasure | In place (manual; runbook "Drill reports") |
| Lichess connect attempts | 10 minutes | Automatic expiry; disconnect; erasure | In place |
| Markers of deleted games | 90 days | Automatic expiry | In place |
| Your share counts per day | 2 days | Automatic expiry (Firestore TTL); erasure | In place |
| Your answers to our questions by email (in our Gmail mailbox) | As long as they help us improve the app | The operator deletes them; erasure | In place (manual; runbook "Asking players how the app works") |
| A "stop" to our questions by email | As long as the account exists | Erasure | In place (manual) |
| Opponents' deletion requests | Kept, so no re-import brings the data back | — | In place; one-time verification codes expire after 7 days |
| Data on your phone | Until you sign out, switch account, or your account is erased | The app | In place; practice from before an erasure is never accepted back on the server |
Erasure and old phones. Erasure ends every sign-in, so your phones show "Sign in again to sync" but keep their copy of your practice until someone acts on them. For 8 days after an erasure the account cannot sign in again. Signing in on a phone during that time removes that phone's copy. After the 8 days, signing in with the same Google account starts a new, empty account. A phone that still holds the old practice can't send it to that new account: the server refuses practice from before the erasure. The old copy stays on that phone until you sign out there or clear the app's data (see Data requests).