Эта страница пока не переведена. Английская версия

Privacy policy

What ForeverDB collects, why, who else is involved, and your choices. Last updated 3 November 2026.

The short version

• You can use ForeverDB without an account. Browsing is measured with analytics, and the site shows ads served by NitroPay.
• If you log in, we get your Battle.net account ID and BattleTag from Blizzard. We never see your password. Nobody else ever sees the number in your BattleTag (the #1234 part): every page, email, Discord message and feed shows only its name. Only the site's admins see the whole BattleTag, to handle reports.
• The addons record public game data, the same things any player sees in the game and that sites like Warcraft Logs and Raider.IO show: character names, the game's player IDs, who looted what, guild rosters and combat logs. You can hide any of your characters yourself (Hide everywhere, in your armory on your profile), or ask us to.
• We never collect strictly personal data: no email addresses (except your own, if you give it to us for the newsletter or reminders), no IP addresses (only scrambled, salted codes to stop abuse), no Windows or PC user names, no account names, no other players' BattleTags and no chat text (except anonymous counts of public gold-spam adverts). Players the addon suspects of being bots are never named on the site.
• Combat logs are read in your browser. Nothing is uploaded unless you choose to upload it, and you can delete what you upload.
• If you send your characters (with the optional ForeverDB Uploader, from your WoW folder on foreverdb.net, or as a share code), your armory keeps a snapshot of each one's gear, talents, professions and the like. Characters stay private until you make one public, and you can delete them at any time.
• If you use the ForeverDB Helper's to-do with the Uploader linked, your lists (their tasks, notes, steps and links, and the character each list belongs to) are kept on your profile so you can see them on the site, with what you add or tick there until the game picks it up. Only you see them. Turn it off in the Helper's Settings, or delete it from your profile, at any time.
• If your guild uses ForeverDB's guild tools, the addon also records your guild's roster (names, ranks, levels and classes) to prove who's in it. Your characters' snapshots stay private from your guild too, unless you switch on "Share with my guild" for a character.
• Questions you type into Ask ForeverDB that need more than a lookup are sent, without your IP address, to the AI service ForeverDB uses (for example Anthropic, OpenAI or Google) to write the answer. Questions are kept without your IP address, to improve the site. Questions many players ask may become an entry in the FAQ, rewritten in our own words, never with who asked.
• If you sign up for the newsletter, we keep your email address and what you chose. Nothing is sent until you confirm your address, and you can unsubscribe or delete it at any time.
• The ForeverDB Discord bot answers its own commands and never reads your server's messages. For news in a channel it stores only the server's and the channel's IDs.
• The companion addon can spot gold spam and likely bots and help you report them. It never reports anyone itself (only Blizzard's own report window does, when you press Send), and the names of the players it flags stay on your PC: they're never uploaded. The only thing the Uploader may share about it is anonymous counts per realm and day: how many spam messages and suspects it saw, the gold-selling website domains and Discord invites those spam messages advertised, and the zones where players were flagged for farming. Never a name, a message or a personal contact.
• The companion addon can share auction house prices: the price and how many of each item were listed, the realm, which auction house and when. Never seller names: the addon never reads who sells or bids.
• If you post a tip, question or correction, it's public with your BattleTag's name (never the number) and, if you choose, one of your public armory characters. Posts are checked automatically, which can mean sending the text to the AI service ForeverDB uses, and you can delete them at any time.
• The ForeverDB Helper addon can share your dungeon runs anonymously: the dungeon, how long it took, the bosses killed and what dropped, the item IDs on your wishlist and where you found Forever's scrolls. Never your name, your group's names, your notes or your goals' titles (a note goes only if you press “Share as a public tip”, and it's checked before anyone sees it, without your name). Sending is optional, and up to you: the Uploader, your WoW folder on the site, or a code you copy from the game. Turn it off in the Helper's settings, and delete what you shared from your profile.
• The server status page checks that Blizzard's login server answers, from our server: nothing from you is involved. If you press “I can't play right now”, we keep the time, the reason you picked and a scrambled, salted code made from your IP address (not the address itself) for 7 days, only so one person can't report many times. The launch checklist's ticks are saved in your browser, and in your account when you're logged in; delete them by unticking them or by deleting your account. The beta errors page reads the log file you drop on it in your browser only: the file is never sent to us.
• ForeverDB's site administrators can view account data, what's uploaded (addon data, logs, Helper data) and private armory characters, to fix problems and handle reports. Each time they do, it's logged.
• If you turn on your player page (off by default), it shows only what's already public: your BattleTag's name (never the number), the public characters you tick, your published tips, answers and tier lists, and your characters' milestones. Logged-in players can follow your page, or a character you let them follow; nobody else sees who follows whom, and you can delete your account yourself on your profile.
• If you agree when it asks, the optional ForeverDB Uploader sends an anonymous check-in once a day (its version, the addon's version and whether CurseForge, Wago or the Uploader updates the addon) so we can count installs. It carries no account, name or address, and it stays off unless you say yes; you can change it any time in its settings. The companion addon tells other players' copies of ForeverDB in your guild and group its version number, so it can say when a newer one is out; switch that off in its settings (General).
• If you turn it on, the Uploader's Live on your realm sends anonymous live data while you play (rares killed, the zone you're in as a count, realm disconnects), read from two log files the game writes on your PC. Never names, your position or chat; it's off unless you turn it on.
• We don't sell personal data for money. NitroPay's ad cookies can count as "selling" or "sharing" under some US state laws, and you can opt out: see US privacy rights.

Who we are

ForeverDB (foreverdb.net, "we") is an independent fan site about World of Warcraft: Forever. It is responsible for the personal data described here. You can reach us through the contact page.

Public game data, and what we never collect

• Public game data. The companion addon may record character names, the game's player IDs (the character's ID in the game), who looted what, guild rosters and combat logs. These are public in the game: anyone in your group, guild or zone sees them, and sites like Warcraft Logs and Raider.IO publish the same kind of data. Where each of them goes, who sees it and for how long is set out in the sections below (for example, the loot log and group names in boss fights are seen only by the guild's verified members and blanked after 120 days).
• Hiding your character. If a character of yours shows up on ForeverDB and you'd rather it didn't, press Hide everywhere next to it in your armory on your profile (the character must be in your armory; when it's in public combat logs or came only from a share code, an admin first checks that it's yours, since anyone can add a character nobody has claimed). Not in your armory? Ask us through the contact page (topic: Privacy request), or use Report on its page, and an admin hides it. A hidden character is shown as "Hidden player" in combat logs, the replay, the rankings, guild rosters, attendance and loot logs, and left out of character search, character pages, the armory (its page, search and guild pages), player pages and the guild roster seen in the game, for everyone but you. We keep its realm and name (and a salted one-way code of its ID in the game) on the hide list for that. You can show it again with the same button, unless an admin hid it on a privacy request. Characters you upload yourself stay private until you make them public.
• Never collected. Strictly personal data: email addresses (only the account owner's own, if you give it to us for the newsletter or guild reminders: Battle.net login doesn't give us one), IP addresses (never stored as addresses: only salted, one-way codes to limit abuse, most of them held in memory for the day; the few that are kept are listed under How long we keep it), Windows or PC user names, account names (your WoW folder's account folder names are read only on your device, by your browser or by the ForeverDB Uploader on your PC, to find the files, and never sent), other players' BattleTags, and chat text, except anonymous counts of public gold-spam adverts (see Bots and gold spam below).
• Your BattleTag's number stays private. Wherever your account is named to anyone else (tips, questions, presets, tier lists, combat logs, player pages, emails, the Discord bot, feeds, search results and the site's structured data), only the name part of your BattleTag is shown, never the #number. Two players with the same name are told apart by their player page's link, never the number. Your own account menu shows the name too. Only ForeverDB's admins see the whole BattleTag, to handle reports and abuse.
• Bot suspects are never named. The players the addon flags as possible bots or gold spammers stay on your PC; the site shows only anonymous counts and never names anyone as a bot.

What we collect

When you browse

• Server and security logs. Our hosting (Railway) and our network provider (Cloudflare) process your IP address, browser details and the pages you request, to deliver the site and protect it from abuse.
• Analytics. We use Google Analytics, NitoPulse, Microsoft Clarity and Finteza to understand how the site is used: pages viewed, time on page, clicks, scrolling, form interactions, page speed and errors, your device type and approximate location. Clarity also makes heatmaps and recordings of how pages are used (mouse movement, clicks and scrolling; it hides what you type). Google Analytics sets cookies (named _ga); Clarity sets cookies (named _clck and _clsk); NitoPulse may use cookies or similar storage; Finteza sets cookies on foreverdb.net (named _fz_uniq, _fz_ssn and _fz_fvdt) and its requests go through our own address (foreverdb.net/fz/), which passes your IP address on to Finteza for approximate location. We don't keep it.
• Advertising. The site shows ads served by NitroPay. To choose and measure the ads, NitroPay and the advertising partners it works with (the companies named in its consent message and in our ads.txt) set cookies or similar identifiers and receive your IP address, your browser and device details, the page you're on and how you interact with the ads. They can use this to show ads based on your interests, and may combine it with what they collect on other sites. ForeverDB itself doesn't receive or keep it. We also use Awin for affiliate links: when you buy through a shop link, the shop may pay us a commission, and Awin sets cookies to record that. When NitroPay and Awin load is set out under Cookies and your choices.

If you log in with Battle.net

• Blizzard sends us your Battle.net account ID and BattleTag after you agree on Blizzard's login page. We store them to keep your account, and record when you last logged in. The number in your BattleTag is never shown to anyone else, and your own account menu shows only its name; ForeverDB's admins see the whole BattleTag, to handle reports.
• A session cookie (fdb_s) keeps you logged in for up to 30 days. The database keeps only a one-way hash of it. A short-lived cookie (fdb_oauth, 10 minutes) protects the login itself.

Combat logs

• The replay reads your combat log in your browser. Nothing leaves your computer unless you press Upload or turn on live logging.
• When you upload, we store the report's title, visibility and file name, and each pull you send: the names, realms, classes and IDs of the characters in it, what they did (damage, healing, deaths, abilities, positions) and when.
• Enemy players are never stored by name. Anyone the game marks as hostile to you (the other team in a battleground or arena, an enemy in world PvP, a duel opponent) loses their name and player ID in your browser, before the pull is shown or sent, and the server removes them again if a page sends them. They are kept and shown only as "Enemy 1", "Enemy 2" and so on, with their faction, race and class when the log shows them.
• Public reports and the characters in them appear in the rankings and on character pages (a character seen only in private or unlisted reports never shows in the character search or on a character page, and a hidden character shows as "Hidden player"). Unlisted reports can be opened by anyone with the link. Private reports are visible only to you. You can change this, or delete a report, from your profile at any time.

Addon data you share

• When you send the companion addon's saved file (from your WoW folder, below, or with the Uploader), we keep only these parts of it: the quests you were offered (the quest, the NPC and where you stood), the items that dropped around you (their tooltip, who dropped them and where), the beasts you saw, the trainers you opened (who, where, and what they offer), the vendors you opened (who, where, and what they sell at what price), the herbs, ore and chests you looted (what they gave and where), your characters' talent builds (the class, level and build, with a salted one-way code in place of the character), and the boss fights in dungeons and raids (the boss and instance, kill or wipe, when and how long, your level and the group's size and level range, what the boss dropped, the spells bosses cast, the enemies seen on the way, where you stood at the kill, and IDs the game gives that boss and that copy of the instance so several players' uploads of one fight count once; the character is again a salted one-way code). From Companion 0.18.0 a boss fight also carries the names of the characters in your group and who won each item, for your guild's loot log and attendance (see Guild tools below): only your own guild's members ever see them, they never appear in the site's public dungeon data (which stays anonymous counts), and we blank them after 120 days. With sharing on, the auction house prices you scanned go too (below). Your raid notes, rotation cards, talent plans and settings are never sent.
• The ForeverDB Uploader app sends the same parts of the same file, from your PC, after you play (and your characters' snapshots for your armory, below). You link it to your account once on foreverdb.net; it gets its own key, which we keep only as a one-way hash with the date it was linked and last used, and which you can remove from your profile at any time. The Uploader also downloads the addon and its data from foreverdb.net, which our hosting and network provider see like any other visit. The Uploader is optional: everything it sends you can send yourself, below.
• Hidden items (Uploader 2.3.0 and later). The Uploader also reads the game's hotfix cache (DBCache.bin in the game's Cache folder) and sends the rows in it for items, and for the quest, spell and talent tables Blizzard also hotfixes: the data Blizzard's server sent your game for things it hides from dataminers (an item's name, stats and the like) once you or someone else found one. Only rows our site doesn't have yet go, and only when the file changed. That is game data only, the same for every player who has the item: nothing personal, no character, account, realm, chat or file name, and nothing else on your PC. It goes with the uploads you already chose (linked to your account, or with “Send game data without an account” on), and you can switch it off on its own (“Send hidden item data from the game's cache”). We keep each row with only a salted, one-way code for who sent it and the game's version, use it to show those items on the site once two independent players (or our own PC) sent the same data (hidden items), and delete rows nobody else confirmed after 120 days.
• Send from your WoW folder (no app). On foreverdb.net/send, your profile and the upload page you can send the addons' saved files yourself. In Edge or Chrome you can choose your WoW folder once: your browser keeps the folder's handle and its permission in its own storage on your device (IndexedDB), not its contents, and may ask you again before the site can read it. When you press Send, the page reads only the addons' saved files, WTF/Account/<account>/SavedVariables/ForeverDB.lua and ForeverDB_Helper.lua, for each account in that folder, and nothing else in it. It reads ForeverDB.lua in your browser and sends only the parts listed above and the snapshots of the characters you tick, never the file itself: the rest of it (the addon's notes on suspected spam bots, your notes, rotation cards and settings) never leaves your device. Your own characters' names are taken out of the quest text first (the game writes your name into some quests' text), as the companion addon does itself from version 0.27.0. It notes each file's time, size and a one-way hash in your browser, so the next send only includes what changed and your profile can say when there's new data; it never reads or sends anything without a click. If you allow it, it also writes one small file into the Helper's folder (Interface/AddOns/ForeverDB_Helper/Data/Upload.lua: the time of the send), as the Uploader does, and nothing else. In any browser you can drop the folder or the files on the box instead; then nothing is remembered. Forget it in the box removes the folder from your browser. The armory characters you tick (and untick) are remembered in your browser's local storage, for the next send.
• The Helper's code (no app, no file). The Helper's Send to ForeverDB page shows its anonymous section, only what hasn't been sent yet, as a code you copy yourself. foreverdb.net/send reads the code in your browser, shows what's in it and sends it, like the folder box, only when you press Send. The code holds exactly the fields listed below and nothing else. The page keeps the code in that browser tab while you log in, and remembers which codes it sent (a short check value per code) to tell you if you paste one twice. Pressing I've sent it in the game changes only the Helper's own saved file.
• Bots and gold spam (Companion 0.19.0 and later). The addon scores public chat for gold spam and notices players who farm one spot for hours, on your PC only. The names of the players it flags, and the spam it saw, stay in the addon's saved file on your PC and are never sent to us: not by the upload page, not by the Uploader. The addon never reports anyone: its Report button opens Blizzard's own report window, and a report goes to Blizzard only if you press Send there. If you leave its setting on (it is by default), the Uploader sends only anonymous counts: per realm and day, how many spam messages and suspected bots the addon saw, and from Companion 0.20.0 the website domains and Discord invite codes advertised in those spam messages (for example goldshop.com, read only out of lines the addon already judged to be spam, never a Skype, Telegram or WhatsApp name or an email address) and the zones where players were flagged for long farming, as numbers. No names and no message text, ever. We keep them with your upload (a later upload raises them rather than adding to them, and an admin can set them aside) and use them only as totals across players: the gold-seller and bot tracker shows spam per realm and day, farming zones, and the sites that at least 3 different players reported and an admin approved. It never shows who reported what.
• Auction house prices (Companion 0.24.0 and later). While your auction house is open, the addon reads its listings (at most every 15 minutes) and keeps, per item, the lowest and the typical buyout price, how many are listed in how many auctions, the realm, which auction house (Alliance, Horde or a neutral one), the time and the game's version. It never reads or keeps who sells or bids. If its setting “Share prices with ForeverDB” is on (it is by default; a note says so the first time), the Uploader and the folder box send those prices and quantities with the rest; switched off, they stay on your PC. We keep each player's prices per realm, auction house and day with your upload (an admin can set it aside), delete them after 45 days, and show them only combined across players on the auction house page, item pages and the profession guides: never who scanned what.
• Paths you walk (Companion 0.31.0 and Uploader 2.4.0 and later). So that the addon's walking routes follow the ground players really use, it notes which 4-yard squares of the open world you walk across, the direction you left each one in, and whether you were swimming or indoors there. Nothing else: no times, no character, realm or name, and nothing in dungeons, raids or battlegrounds, on flights or boats, or while dead. The Uploader sends these squares with the rest of the file. Our server adds them to one shared map of walked ground per continent and keeps, for each square, only the directions walked and how many different players walked it (up to 8, as scrambled codes, never names): your own trail isn't stored. After an upload the addon forgets the squares it sent. Switch it off with “Learn the paths players walk” in the addon's Settings (Recording), or press “Forget my paths”.
• Anonymous game facts (ForeverDB addon with Observations, Uploader 2.5.0 and later). So that quest XP, objectives, creature levels and drop chances on the site and in the addon's planners come from what players really see, the addon notes small anonymous facts as you play: the XP each quest gave and at what level, a quest's objectives as the game shows them, creatures' levels and the XP a kill gave, how many creatures you killed and looted and what they dropped (for quest items also how many you looted while you still needed the item), and how fast you level (typical times per kind of objective and your running speed, by class and level). Numbers and game IDs only: never a name, chat or a position. Each install of the addon makes a random code for itself and numbers its batches of facts. The addon passes these batches to other ForeverDB players over a hidden addon channel in the game, and players whose PC runs the Uploader send them to us with their own upload (your own batches also go with your own uploads, from the Uploader or the folder box below); until then they wait in that player's saved file. The game itself shows the name of the character sending in that channel to every game client in it: ForeverDB never reads or keeps it, but someone sitting in the channel could link a character to its install's code. Our server keeps only a salted, one-way hash of the code: with the batch's number for 45 days, so a batch that two players pass on counts once, and with each fact (up to 8 per fact, 16 for loot and kills) to count how many different installs saw it, never who. The facts themselves are added into totals at once, never stored per player, and one install's facts are capped per day. A fact counts for the install that saw it, never for the player who passed it on. Switch it off in the addon's Settings: “Note anonymous game facts” stops recording them, and “Pass anonymous game facts to other ForeverDB players” stops passing yours and other players' facts over the channel (and with it the name the game shows there).
• Players you see (Companion 0.45.0 and later). So that foreverdb.net/population can show which classes and races WoW Forever players pick, the addon notes the players you target, point at, see a nameplate of or group with: their class, race and level, the number of their home realm and the day. Never a name, a guild, chat or where anyone is. Instead of the game's player number (the GUID) it sends a short scrambled code made from it, so the same player counts once however many players see them; our server hashes that code again with a secret before storing it, so it can't be turned back into the player number, and keeps up to 8 hashed install codes per player only to count how many installs saw them. Your own realm's name goes with them, so realm numbers can be shown by name. They travel with the anonymous game facts above (the same channel, the same Uploader, a daily cap per install). Characters you upload from your account count too, with their level, and only in the totals. Switch it off in the addon's Settings: “Players you see (for the population page)”.
• How you level (Companion 0.47.0 and later). So that ForeverDB's leveling route can show which zones and quests get players to 60 fastest, the addon notes how long each of your levels takes (only time you're actively playing: not while you're away, dead or resting in a city or inn), the zones you spend it in, the XP from quests and from the rest, the time in a group, deaths, your class, race and faction, and the order you hand your quests in with the time and XP between two hand-ins. Each character goes under a random code the addon makes on your PC and never ties to the character anywhere else: never a name, a realm, a GUID or where you are (only the zone's map number). Our server hashes that code again before it leaves for the builders, and keeps the rows for 400 days. They travel with the anonymous game facts above (the same channel, the same Uploader, a daily cap per install). Switch it off in the addon's Settings: “How you level (for the leveling route)”.
• Your finds without the Uploader (Companion 0.46.0 and later). If you don't run the Uploader, the addon also passes on, with the anonymous game facts above, what the Uploader would send: what vendors sell and trainers teach, where herbs, veins, chests, rares and quest givers are (the spots of those NPCs and objects, where you stood next to them), flight times, quest rewards, the items you loot and, for an item ForeverDB doesn't know yet, its tooltip without a crafter's name. Numbers and game IDs, never a name, chat or quest text; a rare sighting carries the hour, your side and your realm's number. Our server keeps them as one anonymous upload per install, under a salted hash of the install's code, and what only such uploads report shows on the site once another player or an account confirms it. With the Uploader on your PC nothing extra is sent this way: the Uploader sends it with your upload. Switch it off in the addon's Settings: “Also pass on vendors, trainers, gathering spots, rares, flight times, quests and items you find”.
• Route reports (Uploader 2.4.0 and later). When you press Report on a route in the addon, it saves the route, where it went from and to, the addon version and why you reported it (no names). The Uploader sends these reports so we can fix the route; only the site's admins see them.
• The ForeverDB Helper addon (sent by the Uploader 1.8.0, from your WoW folder, or as a code). The Helper times your dungeon runs and notes what drops, for you. If its setting “Share anonymous data to improve ForeverDB” is on (it is by default), it also keeps a separate anonymous section in its saved file (ForeverDB_Helper.lua), and the Uploader, the folder box (foreverdb.net/send, your profile, the upload page) or the Helper's code sends only that section: for each run the dungeon and its difficulty, when it started and ended, how long it took and whether you cleared it, the group's size, how many of the group had the Helper, and your level and class; for each boss kill the boss, how long the fight took, the wipes before it, the items that dropped (with how many, and whether you saw them in your loot window or in the group's loot messages, never who looted them) and a short one-way code made from the boss's ID in the game, so a kill recorded by several players of one group counts once (the ID itself isn't sent); each wipe's boss, how long it lasted and the boss's health; the item IDs on your wishlist, when you added each and when you got it; how many goals of each kind you have and the kinds of their tasks, done or not; and where you got Forever's scrolls (looted from which creature or object, bought from which vendor at what price, or from which quest, and where you stood). The folder box sends that section only: the rest of the file stays in your browser.
• Never sent: your name, your characters' names, your group members' names, your notes, your goals' titles or any other text. The one exception is a note you choose to share with Share as a public tip in the Helper: its text goes with the dungeon, boss or quest it's about, it always waits for a check by ForeverDB's admins (it's never published by itself), and if approved it's shown as from “a ForeverDB Helper player”, without your name. You can undo it in the Helper until it's sent. The site checks every upload and refuses anything that isn't numbers, IDs or the Helper's own codes, so a name can't slip in.
• What it's used for. We store it with your account (to count a group's kill once, to apply limits and so you can delete it) and use it only as totals: drop rates per boss, clear times, kill times, wipes and the most wanted items on the dungeon pages, each shown only once enough runs are in (for example 5 kills of a boss for its drop rates), and your scroll finds count towards Forever's scrolls. After an upload the Uploader (or the folder box, if you allow it) writes a small file into the Helper's folder (Data/Upload.lua: the time of the upload), and a code you mark as sent is noted in the Helper's own saved file, so the Helper can tidy up what's been sent. Sending the same data twice adds nothing: kills, loot, wipes and finds we already have count once.
• You decide. Turn sharing off in the Helper's Settings (Your data): it stops recording, clears what's waiting, and there's then nothing to send. Delete everything you've shared with Delete my Helper data on your profile at any time; deleting your account deletes it too.
• We store each upload with your account, the addon version and the time. The site's admins can see who uploaded what, and can set an upload aside or delete it.
• Without an account. You can also send the companion addon's game data without logging in: the folder box on foreverdb.net/send when you're not logged in, or the Uploader (2.1.1 and later) when it isn't linked to an account, if you say yes when it asks (its setting “Send game data without an account”, off until then; switch it off there any time). Then we keep only quests, drops, beasts, trainers, vendors and gathering spots, never your characters, a name, a BattleTag, your address or your talent builds; boss fights, spam counts, auction prices and the Helper's runs need an account and aren't taken. To tell different uploaders apart, your browser (fdb_anon_install in its local storage) or the Uploader makes a random code that's kept only there and sent in a request header, and we store only a salted one-way hash of it with each upload, and when that code was first seen. Your address is used only in memory, as a hash with a random key that's replaced every day and never written down (an IPv6 address by its network block), to limit how much one address can send, to let the admins pause anonymous uploads from it until the end of the day, and to count everything sent from one address on one day as one uploader; uploads that share a code are counted as one uploader too. We keep only the newest uploads from each code, and anonymous uploads go after 90 days. What only anonymous uploads report appears on the site once an account's upload or other anonymous uploaders confirm it. The admins can see these uploads (marked anonymous) and set them aside. Nothing ties them to you, so they can't be shown on your profile; to have them removed, contact us with the day and time you sent them. Logging in is still the better way: your uploads get your credit, and your armory and sync work.
• What goes on the site is combined from everyone's uploads and never names you: it only says how many players saw something. Boss fights appear only as totals per boss (kills, drop rates, abilities, kill times by level and group size).

Your armory (your characters)

• If you send your characters (the ForeverDB Uploader, the folder box with the characters you tick, or one character's share code on Import from game), we get a snapshot of each character: its name, realm, region, level, race, class, faction and gender, its guild and guild rank, the gear it wears (with enchants), its talents, professions and skills, reputations, the account's Legacy progress (Legacy Track, points, perks and challenges), how many mounts and companions it has, a few stats (health, armor and the like), the character's ID in the game and when the snapshot was taken. From Companion 0.17.0 it also sends the food, potions, flasks and other consumables in its bags (which items and how many), its resistances, and the guild roster the game shows it (each member's name, rank, level, class and how long they've been offline; see Guild tools below). It never sends your chat, friends, gold, the rest of your bags or anything else.
• Characters are private by default. Only you see them, on your profile, until you switch one to public. A public character gets its own armory page, shows up in the armory's search and in its guild's roster (which lists only members whose owners made them public), and search engines can find it. Switch it back to private and it's gone from all of those: anyone else gets “not found”.
• Anyone can report a public character or guild (we keep only a salted hash of the reporter's IP address, for a week, to stop floods of reports); ForeverDB's admins review reports and can hide a character or a guild's page, and a character whose snapshot looks impossible waits for their review before it goes public, with the reason shown to you on your profile.
• We keep each character's latest snapshot and up to nine before it, to show what changed. A character can belong to one ForeverDB account only: the first one to upload it.
• You decide. Switch the upload off in the Uploader (“Upload my characters to my ForeverDB armory”; it's on once you link the Uploader, because linking is already your choice), or untick the character in the folder box, or the snapshot itself in the addon's window. Delete one character, or all of your armory data, from your profile at any time; deleting your account deletes it too.

The Uploader's daily check-in and version notices

• What it sends. Once a day, when it checks for updates, the ForeverDB Uploader (from version 2.1.0) sends its own version, the companion addon's version, and whether CurseForge, Wago or the Uploader updates the addon. No account key, BattleTag, character, file or folder name.
• How it's counted. The Uploader makes a random secret and keeps it on your PC; the secret itself is never sent. Each day it sends only that day's code made from it, which changes every day. Our server uses the code only to count your PC once that day: it keeps a salted, one-way hash of it in memory, with a new random salt every day, and never writes the code or the hash anywhere, so one day's check-in can't be linked to another's. Your IP address is only used, the same way, to stop one address sending too many check-ins, and isn't stored.
• What we keep. One number per day, Uploader version, addon version and channel (for example "12 Uploaders 2.1.0 with addon 0.26.0 from CurseForge or Wago"), shown to the site's admins.
• Switching it off. Untick Send an anonymous daily check-in in the Uploader's options. That also deletes the secret; a new one is made only if you tick it again.
• In the game. The companion addon (from 0.26.0) shares only its version number, in hidden addon messages, with the copies of ForeverDB in your guild (when you log in, at most once an hour) and your group (when you join one), and says once a session when someone has a newer one. Like any addon message it reaches them from your character; the addon keeps no names from it. Switch it off with Tell me when a newer ForeverDB is out (Settings, General).

Live on your realm (the Uploader, from version 2.3.0)

• Off unless you turn it on. It's a setting in the ForeverDB Uploader (“Share live realm data while I play”), off until you tick it and say yes. Switch it off there, or with Turn off in the Uploader's Live row, at any time: from then on nothing is read or sent.
• What it reads, on your PC, only while WoW runs. Two files the game itself writes in its Logs folder. Connection.log: the realm you're connected to, the realm's name from the game's realm list, and when you disconnect, with the game's reason code (nothing else in it, such as account or address details). The newest WoWCombatLog file, which the game writes while combat logging is on (the companion addon's Live mode keeps it on in the open world; also off by default): from it only the zone you're in (a map number), the deaths of the rares and faction leaders on our list (whoever killed them) with where that creature stood, and the world buffs on our list that you receive. Everything else in those files, other players' names and your own character's name and position included, is skipped and never leaves your PC. The Uploader also reads which realm you played on last from the companion addon's saved file: a realm's name, never a character's.
• What it sends. Every 5 minutes, one small message (at most 4 KB) to foreverdb.net: the realm's address and name, whether you're online, the zone you're in, the rares and leaders killed (by the creature's ID, the time rounded down to the minute, and the creature's spot on the map rounded to 1%), the world buffs on you (by spell ID) and your realm disconnects (the time and the game's reason code). Never names, never your position, never chat, and never your account key or BattleTag: it isn't tied to your account. It carries a code that changes every day, made on your PC from a random secret that never leaves it (forgotten when you switch Live off), only so one install can't send too often; our server keeps it only as a hash in memory, with a new random salt every day. Your IP address is used the same way, in memory, to limit how much one address can send, and isn't stored.
• What we show. Only totals across players, per realm, on Live, the map and in the companion addon: rares killed or seen, with the time rounded to 5 minutes; how busy zones are, only as Quiet to Very busy, only when at least 3 players are in a zone and 10 on the realm, never split by faction, and 15 to 30 minutes late on PvP, Hardcore and unknown realms; realm restarts (many players disconnecting at once); and open dungeon groups. In return the Uploader writes your realm's live data into the addon's folder (Interface/AddOns/ForeverDB/Data/Live.lua) for its Live page: rares, zones, groups, auction price movers and realm events, no names.
• How long. Zone counts: 48 hours. Rare kills and realm events: 30 days, and the hash that tells two players' reports apart is deleted after 24 hours. Gathering counts, when they come, are held in memory only.

Guild tools

• What they are. A guild's private calendar, sign-ups, roster and gear check on ForeverDB, at its own address, for the guild's verified members only. Nothing in them is public or in search engines.
• How we know who's in a guild. From the armory snapshots: each character's guild and rank, and the guild roster the addon saw (every member's name, rank, level, class and days offline, and the character's ID in the game). A roster lists guildmates who may not use ForeverDB; we use it only to check who's a member and to show the guild's own verified members who hasn't installed the Companion yet. We keep only the latest roster from each character, and replace it with the next.
• Share with my guild is off for every character until you switch it on. Then your guild's verified members see that character's latest snapshot (gear, talents, professions, reputations, Legacy) and whether it's ready for their events (green, amber or red). The reasons behind that colour (item level, empty slots, enchants, the raid's requirements) go only to the guild's officers and to you. Without it they see only its name, class, level and rank, which are in the game's own guild roster anyway, and that it uses ForeverDB's guild tools.
• Your bags. The consumables in a character's bags (flasks, food, potions) are shown to its guild's officers only if you switch on Share my bags with my raid leaders for that character (off until you do; you can switch it off any time). We store that choice. You always see your own.
• Raid plans. For a raid event, officers can save its groups, a bench, the raid's requirements (item level, enchants, flasks, food, potions, resistances), boss assignments and notes; we store them with who saved them last, and they go with the event (12 months). Assignments and notes name characters. The guild's verified members see the groups and assignments (they need them to raid); officers can copy them as a note for raid addons, as a code for the ForeverDB Companion, or as a picture to post in their own Discord channel. None of it is public or in search engines.
• Events and sign-ups. We store the events officers post, and your sign-ups (character, role, status, comment) and officers' confirmations and groups. Every verified member of the guild sees them.
• Discord. If an officer pastes a Discord webhook, new events and reminders (the event's title, time, notes and how many signed up, never email addresses) are posted to that channel, and Discord's own privacy policy applies there. The webhook address is stored and never shown back in full.
• Reminder emails are off until you ask for them. We keep your address, whether you confirmed it, your time zone (for the times in the email) and which reminders went out. Nothing is sent before you confirm, every reminder has a link that stops them, and stopping them deletes your address. They're sent through the same email provider as the newsletter.
• Soft reserves, the loot log and attendance. We store the reserves members make on an event (character and item) and the rules officers set for them, and a loot log: which item dropped from which boss at which event, who won it (a character name, from the Companion's record of the kill or typed in by an officer), whether a reserve was honoured and officers' notes. The log is filled from boss fights uploaded by the guild's verified members that match one of its events (same instance, around its time) or where most of the group is the guild. Attendance is worked out from sign-ups, those uploads and uploaded combat logs of that instance at that time, and officers' corrections are stored. The names can include players in your group who aren't in the guild. All of it is visible to the guild's verified members only, never public, never in search engines.
• Your calendar feed is a private link with a random code; anyone who has it sees your guilds' events, and a new link stops the old one.
• The guild's public page. If the Guild Master or an officer sets up the guild's page, we store what they chose: the banner (game art or a crest of game icons, never an upload), a short about text, the guild's Discord invite link, play style tags, language, time zone, which sections show and which account saved it last (for moderation). The about text and the invite are checked like recruitment posts (our rules, an automatic check, and ForeverDB's admins) and show only once approved; they're public and in search engines, so don't put personal details in them. The page shows only counts and dates of the guild's boss kills, its weekly events from the calendar (never their notes), its recruitment post and members whose own armory page is public; hidden characters are never named there. Officers can change or take the page down any time, and it goes when the guild does.
• The addon's saved file can be edited, so membership can be faked by someone determined; that's why sharing is your choice, officers can remove members, and ForeverDB's admins can hide a guild.

The contact form

We store your message, the topic, the page you were on, and your name and email address if you give them (both are optional). Screenshots you attach (up to 3) are saved again as new pictures without their hidden data (such as the location, the camera, or the time a photo was taken), are seen only by the ForeverDB team (the site's admins), are never shown on the site or on the corrections log, and are deleted with your message. To stop spam we keep a salted, one-way hash of your IP address, never the address itself. Messages are deleted after 12 months at most. Messages are private: only the site's admins read them, and our email replies go only to you. If you answer one of our emails, your answer (its text and the address it came from) is stored with the conversation and kept as long as it; attachments are never kept, and automatic replies are ignored. The one exception is a Wrong or missing data report when you leave Show my report on the public corrections log ticked: we may then put the text of your report and the page it's about on the public corrections log, shown as from "a player", with any email addresses, phone numbers or BattleTags in it removed. Your name, email address, account and IP hash are never shown. Untick the box to keep your report private; messages on any other topic always stay private. To have a report taken off the log, ask us through the contact page.

The newsletter

• What we store. Your email address; what you chose (the weekly digest, big news or both); whether it's waiting for confirmation, confirmed or unsubscribed; a record of your consent (when you ticked the box, the exact wording you agreed to, and the page you signed up on); your ForeverDB account, if you signed up while logged in; and a salted, one-way hash of your IP address (never the address itself), only to stop abuse. Logging in with Battle.net doesn't sign you up: Blizzard doesn't give us your email address.
• Why. To send you the newsletter you asked for. The legal basis is your consent, which you can withdraw at any time.
• Confirmation first. Each address gets one email with a link to confirm it, and only confirmed addresses get newsletters. If you don't confirm, you won't get any newsletters, and the address is deleted 30 days after that email.
• Unsubscribe or delete it. Every email has a link to change what you get, unsubscribe or delete your address. If you signed up while logged in, you can do the same on the newsletter page. Before our first email you can also ask there to remove an address: it's marked straight away and gets no newsletters, and the only email it will get is one link to confirm the removal. Or send a privacy request through the contact page.
• Only ForeverDB's admins can see or export the list. We never sell it or share it, except with the sending service that delivers the emails.

The newsletter's emails are sent through our email provider, currently 20i (Stackmail). It receives your email address and the emails we send you, only to deliver them.

Ask ForeverDB

Ask ForeverDB answers questions from the search box. A plain lookup (a name, where something is, what drops it) is answered on our own server from ForeverDB's data. A question that needs more is sent to the AI service ForeverDB uses, for example Anthropic (Claude), OpenAI (GPT) or Google (Gemini), whose model writes the answer from ForeverDB's own data. If that service is down, the question may go to the next one we've set up. We send it only the question and the ForeverDB data needed to answer it: not your IP address, your account or anything else about you. So please don't type personal details into a question.

We store each question with its answer, the lookups it made, what it cost and whether you rated it, without your IP address or account (only whether you were logged in), for up to 12 months, to improve the site: the questions people ask most, and the ones it couldn't answer, show us what's missing. To apply the daily question limit we count questions per account, or per salted one-way hash of your IP address that changes every day, and delete those counts after two days. An answer to the same question may be shown to others who ask it within a day.

Tips & questions

• What's public. Your post's text, when you wrote it, the game build it was written on, the page it's on, its votes, and your BattleTag's name without the number. If you pick one on your profile, one of your public armory characters shows next to your name.
• What we keep with it. Your account, the results of the checks, and any reports. Votes are one per account: we store who voted, but show only the totals. Reports, and who sent them, are seen only by the site's admins.
• Checks. When you post, the text is checked by our own rules and, where it's switched on, by the AI service ForeverDB uses (the same one as Ask ForeverDB), without your account or IP address, to catch spam, abuse and personal information. A post the checks aren't sure about waits for an admin. Admins can hide a post (you see why) or delete it, and can stop an account from posting.
• ForeverDB's automatic answer. A question may get an automatic answer from Ask ForeverDB, always shown as ForeverDB's, never as a person. Its text goes through Ask ForeverDB like a question typed in the search box.
• Corrections. A correction is also listed on the public corrections log, with your BattleTag's name (never the number), its status, what we changed and our reply (posted under your correction as "ForeverDB team"). You can choose to be shown there as anonymous. If you delete your correction, its text and your name leave the log; what we changed stays, as a record of the fix.
• Deleting. You can delete your posts at any time, on the page or on your profile.
• Posting rules. Be useful, stay on WoW Forever, be kind, and don't post personal information (email addresses, phone numbers, other people's BattleTags). Links to other sites than ForeverDB, Blizzard and YouTube are removed. The full rules are on the Tips & questions page.

Group finder and guild recruitment

• What's public. A group finder post (what it's for, region, realm, faction, ruleset, levels, roles, your note and the character name, class and level you post with), a guild's recruitment post (written by its officers) and a looking-for-guild profile are shown to everyone. Your BattleTag isn't shown on any of them. Group finder posts and profiles show the character you pick, which can be one of your private armory characters: posting it is your choice.
• Applications. When you apply to a guild, your message and the character you pick go to that guild's officers: into its guild tools, and posted in its Discord channel (through the ForeverDB bot or the guild's webhook). Officers see your answer status; you see theirs, and the name of the officer who accepted you so you can whisper them.
• Checks and reports. Posts are checked like Tips & questions: the same rules, the same automatic AI check (the text is sent to the AI service, without your name) and the same reports; admins see who posted, to handle reports and bans.
• Deleting. You can close your group finder posts, remove your profile and withdraw an application at any time; officers can close their guild's post.

Player pages and following

• Off by default. Your player page (foreverdb.net/u/ followed by a link we make from your BattleTag's name and four random characters) exists only once you switch on Turn on my player page on your profile. Switch it off and it's gone for everyone at once.
• What it shows. Your BattleTag's name (never the number), your chosen flair character, "member since" (month and year), the characters you tick (only public ones, and only yours), your approved tips, questions and answers (whether an answer was accepted, never who asked), corrections ForeverDB confirmed, your published tier lists, and your characters' recent milestones. There's no free text: no bio and no chosen name.
• Never on it: the number in your BattleTag, characters you don't tick (so your alts stay apart unless you choose otherwise), group finder and recruitment posts, ForeverDB Helper data, your Companion uploads and boss fights, combat logs, auction house scans, bot and spam counts, guild tools, votes, reports and Discord.
• Milestones. When a character is uploaded we note, as IDs and numbers and the day only, every fifth level, reaching the level cap, learning a profession or reaching 75, 150, 225 or 300 in it, a new Legacy challenge, reaching Honored, Revered or Exalted, and the first epic item it equips. Nothing else (no gear swaps, talents, guild or time online). They're noted for every character, but shown only while the character is public, on your page or followable, and "Post its milestones" is on. Switch a character to private and its milestones disappear at once.
• Following. Logged-in players can follow your page, or one public character you let people follow (the tick Let people follow it; characters made public before player pages arrived aren't followable until you tick it). What they follow shows in their own feed, which only they can see. Nobody, you included, sees who follows whom: you see only a rounded count ("a few", "about 10"). Nobody is told when someone follows them.
• Your choices. Untick a character, switch milestones off per character, Hide my page from feeds, Remove all followers, or Change the link (the old address stops working at once, once a day). Unfollowing is always allowed.
• Search engines. A page that's on and has at least one public character or post can appear in search results and our sitemap. When you switch it off or change its link we ask search engines to drop it. Your feed is never indexed.
• Reports and moderation. Anyone can report a player page (offensive name, impersonation or something else). A page three players report is hidden until an admin checks it, and ForeverDB's admins can hide a page with a reason you see on your profile. Reports are deleted 30 days after an admin has dealt with them, and at once when the page's account is deleted; logged-out reporters are counted by a salted hash of their IP address.
• Deleting your account. On your profile, Delete my account (you type DELETE to confirm) deletes your account, your player page, your follows and the follows of you, along with the rest of your account's data as described here. Your public combat logs can stay without your name, or be deleted too. Owners' accounts can't be deleted this way, and while an account is suspended or its page is held for review, write to us on the contact page instead.

Races and leaderboards

• What's on them. The launch race on the leaderboards ranks characters by when your uploads reached us: the first to each level, the first boss kills and the fastest dungeon clears. A mark keeps the character's realm, class, race and faction, the level, boss or clear time, when it reached us, and the time the game wrote in your upload (shown as "claimed"). Marks are a record book: they're kept until you delete the character or your account.
• Who is named. Characters you've made public are on the boards by name, unless you untick Show this character in races and leaderboards (on the leaderboards page, logged in) or set Races to Guild or Off under Who sees what on your profile. A character that isn't public, is hidden, or that you took off the boards still counts, shown as "a hidden player"; the verified members of its own guild see its name, unless you chose Off for Races or an admin hid it. Clears name only the members who are on the boards by name; the rest of the group is "+N players".
• Never on them: your BattleTag, your account, your guild's name, your IP address, or anything from an anonymous upload (those never enter the race).
• Keeping it fair. Results that look impossible (too fast, a time before the race opened, a character held for review) are held for a ForeverDB admin and never shown; an admin can also strike a result, which is kept with the reason. Boss kills and clears come from the Companion addon's boss fights (above); ForeverDB Helper runs don't feed the leaderboards.

Posts on Blizzard's forums

The community page counts the public posts in the WoW Forever sections of Blizzard's official forums. To count them we keep each post's text, time and thread, and the class and race of the character shown with it, on the computer that builds the site, with a one-way code in place of the poster's name. To judge the mood, the text of a sample of posts (never who wrote them) is read by Claude, Anthropic's AI. We publish only totals and the titles of the busiest threads, never a post's text or who wrote it. To have your posts left out, send a request through the contact page.

ForeverDB tooltips on other sites

Other sites can show our item and spell tooltips with one script. When you hover one of their ForeverDB links, your browser asks foreverdb.net for that item or spell, so our hosting and network provider see a request like any other visit. The script sets no cookies, stores nothing and has no analytics or ads.

The ForeverDB API

If you use the ForeverDB API, we record each key's use under your developer ID: per day, the endpoints and things asked for, the website and kind of program the requests came from, and the country Cloudflare gives. Never IP addresses. We keep it for 90 days, to keep the limits fair, check that the data is credited and stop abuse.

The ForeverDB Discord bot

• The ForeverDB bot answers its own slash commands in the Discord servers that add it. Discord sends us each command with the server, channel and user IDs and your Discord username, like any Discord bot gets; we use them to answer and don't keep them. The bot never reads your server's messages.
• News subscriptions. When someone with the Manage Server permission subscribes a channel to ForeverDB news, we store the server's and the channel's IDs, which news they picked, and which items have been posted there, so nothing is posted twice. Nothing about the person who set it up. It's deleted when they unsubscribe; a channel the bot can no longer post to is paused.
• Questions with /ask are handled like Ask ForeverDB's questions on the site (below): kept without your Discord name or ID. The daily limits use a salted one-way code made from your Discord ID and the day, and a count per server made the same way from the server's ID.
• /character only shows characters their owners made public on the armory. Lookups (items, spells, quests and the rest) aren't stored.
• Linking your Discord account (optional, from your profile) lets the bot sign you up for your guild's events and post to the group finder as you. We store a salted one-way code made from your Discord ID (not the ID itself), your Discord username (shown only to you on your profile), when you linked, and the character and role you picked for each guild's sign-ups. Unlink it on your profile at any time; it's deleted with your account.
• A guild's calendar in Discord. When an officer links a channel with a code from guild tools and someone with Manage Server confirms it in Discord, we store the server's and channel's IDs and the channel's name, who linked it, and which message shows which event. Sign-ups made with the buttons show your character's name in that channel, as they do in guild tools.
• The raid calendar in Discord (optional; officers turn it on in guild tools). Officers can plan, change and cancel the guild's events from Discord (/event create, edit, cancel) and members see their sign-ups with /calendar; that uses your linked account as above and stores nothing more. The live calendar card stores the ID of its message and its channel, and whether it's pinned. The mirror into the server's Events tab stores, per event, the ID of the matching Discord scheduled event, which side made it and which changed it last, and when. Events made in the server's Events tab become events in the guild's calendar (title, time and description, marked as made in Discord). Who made one is matched to a ForeverDB account only through the one-way code of a linked Discord account, and only an officer's character name is shown; the Discord ID isn't kept. The card and the scheduled events show what guild tools already show members: event titles, times and sign-up counts by role, never names.
• Group finder channels. A server can have new group finder posts shown in a channel (/lfg subscribe): we store the server's and channel's IDs, the filters, and which posts went there.
• Link codes are stored as a one-way hash, work once and expire after 15 minutes.

Supporter memberships

• If you join ForeverDB's membership on Buy Me a Coffee, Buy Me a Coffee takes the payment under its own privacy policy. It tells us when a membership starts, renews, pauses or ends, with the member's email address and name. We keep only a salted one-way hash of the email and until when the membership runs: never the address, the name, the amount or a note.
• To get the perks, you link the membership on your profile: you type the email you used, we send a one-time code to it through our email service, and your account keeps the same one-way hash. Unlink it on your profile at any time.
• If you type /supporter in the ForeverDB Discord, we keep your Discord user ID with the link while you have the Supporter role, so the bot can take the role back when the membership ends. It's deleted with the role.
• The supporters list on the About page shows your BattleTag's name (never the number) only if you tick the box on your profile.

Stored on your device

Some settings, such as your map pins, planner setups and display choices, and your privacy choice (fdb_consent) are saved in your browser's local storage, and, if you use them, the WoW folder you chose for sending (in IndexedDB) and what was last sent from it (each file's time, size and a one-way hash), which armory characters you ticked, and the check values of the Helper codes you sent. They stay on your device and aren't sent to us. Not logged in, the folder box also keeps a random code (fdb_anon_install) that goes with each anonymous upload; we keep only a salted hash of it.

Cookies and your choices

The first time you visit, you're asked once what you allow. Logging in (fdb_s), security and your saved settings are strictly necessary, so they're always on; everything else is your choice.

• In the UK, the European Economic Area and Switzerland, NitroPay's consent message (an IAB TCF consent tool) asks what you allow: advertising (NitroPay and its partners, and Awin's affiliate cookies) and analytics (Google Analytics, Microsoft Clarity, NitoPulse and Finteza). Ads are personalised only if you agree. Until you allow analytics, Clarity, NitoPulse and Finteza don't load and Google Analytics runs without cookies; Awin loads only with advertising allowed.
• If NitroPay's message can't load there (an ad blocker can stop it), ForeverDB's own popup asks about analytics and advertising instead.
• Everywhere else, ForeverDB's popup asks about analytics and advertising. They're on unless you turn them off. With advertising off, NitroPay's ads and Awin don't load at all. If your browser sends a Global Privacy Control signal, we treat it as advertising turned off.

You can change your choices at any time with Privacy and cookie settings at the bottom of every page, which opens the same message you were asked with. ForeverDB's popup asks again after 12 months; NitroPay's message asks again when its rules say so. You can also block or delete cookies in your browser settings; the site keeps working, though you'll be logged out.

Why we use your data (UK GDPR)

• To provide what you ask for (your account, your uploads, your tips and questions, answering your message): performing our service to you.
• To run, secure and improve the site: our legitimate interests, which we balance against your privacy. This includes checking posts in Tips & questions for spam and abuse, and acting on reports.
• Analytics and advertising cookies: your consent, where the law requires it.
• The newsletter: your consent, which you can withdraw at any time by unsubscribing or deleting your address.

Who else processes data

Railway (hosting and database), Cloudflare (network and security), Google (Analytics), NitroPay (advertising, with the advertising partners it works with), Awin (affiliate links, with advertising allowed), NitoPulse (analytics), Finteza (analytics), Microsoft (Clarity analytics), the AI service that writes Ask ForeverDB's answers and checks posts in Tips & questions (for example Anthropic, OpenAI or Google), Anthropic (reading the mood of public forum posts), Blizzard (Battle.net login) and Discord (for the ForeverDB bot, in the servers that add it). Some are based in or process data in the United States; they're bound by their own terms and data protection commitments. We don't sell personal data for money. Letting NitroPay and its partners use cookies for ads based on your interests can count as "selling" or "sharing" personal information under some US state laws: see US privacy rights for your choices. Buy Me a Coffee runs supporter memberships and their payments. We don't share personal data with anyone else, unless the law requires it.

The newsletter is sent through 20i (Stackmail), which receives your email address to deliver it.

How long we keep it

• Your account: until you delete it (Delete my account on your profile) or ask us to. Sessions expire after 30 days.
• Addon uploads, and the boss fights and anonymous spam counts (with the advertised sites and farming zones) that came with them: until you or an admin delete them, or your account (they're deleted with it).
• Auction house prices that came with an addon upload: 45 days, or until the upload or your account is deleted.
• ForeverDB Helper data (runs, boss kills and their loot, wipes, wishlist and goal counts, scroll finds): until you delete it (Delete my Helper data on your profile), an admin deletes it, or your account is deleted. Your wishlist and goal counts are replaced by each upload. Tips you shared from the Helper: until you or an admin delete them.
• Armory characters and their snapshots: until you delete them or your account. Switching the upload off stops new snapshots.
• Guild tools: each character's latest guild roster until the next one replaces it or the character is deleted; events and sign-ups (with their reserves and attendance corrections) for 12 months after the event; loot log entries for 12 months; the group and winner names in uploaded boss fights for 120 days; a guild's settings (with its Discord webhook) while any of its members is on ForeverDB; your reminder email address until you stop the reminders.
• Uploader check-ins: daily counts per version and channel, with nothing that identifies an install, kept to show how ForeverDB is used. The daily codes' hashes are held in memory only and dropped every midnight (UTC).
• Live on your realm: zone counts 48 hours; rare kills and realm events 30 days (the hash that tells reporters apart is deleted after 24 hours); the daily codes' hashes and IP hashes are held in memory only.
• Uploaded reports: until you delete them, or your account.
• Player pages: until you switch yours off or your account is deleted. Character milestones: 60 days. Follows: until you or the other player remove them, or either account is deleted. Reports on a player page: until they're handled.
• Tips, questions, answers and corrections: until you delete them. If your account is deleted, they stay without your name (shown as "a former player"); your votes, reports and choice of character are deleted with it. Pages waiting to be sent to search engines are kept a few minutes.
• Contact messages: up to 12 months. A report you agreed to show on the corrections log stays there (its text and page only) until you ask us to remove it.
• Newsletter: until you unsubscribe (the address is then deleted 30 days later) or delete it. An address that isn't confirmed within 30 days of our confirmation email is deleted. The IP hash is blanked after 30 days; signup attempts (as salted hashes, for rate limits) are kept two days.
• Ask ForeverDB questions and answers: up to 12 months, without IP addresses or accounts. Daily question counts: two days.
• Discord bot news subscriptions: until the server unsubscribes (with the list of items posted to the channel). /ask counts per Discord user and server: two days.
• Group finder posts: deleted a week after they expire or are closed. Recruitment posts: while the guild's officers keep them (they're marked expired 30 days after the last save); looking-for-guild profiles: deleted 30 days after they expire. Applications: 90 days after the officers answer (or 180 days if they never do). Reports on them: until they're handled.
• Discord links: until you unlink (your account) or the guild's officers unlink (a channel); group finder channels until the server unsubscribes. The calendar card's message ID: until officers turn the card off or unlink the channel. Scheduled event IDs: with their event (12 months after it happened), or sooner when officers turn the mirror off.
• Analytics and advertising data: as set by Google, NitoPulse, Finteza and Microsoft (Google Analytics keeps event data for 14 months at most).
• A supporter membership's hash and dates: while it's linked, and for a year after it ends. The link on your account: until you unlink it or delete your account. The webhook's event log (what happened, never an email): 90 days.

Your rights

You can ask for a copy of your data, have it corrected or deleted, object to how we use it, or withdraw consent at any time. You can delete your account yourself with Delete my account on your profile. Otherwise, send a request through the contact page (topic: Privacy request); if you have an account, send it while logged in so we can match it to you. You can also complain to the UK's data protection regulator, the Information Commissioner's Office.

US privacy rights

If you live in California or another US state with a privacy law (such as Virginia, Colorado, Connecticut, Texas or Oregon), you have these rights as well. This section gives the disclosures the California Consumer Privacy Act (as amended by the CPRA) asks for.

• What we collect, and from where. In the last 12 months: identifiers (your Battle.net account ID and BattleTag if you log in, your email address if you give it to us, and the cookie or device identifiers and IP addresses our analytics and ad partners receive); internet activity (the pages you view, how you use them and how you interact with ads); and approximate location (the country or region your IP address points to). They come from you, your browser and device, Blizzard when you log in, and the uploads you send, as set out above.
• Why. To provide and secure the site, to understand how it's used, and to show ads, as set out in What we collect and Why we use your data.
• Selling and sharing. We don't sell personal information for money. NitroPay and its advertising partners do collect identifiers and internet activity through cookies on ForeverDB to show ads based on your interests, which California law can count as "selling" or "sharing" and other states call "targeted advertising". Our analytics partners receive the same kinds of data to measure the site. We don't use or disclose sensitive personal information, and we don't knowingly sell or share the personal information of anyone under 16.
• Opting out. Use Do Not Sell or Share My Personal Information at the bottom of every page (in California it's NitroPay's link), or turn Advertising off in Privacy and cookie settings. Either way, NitroPay's ads stop loading in that browser. We also honour the Global Privacy Control signal as an opt-out.
• Your other rights. You can ask to know what personal information we have about you and get a copy, have it corrected or deleted, and you won't be treated differently for using these rights. Send a request through the contact page (topic: Privacy request). We check it's you by matching the request to your account or to details only you would know, and answer within 45 days. Someone you authorise can make a request for you, with your signed permission.
• How long we keep it. As set out in How long we keep it, above.

Children

ForeverDB isn't directed at children under 13, and we don't knowingly collect their data.

Changes

If this policy changes, the new version will be posted here with a new date.