Privacy

Wardogs Zone runs its own visit counter on its own server. It works without cookies. When you open a page it records that the page got a visit: the page address, the country the visit came from, the browser family and the site that linked here. Your IP address helps resolve the country and is not kept with the counts.

The tools also count anonymous usage events, things like a weapon being picked in the damage calculator or a squad board going live. Events carry item names and mode flags, never free text you typed. The counter has no advertising ID and does no cross-site tracking, and its numbers never leave the server.

Your work lives in your browser's local storage: saved loadouts, cargo manifests, artillery boards, progression checklists, interface preferences and the acknowledgment of the privacy notice. It stays on your machine. The site receives a piece of it only when you publish a build or take a board live, and both of those are deliberate button presses. Clear your browser data and the local copy is gone.

The loadout hub, the base boards and the prefab store are the parts of the site with accounts, and there are two ways in: Discord and Steam. One account can have both connected.

Signing in with Discord asks for the identify scope, which covers your Discord ID, username, display name and avatar. That is the whole request. It cannot read your email, your server list, your messages or anything else on your Discord account.

Signing in with Steam hands the site your SteamID and nothing else. From that the site reads your public Steam profile: your Steam name, picture, the country you show if any, the date the account was made, and your hours in WARDOGS when your game details are public. The hours are refreshed when you sign in and when you press Refresh on your profile. Disconnecting Steam removes all of it.

Those values are stored here, along with the date you first signed in and the date you were last seen. They stay until the account is deleted. Signing out clears the cookie and leaves the account in place, so signing back in picks up where you left off. Connecting a sign-in that already has an account of its own folds that account into the one you are signed in to.

When you connect game progression, we exchange your signed Steam login with the WARDOGS backend and keep the resulting game session encrypted on our server. This is separate from signing into this website. The integration reads progression; it does not purchase items or change your loadout.

We store dated readings of your season, role levels and XP, cash, gold, purchased unlocks and collection. Optional automatic refresh reads these about every fifteen minutes. Uploaded progression files are labelled as player supplied. Your recorded role levels appear on your public profile. Cash, unlocks, collection and history are visible only to you.

Tracking begins with the first reading. Unlock dates mean the date we first observed them, and catalog prices do not establish what you paid. Disconnecting progression deletes the stored game session and all progression history. Disconnecting Steam or deleting your account also removes this data.

These are set by this site. None is ever set if you never sign in. The ad cookies are Google's, and they get their own section below.

These are required for a sign-in you asked for, which is why there is no consent banner to click through. Nothing here is used to profile you or to follow you onto other sites.

Publishing a build stores its name, your notes, the loadout itself and the time you posted it, filed under your account. Anyone can read it. Voting records which account voted which way on which build, so a vote can be changed later and still be counted once.

Publishing also writes a short-lived flood record: the time, your account and a scrambled fingerprint of your connection, kept for two hours to hold the posting limits. The address itself is never stored, and the fingerprint cannot be turned back into one.

Your profile page shows your display name, handle, avatar, join date, published builds and the score they have earned, and once Steam is connected your Steam name, the country you show and your hours in WARDOGS. It sits at /u/your-handle and is visible to anyone, signed in or not.

A live artillery board is the one thing that leaves your machine with no account involved. Going live shares the board through a relay server: gun and target positions, markers, drawings and the callsign you typed. Anyone holding the board code sees that state. That is the point of it.

Rooms exist only in the relay's memory. They close a few minutes after the last player leaves and are never written to disk. Pick a callsign you are comfortable showing to your squad.

A few pages carry one ad each, served by Google AdSense and labelled as such: the end of a guide or a Field Manual chapter, the foot of an item page, and a published build, base or prefab. The tools, the calculators, the builder and the maps carry none.

Google and the advertisers it works with may set cookies and read identifiers from your browser to pick and measure those ads, including from your visits to this and other sites. In the EU, the UK and Switzerland the Google consent dialog asks before any of that happens, and the button below opens it again so a choice can be changed. Elsewhere Google serves the ads under its own rules.

How Google uses that data is set out on its partner sites page. Personalised ads can be switched off in Google Ads Settings. An ad blocker is respected: nothing on the site works around one.

Reserved slots on our community servers are paid for through Stripe. Your card details go to Stripe and never reach this site, and Stripe handles them under its own privacy policy as the payment processor.

What the site keeps is the record beside the money: which subscription you hold, whether it is paid up, the SteamID64 it was bought for, and one row per invoice with the amount, the date and a link to Stripe's own receipt. Your name goes to Stripe with the customer record so an invoice has something on it.

Your SteamID64 is the part that has to leave the site. It is written into the server's own reserved slot list, because that is how a game server recognises you at the door, and it is removed from that list when your slot ends.

Deleting your account cancels any subscription and removes every row above. Stripe keeps its own copies of the payments, which it has to for tax and accounting reasons, and those are not ours to erase.

When you play on one of our community servers, the server reports your SteamID64, your in-game name and your scoreboard for the match: kills, deaths, the cash the match has paid you and the faction you are on. The site keeps running totals of those, and of the time you spend on each server, filed under your SteamID64, and it keeps each match you played as a row of its own: the map, the result, and what your scoreboard added up to on it, with your name as the scoreboard showed it.

The match history on this site and the match log on our Discord name players the way the in-game scoreboard did, so anybody who was in the match could have read the same names there. The lifetime totals appear beside your account only once that SteamID64 is connected to one here: on the server leaderboard, on your profile, and on the leaderboard on our Discord when Discord is connected as well. Staff can read any player's record by SteamID64, match by match, which is how a player who is reported gets looked at, and they can write notes on it for each other and record a warning against it, with who wrote each one. A warning is also whispered to you in game, the moment it is written if you are on the server and the next time you join one if not. Both stay on the SteamID64 as moderation records, the way the server's own ban list does. With Discord connected, time you spend seeding a server also pays XP on our Discord, which is recorded against your Discord account, and so does time you spend with the community clan tag on. A server you join without both accounts connected may whisper you one line in game saying where to connect them, once a day at most.

Our servers also report every kill as it happens: who killed whom, with which item, from how far, and whether it was a headshot or a melee kill. The site keeps each kill for ninety days and a daily total per weapon for as long as the record exists. Staff read them to spot play that should not be possible, such as a headshot rate far past what everyone else lands with the same weapons, or kills from further than a weapon reaches, and a flag from those checks is a reason for a person to look rather than anything that acts on its own.

Disconnecting Steam takes your record off every board straight away, and deleting your account removes the record itself, the match rows that named you included. A kill between you and another player stays on their record with your side of it blanked.

Google serves the ads, as described above. No social widgets and no third-party analytics. Fonts are served by the site itself.

Discord and Steam are the others, because they run the sign-in. Starting a sign-in sends you to the one you picked, where its own privacy policy applies. Profile pictures on the hub load straight from Discord's and Steam's image servers, so they see those requests from any visitor reading hub pages, signed in or not.

Stripe is the third, and only if you buy a reserved slot. Nothing of Stripe's loads on a page until you press the button that takes you to its own checkout.

Outbound links (Steam, the Discord) lead to their own sites with their own policies.

A build comes down from its own page, with the Delete button under it. Removing it takes its votes with it.

Deleting the whole account is on your profile page. It removes the account, every build you published and every vote you cast, and nothing about you is kept behind. It cannot be undone, and it does not touch your Discord or Steam account. Signing in again afterwards opens a fresh account.

Anything held in your browser is yours to clear at any time through your browser's own settings.

Wardogs Zone is run by the volunteers behind the community Discord. Ask there. A /ticket opens a private line to the people who run the site, and that is the place to raise anything about your data that the buttons above do not cover.