Happy Easter from Bannerwake. Winter is here. Choose the winter climate for a snowy map. Autumn is here. New Skirmish matches and rooms open on an autumn map. The game was updated.
Privacy
Match records
Single-player matches are saved as files on the game server (commands, a timeline, pauses, how often a few controls were used, and the result) so the game can be improved from real play. Multiplayer matches are always recorded by the server.
Bannerwake (bannerwake.io) is a free real-time strategy game that runs in your browser. This notice explains what it collects, why, how long it keeps it, and what you can do about it. Last updated 4 November 2026.
What the server records
For statistics and abuse prevention, the game server records: a random player ID stored in this browser (in local storage and a first-party cookie, bw_pid), your IP address, your browser, operating system and device type, your screen and browser window size, pixel ratio, time zone and language, and the pages and matches you play (their settings, the factions played, your result and the stage you reached, in Last Stand the wave and level you reached and what you did with the cards, and how far the match guide got you, with your player name if you chose one), the address you came in on and the site that sent you there, the country your connection comes from (two letters, as Cloudflare, which carries the site’s traffic, reads it from your IP address), which version of the home page you saw when we compare two, on a phone, which way you sent the page’s link to your computer (never the link or to whom), and which invitations to sign in you saw and pressed, whether you opened the sign-in page and pressed Google or Discord, and how that sign-in ended (a new account or not, cancelled, or failed, but never your email or your Google or Discord ID). When you open What’s new it records that you opened it, what it showed, how long it stayed open and what you pressed in it, and nothing more. When you leave a page it records how long the page was open, what you pressed first (one of a few words, such as Play, the cookie banner or the top bar), how far down you scrolled and how many seconds of music played. If you leave a page before the game has started on it, the page sends one short note as it closes: its path, the site that sent you, the tags of the link you came by (such as which ad or keyword), whether the link came from an ad (never the ad’s click ID), which version of the home page it showed when we compare two, and how long the page was open. That note carries no player ID and no cookie, and its IP address is not kept. In a match it also records how smoothly the game runs on your device: frame times, in multiplayer the round trip to the game server and prediction corrections, your device’s memory and number of processor cores as your browser reports them, the name of its graphics card, and the size the game draws at. At the end of a match it records how often you used a few of its controls: control groups, a key or a click to train units and to choose a building, and the idle Laborers button. These are counts only, never which keys you pressed or when. While a match is open it also records whether it is paused and how long ago you last used the mouse, keyboard or screen (to the minute, never what you did). This is kept for 180 days. After that only daily totals remain (with the random player IDs and which of them the developer linked as one person, without IP addresses or browser details). Match records (the commands, timeline, pauses and result of a match, and in single player those counts of controls, used to improve the game) and a results entry per match (each player’s random ID, name, faction, result and match statistics, without IP addresses or browser details, for a future leaderboard) are kept until they are deleted. You can turn match records off for single player above. It is not shared or sold. The developer may watch multiplayer matches live to improve the game. An eye icon in the top bar shows when this happens.
Game servers in other regions
Besides the game server in Germany, multiplayer rooms can be on game servers in the United States and in Singapore, run for Bannerwake by bunny.net (BunnyWay d.o.o.). When the form to host a room is open, your browser asks each of them a few times for a short answer with nothing about you in it, to measure how far away they are and pick the nearest. A room on one of them sees your IP address and browser while you play there, as the server in Germany does. If you are signed in, the site gives your browser a pass that lasts two minutes and tells that server your account’s ID, name, level, roles, frame and skins, so the room shows them and the match counts for you. At the end of the match that server sends the match record and its results to the server in Germany, which keeps them as described above.
Analytics
The site uses Google Analytics through Google Tag Manager (Google Ireland Ltd.) to measure visits: the pages you open, your device and browser, your approximate location, the kind of match you start and how it ended, and when you sign in or make an account and with which provider (never your name or account). It sets the cookies _ga and _ga_*. You can block it with your browser’s cookie settings or a tracker blocker.
Sign-in with Google or Discord
An account is optional: the game plays the same without one. If you choose Sign in with Google, Google asks whether Bannerwake may see your basic profile (the openid and profile permissions), and Bannerwake receives from Google your Google account’s unique ID, your name, and the address of your profile picture. With Discord (the identify permission), Bannerwake receives your Discord user ID, username, display name, and avatar. Bannerwake never asks for, receives, or keeps your email address, password, contacts, or anything else in your Google or Discord account.
How it is used. Only to sign you in, to show you your name and your own statistics on your account page (the matches, results, factions and time played of the browsers you signed in with, from the data described above), and to keep your player name and statistics together on every device you sign in on (the browsers you sign in with count as one person in the game’s statistics). In multiplayer rooms, matches, and the weekly challenge’s board, other players see the display name you choose on your account page (it need not be unique, and you can change it). Without one they see your username, and without that your Discord display name (or, in rooms and matches, the name you chose in Play). A username is chosen once, is unique across Bannerwake accounts regardless of capital letters, and is also shown beside your name in multiplayer rooms. The name shown in a match is kept with its results. Your Discord avatar is shown beside it, to other players too. Your Google name and picture are never shown to other players: your picture only to you, at the top of the site and on your account page. The game server fetches pictures from Discord or Google itself and keeps a copy in memory for up to a day, so your browser never contacts them for it (other players see a Discord avatar by an address that does not give away your Discord ID). An account Bannerwake gives a role (Developer, Tester, or Member) shows its badge beside the player’s name, to other players too. Developers’ play is left out of the game’s statistics. For support, the Bannerwake team can open an account’s page as its player sees it (its name, sign-ins, and statistics), view only and for 30 minutes at most. Every such view is logged. It is not used for advertising, not sold, and not shared with or transferred to anyone else, unless the law requires it. The access token Google or Discord gives Bannerwake at sign-in is used once, to read the details above, and then revoked. It is never stored.
XP and levels. Signed in, the matches you finish earn your account XP. A multiplayer match’s XP is worked out by the game server from the match it ran. When a single-player match starts, the server notes its ID and when it started (and later whether it earned XP). When it ends, its record (its settings and every command given in it) is sent once to the server, which plays it through to work out the XP it earns, and is not kept for this (it is kept as a match record only if match records are on). Your XP and its history (for each change: the amount, when, and either the match’s mode, result, length, AI level, and when it was played, or the bug report it was for, or the team’s note for a change made by hand), and which of your matches earned none and why, are stored with your account and deleted with it. So are your achievements, which the server judges from the same matches: which you unlocked, when, the match that earned each and the XP it paid, and for those earned over many matches the factions you won with, the map types you finished, and your running counts towards them (boars slain, camps sacked, wins, and the like). Your level, with its rank’s badge, shows beside your name to the other players in a multiplayer room and its match. Your skins are stored with your account and deleted with it too: which you own, when, how each came (given by the team, an event code you redeemed, the weekly challenge, an event’s rewards, the Founder frame you claimed and its number of the 100) and why, which you wear, and which event codes you redeemed. The frame you wear shows round your picture to the other players in a room, and your units wear your unit skins in its match. If you delete the account, its Founder frame’s number goes to the next player who claims one.
Matches played without signing in. When you play a single-player match signed out, the server keeps what it needs so that signing in can add the match’s XP to an account: this browser’s random player ID, the match’s ID, when it started, and a fingerprint of a code only this browser holds (the code itself stays in this browser’s local storage). When the match ends, its record is sent once and played through as for an account, and is not kept for this. The server then keeps what the match earned and what adding it later needs: its result, length, AI level, when it was played, a fingerprint of its record and of its map, and the achievements it reached. If you sign in within 24 hours, this browser hands the code to your account, and the match is added to it and kept with your account like your other matches. Either way these details are deleted 14 days after they last changed.
Events. For each match that counted in an event, the server keeps how many pumpkins you brought home, how many counted, and when, with your account and deleted with it. To keep an event’s limit on rooms against the same player, it also counts those rooms for each day. Your name, frame, and count show on the event’s public leaderboard.
Bug reports. Signed in, you can report a bug. A report keeps what you write (a title, what happened, and what it is about), the pictures you add (at most three, each saved again by your browser first, so nothing a photo carries besides its pixels, such as where or when it was taken, is sent), and what the page knew: the game’s version, your browser and system (such as “Firefox 131 · Linux”), your screen size, and in a match its mode, map, seed, faction, and how far in it was. If you choose, it also keeps a single-player match’s record. The team reads reports in the game’s statistics, and new reports and their changes go to the team’s private Discord channel with the name other players see (never your Google name) and the first picture. A report is kept with your account, shown to you on your account page with the team’s answers (each message and change of status, with its time), and deleted with the account.
Profiles, friends, and messages. With a username you get a profile page that other signed-in players can open. It shows your name, picture, and frame, and unless you make it private on your account page, also your level, roles, the month you joined, how many friends you have, your achievements, and your last five matches that earned XP. If it’s private, only your friends see more than your name and picture. Profiles are not shown to search engines. Friends find each other by username. The server keeps your friends, the friend requests you sent and got (for 30 days after the last time it was sent), the players you blocked, and your private messages to and from friends (what you wrote, when, and whether it was read). Messages are deleted 90 days after they were sent, and you can delete a conversation from your side at any time. To keep the daily limit on messages, it also counts how many you sent each hour, and forgets that after a day. Nobody else reads them, the team included, unless you or the other player report a conversation: then its last 50 messages are sent to the team with the reason, kept for 180 days, and used only to deal with the report. While you have the site open, your friends can see that you are online, in a room, or in a match. A game invite lives only in the server’s memory and ends after five minutes.
What is kept, and how. Your Google or Discord user ID and display name, and the username and display name you choose, if any, the address of your Google picture or the identifier of your Discord avatar, when the account was created and when you last signed in, your sign-in sessions (when each began and was last used, with a session key: a random value in an HttpOnly cookie, stored on the server only as a hash), and the random player IDs of the browsers you signed in with. While a sign-in is under way (ten minutes at most) the server also keeps one-time security values for it. The log of the team’s support views and role changes (who opened which account’s page or changed its roles, when, and from which IP address) is kept for a year. The data travels only over HTTPS and is kept in a database on the game’s server that only the server can read.
How long, and deleting it. Until you delete the account. A session ends when you sign out, after 30 days unused, or 180 days after the sign-in at the latest. On your account page (bannerwake.io/account) you can download this data or delete the account at once: the account, its sign-ins, its sessions, its XP, achievements, skins, and event pumpkins, its bug reports, its friends, requests, and blocks, and every message you sent or received are erased (a report already posted to the team’s Discord stays there until the team removes it, and a reported conversation stays with the team for its 180 days), you are signed out on every device, and your matches stay as a guest’s. You can also ask by email (below), and remove Bannerwake’s access any time in your Google Account or in Discord (User Settings → Authorized Apps).
Bannerwake’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Your rights
You can ask to see the data about you, to correct or delete it, or object to its use. If you are in the European Union, you may also complain to your data protection authority.
Contact
Questions, data requests, or deletion: [email protected]