Chanki

Breach response

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:

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:

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