Privacy

• First-party: set by this site, for this site (SameSite=Lax; Secure). No other site can read them and they are not shared with anyone. The rest of this list is about wf_you; the sign-in cookies are described under Accounts.
• wf_you holds settings, not an identity. There is no id and no date in it: two people who picked the same class, level and spoiler level have the same cookie.
• The site reads it in your browser, to draw the page in your class colour and to cover what you asked to have covered before the page first paints. Like any cookie, your browser attaches it to the requests it makes to this site; nothing on our side reads it, stores it or writes it to a log.
• It is never used to recognise you, to count you or to join one visit to another.
• If you chose these settings before the cookie existed, they were in browser storage. The first page you open moves them into the cookie once and removes the old keys.
• Clearing cookies for this site, or setting the three back to their defaults, removes it. With cookies blocked the settings still work, for the page you are on.

When you finish a build, copy its link, save it, or open a build somebody shared with you, the calculator may tell our server which class it was and which talents were picked, so we can show how often each talent is taken. That message contains the build and nothing else: no cookie, no account, no identifier, and nothing about you or your device. We do not keep IP addresses with the counts; an address is used for a moment to stop one person from counting a thousand times, then forgotten. We publish rates for a class only after 100 builds.

The site also counts four kinds of thing you do here, so we can tell which parts of the site are worth keeping and which buttons nobody finds. Each one is a number going up by one, not a record of your visit:

• A button pressed. Which named button it was ("the What's new pill", "Copy link in the calculator"), and nothing about the page you were on.
• A choice you made. The class you picked, the faction you picked, and the ten-level band your level falls in (60, or 50-59), never the exact level.
• A tool used. That the calculator, the spellbook, the atlas, the search box or the Classic comparison was used at least once while this tab was open.
• A section opened. The name of the part of the site, once per tab: "talents", "guides", "database". Which page you read inside it is not counted, ever.

What is never counted: what you type in the search box, which item, spell, quest or zone you looked at, the address of the page you were on, where you came from, your name, your email, your IP address, your country, your browser, your screen, or the time beyond the date. There is no identifier of any kind, so two counts are never known to be the same person and never known to be two. Nothing is kept that could be joined back together later, because nothing that could be joined is written down. Your answer to a cookie or consent banner is not counted either.

Those four are counted only if you say yes. In a build that counts them, a bar at the bottom of the page asks before anything is sent: Accept and Decline, the same size and the same weight, and Choose if you want to answer category by category. Nothing about what you do is sent or stored until you answer, and what you did before you answered is not kept anywhere to be sent afterwards. Your answer is kept in your browser, in localStorage, under wf_consent (the table above); it is the only thing that is written for this, and it holds your answer and the date of it, nothing else. Changing your mind is one click on Privacy choices in the footer.

The talent build count is not behind that question, and here is why: it holds a build code and a class, it writes nothing to your browser except a note to itself not to count the same build twice in this tab, and it carries no identifier, so there is nothing of yours in it to ask about. Builds are tallied anonymously whatever you answer; page and button counts happen only after Accept.

If your browser sends "Do Not Track" or "Global Privacy Control", all of it is off: not the builds, not the buttons, not the tools, not the sections. Nothing is sent, nothing is asked, and nothing is stored in your browser for it.

None of these messages carries the one cookie this site sets. Your browser attaches a first-party cookie to every request it makes to the site it belongs to, so these counts are sent in the one way that leaves it behind (credentials: 'omit'): wf_you never reaches a counter.

Every record page and every calculator has a "Wrong number?" form at the foot of it. When you send it we receive what you typed, the address of the page you were on, which record that page is about ("item 1913"), the game build it showed, and, if your browser runs scripts, the part of that address after the ? or #, which is the level, filter or build code you had picked, so the number you are reporting can be seen the way you saw it. If you pressed "Wrong?" on one line of an item's "Where to get it", the report also says which line that was and the figures it showed (a vendor and its price, a drop count), so we can find it without asking. We keep those so the page can be fixed. Its time is kept to the hour only; your IP address is used for a moment to stop one sender from flooding the form, then forgotten. The report text is also delivered to the site team's private Discord channel, so please do not put personal details in the message. The separate Email for a reply field is optional. Leave it empty to send anonymously. If supplied, it is kept privately with this report and used only to answer it, never for marketing, statistics or account matching. It is not included in Discord notifications, public corrections or credit. The site owner can retrieve it through a protected inbox. It is kept until the report is deleted or its reply address is cleared; removal is handled by the owner and does not run automatically. To remove the address, send feedback from the same page identifying the report, or use the contact form.

The name you may put in "Credit me as". That form has one optional field and one tick box, and they work like this:

• Optional. Leave the credit name and reply email empty to send anonymously.
• It is a handle, not an email. Up to 32 characters of plain text. An address (anything with an @ and a dot after it) or a web address is refused in this field by the form and by the server. Use the separate private reply field if you want an answer.
• Stored only if you tick the box. "Show this name next to the fix" is off unless you turn it on. With the box off the name is dropped before anything is written down: not stored, not forwarded, not logged.
• What it is used for, and nothing else. One line on the changelog next to the correction you found: "Caught by <your name>". It is never joined to any other report, never used to recognise you on a later visit, and never given to anyone.
• Nothing appears by itself. A name becomes public only when we publish that correction by hand, which is also when the fix goes out. If we never publish the catch, the name is never shown anywhere.
• Taking it back. Send the form again from the same page and say so in the message, and the name comes off the list and out of the store. You can also use the contact form on About.
• How long it is kept. With the credited catch, for as long as that correction is on the changelog, because the credit is part of the correction. A name from a report we never publish is deleted with the rest of that report when the store is cleared. Reports are not kept on a timer today; when they are, the rule will be written here.

From a talent calculator's Share menu you can publish a finished build to the list on Builds, and on a published build's page you can vote for it. There are no accounts, so neither of these is tied to you. Here is everything that is stored, and where.

• A published build. Its class, its build code, which game build's talent trees it was made on, the points per tree, the purpose you picked (leveling, dungeons, raid, PvP or none), the note if you wrote one, the date, and the hour it arrived. Not your name, your email, your IP address, your browser, a cookie or any identifier. The name it is listed under is made from the build itself ("Arms 31/20/0"), never typed.
• A note. Optional, one line, 140 characters. A person reads it before it is shown; until then the build is listed without it. Links, addresses and names to contact are refused. A note we turn down is deleted, not kept.
• A vote. One more in that build's count for the day, and nothing else: the stored row is the date, the build and a number. Who voted is not written down anywhere.
• One vote per build. Your browser remembers the builds it voted for and when (wowforever:voted:v1 and wowforever:voted-at:v1, in the table above). The server stops one address from voting for the same build twice in a day by keeping a scrambled form of the address (a keyed hash under a secret that is replaced every midnight UTC and never written to disk) in memory only. After midnight, or a restart, nobody can tell whether an address voted, including us.
• The bot check. Publishing and voting use Cloudflare Turnstile, the same check as the contact form. Its script loads only when you press Publish or Vote, and Cloudflare sees that request the way it sees any page it checks. The proof it hands back is checked with Cloudflare once and thrown away; it is never stored. We do not send Cloudflare your address.
• What the site shows. Each build's class, name, purpose, approved note, publish date and vote total, with the date the votes were counted. The count on the page moves when the site is next updated.
• Removal. Published builds carry nothing that says who published them, so there is no "my builds" to delete. If a build or note should come down, use the "Wrong number?" form on its page or the contact form, and we take it off the list.

None of these requests carries the site's cookie (credentials: 'omit'), and a browser that sends Do Not Track or Global Privacy Control can still publish and vote: nothing here is a measure of you.

Writing a comment, voting on one or reporting one needs a WoW Forever account. You open one by signing in with Battle.net, Google or Discord; there is no password here to lose. It is an account of this site only: it is not your Blizzard, Google or Discord account, and those services are not told what you do here.

• What we keep, per sign-in method. The provider's id for you (a number or a code that means nothing on its own), the email address the provider gives us and whether the provider has confirmed it (Google and Discord give one; Battle.net gives none), and the name the provider calls you (your BattleTag, your Discord name), which we offer as your display name. The day you first and last signed in that way.
• What we keep about the account. The display name you choose, whether you are a moderator, and, if moderation ever removed comments of yours, the penalty points and any posting suspension that followed.
• What we never keep. A password, the provider's access tokens (each is used once, to ask who you are, and then dropped), your IP address in any form, your browser's description, or the time of day you did anything finer than the hour.
• Email addresses are never shown and never used to write to you. They are compared, in one place only, with the short list of moderator addresses, and only when the provider confirmed the address. Two sign-ins with the same email address stay two accounts unless you link them yourself by signing in with the second one while signed in with the first.
• Sessions. Signing in sets the __Host-wf_session cookie (see Cookies); the server keeps a scrambled form of its value, so its own records cannot be used to sign in as you. Signing out ends that session everywhere it was copied.
• Deleting your account. The account menu at the top of every page has "Delete my account". It removes the account, every sign-in method and every session at once. Your comments stay in their threads as "[deleted]", with no name and no text, so replies keep their place; your votes are withdrawn.

Item pages, published builds and the talent calculators take comments. Reading them needs nothing; writing needs an account (Accounts). Here is everything that is stored, and where.

• A comment. The page it is on, the comment it answers if it is a reply, your account, the text, the date and the hour it arrived (and the hour of the last edit). Not your IP address (not even scrambled) or your browser.
• Public. A published comment is shown on its page under your display name, with its date and score, and is part of the page's HTML from the next site update, where search engines can read it.
• Checked first. Links, email addresses, @handles and a list of insults in eight languages are refused before anything is stored. Every comment and every edit is then read by an automatic check: its text, the page it is on and whether it is a reply are sent to Google's Gemini model, never your name, account or email. If the check fails or is unsure, a moderator decides. Your first comment always waits for a moderator; after one of yours is published, your next ones show as soon as the check passes them.
• Votes and reports. We keep which account voted which way on which comment, so you can take a vote back, and which accounts reported a comment, so one account counts once. After three reports a comment leaves the page until a moderator looks at it.
• The bot check. Writing uses Cloudflare Turnstile, as publishing and voting on builds do. Its script loads only when you write, and one check counts for half an hour.
• Removal. You can edit or delete your own comments; a deleted comment's text is erased, not kept. A comment moderation removes keeps its text, for the moderators only, so a mistake can be undone.

Three flows on this site ask for an email address. Feedback offers an optional private reply address, described under Build counts and reports. Another is the form on the simulator page, which is there so you can be told when the simulator or the recording addon opens; everything about it is below. The third is the contact form (the home page's Contact card, and "Write to us" on About), described under Contact. Apart from an account you open yourself to comment (Accounts), an address you type is the only personal data this site stores, and everything about the simulator form is below.

• What is stored: your address, which of the two boxes you ticked ("the simulator", "the addon"), and the date you sent it. That is the whole row. No name, no IP address, no country, no browser, no page you were on, no identifier, and no time of day.
• Why: to send you one message when the thing you ticked opens. Not a newsletter, not a digest, not an offer. If you ticked both, that is two messages, ever.
• Who else sees it: nobody. It is never shared, never sold, never handed to an advertiser or an analytics service, and it is not put into a mailing service today. It sits in this site's own small database on this site's own server.
• How to be removed: the same form. Tick Remove my address instead, type the address and send it, and the row is deleted. You do not need to write to anyone and you do not need an account.
• How long it is kept: until the announcement has been sent, and at the latest 12 months from the day you sent it. After that it is deleted whether the announcement went out or not.
• No confirmation email is sent today. Nothing arrives to say "you are on the list". The page says it on the page instead. The first message you get from us will be the announcement itself.
• The answer is always the same. The form answers the same way whether the address was stored, was already there, was removed, or was rejected. That is deliberate: an answer that differed would let anybody test whether a given address is on the list.

The form is only there in a build that was given an address to send to; today it may be absent entirely, and then the announcement signup is absent. Feedback and contact forms have their separate rules above.

We would like to know the boring things: how many people came, which pages they read, whether the talent calculator is actually being used. For that we use PostHog, a product analytics company in the United States. It is the only outside service this site loads, and it loads only if you say yes.

• It only runs if you accept. The bar at the bottom of the page asks first. Nothing is loaded and nothing is sent until you press Accept, and if your browser says "Do Not Track" or "Global Privacy Control" we do not even ask.
• It uses cookies. Your browser gets a random id so two page views can be seen as one visit. That id is not a name and we never attach one to it: we do not run accounts and we never tell PostHog who anybody is.
• What it sees: the pages you open, the buttons you press, the site that linked you here, your device and browser, and roughly where in the world you are, worked out from your IP address as the request arrives.
• What it never sees: what you type into the search box, what you write in a "Wrong number?" form, your email address, or the talent build code in the address bar. Those fields are marked so the tool skips them, and page addresses are rebuilt from a short list of allowed parts before anything is sent.
• How long. PostHog keeps events for as long as our plan says, which today is seven years for events and one month for any session recording. If you want yours gone sooner, ask us and we will have it deleted.
• Changed your mind? Privacy choices in the footer, any time. Decline and we stop it and clear its cookies from your browser.

This is for us, not for you: nothing it collects is shown on the site or sold to anyone. The numbers the site does show you, like which talents people take, come from our own counting described above, which uses no outside service at all.

Source links lead to Blizzard's own posts, and the Contribute card on the home page leads to this site's ko-fi page. Nothing is loaded from them until you follow one; after that, their own policies apply.

One other outside service has a part on this site, and it waits for you too: Cloudflare Turnstile, the bot check on the contact form. Its script is loaded only when you open that form, never on a plain page view, and from that point Cloudflare's own policies apply to what its check does.

Coming soon Hosting provider. Not chosen yet; this section will name it and say what its access logs keep.

The home page has a contact form (the Contact card at the foot of it; "Write to us" on About opens the same form). It asks for your email address and your message, lets you say which of four things it is about, and sends them with the address of the page you were on. Your address is used to answer you, and for nothing else: no list, no newsletter, no sharing. We read everything and reply within 24 hours. The message is delivered to the site team, so put in it only what the answer needs.

• The bot check. The form is protected by Cloudflare Turnstile so one program cannot flood it. The answer to the check is verified on our own server before your message is accepted, the proof is single-use, and it is never stored with your message. Your IP address is not sent to Cloudflare by us and is not written down here.
• What is kept: your address, your message, which of the four subjects you picked (or none), the page's address, the site build it was made from, and the day and the hour. No name unless you write one, no browser fingerprint of ours, no identifier, and nothing about your device.
• How long: 12 months at the outside, and sooner when the conversation is done. There is no account tied to a message to look it up with, so ask in any later message and it comes off early.

The form is only there in a build that was given an address to send to; today it may be dormant, with a "Coming soon" mark where Send will be. As with everything else on this page, this was written before the feature was switched on.

About this site · What we publish