Raid Team Stats

Security & your data

Raid Team Stats is built to keep a guild's data private and protected. Below, in broad terms, are the safeguards the software provides. It is self-hosted: each instance is set up and run independently by whoever operates it, on infrastructure they control — so this page describes what the software itself does, not any particular operator's systems.

Encryption in transit
The companion uploader refuses to send data over anything but an encrypted (HTTPS) connection, and the included production configuration serves the site over HTTPS/TLS with HSTS.
Encryption at rest
Sensitive fields are encrypted in the database by the application itself using authenticated AES-256-GCM: account email addresses, third-party (OAuth) access tokens, two-factor-authentication secrets, display names and avatars, and recruitment-form answers (numeric ratings and scores are additionally kept as plain numbers so reviewers can sort by them). Each value gets a fresh random IV and an authentication tag, so it cannot be read or altered without the key. (Email uses a separate keyed blind index so you can still sign in without the address ever being stored in the clear.)
Passwords & tokens
Account passwords are never stored — only a one-way Argon2id hash (a slow, memory-hard algorithm) is kept, so the original cannot be recovered. Companion upload tokens are stored only as SHA-256 hashes and rotate automatically on each sync, so a leaked token stops working after the next upload.
Access & sessions
Sign-in supports Battle.net (OAuth) and email + password, with optional time-based one-time-password (TOTP) two-factor authentication. Read-only share links are signed with HMAC-SHA256 and can be switched off at any time, which immediately re-locks every outstanding link. Guild and team data is private by default and checked against your role on every request.
Hardening & logging
The app enforces a strict, nonce-based Content-Security-Policy, rate-limits sign-in and other sensitive endpoints, and keeps an audit log of privileged actions that is only ever appended to — entries are never altered after the fact, though old ones may age out under a configurable retention policy. In the shipped setup the application runs as a non-root container with Linux capabilities dropped and privilege-escalation disabled. Personal data and secrets — including email addresses and tokens — are stripped from the application's logs.
What's collected — and what isn't
To power your dashboards the app stores World of Warcraft character, guild, and raid data, plus the email address used to sign in — all on the infrastructure of whoever operates this instance, not the project's. Your email is used only as your login identifier and for any notifications you turn on; it is encrypted at rest, sent over encrypted connections, kept out of the application's logs, and access-controlled. The software ships with no advertising, third-party analytics, or data-broker integrations, and so has no means to sell, rent, or share your data.

Responsible disclosure

Found a security vulnerability? Please report it privately through the project's GitHub repository (a private security advisory) rather than opening a public issue, so it can be fixed before it is widely known. Other bugs are welcome as a regular GitHub issue.