Privacy

What we store

• Discord identifiers — your Discord user ID, username and avatar when you log in, and the IDs, names and icons of servers, channels and roles the bot is configured for.
• Guild settings — the channels, roles, toggles and thresholds you choose in the dashboard or with /setup.
• Warcon API key — stored encrypted at rest. It is never shown back to anyone; the dashboard only displays a short hint.
• Game data seen through the Warcon API — player SteamIDs and names, match results and per-player match stats (kills, deaths, cash), seeding time and whitelist entries.
• Action log — who ran which action (kick, ban, broadcast, and so on), on whom, when, and whether it succeeded.
• Reports — the reported player's SteamID and name, the category, description and evidence (links, and uploaded images or clips, which the bot stores so they don't expire), the reporter's Discord ID and name, and the admin decision.
• Suspicious-performance alerts — statistical flags (kill rate, K/D) for a player in a match, and the admin decision.
• Ban appeals — the SteamID you appeal for, your Discord ID and name, the text of your appeal, and the admin decision with its note.
• Notification subscriptions — your Discord ID and what you asked to follow with /notify (a player count on a server, or a specific player), so the bot can DM you. Remove them at any time with /notify clear.
• Linked accounts — the connection between a Discord account and a SteamID when a member links them, used for automatic roles, the booster whitelist and appeals.

Automatic roles

If a server owner sets up automatic roles, the bot reads that community's own stats for linked members — seeding time, matches played and kills — to decide who gets a role. Nothing is shared with other communities, and members who never link an account are never processed.

Public server browser

A community only appears on the public server browser when someone who manages its Discord puts it there: either by turning the listing on in the bot's dashboard, or by adding it on the listing page without the bot. To check that, the listing page reads which Discord servers you manage from your login and looks up the invite you paste. Anyone can then see the community name, icon, member count, description, region, language, style tags, Discord invite and, for communities running the bot, the live stats of its servers (name, player count, map, mode, seeding status, match clock). We store the Discord ID of the person who made a listing, so only they can change it; it is never shown. No player names or personal data are published there. Listings whose invite stops working are taken off the page automatically.

Network bans (shared between communities)

When an admin bans a player from a report and the community shares bans with the network, other communities using the bot receive the player's SteamID and name, the ban reason and category, the evidence, and the name of the banning community. The reporter's identity is never shared. Each community decides for itself whether to ban. If the ban is revoked, the other communities are told.

Public leaderboards

There are two kinds. A community's own public board is off until its admins turn it on, and it carries that community's name. The network leaderboard at wardogsbot.com/leaderboard is one ranking of everyone who plays on a server running the bot, and it counts every community. Both show the player's in-game name and their match statistics: kills, deaths, matches played, seeding time and in-game money earned. Players are matched across communities on their SteamID, so someone who plays on several of these servers appears once with their totals. The SteamID itself is not printed on either page, and the network page names only those communities that publish a board of their own. Permanently banned players are left off both.

Player profiles

Every player seen on a server running the bot has a profile page at wardogsbot.com/player/ followed by their SteamID64. It shows their in-game name, the same statistics as the leaderboards added up across the network, their most played maps and factions, their last ten matches and badges earned from those numbers. Communities are named only where they publish a board of their own. A player who proves the Steam account is theirs (by signing in with Steam here or in a Discord that runs the bot) can hide the page, and may choose to show their Discord name and picture and a short line about themselves; nothing of that is shown unless they switch it on. Hiding the page does not remove the player from community leaderboards.

Steam data

For players seen on a connected server, the bot asks the Steam Web API for what their public Steam profile shows: Steam name and picture, when the account was created, whether the profile is private, VAC, game and community bans, and hours played in WARDOGS where the profile shows them. It is kept for at most a day (bans for six hours) and refreshed from Steam after that. Community staff see it in player files as an advisory hint; the public player profile shows only the Steam picture and hours played, never bans.

Direct RCON connections

A community can connect its game servers without Warcon. For each server we then store its public address and RCON password, the password encrypted at rest. It is only used to send the requests the community triggers or switches on (status, moderation, map control) to that server, is never shown back, and is deleted when the server is disconnected.

WarDogs agent, API keys and webhooks

A community can run the WarDogs agent on its own server. We then store the agent's name, a hash of its token, the machine name and version it reports, and when it was last seen. The agent keeps the RCON password on that machine; we never receive it. The answers of the game server pass through us like on any other connection.

For API keys we store a hash of the key, its name, scopes, who made it and how often it was used. Actions made with a key are logged like any other. For webhooks we store the URL, the chosen events and the signing secret (encrypted), and send event data (staff actions with the staff member's Discord ID and name, match results with player names and SteamIDs, server up and down) to that URL. The community decides where that goes and is responsible for it.

A key with the links scope reads which Discord account linked which SteamID in that community's own Discord, for the community's own rosters and league tools. Links made in other communities are never included.

A team in the WarDogs League (WDL) can store its WDL team key, encrypted. The bot uses it only to read that team's member list (Discord IDs and names) from wardogsleague.net, keeps it in memory for a few minutes and shows in event rosters who is on the team. Nothing is sent to the league.

Status bots

A community can add bots of its own that show its servers in their Discord status. For each one we store the bot token encrypted at rest, the bot's name and picture, and the status text the community chose. The token is only used to sign that bot in and set its status; it is never shown back and is deleted when the bot is removed in the dashboard. The status bot reads no messages and no member list.

Payments (community shops and donations)

Payments are processed by Stripe. A community shop takes payments on the community's own Stripe account; a donation to the bot on ours. Card and bank details go straight to Stripe and never reach us. For each purchase we store the buyer's Discord ID and name, the linked SteamID when a whitelist slot was bought, the product, amount, currency, our fee, its status (paid, active, refunded …), until when it runs, and Stripe's reference numbers, so the slot and role can be handed out, renewed and taken back on a refund. The community sees its own sales in its dashboard. For donations to the bot we store the amount and, if given, a name and message, shown on the supporter wall only when you ticked it. Stripe's own privacy policy applies to what Stripe processes: stripe.com/privacy.

What we don't store

Your RCON password. The bot only talks to Warcon through the scoped API key you create and can revoke at any time.

How it is used

Data is used only to provide the features: status panels, moderation, recaps, seed calls, leaderboards, the whitelist, appeals, automation and the action log. It is not sold or shared with advertisers. Publishing a leaderboards are where player names and statistics become visible outside a community, as described in 1.6.

Session cookie

Logging in sets a single session cookie that keeps you signed in to the dashboard. There are no tracking or advertising cookies.

Visitor counting

The website counts its own visitors, without cookies and without any third-party service. Each page view sends the page address, the site you came from (its domain only) and, where our host provides it, your country. From your IP address and browser we compute a one-way hash that changes every day, so a visitor counts once per day and cannot be recognised on the next day; the IP address itself is not stored. We also note whether the page was opened on a phone or a computer. The counts are kept for at most 400 days and are only used to see how the site is used and to tell advertisers how many people see the server list (legitimate interest).

The Sponsored spots on the server list are counted the same way: an ad counts as seen once per visitor and hour when at least half of it was on screen for a second.

Hall of Shame

The public Hall of Shame lists players banned across the network for cheating: their in-game name, SteamID64, what they were banned for, the date and the video or picture evidence. An entry is only published after the WarDogs Server Commands team has checked the evidence; nothing appears there automatically. This protects the WARDOGS communities and their players from repeat cheaters (legitimate interest). Anyone listed can ask for a review; entries that do not hold up, and bans that are revoked, are taken down.

Retention & deletion

Disconnecting Warcon in the dashboard deletes the stored API key. Removing the bot from your server stops all data collection for it. To have your server's data or your personal data deleted, get in touch.

Contact

Contact: via the support Discord.