How we protect your account and data
- Encrypted connections. This website, the game, the account server and the game server are served only over HTTPS and secure WebSockets (TLS). Certificates are issued and renewed automatically.
- Passwords are never stored. We keep only a salted scrypt hash of your password, which can’t be turned back into the password.
- Log-in protection. Sign-up and log-in attempts are rate-limited, and repeated failed log-ins for an email address lock it out for a while. A failed log-in gives the same answer whether or not the email address has an account.
- Signed sessions. Staying logged in uses a cryptographically signed token that expires after 30 days.
- A server-authoritative game. Matches are simulated on our server, not on players’ computers. Joining a match needs a signed, single-use ticket, and match results are accepted only when signed by the game server. That is our main defence against cheating and forged results.
- Limits on abuse. Request sizes, connection counts and message rates are capped per connection and per address.
- A small attack surface. The servers sit behind a firewall that allows only web traffic and administrative access, and each service runs in its own container.
- No payment data. We don’t take payments, so we hold no card or bank details. Donations are handled entirely by Venmo.
- Very little personal data. We don’t ask for your real name, address or phone number. The less we hold, the less there is to lose. See the Privacy Policy.
- No third-party code on this site. This website loads no third-party scripts, fonts, trackers or embeds, and sends a strict Content-Security-Policy.
- Backups. The player database is backed up every night.
SpeedBall Legends is a small, independent project in open beta. We take security seriously, but no online service is perfectly secure and we don’t claim to be.
What you can do
- Use a password you don’t use anywhere else. A password manager makes this easy.
- Never share your password. Nobody from SpeedBall Legends will ever ask for it, by email, in chat or anywhere else.
- Only log in at play.speedballlegends.com. Check the address bar.
- Don’t install “trainers”, “mods” or “free unlock” tools for the game. There are no official ones. They are how accounts and computers get stolen, and using them is cheating.
- Log out on shared computers.
- If you think someone else has been in your account, email info@speedballlegends.com from the address on the account.
Reporting a vulnerability
If you’ve found a security problem, we want to hear about it before anyone else does.
- Email info@speedballlegends.com with the subject “Security report”.
- Tell us what you found, where (address, endpoint or game feature), how to reproduce it step by step, and what you think the impact is. A proof of concept helps.
- Please don’t include other people’s personal data in the report.
- Tell us if and how you’d like to be credited.
What to expect from us:
- an acknowledgement within 5 business days;
- an honest assessment, and updates as we work on a fix;
- credit on this page once it’s fixed, if you want it.
We don’t run a paid bug bounty. This is a free game made by one developer. You will have our thanks, and credit if you’d like it.
Our machine-readable contact details are at /.well-known/security.txt.
What’s in scope
| In scope | Out of scope |
|---|---|
| speedballlegends.com play.speedballlegends.com api.speedballlegends.com game.speedballlegends.com | Our hosting provider’s own systems, Venmo, and any other third-party service. Other players’ accounts, devices and networks. |
We’re especially interested in: account takeover, authentication or session flaws, access to other players’ data, forging match results or tickets, remote code execution, injection, cross-site scripting, and ways to crash or take over a match that affect other players.
Generally not eligible: reports that only show a missing best-practice header with no demonstrated impact, automated scanner output without a working example, rate-limit or volume testing, social engineering, physical attacks, self-XSS, and problems that need a rooted or malware-infected device.
In-game cheats and exploits that don’t involve a security flaw (for example, a spot on a field where you can’t be hit) are bugs: please send them through the Contact page.
Ground rules for testing
- Test only against your own account. Don’t access, change or delete anyone else’s data. If you come across other people’s data, stop and tell us.
- Don’t degrade the service for players: no denial-of-service, flooding, spam or load testing.
- Don’t use a vulnerability to cheat in matches with real players, or to affect ranks or tournaments.
- Don’t use social engineering or phishing against us, our providers or players.
- Give us reasonable time to fix the problem before telling anyone else. We ask for 90 days, and we’ll tell you if we need longer and why.
- Follow the law where you are.
Our commitment to you
If you make a good-faith effort to follow this policy, we will treat your research as authorised. We won’t take legal action against you or ask law enforcement to investigate you for it, and we won’t ban your account for testing done within these rules. If someone else brings a claim over research you carried out in line with this policy, we’ll make it known that you acted with our authorisation.
This commitment covers only our own systems listed above. We can’t authorise testing of systems that belong to anyone else.
If something goes wrong
If we learn of a security incident that affects your personal information, we will fix it, tell the people affected without undue delay with what happened and what to do, and notify regulators where the law requires.
Version 2026-11-13 // Questions: info@speedballlegends.com
