Chanki

Retention

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).

DataKept forDeleted byStatus
Your account and practiceAs long as the account existsYour erasure request (done within 30 days)In place (operator tool erase-user)
An account not used for 36 months36 months after its last useAn inactivity sweepNot built yet. The first account could reach 36 months in 2029; the sweep must exist before then (runbook item)
Sign-in sessions60 days after you last opened the appAutomatic expiry (Firestore TTL); also sign-out and erasureIn 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 accountIn place
The sign-up's reminder tick (cookie __Host-cot_remind)At most 10 minutesThe sign-in's answer; unticking; the cookie expiresIn place
Scaleway's delivery record of each reminder emailUnder 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 itIn place once reminders are switched on
Server logs (IP address, browser, pseudonymous code)30 daysAutomatic (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 minuteNever written; held in memory onlyIn place
Cost counters35 daysAutomatic expiry (Firestore TTL)In place
Administrator audit logs400 daysGoogle, automaticallyIn place
Erasure recordsKept—In place; holds a hash, a date and a ticket reference only
Lichess link and tokenUntil you disconnect or are erasedDisconnect; erasureIn place
Your games and their analysis24 months after the game was playedA daily retention job; disconnect; erasureIn place
The copy of your games on your phoneAs on the serverThe next download removes games deleted on the server; disconnecting lichess, signing out and erasure remove them allIn place
Monthly practice countsUntil you switch them off, disconnect lichess or are erased; only the last 13 monthsSwitching "Share monthly practice counts" off; disconnect; erasure. Each update from your phone replaces them and drops months older than 13In place
Usage records ("Help improve Chanki")13 months after they reach usAutomatic expiry (Firestore TTL); switching "Help improve Chanki" off; erasureIn place
Counts by ad campaign13 monthsAutomatic expiry (Firestore TTL)In place once gcp-bootstrap.sh has run
Your cookie choices6 monthsThe cookie expires; you change itIn place
Usage records waiting on your phoneUntil they are sentSending them; switching "Help improve Chanki" off; signing out; erasure. At most 40 batches wait; the oldest goes firstIn place
Drill reportsWith your practiceErasure, as your practiceIn 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 daysThe operator deletes it after checking the reports, and any copy older than an erasureIn place (manual; runbook "Drill reports")
Lichess connect attempts10 minutesAutomatic expiry; disconnect; erasureIn place
Markers of deleted games90 daysAutomatic expiryIn place
Your share counts per day2 daysAutomatic expiry (Firestore TTL); erasureIn place
Your answers to our questions by email (in our Gmail mailbox)As long as they help us improve the appThe operator deletes them; erasureIn place (manual; runbook "Asking players how the app works")
A "stop" to our questions by emailAs long as the account existsErasureIn place (manual)
Opponents' deletion requestsKept, so no re-import brings the data back—In place; one-time verification codes expire after 7 days
Data on your phoneUntil you sign out, switch account, or your account is erasedThe appIn 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).