Esta página aún no está traducida. Versión en inglés

Privacy policy

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

The short version

• You can use ForeverDB without an account. Browsing is measured with analytics, and the site shows ads from Google.
• If you log in, we get your Battle.net account ID and BattleTag from Blizzard. We never see your password.
• 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 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.
• 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.
• 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.
• We don't sell personal data.

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.

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 and Microsoft Clarity 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.
• Advertising. The site shows ads from Google AdSense. Third-party vendors, including Google, use cookies to serve ads based on your prior visits to this website or other websites. Google's use of advertising cookies enables it and its partners to serve ads to you based on your visits to this site and/or other sites on the internet. You can opt out of personalised advertising in Google's My Ad Center, and learn more in how Google uses information from sites that use its services.

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.
• 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.
• Public reports and the characters in them appear in the rankings and on character pages. 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. 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.
• 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 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.
• 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.
• 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.

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, the consumables in its bags) and its readiness for their events. 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.
• 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 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). 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.

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.
• 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.

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 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.
• 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.

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. Where Google's consent message asks, Google keeps your answer in its own cookie.

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, Google's consent message asks. Google requires a Google-certified consent tool that uses the IAB Transparency & Consent Framework for ads there, and its message is one. Your answer covers the ads and ForeverDB's analytics (Google Analytics, Microsoft Clarity and NitoPulse), which runs only if you allow storing and accessing information on your device, measuring content performance, understanding audiences through statistics, and developing and improving services. Until you agree, nothing optional runs: Clarity and NitoPulse don't load, and Google Analytics runs without cookies.
• Everywhere else, ForeverDB's privacy popup asks about analytics and personalised ads. They're on unless you turn them off; with personalised ads off you still see ads, but not based on your browsing.
• If Google's message can't load in the UK, the EEA or Switzerland (an ad blocker can stop it), ForeverDB's popup asks about analytics instead, and ads aren't personalised.

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; Google's message asks again when Google's 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 and AdSense), NitoPulse (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 or share it 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 ask us to delete it. 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).
• 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.
• Uploaded reports: until you delete them, or your account.
• 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.
• 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.
• Analytics and advertising data: as set by Google, NitoPulse and Microsoft (Google Analytics keeps event data for 14 months at most).

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. 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.

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.