What we do if personal data is lost, exposed or changed without permission. Last updated 5 October 2026 (version 1.1).
A breach is any security incident that destroys, loses, changes or exposes personal data, or lets someone access it without permission. Examples: a leaked session or lichess token, a misconfigured storage bucket, a bug that shows one account's data to another, a stolen administrator credential.
Who
The operator (Johannes Rummel) handles every breach and keeps the record. Contact: johannesrummel@gmail.com.
Steps
1. Contain, at once
Stop the leak:
- pause the affected service or queue (runbook "Kill switch"; shared games run on their own service
analyzer-shareand queueanalysis-share, runbook "Share lane"); - revoke sessions (
revoke-sessions); - disable a compromised key version (Cloud KMS) or credential;
- roll back a bad release.
2. Assess, the same day
Establish what data and whose (how many accounts, which fields), since when, whether it was read or copied, and how likely and how serious the harm to the people affected is. Use the logs (30 days) and the administrator audit logs.
3. Notify the authority
Do this when the breach is likely to put people's rights at risk:
- as soon as possible, and within 72 hours of noticing it, tell the Swiss FDPIC where the risk is high (FADP Art. 24), and the competent EU/EEA authority where people in the EU or EEA are affected (GDPR Art. 33);
- say what happened, the likely consequences, and what we did or will do;
- if not everything is known within 72 hours, notify what is known and add the rest later.
4. Tell the people affected
Do this when it is needed for their protection, or when the risk to them is high (GDPR Art. 34), and whenever the FDPIC asks. Use plain words: what happened, what it means for them, what we did, and what they can do (for example sign out everywhere, or revoke the app's access in their lichess settings).
5. Fix and learn
Repair the cause, add a test or a check that would have caught it, and update the runbook.
Record
Every breach goes in the breach log: date found, what happened, data and people affected, the assessment, whether and when the authorities and people were told (and why not, if not), and what was fixed. Breaches that didn't need reporting are logged too.
Specific playbooks
- Leaked lichess tokens. Disable the KMS key version, mark links for reconnection, and tell players to revoke the app at lichess.org/account/oauth/token (runbook "Lichess link").
- Another account's data shown. Stop the service, find the code path, and check the request logs for which accounts saw what (runbook "Find one user's lines").
- Restored backup. After a point-in-time restore, re-apply erasures made since the restore point (runbook "Firestore point-in-time restore").