Privacy
No accounts, no ads, no tracking cookies.
What I store
- Ladders: name, description, visibility, and a hash of the admin link (never the link itself).
- Players: the display name the player or coach typed, their Lichess and chess.com usernames, and whether they verified.
- Readings: public ratings, game counts and results per day, read from Lichess and chess.com.
- Weekly post targets: the Discord webhook, Telegram chat ID or URL you enter, deleted when you turn posting off.
- Club pass: a hash of the license key and, if you add one, a passkey's public key. Your card details go to Stripe and never reach me. I keep the payment's session id and the email Stripe provides, nothing else.
- Abuse limits: a salted hash of your IP address for 2 days when you create a ladder or join one.
What stays in your browser
Admin links for ladders you run, the Club pass sign-in token, your theme and preferences, and the coach's note on a report. None of it is sent anywhere except the admin link, to prove you can manage that ladder.
What I never ask for
Passwords, email addresses of players, birthdays or school names. Players prove an account with a code in their public profile, which they can delete straight after.
Analytics
None at the moment. If I turn on Cloudflare Web Analytics, it counts page views without cookies or personal data.
Aggregates
Ratings collected for the comparison and benchmarks only appear in groups of 10 or more (comparison) and 20 or more (benchmarks).
Removal
Coaches remove players from the admin page. A player can ask their coach, or write to contact@chessclubladder.com and I'll remove them from every ladder.