Privacy
There is no account here, no sign-in and no profile. This page says what you give the site, what the server records, how long it keeps it, and which other companies see anything.
What you give it
One of three things, depending on the tool.
- A Warcraft Logs report URL. The report code goes to this site's server, which asks Warcraft Logs for that report. Only logs that are already public on Warcraft Logs can be read: the server authenticates as this application rather than as you, and that only reaches public reports.
- A character name and realm (the Raider Lookup). The name, realm and region go to this site's server and are forwarded to two places: Blizzard's Battle.net API, which answers with the character's current public armory profile — the default gear shown — and Warcraft Logs, for their logged raids. Each of those services learns which character was looked up; each sees the server making the request, not your address. The armory answer is held in server memory for up to 15 minutes and is never written to storage.
- An addon export paste. The paste is read in your browser and is never uploaded as a whole. One thing does leave: if a gear simulation runs on the server rather than in your browser, that raider's equipment — the item, enchant and gem ids, and the spec — is sent to the server to be priced, without the character name or the report code.
The Warcraft Logs API credentials live on the server and are never sent to your browser. The example audit on the front page asks Warcraft Logs nothing at all: its data ships with the site.
What the server records, and for how long
A request to this site's server — a report, a lookup, a simulation — writes one line to a log. The lines hold:
| Recorded | What it is |
|---|---|
| The report code | Which public log was audited, which Warcraft Logs host it came from, and which of this app's queries was asked. |
| The spec simulated | For a simulation: the spec name and how many item swaps were priced, with neither the gear nor the character name. |
| A visitor value | The first 12 characters of a keyed hash of your IP address — HMAC-SHA256 under a secret held on the server. Your address itself is never written down. It is used to count how many people use the site and to spot a single caller flooding it. Because it is derived from your address, it is treated as personal data. |
| A refused request | The status, a short reason, and the message sent back, cut to 200 characters. When a request names a server this site will not talk to, that message repeats the name you sent. |
| Unexpected fields | If a request carries field names a query does not use, they are dropped and up to five of those names are recorded, each cut to 40 characters. |
Log lines are deleted after 14 days, automatically. Ordinary page views are not logged anywhere.
One more thing is kept, separately from the log lines above and for longer: that someone looked at a particular report, stored as that report's code and the same keyed hash of your IP address described above. The number shown on a report is simply how many of these are still on file for it, so there is nothing separate to keep count of. It is not joined to a name, it does not record what you did on the page, and it is deleted after 30 days.
One other thing writes a line. When a /report/CODE link is pasted into Discord,
Slack, Telegram or anywhere else that shows a preview, that app fetches a preview card from this
site, and the report code and the Warcraft Logs host are recorded. Those lines are deleted after
14 days too.
What is cached
- Warcraft Logs report responses. A report never changes once uploaded, so the response is stored and reused instead of asking again. The stored copy is the Warcraft Logs response as it arrived, holding only what the public report already shows, without anything derived or indexed per player. These are deleted after 30 days. Opening the report again after that simply asks Warcraft Logs for it again.
- Character lookups are never cached. No lookup result is stored on the server at all — every one goes live to Warcraft Logs.
- Simulation results. Stored under a hash of the whole simulator question: the gear, the spec's race, class, talents, rotation, consumables and buffs, the encounter, the iteration count and a fixed seed. What is kept is a single number. Two people asking about the same gear share one entry because it is the same question. There is no automatic expiry on it.
- Numbers computed in a browser. When the simulator runs in your browser rather than on the server, the resulting number is sent back and stored, so later visitors asking about the same gear are not made to recompute it. A record holds three things: the number, what it measures, and whether it has been disputed. Nothing about who sent it — no address, no identifier of any kind. Like the entry above, it is filed under the gear it describes, so it says nothing about a person even in principle. If a later browser reports a different number for the same gear, the record is marked disputed and stops being served.
What stays in your browser
Every correction you make — a spec you overrode, a raider you marked as an enchanter, which worn
set a raider is audited on, the phase, the raid, the raider you are looking at — lives in the
# fragment of the address bar. Browsers never put that part of a URL in the request
line, so this site's own servers never receive it and nothing in it is stored
here. It is what makes a copied link reopen exactly what you were looking at without anything
being written down about you.
The advertising script is the exception, and it is a real one. A script running
on the page can read the whole address, fragment included, and Google's ad script does: it sends
the complete URL of the page you are on to googleads.g.doubleclick.net. That means
the report code, the character name in a /character/… link, and — on a shared addon
export link — the exported gear string and the character name inside it are all sent to Google.
This was measured on the live site in August 2026, and this page previously claimed the opposite;
the claim was wrong and has been corrected rather than quietly dropped.
Two things follow. Ads are only loaded on the public site, so nothing above applies to a page
served without them. And if you would rather not send a gear export to Google, do not open a
shared #export= link on a page carrying ads — paste the string into the Raider
Lookup instead, which keeps it in the browser.
Two things do ride the visible path rather than the fragment. A report link is
/tbc/report/CODE, so the code reaches this site's CDN and the preview endpoint above. A
lookup result is /tbc/character/region/realm/Name; the name is rewritten away at the
edge before the request reaches storage, and since page views are not logged, it is not written
down anywhere.
One value is stored in the browser itself, rrr-sims-local-only: a note that
simulations here previously had to run in your browser rather than on the server, so the next
visit can start the in-browser simulator early. It holds no identifier, is never sent anywhere,
and goes when you clear this site's data.
And one cookie, rrr-game, holding the word tbc or forever
and nothing else: which game you were last on, so that opening the bare address
rabblesreadyraiders.com takes you back to it. It is the only thing this site's own
server reads from your browser, it holds no identifier, it is not shared with anyone, and it
lasts a year or until you clear this site's data. Without it you land on TBC. The same word is
kept in the browser's own storage under the same name, along with any talent builds you save.
Advertising
Google's AdSense script runs on every page of this site, including this one. Opening a page makes a request to Google, which sees your IP address, your browser's user-agent, and any Google cookies already in your browser. No ad unit is configured, so no ad is placed on the site today; the script runs regardless. Blocking it changes nothing you see here — no number on this site depends on an ad.
Third-party vendors, including Google, use cookies to serve ads based on your prior visits to this website or other websites. Google's use of advertising cookies enables it and its partners to serve ads to you based on your visit to this site and other sites on the internet. Their practices are described in how Google uses information from sites that use its services.
You may opt out of personalised advertising at Google Ads Settings, and out of a third-party vendor's use of cookies for personalised advertising at aboutads.info.
Any cookie-consent banner you see comes from Google's own consent service, delivered by that same script. This site has no consent code of its own, and no control over which of Google's ad-serving domains your browser contacts once the script is running.
Who else sees anything
The item database, the best-in-slot lists and their scores ship with the site, so nothing is ever asked of wowsims or wowtbc.gg while you use it. The requests that are made are listed below, split by who makes them: a request your browser makes shows that company your IP address, and a request this site's server makes does not.
What your browser requests directly
| Who | What for | What they see |
|---|---|---|
| The AdSense script, on every page. | Your IP address, your browser's user-agent, any Google cookies already set, and
the full address of the page you are on, including the # fragment
— see "What stays in your browser" above. Covered under Advertising, with the opt-out links. |
Google is the only one. This site used to load item icons from Wowhead and boss portraits from Warcraft Logs, which showed both companies your IP address and roughly what was on your screen; those hotlinks were removed in August 2026. Item icons, consumable icons and boss portraits have since returned as Blizzard’s own art, downloaded once when the site is built and served from this site itself, so no other company is contacted for any of them.
Item names link to Wowhead and kill links go to Warcraft Logs, but those are ordinary links:
nothing is requested until you click one. The typeface is served from this site, not from a font
host. Every page here sends Referrer-Policy: strict-origin-when-cross-origin, so
those companies are told only that a request came from this site — never which page. That covers
the Referer header only; it does not cover what a script on the page chooses to
send, which is why the advertising script is called out separately above.
What this site's server requests for you
When you look up a report, this site's server asks Warcraft Logs and nothing else: a fixed list of this app's own queries to three Warcraft Logs hosts, and anything else is refused before a request leaves. A raider lookup by name asks TWO upstreams — Warcraft Logs for the logs, and Blizzard's Battle.net API for the armory (the gear they are wearing right now), as described under “What you give it” above. Both are asked the same way: the server authenticates as this application, never as you, which is why only public data is readable, and each upstream sees the server and not you. Because game art is served from this site itself, your browser reaches Warcraft Logs or Blizzard only if you click through to a log or an item yourself.
What this site does not do
- No accounts, no sign-in, no passwords, no email addresses collected.
- No user database. There is nowhere for a profile to live.
- No analytics service, no tracking pixels, no session recording.
- One cookie set by this site itself,
rrr-game, which says which game you were on and nothing else. Ad cookies come from Google, as described above. - Looked-up character names are not written to any server log: the line for a lookup records the Warcraft Logs host, the query asked and the visitor value, never who was looked up.
- Nothing sold or shared with anyone. There is nothing to sell.
- No plain HTTP, and no embedding this site in another site's frame.
Other people's data, and removal
A raid log names other players. Those names, and the gear they wore, come from a report that was already public on Warcraft Logs before this site ever saw it, and the only copy kept here is the cached public response described above. To take a log out of public view, remove it at Warcraft Logs; once it is gone there, ask and the cached copy here is deleted.
Not affiliated with Blizzard
Game data and item art come from Blizzard Entertainment's official API. World of Warcraft and Burning Crusade Classic are trademarks of Blizzard Entertainment. This site is not affiliated with or endorsed by Blizzard.
Getting in touch
Questions about any of this, or a request about data: rabblesreadyraiders@proton.me.
Last updated 22 September 2026.