Privacy

Privacy policy

Last updated October 21, 2026

What DungeonRecap collects, why, and what you can ask for.

Combat logs

  • Your browser reads your log on your own device. Only the run you pick is sent to us, and we don't keep that raw slice after reading it.
  • We keep what we work out from it, for everyone in the run: character names, classes and specs, damage, healing, deaths, casts and where each player stood.
  • Anyone with a run's link can see it, and recent runs are listed on the site.

Analytics

We use Google Analytics and PostHog to count visits and see how the site is used. They set cookies or local storage in your browser and receive your IP address, browser and the pages you visit. We don't sell data and there are no ads.

Accounts

If you sign in, we keep your email address and a one-way hash of your password, plus a session cookie to keep you signed in. With a username, your profile page is public: it shows your username, the runs you uploaded and the characters in them.

Early access

If you ask for early access to the games, we keep your email address to tell you when you're in, and use it for nothing else.

Your choices

Ask us to see, correct or delete what we hold about you, or to take down a run you're in: [email protected].

Getting a combat log

  1. 1
    Turn on Advanced Combat Logging (once)

    In game press Esc → Options → Gameplay → Network, and tick Advanced Combat Logging. Without it the log has no positions or health, so the replay has nothing to draw.

  2. 2
    Start logging before the run

    Type /combatlog in chat. The game answers "Combat logging enabled". It stays on until you type it again or log out, so do it at the dungeon entrance, before the key goes in. Some addons turn it on for you when you enter an instance.

  3. 3
    Find the file

    It is World of Warcraft/_retail_/Logs/WoWCombatLog-<date>.txt. Drop it on the upload page: it is read in your browser, every run inside is listed, and only the one you pick is sent.

Logs grow fast (a raid night can be over a gigabyte). Delete old ones now and then, or start a fresh file by typing /combatlog twice.