Privacy Policy

There's no account and no sign-up. We don't run analytics, ad tracking, or tracking cookies. The main thing we process is the Warcraft Logs report you point us at — which contains data about everyone in that raid or group, not just you — plus the ordinary server logs any website generates. We don't sell anything to anyone.

The rest of this page is the precise version, including the parts that are less comfortable — like the fact that an IP address counts as personal data, and that analyzing a raid means processing data about people who never came here.

The Site is operated by RaidMetrics, who is the data controller for the processing described here. You can reach us at raidmetrics@gmail.com for anything in this policy, including to exercise the rights below.

1. The report you submit

When you paste a Warcraft Logs report link, we send that report code to Warcraft Logs' API and retrieve the log: fights, the roster, casts, damage, healing, deaths, gear, talents, consumables, and similar combat detail. We also query Battle.net for talent-tree reference data and spell names, and Warcraft Logs for spell names and icon file names. These requests go out under the Site's own API credentials, not yours.

2. Data about other people

This is worth stating plainly: a raid report covers up to twenty players, and a Mythic+ report covers five. When you analyze one, we process data about all of them — character name, realm, guild, class and spec, what they cast, when they died, what killed them, which mechanics they missed, and whether they brought food and flasks. Those people didn't visit this Site and didn't agree to these terms.

We rely on legitimate interests for this (Article 6(1)(f) GDPR). In weighing that: the data is already published on Warcraft Logs by whoever uploaded the log, is already displayed there to anyone with the link, is pseudonymous (character names, not legal names), and is used here only to produce analysis for the person who already had access to that report. We don't build profiles across reports, don't retain the data after the cache expires, and don't make it findable by anyone who didn't already have the link. If you are in one of these logs and object to that processing, contact us and we will honour it — though note that removing the log itself is something only its uploader or Warcraft Logs can do.

3. Technical data

Like any website, the Site generates server logs. Our host, Vercel, records request data including your IP address, the time of the request, the page or API route requested, and your browser's user-agent string. An IP address is personal data under GDPR, so this is disclosed here even though we never look at these logs to identify anyone. We use them, and Vercel uses them, to serve the Site, keep it up, and deal with abuse or attacks. Legal basis: legitimate interests in operating and securing the Site.

4. What stays in your browser

The Site stores a few small values in your browser's local storage: the last report code you opened (so moving between the Site's three pages doesn't mean pasting the link again), a timestamp used to back off for a couple of minutes after Warcraft Logs' rate limit is hit, which Boss mechanics rows you folded down, and, on a Mythic+ key, any pulls you rearranged and any Keystone Guru route link you pasted. All are strictly functional, never sent to our server, and cleared when you clear your browser's site data. We don't use them to recognise or track you.

The Site sets no cookies for visitors. The only cookie is for its administrator: logging in to the admin page sets a sign-in cookie that expires after 12 hours.

• No account, password, or email address is collected — there's nothing to sign up for.
• No analytics, advertising, fingerprinting, or cross-site tracking of our own. (A Keystone Guru map you choose to load brings its own analytics; see below.)
• No sale or sharing of personal information, as those terms are defined under the CCPA/CPRA. We have never sold personal information.
• No automated decision-making with legal or similarly significant effects. The Site grades gameplay; it doesn't decide anything about you.

Report data fetched from Warcraft Logs is held in server memory only, for up to 15 minutes for raw log data and up to 24 hours for small derived results (like a boss's top-kill baseline), purely so repeat views don't re-fetch the same thing and burn the shared API budget. It is never written to a database or to disk, and it disappears when it expires or whenever the server restarts or redeploys. Server logs are retained by Vercel under their own retention schedule.

• Vercel — hosting and server logs (processor).
• Warcraft Logs (RPGLogs, LLC) — the source of all log data; we query their API and they see our requests.
• Blizzard (Battle.net API) — talent-tree reference data and spell names. Spell icons load in your browser from Blizzard's image server (render.worldofwarcraft.com), which receives your IP address the way any image host does.
• Wowhead (zamimg.com) — a script loaded in your browser to render spell tooltips. Because it loads in your browser, Wowhead receives your IP address and may set its own storage under its own policy, which we don't control. Spell names on the Site are links to Wowhead; hovering one is what triggers the tooltip.
• Keystone Guru (RaiderIO, Inc.) — only if you paste a Keystone Guru route link into a Mythic+ key and click to load it. Their map then loads inside the page, in your browser: Keystone Guru receives your IP address and sets its own cookies, including Google Analytics, under its own policy. The link you paste stays in your browser.

These are all US-based services, so data involved in running the Site is transferred to and processed in the United States. Where that transfer is from the EEA or UK, it relies on the relevant provider's transfer mechanism (such as Standard Contractual Clauses or an adequacy decision).

If you're in the EEA or UK, you have the right to access, correct, erase, restrict, or object to processing of your personal data, and the right to data portability. Where we rely on legitimate interests — which is most of what happens here — you have the right to object, and we'll stop unless we have overriding grounds. You can also complain to your local supervisory authority.

If you're in California, you have the right to know what categories of personal information are collected and why, to request deletion, to correct inaccurate information, and not to be discriminated against for exercising those rights. Since we don't sell or share personal information, there's no opt-out to offer.

To exercise any of this, email raidmetrics@gmail.com. Be aware of the practical limit: with no accounts, the only personal data we hold about a visitor is transient log data we can't tie to a person, so a request about a report usually has to go to Warcraft Logs, who hold the log itself.

The Site isn't directed at children under 13 and we don't knowingly collect their personal data. If you believe a child has provided personal data through the Site, contact us and we'll delete what we hold.

The Site is served over HTTPS and our API credentials are held server-side and never exposed to the browser. That said, no service is perfectly secure, and the Site is a hobby project run without a dedicated security team — please don't send us anything sensitive.

We may update this policy. The date at the top changes when we do, and material changes will be noted in the changelog. See also the Terms of Use.