What this server keeps about you, why, and how to get it removed. Short version: your Discord name and avatar for signing in, your tag and results, and the replays you upload. No email address, no tracking, nothing sold.
Who runs this
Ask the organisers of this server.
Signing in with Discord
Signing in goes through an identity service (Zitadel) that this server uses, and Discord. We ask Discord for one permission only, identify: your Discord id, username, display name and avatar. We do not ask for your email address, your servers or your friends, and cannot see them.
The identity service stores an account for you: its own user id, a username like discord-123456, your Discord display name, the link to your Discord login, and a made-up email address of the form <your Discord id>@users.invalid that receives nothing. It also keeps your sessions, with the browser (user agent) and IP address you signed in from, and a history of what happened to the account.
What this server stores
- Your account: an account id, your Discord id, username, display name and avatar (a picture id; the picture itself stays at Discord and is never loaded on public pages), when you first and last signed in, and your settings (pings and sharing analysis, both off until you turn them on).
- Your tag, and any connect code you add.
- The public keys of game clients you linked. These are public keys, not secrets.
- Your event entries, sets, games and results. These are shown publicly, with your tag.
- The replays you upload. They are kept as the event’s record, with no automatic expiry. A replay can contain your in-game name or connect code.
- A log of what organisers do (who, what, when), including the organiser’s Discord display name.
- The server’s own log of events (such as a player registering, with their tag, or a result being counted) and rejected requests. It holds short key prefixes, but no IP addresses and no request bodies.
This server does not keep IP addresses: it holds them in memory only, to limit how fast one client can call it, and writes them to neither its database nor its log. The components around it may log them: the web server in front of this one (an ordinary access log: time, address, page asked for), the sign-in proxy and the identity service. How long those logs are kept is up to whoever runs the server.
Browsing the public pages sets no cookies, and they load nothing from other sites. Signing in sets a session cookie on this site (the sign-in proxy’s, for about 7 days) and login cookies on the identity service’s own address. They only keep you signed in; there are no tracking or advertising cookies. Signing out, or waiting for them to expire, removes them.
Getting your data removed
Delete your account in the identity service’s own account settings, or ask the organisers. Either way this server anonymises your profile: your tag is replaced, your linked keys and Discord details are removed, and your account can never be re-created. Your results are not deleted, because other players’ brackets depend on them; they stay, but no longer name you. Entries in the organiser log naming you are anonymised too.
Replays are different: anonymising does not delete or edit them, so a replay can still hold your in-game name or connect code. There is no tool for deleting replays; if you want yours removed, ask the organisers (see “Who runs this”), who can remove records by hand.
Backups
The databases (this server’s, and the identity service’s if this server has one) are copied nightly to the same machine, and the last 7 copies are kept. There is no off-site copy. A removed account can therefore still appear in a backup for up to 7 days.
Questions
Ask the organisers of this server.