Tactical RerollTactical RerollPurge the odds.
⋯

Privacy

Short version: no accounts, no ads, your lists stay on your device, and analytics without cookies or personal data. We count anonymous names (which units people pit against each other, which units uploaded lists take) and keep players' ratings of units, with nothing that identifies you.

Your army lists stay on your device

Roster files and pasted lists are read in your browser and saved only in your browser's local storage, along with:

The lists and figures themselves are never uploaded, except a list you play in an online Arena or Table game (below): we only count the unit names in them (see Our own counts below).

A list builder share link carries the list itself after the # in the address, a part browsers never send to a server: only whoever opens the link reads it.

Your browser also keeps a copy of the site's own files and of the datasheets it has loaded, so the site opens quickly and works offline. Clearing your browser data removes all of this.

Game data

Datasheets load in your browser from the BSData project's public files on GitHub (raw.githubusercontent.com), or from the jsDelivr mirror if GitHub can't be reached. Like any website, those services see your IP address when your browser requests the files. Nothing about you or your lists is sent.

Feedback

The Feedback and bugs form at the foot of the calculator sends what you type, your email only if you give it, the page you were on, your matchup's link, the data version, and your browser and screen size to a Google Form that only we read (see Google's privacy policy). Nothing is sent unless you press Send.

Our own counts and ratings

Our small server (a Cloudflare Worker) keeps anonymous daily tallies of how the site is used, to show fan favourites and build our own picture of the game: which units are pitted against which (and whether they shoot, fight or go to the death), which units are picked, the detachments picked, winning lists loaded, results shared and units whose card or page is opened. When you load a list, it counts the list's faction, what kind of file it was, and the names of the units in it, once per list: never the list itself, its points, or anything you typed. When one of our pages hits a script error, it counts that too, once a visit: the error's message with any numbers, addresses and quoted text taken out, which of our files and lines it came from, and which part of the site it was on, so we can fix what breaks on your device. Only names and totals are kept, with no address, cookie or ID, so none of it can be tied to you. We keep these tallies indefinitely, and publish each week's top units and matchups as the meta report. When you share a matchup, its settings (units, wargear, modifiers and the result) are saved on the same server under a short code, so the link stays short and goes on working; nothing about you is saved with them, and anyone with the link can open that matchup. A shared link passes through the server on its way here, so chat apps can show its result as a picture; nothing about the visit is kept.

If you rate a unit, your browser makes a random voting number, kept in its local storage, so each device has one vote per unit and can change or take it back; we keep your score with a scrambled (keyed-hash) form of that number, never the number itself. Before a vote, Cloudflare Turnstile checks that a person is voting (Cloudflare sees your IP address and some browser signals for that check). To stop floods, the server counts each network's requests for an hour under a scrambled form of its address and the hour, and forgets them daily.

Online games in the Arena and the Table

If you make or join an online game in the Arena or the Table (our test pages at /lab/arena/ and /lab/table/), our server keeps that game so both players can play it from their own browsers: the two lists as the game uses them (unit names, model counts, wargear counts, the Warlord, enhancements and the list's title; for a Table game also its mission: the deployment, the terrain layout, the battle size and each side's Force Disposition), the sides' names, every choice made in the game and the dice the server drew after each one. Each player's link holds a private key, which we keep only in a scrambled (keyed-hash) form. If you ask to be notified on your move, your browser hands us an address at its push service (Google's, Mozilla's, Apple's or Microsoft's, depending on the browser), which we keep with the game and use only to send a notification with no content; the push service sees that one was sent. Your browser keeps your games' links in its local storage. No account, email or IP address is kept. A game, its moves and its push address are deleted 30 days after its last move, or at once when either player deletes it.

Analytics

We use Plausible Analytics, which does not use cookies and does not collect personal data. It counts page views and a few anonymous events to show which features people use: which button or screen was used, with at most an army or unit name, a side, a file type or a choice (for example "roster imported" with the faction and file type), and which links to other sites are followed (the link's address). The search on our pages sends only whether it found a unit, an army or nothing, never what you typed. No event carries your lists, your ratings or anything that identifies you.

No ads

Tactical Reroll carries no advertising and no ad trackers.

Links to other sites

Some pages link to other sites: creators' videos on YouTube, Stat Check's published win rates, tournament results on MiniHeadQuarters, ChampionsHub and Listhammer, the BSData project on GitHub and the list tools our exports open. Nothing is sent to them until you follow a link, and then you're on their site, under their own privacy policy.

Contact

Questions or requests: write to us through our private form.

Last updated November 5, 2026.