Loading…
Loading…
Last updated August 22, 2026
We'd rather explain how this actually works than post a generic “we take security seriously” paragraph. Here's the real picture.
Every admin login requires a password and a 6-digit code emailed to the account holder — there's no bypass, including in our own development environment. Login attempts and OTP verification are both rate-limited with a lockout after repeated failures, and a code expires after 5 minutes.
A session is a random, high-entropy token stored in an httpOnly cookie — it can't be read by JavaScript and carries no data itself. The actual session (who you are, what role you have) lives server-side; a stolen cookie is useless without also compromising the server. Logging out immediately invalidates the session server-side, not just on your device.
Editor and Super Admin permissions are checked on every request to an admin route or API endpoint before it does anything — hiding a button in the interface is never the only thing standing between a role and an action it shouldn't be able to take.
Live scores come from a third-party provider, but your browser never calls that provider directly — only our own server does, on a fixed interval, writing normalized results into a cache that public pages read from. That keeps upstream API credentials off the client entirely and means a provider outage degrades to “no live score,” not a broken page.
Admin passwords are hashed (bcrypt) before storage — we don't store, log, or have any way to recover your actual password.
If you find a security issue, we'd genuinely like to know before anyone else does. Email [email protected] with what you found and how to reproduce it. Please don't publicly disclose an issue before we've had a reasonable chance to fix it, and please don't access or modify data beyond what's needed to demonstrate the issue. We won't pursue action against good-faith research reported this way.