1. Controller
The controller responsible for processing personal data on wowcore.io is:
Marcel Bartoschek (BartoDesign)Landstr. 76, 34474 Diemelstadt, GermanyEmail: kontakt@wowcore.io
WoWCore is a private, non-commercial project. Please send data protection questions to the email address above.
2. Overview
WoWCore is a platform for World of Warcraft guilds. It shows character profiles, rankings, raid and Mythic+ progress, guild pages, raid planning, combat log analysis and crafting plans. Game data comes exclusively from the official Blizzard interface (Battle.net API).
We do not sell data, show no advertising and integrate no third-party tracking services. No automated decision-making with legal effect takes place.
Most pages can be used without logging in. Personal areas (account, raid planning, combat log upload, crafting plans) require logging in with Battle.net.
3. Operation and hosting
We run WoWCore on a server at STRATO. The data centres are located in the EU, and according to STRATO the data is stored exclusively in the EU.
We have a data processing agreement (DPA) with STRATO. It has applied automatically to contracts since 18 July 2022. For parts of the processing, STRATO uses sub-processors: SiteLock LLC (USA), Dropsuite Ltd. (Singapore) and Virtuozzo/Plesk (Switzerland). Processing takes place predominantly in the EU.
A reverse proxy (Caddy) receives connections and encrypts them with TLS. Let's Encrypt issues the certificates. Only the domain name is transmitted in the process.
Legal basis: Art. 6 (1) (b) and (f) GDPR.
4. Connection data and server messages
When you open a page, technically necessary connection data arises: IP address, time, requested address and browser identifier (user agent).
We do not keep general access logs. The web server writes this data into its messages only when a connection is aborted or an error occurs. We delete these messages after 7 days at the latest.
Legal basis: Art. 6 (1) (f) GDPR (secure and stable operation).
5. Logging in with Battle.net
If you log in with your Battle.net account, Blizzard redirects you to the login. Logging in takes place at your request. We then receive from Blizzard your Battle.net ID and BattleTag, together with an access token and, if Blizzard issues one, a refresh token. We use these to retrieve your character data from the Blizzard interface. We store:
- your Battle.net ID and BattleTag,
- the tokens encrypted (AES-256-GCM) with their expiry time,
- your Retail characters with name, realm, class, specialisation, level, guild and item level,
- for WoW Forever: which characters belong to your account, which of them is your Forever main, the portrait of that character and when we last synced your list (not public),
- your links to guilds and your role in them (see section 11).
We do not request an email address.
WoW Forever: On forever.wowcore.io you can sync the WoW Forever character list of your Battle.net account with Blizzard in your account. We only request this list from Blizzard when you click “Sync with Battle.net”. This never happens at login and never merely when a page is opened. We store which characters belong to your account, your Forever main, its portrait and the time of the last sync per region. This assignment and your main are not public and visible only to you. The characters themselves appear in the public directory like all discovered ones (section 7).
The assignment ends when, at a later sync, Blizzard returns a list without the character. An empty or missing response deletes nothing. It also ends when we could not confirm the character for 30 days, when you have the character removed from the directory, or when you delete your account. If a character drops out, it is no longer your main. You can change your main at any time.
Logging in uses a session cookie (section 8). Blizzard Entertainment processes the data arising during login as an independent controller under its own privacy policy (Blizzard privacy policy). Where data is transferred to third countries in the course of this, it takes place for the login you requested (Art. 49 (1) (b) GDPR).
Legal basis: Art. 6 (1) (b) GDPR (providing login and account functions).
6. Game data from the Blizzard interface
WoWCore displays game content that Blizzard provides through its interface: character profiles, equipment, talents, Mythic+ and raid results, PvP rankings, guild member lists and guild achievements. This applies to Retail and to WoW Forever. For both game versions, the public character and guild pages show in essence the same as Blizzard's public armory. This data concerns players and their characters. We use it only to display game content and to calculate rankings.
Legal basis: Art. 6 (1) (f) GDPR. Our interest is operating a platform for game content. Blizzard provides the data through its interface, and we use it only for this purpose.
Currency and deletion:
- We retrieve public Blizzard data again at regular intervals: active characters more often, less active ones less often.
- Historical rankings of individual seasons (season archives) are kept as an overview. They are public ranking snapshots.
- For the ranked PvP ladders we store a history point whenever a rating changes (character, rating, time) to show the progress of the current season. This causes no additional Blizzard requests. History points are removed when a character is blocked or deleted; "place among recorded players" and percentages only refer to our own sample.
- If Blizzard no longer provides a character profile, for example after a rename, transfer or deletion, we hide the character from search, rankings and the character page. We check again later; if it can be retrieved again, we show it again. In WoW Forever we delete it instead (see section 7).
- If a character no longer appears in its guild's member list at Blizzard, we remove it from that guild.
- Immediately on request: If a character should no longer appear with us permanently, ask us by email at kontakt@wowcore.io (for Retail with character and realm, for WoW Forever with first and last name and region; the realm type is optional there) to block it. This applies to Retail and to WoW Forever. We then add the character to our block list, remove its stored data, hide it permanently and no longer retrieve it from the Blizzard interface. For WoW Forever this automatically also covers sightings by other WoWCore users that carry first and last name. Entries from the WoWCore addon, however, usually only know the first name and the realm name from the game (for example “CAMWOW EU5 Realm 7 PvE”); we block and delete them if you also tell us this realm name. It is shown next to the region on the character page of the addon entry.
7. WoW Forever directory
On forever.wowcore.io we keep a directory of the WoW Forever characters and guilds we find through Blizzard's interface. It can be searched publicly (Armory, guild list, rankings) and is the basis of the “Population” statistics. The data does not come from you but from Blizzard (Art. 14 GDPR). The directory covers the regions in which Blizzard provides WoW Forever (currently Europe, the USA, Korea and Taiwan). Names can also be written in Korean or Chinese script.
How we find characters and guilds: through the member lists of guilds at Blizzard, through the guild named in a character profile, through the WoW Forever account list of your Battle.net account when you sync in your account on forever.wowcore.io, when someone searches for a character or opens a character or guild page on forever.wowcore.io, through sightings by other WoWCore users that carry first and last name (see “Seen players” in section 10), and continuously through the guild names from the Retail part of WoWCore (only the guild name of the respective region, no members; to find guilds of the same name in WoW Forever). We go through these names one by one, the most common first. When a pass is finished, we start again after about a month, because new guilds keep appearing in WoW Forever. For each such hint we retrieve the public character profile or the guild with its member list from Blizzard. If Blizzard does not know a name, we do not add it to the directory. We limit how many hints a single account can contribute. This way nobody can flood the directory with names.
Function check: We automatically check about every 15 minutes whether Blizzard's interface provides WoW Forever data in a region and which sections we can show. For this, our system usually picks one character per region at random from the directory (level 10 or higher, with a guild, confirmed by Blizzard within the last 72 hours, not blocked); as a fallback we use a character named by us, for example one of our own. We retrieve its public profile, its equipment and, in turn, its guild with the member list (a sample). We only evaluate whether the retrievals succeed. We store the name, Blizzard's ID of the character (so that a later block also works after a rename), the guild and the time of the last check in our non-public operating state; the sample does not appear anywhere on the site. We replace a randomly picked character after 7 days at the most, as soon as another suitable character is available (if there is none, the current one stays until then). We also replace it as soon as Blizzard no longer provides it, when the region is downgraded, and immediately when it is blocked: a blocked character is discarded before the next retrieval and never chosen for this again. We can switch this automatic selection off at any time.
We store per character: first and last name, region, realm type, class, race, gender and faction of the character, level, experience, item level, guild and guild rank, the last login according to Blizzard, Blizzard's character ID, and when we found it, last confirmed it and first saw it at level 60. Per guild we store name, region, realm type, faction, member count, founding date and figures derived from them (for example the median level). We do not display the time of the last login. We use it to retrieve active characters more often and for figures such as “logged in during the last 7 days”.
Currency and deletion: We retrieve active characters more often (login on the previous day daily, during the last week every 3 days, during the last month weekly; for the “Race to 60” ranking, the 200 most advanced characters below level 60 per region and realm type with a login on the previous day every 6 hours), all others from level 10 at the latest after 28 days. We do not retrieve characters below level 10 individually, because Blizzard provides no profile for them. We retrieve guilds daily to weekly. The test character of the function check (see above) is the exception: we retrieve it about every 15 minutes, but only until it is replaced (after 7 days at the most, as soon as another suitable character is available). If Blizzard no longer provides a character or guild, we check again at the earliest 24 hours later and delete the entry at the second “not found”. We also delete entries we could not confirm for 30 days. The hints we search with are not public. Unchecked hints expire after 30 days. We delete checked ones 30 days after the check. Deletion runs independently of retrieval: even if we switch off retrieval from Blizzard for a while, we keep deleting.
Your own characters: Characters you sync through your account appear in the public directory like all discovered ones as soon as Blizzard's profile or a guild list has confirmed them. Only what applies to all discovered characters is public. We show nobody that a character belongs to your account or which one is your main. If Blizzard reports a character of your account as “not found”, we do not delete it right away. It drops out when we could not confirm it for 30 days.
Removing yourself: In your account on forever.wowcore.io you can have one of your own characters removed immediately under “Remove from the directory”. We then block the name and, where known, Blizzard's ID. We delete the character from the directory, from all hints and from your account, and do not add it again. The block is lifted only on request by e-mail.
Population: it shows only figures without names (for example characters per class, race and level). We keep these daily values as a history.
Legal basis: Art. 6 (1) (f) GDPR. Our interest, and that of our users, is a directory and statistics of the game world that are as complete and current as possible, and safe operation (the function check). We only use information Blizzard provides through its interface, do not show login times and delete entries that are no longer confirmed after 30 days at the latest.
Objection and block (Art. 21 GDPR): write to kontakt@wowcore.io with first and last name and region, or use “Remove from the directory” in your account. We block the character as described under “Immediately on request” in section 6, delete it from the directory and from all hints, and do not add it again. The block applies to the character itself: we block the name. As soon as we know Blizzard's ID of the character, we block it as well. When you write to us by e-mail, we retrieve Blizzard's public profile once for this; with “Remove from the directory”, the ID comes from your account list. The block of the ID also stays in place after a rename. If Blizzard does not provide the character, the block of the name remains.
9. Our own web analytics without cookies
We count page views to see which areas are used. For this, your browser sends a short record to our server when you change pages. It contains:
- the page area without query parameters. If the page follows a known pattern, a placeholder replaces the names. In that case we do not store character, guild or report names,
- the domain of the page you came from (without path), if your browser provides it,
- a visitor identifier. It is a hash of the date, IP address, browser identifier and a secret key. It changes every day. We do not store the IP address itself.
The visitor identifier is a pseudonym. It allows us to count visits on one day, but it is not linked to your account. We do not record the country. We filter known crawlers by their browser identifier. This does not always work completely.
The data is deleted after 90 days. It is evaluated internally only and is not passed on.
Our server's response to this record sets the technically necessary cookie wowcore_live (section 8). We do not use it for web analytics.
Legal basis: Art. 6 (1) (f) GDPR (interest in analysing use for operating the service). You can object to this processing by email to kontakt@wowcore.io (Art. 21 GDPR).
10. Desktop app, addon and combat logs
Addon (World of Warcraft add-on). The addon runs in the game and stores data locally on your computer. The history with Mythic+ runs, raid evenings, fellow players, and their equipment and talents remains on your device. We do not receive this data. The exception is the add-on module “WoWCore Guide”: it shares quest observations without your account via the desktop app (see “the guide learns together”).
Add-on module “WoWCore Messenger”. The messenger shows whispers in their own windows and stores the history exclusively locally, in the saved variables of World of Warcraft on your computer. It transmits nothing to WoWCore, not even through the desktop app; we receive neither messages nor names. You can delete the history in the addon at any time or turn off saving.
Desktop app "WoWCore Live". You connect the app to your account by confirming the connection on wowcore.io in your browser; the browser passes the confirmation only to the app on the same computer (address 127.0.0.1, it does not leave your computer). Alternatively you enter a device code. The app then receives a device token. It is valid for 30 days, renews when used and ends after at most 365 days. We store only a hash of the token, not the token itself. Through the app we transmit:
- actions for guild planning (your raid confirmations or declines), which the addon hands over to the app,
- live data from fights and uploaded combat logs,
- in WoW Forever, the data of your own characters that the addon records (see below),
- with the guide installed, its quest observations without your account, pseudonymised (see “the guide learns together”).
Device name when connecting. So that you can tell on the confirmation page that the request comes from your own computer, the app reports your computer's name (letters, digits and hyphens only, at most 15 characters, without a domain suffix; otherwise "Windows PC" is shown) and its version number. While the request is open (at most 10 minutes), signed-in visitors who open the link of the request can see both; afterwards only you can, on the confirmation page and under "Connected devices" in your account settings. It is kept until you sign the device out or the token ends (after 365 days at the latest). We delete unconfirmed requests after about 7 hours at the latest, and everything when you delete your account. Legal basis: Art. 6(1)(b) GDPR (connecting the app you use to your account).
WoW Forever: character data. The desktop app uploads the data of your own characters that the addon records: name, realm name from the game, class, race, level, experience, zone, guild, item level, equipment, specialisation, talents and time played. The data is publicly visible on forever.wowcore.io (character page, "Race to 60" ranking). It is tied to the account of the device and removed when you delete your account. Legal basis: Art. 6 (1) (f) GDPR (public character pages and ranking).
Share live (voluntary, off by default). If you turn on “Share live” in the addon and in the desktop app, the addon draws a small colour strip at the screen edge that the desktop app reads inside the World of Warcraft window (only while the game is running; no input is sent to the game and nothing is recorded). Only values that are publicly visible in the game are transmitted: in WoW Forever level, experience, zone, time played, character name and realm; in Retail the boss fight status (boss, difficulty, pull number, start and end, kill or wipe) with character name and realm. Boss health, damage, healing or any other combat values that Blizzard treats as secret are never transmitted. Later extensions of the same feature (sections from the SavedVariables) use the same consent. The values are assigned to the device account. Retail fight status is held only in the server memory (12 hours at most) and appears as a “live” card on your guild page without the names of individual members; Forever values appear on forever.wowcore.io with a “live” mark when Blizzard’s account list assigns the character to your account. To stop: switch it off in the addon or the app; nothing is then drawn or read. Legal basis: Art. 6(1)(a) GDPR (consent by switching it on, revocable at any time).
Seen players (sightings). With “Share seen players” in the addon (on by default in WoW Forever, off by default in Retail) the addon keeps a list of other players you see in the game: from your group and raid, the guild roster, your target, the mouse pointer, nameplates, inspecting, as senders of messages in public chat channels (say, yell, emotes, general channels), in your group, raid and guild (never whispers or officer chat, never the content of a message) and the player search (/who, only when you click). Only details anyone can see in the game are stored: name, realm, class, race, level, guild, zone, time and kind of sighting – no guild roster notes, no combat values. During combat, seen players are only noted in memory and stored after the fight. In WoW Forever we also use sightings with first and last name to retrieve the public profile of that character from Blizzard and add it to the WoW Forever directory. We use the guild of a sighting to find that guild. We do not use opted-out and blocked names for this. The desktop app only uploads the list if “Share live” is also turned on in the addon and the app. On wowcore.io these players appear in grey as “seen by WoWCore users” with the date of the sighting: in WoW Forever in the character search and in “Race to 60” (without a rank), in Retail only in the search when we do not have the character. Data from Blizzard and self-reported data always take precedence. We do not show who reported a sighting; to prevent abuse we store the last reporting account internally. Deletion: 90 days after the last sighting. Opting out: if you do not want to appear as a seen player, write to kontakt@wowcore.io (name, realm, region); we delete the entries and put the name on a block list that future uploads ignore. Legal basis: for your upload your consent (Art. 6(1)(a) GDPR, turn it off at any time), for the persons seen our legitimate interest in a more complete character search with details that are publicly visible in the game anyway (Art. 6(1)(f) GDPR); objection under Art. 21 GDPR by e-mail.
WoW Forever: leaderboards (with “Share live”). With “Share live” turned on, the addon also stores a section with your Forever characters that the desktop app uploads after logging out or /reload: time played until level 60 (from /played), professions with skill and the time the maximum was first seen, and the number of dungeon runs and dungeon boss kills. Only if you also turn on “Share gold” in the addon (voluntary, off by default) are your gold, the number of your mounts and your first mount (name and time) added; if you turn it off, we delete these details with the next upload, and they are shown for at most 30 days after the last upload. The values appear publicly in the leaderboards on forever.wowcore.io and are only stored in character rows that belong to your account. For the “players per zone” list we count the live zones without names; a zone only appears from two different accounts. Legal basis: Art. 6(1)(a) GDPR (consent by switching it on, revocable at any time).
WoW Forever: the guide learns together (part of the add-on module “WoWCore Guide”). The guide is a community guide: we calculate quest locations, quest order and quest levels from the observations of all users. Sharing is therefore an integral part of using the guide. There is no choice and no consent prompt: the add-on always learns, and the desktop app uploads the observations as long as the guide is installed. We point this out before installation and afterwards permanently: in the desktop app, on the download page, in the file “LIESMICH.txt” in the ZIP and at the very bottom of the guide section of the WoWCore window in the game (with older WoWCore versions: at the very bottom of the guide page in the settings) there is a notice about the sharing. In the game it names quest locations and enemy assignments, which are shared with everyone without an account, and also says that by using the guide you agree to the sharing; legally, however, we do not base the sharing on consent but on the legal bases named below. If you do not want to share, do not install the guide, or opt out: turn off the switch “Install guide” in the desktop app or delete the guide folder (“WoWCore_Guide” together with the route folders “WoWCore_Guide…”) in the AddOns folder; the app then sends nothing more. The main addon and all other features remain usable without it.
What the add-on records: On your computer the add-on notes the quest number, where you accepted and handed in a quest (map, position and number of the quest giver), where you first made progress on a quest objective and where you completed it, which quest was offered right after you handed in another one, your level, the quest level, the experience received, the race, class and faction of the character, and the game version, game language and map names. It also records enemy-to-quest assignments (game data): the number of an enemy and the quest objective it belongs to, as numbers only and never with the enemy's name. It does not record character names, realms, guilds, times of day or the way you travel between these events.
What we store: The desktop app uploads these observations; it signs in with its device token to do so. We store the reports pseudonymised, that is without your account, device token or IP address. Each report only carries a check value (HMAC) of the random installation identifier that the add-on creates when it is installed (we do not store the identifier itself), the day of receipt without the time, and a coarse network number between 0 and 32,767. We derive this number from the network of your address (IPv4: the first three number blocks, IPv6: the first three blocks); many networks share the same number. We only use it to count whether a location is confirmed from at least two different networks. We assign map names to a zone on receipt and do not store them. Besides the reports we store, per installation, the maps used with their zone and the experience per level (at most 20 entries per upload).
Misuse limit: So that nobody can push wrong locations with many installations or accounts, we only accept reports from accounts that Blizzard lists with at least one WoW Forever character (checked with the request, nothing extra stored). The server keeps in memory for at most 24 hours after the last upload which installations (as a check value) sent data via which account and which network (IPv4 /24, IPv6 /48), and counts calls per device token and account (these counters for about one hour at most). Daily counter per account: So that the limit of 6,000 reports per account and day also holds across restarts, we store one counter per account and day in the database. It contains the day, the number of reports and, instead of the account ID, a check value (HMAC) of the account ID and a key that changes daily and that we derive from our secret server key (daily salt). With this secret key we could assign the check value to an account; we do not do this, it is only used for this limit. The counter is not linked to the reports. We delete it after 3 days at the latest. If the storage for raw reports is full, we delete the oldest raw reports first, never those of the current day.
Retention and deletion: We delete raw reports after 30 days, and the header details of an installation (maps, experience per level) 30 days after its last upload. You can ask for deletion or object at any time by e-mail to kontakt@wowcore.io; please give your installation identifier, which the command “/wcg info” shows in the game. We then immediately delete all raw reports and header details of this installation. Without this identifier we cannot assign reports to any person, because we store neither an account nor a name (Art. 11 GDPR). Deleting your account does not change this data, because it is not assigned to any account.
Shared values: From the reports we calculate shared values, for example the middle position of a quest giver or which enemies belong to a quest objective. These contain only numbers with no link to a person, account or installation, become part of the guide and are delivered to all users, also in the public download. If they are not confirmed again for 60 days, we delete them.
Legal basis: primarily Art. 6(1)(f) GDPR: our legitimate interest, and that of all users, in accurate, jointly improved quest information, with pseudonymised data without account, name or time of day. In addition, sharing is part of the community guide you install and use (Art. 6(1)(b) GDPR). Reading the add-on file on your computer is strictly necessary for this service you explicitly asked for (Section 25(2) no. 2 TDDDG). Objection (Art. 21 GDPR): turn the guide off in the app or delete the guide folder, and write to us with your installation identifier; we will then delete your reports immediately.
Retail: guild in game (with “Share live”). With “Share live” turned on, the addon additionally transmits only publicly visible game values for your guild’s page: live, whether your character is currently in combat, in a Mythic+ keystone, in a raid or dungeon, and the zone; after logging out or /reload your own keystone (dungeon and level), your raid lockouts of the week (raid, difficulty, defeated bosses) and the list of guild members who are online right now (name, realm, zone – no notes, no ranks). From the boss fight status we store per pull the boss, difficulty, start, duration and kill or wipe as the guild’s raid night history, without your name. Only an own character of your Battle.net account that Blizzard assigns to this guild is matched; members of the online list only appear if Blizzard also assigns them to this guild. All of this is visible to signed-in guild members only. No boss health, no damage, no healing. The legal basis is your consent (Art. 6(1)(a) GDPR), for the online list of other members our legitimate interest in a guild overview that is open to all guild members in the game anyway (Art. 6(1)(f) GDPR). Turning off “Share live” stops the transmission immediately.
Retail: readiness check (with “Share live”). Outside combat the addon checks your own equipped gear for missing enchants, empty sockets and differences from your Forge plan. With “Share live” turned on, the desktop app uploads the result: only the counts and the affected gear slots, no items. It is linked only to your own character that Blizzard assigns to your guild and is visible only to signed-in members of that guild (“Ready” per member). Legal basis: Art. 6(1)(a) GDPR (consent by turning it on, revocable at any time).
Retail: Mythic+ run debrief (with “Share live”). After each completed key the addon also stores a section that the desktop app uploads: dungeon, level, final time, the times of your fights, the progress of enemy forces in percent, the times of boss kills, and the time and class of deaths in the group (without the names of other players) and the penalty time from deaths. It is stored only for your confirmed characters; no secret or restricted combat values are read. The data appears only on your character page. It is deleted 120 days after the run, and at most 30 runs per character are kept.
Group readiness before the key. In a dungeon group before a key starts, the addon sends players with WoWCore, through the in-game addon channel of the group, your key (dungeon, level), your role and whether you are ready. This happens only when Blizzard allows sending, never during a running key, and only between players; WoWCore servers receive nothing of it. To turn it off, use the command /wowcore ready off.
Retail: character page (with “Share live”). With “Share live” turned on, the addon additionally stores a section for your Retail characters that the desktop app uploads after logging out or /reload: the state of the Great Vault (raid, Mythic+, world: progress, level, item level of the reward), your crest currencies (amount, weekly or season cap), the upgrade state of your equipped gear, the upgrade costs the game showed you at the upgrade vendor, and the progress of a few season achievements (e.g. Keystone Master, Ahead of the Curve) with their steps. Live, a running Mythic+ keystone is added (dungeon, level, start, time limit, deaths, result) if the addon’s M+ timer is on. We only store data for characters that Blizzard’s account list assigns to your account. The data appears publicly on the page of the respective character; the running keystone also appears on the guild page, there without character names. No boss health, no damage, no healing. Legal basis: Art. 6(1)(a) GDPR (consent by turning it on, revocable at any time).
State code for the Forge (voluntary). Only when you type /wowcore code in game and paste the code into the Forge on wowcore.io do we receive the state of your character: name, realm, region, character number, class, race, faction, level and specialization; your equipped gear and equippable items from your bags, character bank, warband bank and the Great Vault options (item, item level, enchantment, gems, bonus IDs, upgrade state, stats); your crest and upgrade currencies with their weekly or season caps and the costs the upgrade NPC showed you; your talent builds with their names (Omnium runes only once the addon reads them); your main professions with their skill level; the count of selected reagents and consumables. Never included are gold, guild, zone, played time, friends, chat, notes, your Battle.net name or IDs of other players (the addon drops the crafter ID of an item). If you are signed in and Blizzard's account list assigns the character to your account, we store the checked state on that character so the Forge and simulations can use it; it is deleted 60 days after the in-game state, immediately with “Remove snapshot” in the Forge (including the calculations made with it, section 13), and with account deletion. If you are not signed in or the character is not yours, we do not store the state: it stays only in the storage of this browser tab (sessionStorage) and is gone when you close the tab. If you then get a plan code or save a plan, we send only the items from the state that the plan uses, so the plan can be recalculated. The state itself is not stored. If you save the plan, it contains the chosen items like any Forge plan – then including their location (e.g. “bags”) – and follows the retention of Forge plans (section 12); a plan code is not stored. If you pick a talent build from the state for a simulation, section 13 applies. No sharing with third parties; the code itself is not stored. Legal basis: Art. 6(1)(b) GDPR (use of the feature at your request).
Combat logs. A combat log contains in-game character names and combat data that the game itself records. For uploaded reports we store the title, zone, fights and results. For each fight we store the participants with character names, class, specialisation and performance values (damage, healing, damage taken).
- Uploaded reports are readable by all visitors, even without logging in. They therefore contain names and performance of other players.
- Archive instead of deletion: combat logs and live data are kept without time limit. After an expansion ends, we file them in an archive of that expansion. They remain listed, clickable and fully viewable.
- Original files: we keep the uploaded log files (raw data) so that reports can be evaluated again. We delete them 30 days after the report's first upload, once every fight has been fully evaluated. The evaluated report remains.
- Shared reports: if several players upload the same fight, we combine the uploads into one shared report. It contains the fights from all uploaded logs. If several logs show the same fight, we use the most complete copy.
- Forge for healers: From every analysed fight we calculate at night, for each healing participant, how strongly their effective healing responds to more critical strike, haste, mastery, versatility and intellect. We also store the fight duration, the character's combat stats and a group signature made of check values of the fellow players' game IDs; it only serves to recognise reports from the same group. These figures are kept with the participant in the report, for as long as the report exists. A character's public Forge page uses them to calculate its stat weights. Every fight from the last 30 days of the current season that we assign to the character as a healer counts, no matter who uploaded it; fights uploaded twice count once. The Forge shows the number of fights and reports and the time range, but no names of other people. We also combine the figures of all healers of a specialisation into a pool without names or IDs, containing only numbers, counts and the time range. It only applies from 20 fights by at least 3 healers, 3 uploaders and 3 groups and is recalculated every night. We read who uploaded a report only while calculating, to count uploaders. A report removed from your own logs still counts, because it remains. If a character is made unrecognisable on request, its fights no longer count for it or in the pool: we recalculate the pool immediately, at the latest the following night, and remove its check values from the group signatures of the other healers in the same reports. Legal basis as for combat logs (Art. 6(1)(f) GDPR).
- Removing from your logs: uploaders can remove their reports from their logs at any time. We then delete only the link to your account: you are no longer listed as the uploader, and the report no longer appears in your logs. The report itself stays public, with all fights and participants. Your characters also remain in it as participants, like everyone else. If nobody else uploaded the report, it stays without an uploader. We only store that the report is hidden for you, and the time offset between your PC's clock and the report, so that further uploads from your app are matched to the same fights. Until the raw data is deleted after 30 days, we also keep a record of which raw data parts came from you (your account ID as their source). If your app uploads the same fight again later, the data flows back in, but the report stays hidden for you. For everyone else the report remains with all fights and participants, with all character names, including yours. Only a file name or title you chose yourself is replaced with a neutral one. A character is only made unrecognisable on a formal request (next item).
- Deletion on request: affected persons can object or request deletion. This also applies to fellow players who are named in a log. Write to kontakt@wowcore.io and state the region, realm and name of the character. We review each request individually. Only on such a request do we make the character unrecognisable in all reports; removing a report from your own logs (previous item) does not do this. We replace the name with a neutral placeholder (shown as “Unknown”) and remove the link to the character profile. We replace the character’s game identifier (GUID) with a substitute identifier per report. This substitute is not random: it is a hash value we calculate from the report’s identifier and the game identifier. It contains neither the name nor the game identifier. However, anyone who already knows the real game identifier, for example from their own log of the same fight, can recalculate it and so recognise the character. We delete the original files of these reports at the same time. The combat values remain without a name so that the reports stay complete for everyone else involved. For logs uploaded in the future we keep a block list with the character’s region, realm and name and the game identifiers (GUIDs) we found for it in existing reports. This way it is also made unrecognisable automatically in future logs, even if it only appears there with its game identifier.
- Live recordings from the desktop app are readable by everyone, like uploaded combat logs.
Legal basis: Art. 6 (1) (f) GDPR. Our legitimate interest is a traceable, lasting game history for guilds and players. We weigh this interest against your rights. You can object by email under Art. 21 GDPR. An objection leads to deletion unless our interest prevails. We provide the reasoning on request.
11. Guilds, raid planning and recruitment
- Guild pages: texts entered by the guild leadership are public.
- Raid planning: for guild members we store events, your confirmation or decline with the chosen character, and the time of your reply. Visibility follows your guild's settings.
- Raid plans (boss plans): Raid leadership decides per boss and difficulty who presses which cooldown. We store the draft, the last 5 released versions and the ID of whoever last changed or released it. Guild members see the released plan.
- Pickup log: If the desktop app fetches a plan version for your account in which one of your characters has an assignment, we store your account, the version and the time of the first fetch. Raid leadership only sees from this which guild characters have fetched the plan (by character name, without account details) and which characters are not linked to any WoWCore account (“no account”). The log is deleted with the version, for a replaced version 30 days after it was replaced, and with your account. Anyone who only pastes a plan into the addon as an import code needs no account for this; no log is created.
- Guild in game: confirmed actions are kept for 30 days. Deleted events can be restored for 30 days, after which we remove them permanently.
- Guild health (guild leadership only): From Blizzard's public guild roster we show guild leadership the activity and roles of their members as counts, plus joins and departures. For this we store at most once a day which characters Blizzard lists in the guild (IDs only), for 90 days. Legal basis: legitimate interest in guild management (Art. 6(1)(f) GDPR).
- Guild recruitment: What guild leaders enter in their recruitment post (openings, times, text) is public while the post is switched on. It expires 30 days after the last confirmation and is then no longer public. Contact details (Discord invite, BattleTag, in-game contact) are only shown if the guild explicitly makes them public. We delete these contact details automatically 90 days after the post expires or is switched off. Only authorised guild members can see who last edited the post.
- Applications and messages: When you apply, the guild receives the name, realm, class, specialisation, item level and M+ rating of the chosen character (from Blizzard data) as a snapshot, plus your message. Guild members with recruitment rights can see this. An expired or switched-off post does not end any application or conversation. We delete conversations, including their messages, 180 days after the last message. This applies to all conversations: with guilds, with players and in Mythic+ groups. We delete applications 180 days after the last activity, together with the conversation: the application text, the character snapshot and the application itself, including the record of who applied where.
- PvP partners and group tone: If you look for a PvP partner (2v2/3v3) or pick a tone (learning group, relaxed, ambitious) for a group search, this is published together with the listing. The rating in the listing is read by WoWCore from the Blizzard ladders, as are M+ rating, achievement points and raid progress used as evidence. Contact only works through the BattleTag or Discord you enter in the listing yourself; there is no automatic matching. The details disappear when you delete the listing or your account.
- Account deletion: If you delete your account, we remove your applications including the snapshot, your own posts and conversations in which you are the player. Replies you wrote on behalf of a guild remain in the guild's conversation without a link to your account (as “Deleted account”) until regular deletion. Contact details (BattleTag, character) you entered or that belong to you are cleared from guild posts.
Legal basis: Art. 6 (1) (b) GDPR.
12. Crafting plans
Logged-in users can save plans. A plan contains the chosen character, the specialisation, your settings and a result snapshot. It is valid for 30 days from its date. After that we remove content and result. The character and settings remain.
Deleted plans can be restored for 24 hours. After that we remove them permanently.
Legal basis: Art. 6 (1) (b) GDPR.
13. Simulations in the forge
With “Calculate precisely” and “Best combination”, a simulation service on our own server works out how much damage your gear gives you (software: SimulationCraft).
What goes to the service: game data only, namely your equipped items, specialization, talents and race. Your character’s name, realm and guild are not included; the profile always uses the name “wc”. We pass nothing on to third parties. If you are signed in, the job is linked to your account so that only you can see it. “My raid” also uses average values from your uploaded combat logs (fight duration, extra targets, downtime); they are visible to you only.
Guests with an addon code: If you pick a talent build from your addon code as a guest, it goes to the service with the job. The job and the result, including this build, stay with the service for up to 30 days without any link to an account. Other guests never receive a result with your own build, only someone who runs the same gear with the same talents.
Guests: We do not store an IP address. For the daily limit, a key is derived from the address; it changes every day. Without our secret server key it cannot be traced back to the address. After the day ends (UTC) we remove it from your jobs; the result then stays without any link to you.
With the state code from the addon (section 10): If a state is saved to your account, the service additionally receives your Omnium runes (once the addon reads them), the talent build you chose (also one of another specialization), your equipped gear from the code (if it is newer than Blizzard's data) and, for “Best combination”, items from your bags, bank, warband bank and Great Vault – again game data only. Such results belong to you alone and are never reused for anyone else.
Deletion: We delete jobs and results after 30 days, and your results together with your account. “Remove snapshot” in the Forge immediately also deletes your personal calculations for this character (with the addon code or your own combat logs) and jobs still waiting; a calculation that is running right now is deleted after 30 days once it has finished.
Legal basis: Art. 6(1)(b) GDPR (a function you start yourself), for guests Art. 6(1)(f) GDPR (protection against abuse).
14. Donations
WoWCore is not financed by advertising or subscriptions. Voluntary donations are possible. You pay a donation through PayPal. PayPal handles the payment. The provider is PayPal (Europe) S.à r.l. et Cie, S.C.A., 22-24 Boulevard Royal, L-2449 Luxembourg. PayPal processes your payment data under its own responsibility according to its privacy policy.
We store:
- amount, fee, currency, time and status of the payment,
- a hashed transaction reference, so that no payment is booked twice,
- the source (PayPal) and the status (confirmed, refunded or charged back). We record refunds and chargebacks as separate booking lines.
We do not store donors' names, email addresses or message texts. We do not log raw PayPal data.
On the donations page we show the costs and received donations per month, with date and amount of each donation. We do not show names. We do not show bank statements.
Bookings remain permanently so that the cost overview stays traceable. They contain amount, fee, date and a hashed transaction reference. This reference is pseudonymous: with access to the operator's PayPal account it can be linked to a payment. On request we delete the reference; amount and date then remain without any link to you.
Legal basis: Art. 6 (1) (b) GDPR (processing the donation); Art. 6 (1) (f) GDPR for permanent traceability.
15. Discord
- Linking: you can link your Discord account with WoWCore. We ask Discord only for your identity. We store your Discord user ID with your WoWCore account so that Discord commands can be matched to your account.
- WoWCore Discord bot: on request, the bot assigns roles, welcomes new members and posts raid invitations and patch notes.
- Guild posts in Discord: If guild leadership turns it on, the bot posts the guild's first kills (boss, difficulty, time according to Blizzard) to the guild's linked channel, and once a week the weekly goal with the guild's status (number of bosses defeated, shared keys and full Great Vault rows, without names). For each post we only store the message ID, for at most 30 days.
- Discord processes data under its own privacy policy. Discord states that it is certified under the EU-U.S. Data Privacy Framework.
Legal basis: Art. 6 (1) (b) GDPR (linking) and Art. 6 (1) (f) GDPR (operating the community server).
16. Twitch
For visitors: on the character pages of players who have linked their Twitch channel, we show a notice during a World of Warcraft live stream. Your browser loads nothing from Twitch for this, not even a preview image.
Only when you click “Watch live” does the player load from Twitch Interactive, Inc. (San Francisco, USA; a company of the Amazon group). Twitch then receives, among other things, your IP address, browser data and the address of the page, and Twitch may set cookies. Twitch Interactive, Inc. is not certified under the EU-U.S. Data Privacy Framework (checked on 27 October 2026 in the official list at dataprivacyframework.gov; the certification of Amazon.com, Inc. does not cover Twitch). For this transfer to the USA there is therefore no level of data protection recognised by the EU: US authorities may be able to access the data, and your rights are harder to enforce there. The legal basis is your explicit consent given by the click (§ 25 (1) TDDDG, Art. 6 (1) (a) and Art. 49 (1) (a) GDPR). Twitch's processing: Twitch privacy notice.
Your consent applies only to this one load; on the next page view nothing loads from Twitch until you click again. You can delete cookies already set by Twitch in your browser settings.
Links: “Open on Twitch” and “Open in Twitch” are ordinary links. Twitch's privacy terms apply only on twitch.tv or in the Twitch app.
For streamers: you can connect your Twitch channel in the account settings. Through Twitch we only request your channel ID and channel name; we revoke the access key received for this and its refresh key immediately and do not store them. We store: channel ID, login and display name, time of linking, your character selection and the last known live status (stream title, category, viewer count, start time, time of check).
Our server queries the live status every minute through the official Twitch interface and checks once a day whether the channel still exists; it transmits only channel IDs, no visitor data. The live status query goes to Twitch in the USA; it is necessary for the function you requested (Art. 6 (1) (b), Art. 49 (1) (b) GDPR). The live details are public while you are live. If you disconnect or delete your account, we delete this data immediately.
Abuse (e.g. offensive stream titles): we can exclude a channel from linking; for this we store its channel ID and the channel name at that time. Legal basis: Art. 6 (1) (f) GDPR (protecting the site and its visitors from abuse).
17. Email contact
If you write to kontakt@wowcore.io, your message goes through our own mail server. It runs on the same STRATO server in Germany as the website (section 3). We operate it ourselves; there is no external mail service.
- Content: we store the content of your message and your sender address so that we can answer your request. As soon as the request has been handled and no statutory retention duty applies, we delete the message, at the latest after 2 years.
- Server logs: the mail server logs sender, recipient and the IP address of the connection. We delete these logs after 30 days at the latest.
- Backups: backups of the mailbox are kept for at most 30 days.
- Spam check: we check incoming mail on our own server. We do not use external services for this. However, we check the sender's IP address against public DNS blocklists. Only the IP address is transmitted in that process.
Legal basis: Art. 6 (1) (b) GDPR where your request concerns a contract or pre-contractual measures. Otherwise Art. 6 (1) (f) GDPR (operating the mailbox, preventing spam and abuse, traceability of communication).
18. Recipients and third countries
- STRATO: hosting of the server (processor, see section 3).
- Blizzard Entertainment: login via Battle.net and retrieval of game data. Our server calls the interface. Blizzard therefore sees the IP address of our server, not yours.
- Ability icons: your browser loads ability icons directly from
render.worldofwarcraft.com, that is from Blizzard's render server. In doing so your browser transmits your IP address to Blizzard. - Guild crests: your browser loads guild crests directly from
render.worldofwarcraft.com, that is from Blizzard. In doing so your browser transmits your IP address to Blizzard. - Discord: linking and bot (USA, see section 15).
- Twitch Interactive, Inc. (USA, no adequacy decision): live status of linked channels (our server, channel IDs only) and — only after your click — the player in your browser (section 16).
- Payment provider: only for donations (section 14).
- Let's Encrypt: only the domain name when certificates are issued.
- Fonts: the font files are stored on our server. Your browser does not connect to Google for them.
- Email: requests reach us through our own mail server.
We do not sell data and do not pass it on to advertisers.
19. Retention periods at a glance
| Data | Retention |
|---|---|
| Server messages with connection data | 7 days at the latest |
| Session (login) | up to 30 days without activity or until logout |
| Blizzard game data | retrieved again at regular intervals (active characters more often); characters no longer provided are hidden (WoW Forever: deleted, see directory); immediate deletion and block on request |
| Retail character data in the account | until the account is deleted or the character is blocked |
| WoW Forever: assignment account ↔ character, Forever main and its portrait (not public) | until the character is no longer in your list at a later sync, 30 days without confirmation, until it is removed from the directory, or until your account is deleted; an empty or missing response from Blizzard deletes nothing |
| WoW Forever: time of the last sync per region | until your account is deleted |
| Own web analytics | 90 days |
| Guild in game: confirmed actions | 30 days |
| Deleted raid events | restorable for 30 days |
| Recruitment: contact details in a guild post | 90 days after the post expires or is switched off |
| Recruitment: conversations and applications | 180 days after the last activity; application with text and snapshot together with the conversation |
| Crafting plans | 30 days from plan date, content removed afterwards; deleted plans restorable for 24 hours |
| Forge simulations: jobs and results | 30 days; results immediately upon account deletion |
| Raid plans: draft and released versions | draft and the last 5 versions per boss and difficulty; older versions are deleted |
| Raid plans: pickup log (account, version, time) | deleted with the version; for a replaced version 30 days after it was replaced; with account deletion |
| Desktop app device token | 30 days, renews when used, at most 365 days |
| Desktop app connection request (computer name, version) | unconfirmed at most about 7 hours; once confirmed, kept with the device (until it is signed out or the token ends); deleted with your account |
| WoW Forever: directory of discovered characters and guilds | as long as Blizzard provides them; deleted after two “not found” results at least 24 hours apart or after 30 days without confirmation; immediately on request (block, also after a rename) |
| WoW Forever: hints for finding characters and guilds (not public) | unchecked ones after 30 days, checked ones 30 days after the check |
| WoW Forever: test character per region for the function check (name, Blizzard ID, guild; not public) | until replaced: after 7 days at the most, as soon as another suitable character is available; earlier on replacement (no longer provided, blocked, region downgraded) |
| WoW Forever: population (figures only, no names) | kept permanently as a daily history |
| WoW Forever: uploaded character data | until your account is deleted |
| WoW Forever: guide observations (raw reports, pseudonymised with a check value of the installation identifier, day of receipt and coarse network number) | 30 days; immediately on request (e-mail with the installation identifier from “/wcg info”) |
| WoW Forever: guide header details per installation (maps, experience per level) | 30 days after the last upload; immediately on request |
| WoW Forever: misuse limit of the guide (check value of the installation per account and network, call counters per device token and account, memory only) | at most 24 hours, never in the database |
| WoW Forever: daily counter of guide reports per account (day, count and a check value of the account ID and daily salt, not linked to the reports) | 3 days at the latest |
| WoW Forever: values learned together for the guide (numbers only, no personal reference) | as long as they are confirmed; deleted after 60 days without a new confirmation |
| WoW Forever: leaderboard details (professions, dungeons, time to 60; gold and mounts only with “Share gold”) | until your account is deleted; gold and mounts until “Share gold” is turned off |
| Share live: guild fight status (memory only) | 12 hours at most; a server restart clears it |
| Seen players (sightings) | 90 days after the last sighting; opt-out on request immediately (block list until revoked) |
| Guild in game: keystones and raid lockouts | 14 days after the last report |
| Guild in game: online list and presence (memory only) | 90 minutes or 10 minutes at most; a server restart clears them |
| Guild in game: raid night history (without names) | 180 days |
| Guild in game: readiness check | 14 days after the last report |
| Guild leadership: daily roster state (only character IDs from Blizzard's guild roster) for joins and departures | 90 days |
| Character page: Great Vault, crests, upgrades, season achievements | 60 days after the last report |
| Forge: state code from the addon (own character only, signed in) | 60 days after the in-game state; immediately with “Remove snapshot” or account deletion; without sign-in only in the browser tab |
| Character page: Mythic+ run debrief | 120 days after the run, at most 30 runs per character |
| Character page: running Mythic+ keystone (memory only) | until time limit + 15 minutes or 30 minutes after the end; a server restart clears it |
| Twitch link (channel ID, name, selection) | until you disconnect or delete your account; if Twitch no longer finds the channel, after 30 days |
| Twitch live status | overwritten every minute; stream details are deleted as soon as the stream ends |
| Twitch access keys | not stored, revoked immediately |
| Blocked Twitch channel ID (abuse) | until we lift the block |
| Combat logs and live data | without time limit as an archive per expansion; uploaders can only remove the link to their account, the report remains; on request a character is made unrecognisable in all reports, including future ones |
| Original log files (raw data) | 30 days after the report's first upload, once every fight has been evaluated |
| Donations: bookings (amount, fee, date, hashed reference) | permanently, without names; reference deleted on request |
| Database backups | 30 days |
| Email content | until the request is handled, at most 2 years (unless a legal retention duty applies) |
| Mail server logs (sender, recipient, IP) | 30 days |
| Mailbox backups | 30 days |
20. Your rights
You have the right to:
- access to your data (Art. 15 GDPR),
- rectification (Art. 16 GDPR),
- erasure (Art. 17 GDPR),
- restriction of processing (Art. 18 GDPR),
- data portability (Art. 20 GDPR),
- objection to processing based on legitimate interests (Art. 21 GDPR),
- withdrawal of consent with effect for the future (Art. 7 (3) GDPR).
To exercise these rights, write to kontakt@wowcore.io. We reply within one month (Art. 12 (3) GDPR). You can have your own WoW Forever characters removed yourself under “Remove from the directory” (section 7).
Deleting your account: you can delete your account yourself in the account settings. We then remove your links to characters and guilds, your crafting plans, your simulation jobs and results, your pickup log for raid plans, your devices and tokens, the character data uploaded for WoW Forever, your WoW Forever assignment with Forever main, portrait and sync times, and your Discord link. Your combat logs are unlinked from your account: we delete the account link and your entry as the uploader. The reports stay public with all fights and participants, and your characters remain in them as participants. Live data from the desktop app that is visible to your guild or the public also remains, without any link to your account; private live data is deleted. We delete your original files in them when the 30-day period ends. The combat logs remain in the archive until you or an affected person requests deletion; we then make the character unrecognisable in all reports (see “Deletion on request”). You can send such a request to kontakt@wowcore.io before or after deleting your account. Acceptances and declines for raid events belong to the character, not to the account: they remain in your guild's raid planning without any link to your account. On other devices your sign-in ends after 5 minutes at the latest.
We also delete a Twitch link (channel ID, names, character selection and live status) in this process.
21. Right to lodge a complaint
You may lodge a complaint with a data protection supervisory authority (Art. 77 GDPR). The authority responsible for us is:
The Hessian Commissioner for Data Protection and Freedom of Information (Der Hessische Beauftragte für Datenschutz und Informationsfreiheit), Wilhelmstraße 7, 65185 Wiesbaden, Germany. Phone +49 611 1408-0, poststelle@datenschutz.hessen.de, www.datenschutz.hessen.de
22. Changes
We update this policy when functions or the legal situation change. The current version applies. Last updated: 20 November 2026.
