Privacy
Version alpha1-1. What Botlash collects during Alpha 1, what stays on your PC, who sees what in a squad, and how to export or delete your data.
Who runs Botlash and age limit
Botlash and Alpha 1 are operated by the Botlash team. Privacy questions, export help and deletion requests go to hello@botlash.net.
Alpha 1 is only for players 16 or over. Botlash does not knowingly collect personal data from anyone under 16; if an account belongs to someone under 16, write to hello@botlash.net and we delete it.
Discord sign-in: what we keep and what stays on your PC
When you sign in with Discord, Botlash keeps your Discord user ID and name (along with your Discord account's age read from that ID, whether you are in the Botlash Discord server, and an encrypted Discord token used to check server membership), never your password, your email address or your friend list.
Discord's consent screen lists broader permissions because Discord's Social SDK shows your friends and runs squad voice on your own PC; Botlash's servers never receive or store your friend list, your direct messages or your voice audio.
Your account, cookies and local storage
In its platform database, Botlash stores your player ID and chosen screen name, your access request and grant, the versions of the rules, the terms and this privacy text you accepted and when, keyed hashes of friend codes and who invited whom, hashed sign-in session tokens (at most five active sessions, with last use rounded to the hour), chat blocks and moderation or bug reports you file.
alpha1.botlash.net runs no ad pixels, analytics scripts or third-party trackers. Its only
cookie (__Secure-botlash) keeps you signed in; friend-code links hold the code in your browser
tab's sessionStorage only until sign-in finishes. On Windows, the launcher stores your session
in Windows Credential Manager for your user account, and your game settings stay in your local Windows
profile.
Squad connections, IP addresses, chat and voice
Matches are hosted by one squad member's PC. By default, Connect directly to squad members is on in Settings: the host's game and each direct peer's game connect directly over UDP and see each other's IP address for that match, while two non-host peers never connect to each other. Turn Connect directly to squad members off in Settings to keep your traffic on Botlash's relay so no other player sees your IP address (when the host turns it off, every guest in that lobby uses the relay too). Botlash's web edge and relay see IP addresses in memory to route traffic, introduce peers and enforce rate limits, and do not store them.
Nothing in Botlash records voice. In-game lobby chat keeps at most the last fifty short lines in memory while the lobby is open and discards them when it closes, unless someone files a player report that attaches those fifty lines for staff moderation. If a squad posts a public lobby thread in the Discord server, that thread follows the server's moderation and is deleted a week after the lobby closes.
Telemetry and how long it stays
- Always sent while signed in: crash reports (a minidump when the game or launcher crashes or panics, with build identity, session and run IDs and the last two hundred log lines) and match run results (who played, when, the outcome and waves cleared, plus the host's run summary of hero classes, cards, wave times and where the squad fell; offline solo runs queue up to twenty runs until your next sign-in).
- Behind one telemetry switch in Settings (on by default): per-match session samples (frame-time percentiles, hardware tier, whether each link used direct UDP or the relay, round-trip time, packet loss and relayed bytes) and a one-per-build hardware survey (processor, core count, memory, graphics adapter and VRAM, Windows build, display resolution and refresh rate). Switch telemetry off in Settings and the game stops sending both.
- Retention: all telemetry (crash dumps and signatures, session samples, the hardware survey and each run's analytics detail) is kept until Alpha 1 ends and removed then. Basic run history (who, when, outcome and waves cleared) is not telemetry: it stays with your account and carries into the beta unless you delete your account.
Where data lives, JSON export and 7-day deletion
Botlash's platform, crash store and relays run on Amazon Web Services in the United States
(us-east-1, fronted by CloudFront), Discord handles sign-in and voice under Discord's own
privacy policy, and Cloudflare routes inbound email sent to @botlash.net to the operator's
mailbox. Botlash never sells your data.
Export: from your account page, you can request a machine-readable JSON export of everything keyed to your player account.
Deletion: from your account page (or by emailing hello@botlash.net), you can request account deletion. A deletion request waits seven days (a 7-day cancellation window) in case it was a mistake: signing back in during those seven days cancels it. After seven days, Botlash unlinks your identities and revokes stored Discord tokens, deletes your sessions and telemetry, removes the link between your player ID and past runs or reports, and empties your player row. If an account was banned, a keyed hash of the banned external ID stays solely so a ban cannot be bypassed with a fresh account, and encrypted backups age out within thirty days.