ForeverBuilds Privacy Policy
ForeverBuilds is a community website for planning character builds, comparing gear, tracking progress and sharing builds and character profiles.
ForeverBuilds operates this service. Contact: support@foreverbuilds.io. This policy covers the production service at foreverbuilds.io.
Information we receive
- Sign-in information. When you choose Google or Discord sign-in, the provider supplies an account identifier, email address and basic profile information, such as your name and avatar, according to the permissions you approve. Our authentication service processes this information to identify your account. We do not receive your Google or Discord password.
- Your content. We store the information you save: builds, character details and appearance choices, talents, stat weights, planned gear, acquired-item progress, notes, profile text and links, comments, stars, follows and notification read status.
- Technical information. Hosting and authentication services process information needed to deliver and protect the service, such as IP addresses, browser information, request timestamps, errors and security events. We record build-view activity and aggregate engagement counts.
- Support messages. If you contact us, we receive the information you include. Please do not send passwords or sign-in secrets.
How we use information
We use information to sign you in, associate your saves with your account, sync and recover your workspace, display content you share, provide community features, count build views, respond to requests and investigate errors or abuse. A verified email may allow supported sign-in methods to connect to the same account.
Google account information is used for sign-in and account features. The app requests basic identity and email access, rather than access to Gmail messages, Google Drive files or Google contacts. Discord sign-in requests profile and email access, rather than permission to read or send your messages.
What other people can see
Public builds and characters may appear in Discovery, search and public creator pages. New builds and characters are intended to default to Public; review the visibility control before saving or sharing. Your creator profile and community interactions may also be public.
Unlisted means anyone with the link can view the shared page, but it is excluded from the service's public listings. An Unlisted link is not password protection: recipients can forward it. Making a build or character Unlisted does not necessarily hide separate public comments or creator-profile information.
The shared build and character projections exclude private build notes and acquired-item details. Shared pages can include planned gear, talents, weights, character appearance and linked builds. Information you deliberately put in public titles, descriptions, comments or profile fields is visible to others.
Changing visibility or deleting your original content cannot recall screenshots, outside caches or independent copies already made by other people.
Visit counts and optional analytics
We use PostHog in its United States region for basic page-view and visit counts. Basic measurement starts without setting analytics cookies or storing visitor identifiers in local or session storage. A random identifier exists only in the open page's memory and is replaced after a reload or a new visit. We do not use IP/browser fingerprinting or link these counts to your account. Page names are fixed categories such as planner or discovery, not actual profile/build URLs, handles, query strings or search text. Unique visitor totals are approximate visits, not counts of distinct people. We also record the referring website’s domain, without its page path, query or fragment, and bounded campaign labels (utm_source, utm_medium and utm_campaign) when present. These help show where visits come from; private URL parameters and character names are excluded. Page views and page leaves also include a broad browser-width range (760 CSS pixels or below, 761–1650, or 1651 and above) to improve responsive layouts. We do not record the exact viewport width, screen resolution or zoom setting. We request that IP storage and geolocation enrichment be disabled; the service still receives ordinary network connection information when a request is delivered.
Basic measurement also includes limited technical error reports to help us find and repair broken features. Reports contain a fixed error category, first-party source file and line number where available, page category, site release and broad device/layout category. They use a separate random identifier held only in the open page’s memory to count affected page loads, not people. We do not send raw error messages or stacks, full URLs, account IDs, character names, search text or saved setups. Reports are limited to ten distinct issues per page load. Turning all analytics off, Do Not Track or Global Privacy Control prevents these reports.
Account journey analytics is separate and starts only if you choose Allow optional analytics in Privacy & analytics at the bottom of the app. These events help us understand creation, signup, saving, discovery, sharing, character-search outcomes and completed simulations. Search and simulation events include only broad class, outcome and tool categories; character names, gear, talent allocations and damage/healing values are excluded. When you are signed in and optional analytics is enabled, page views and page leaves also use the same hashed account identifier. Basic visits collected before that choice remain anonymous; signing out or returning to basic visits stops account linking for new traffic. They use separate random browser and pseudonymous account identifiers with limited properties such as class, device category and action type. Their sessions expire after 30 minutes of inactivity or 24 hours. Names, emails, private notes and build contents are excluded. Session recordings and automatic click capture are not installed.
You can use basic visits only or turn all analytics off in Privacy & analytics. Earlier opt-outs remain respected. Browser Do Not Track and Global Privacy Control preferences suppress both types of collection. Only your deliberate choice writes an analytics preference; optional account analytics uses separate browser storage and never changes your builds, characters or progress. Staging events are labeled test traffic and kept separate from production reports.
Signed-in activity and completed Sim counts
To measure daily, weekly and monthly use separately from registrations and fresh sign-ins, ForeverBuilds records at most one first-party activity entry per signed-in account per UTC day. It contains the account identifier, date and first observed time, not page URLs, searches, character names, gear, talent choices, IP addresses or simulation results. It is stored in the same isolated account database and is not sent to PostHog. Administrators receive aggregate counts only. Repeated visits do not add another account to the same period.
This first-party count is separate from optional account journey analytics. Turning all analytics off, Do Not Track and Global Privacy Control suppress this activity collection. Basic PostHog visits remain unlinked to accounts. Older activity is not reconstructed from a latest sign-in timestamp. Entries older than 400 days are removed when that account next records activity; account deletion removes its activity records.
When basic measurement is enabled, completed manual Sim comparisons may record your account ID, a random run identifier and completion time in our own database. This separates completed runs from distinct registered people in administrator reports. We do not include character names, gear, talents, damage or healing results in this record. Failed or canceled runs and automatic estimates are excluded. The same analytics-off, Do Not Track and Global Privacy Control choices apply. Records older than 400 days are removed on subsequent recording for that account; account deletion removes its records.
Browser storage and cookies
The app uses browser storage for guest builds, cached account workspaces, preferences, drafts and recovery copies. Guest data is specific to that browser. Signing out does not automatically erase its stored copies. You can clear site data through your browser, but export anything you want to keep first.
Production uses secure cookies for sign-in sessions, temporary sign-in requests and a pseudonymous identifier for build-view counting. Session cookies are set for up to seven days, temporary sign-in cookies for ten minutes, and the view-count cookie for up to one year. Server-side records may expire or be cleared sooner. These are configured lifetimes, not a promise that every backup or log disappears at the same time.
Service providers and outside sites
We use Cloudflare for website delivery, server processing and session storage, and Supabase for authentication and database storage. Google or Discord handles sign-in when you choose that provider. These providers process information according to their roles and their own policies.
Game item information, icons, tooltips and model assets use third-party sources, including Wowhead/ZAM. Some resources are relayed through our server; others may load directly in your browser. Direct requests disclose ordinary connection information to that provider. Public profile links, including optional Warcraft Logs or social links, lead to outside services with their own policies.
When the creator is live, an optional Twitch player may open on desktop if automatic opening is enabled. Loading it connects your browser to Twitch, whose player and cookies follow Twitch’s own policies. It starts muted. Closing the panel stops playback and dismisses it for the current tab session; unchecking automatic opening stores a separate browser preference until you re-enable it. We check the creator’s public live status on our server without sending your account or character information to Twitch. Twitch application credentials stay on our server. No player loads while live status is offline or unavailable.
We may disclose information when reasonably needed to comply with applicable law, protect users or investigate abuse. we do not sell personal information or use Google account information for targeted advertising.
Public Armory search
You can search Blizzard’s public WoW Forever Armory by region and full character name without signing in. We retrieve the public character identity and equipped gear using server-held application credentials, then calculate recommendations. Public lookup results and character share images are cached for about five minutes. Searching does not create, link or save a character in an account, and does not expose private ForeverBuilds plans, notes or collection progress.
A named recommendation link and its social preview can show the public character name, region, ruleset, level, class, race, faction and equipped gear. The face artwork represents the reported race and body type; it is not a customized in-game portrait. Making a ForeverBuilds plan private or disconnecting Battle.net does not remove information Blizzard independently publishes in the Armory.
Battle.net character workspace
Your verified BattleTag is kept with your sign-in identity in our authentication service, separately from temporary Armory access and character-list caches. Expired Armory access does not erase this account identity. We display only the nickname to you and authorized site administrators; it does not replace your chosen public profile name or appear in public character URLs.
Battle.net sign-in creates or opens your ForeverBuilds workspace. Our authentication service receives your Battle.net identity and the authorized WoW profile access. You do not need to provide an email or another password. Existing users may explicitly connect Battle.net sign-in to their current workspace; we do not merge workspaces by character name or BattleTag.
We read your Forever character list and the identity/equipped gear of the character you choose. Your imported character starts private. Provider tokens remain server-side and are never stored in browser JavaScript, analytics or public profiles. The managed sign-in grant has a 24-hour application retention cap when Blizzard expiry information is not supplied; this is not represented as a verified provider expiry. When authorization expires, you can keep opening recommendations from your remembered list using the public Armory. Reconnect to update your Battle.net list or perform a fresh ownership-verified import.
Linking and explicit refresh sync the chosen name and level. Supported specialization reported by Blizzard can prefill recommendations, without importing or rewriting talent allocations. Your planned gear, build names and collected-item marks remain separate. Equipment expires after 24 hours. We keep the last authorized character list and linked identity for up to 30 days from their successful retrieval, separately from the shorter-lived access token. Merely viewing this list does not extend retention or verify current ownership. Disconnecting removes the remembered list. Minimal account-owned character bindings survive token expiry so a returning selection can reuse the same saved character; fresh ownership checks still apply.
Unlinking a character or disconnecting removes its private connection data and bindings, preserving saved plans and progress. Disconnecting Armory access does not remove a linked sign-in method from your account. Connecting does not publish your private ForeverBuilds plans or collected-item progress. Public Blizzard Armory information remains independently searchable as described above.
Storage, retention and security
Production uses a database separate from our development and staging environments. The current production database is in the United States; providers may process information in other countries. We use access controls, encrypted transport and server-side session handling, but no service can promise perfect security.
account content is retained while your account is active or until it is deleted, subject to legitimate security, dispute and legal needs. Production database backups currently have seven-day retention. Backups, technical logs and copies on your own devices may remain after a live record is removed. We retain technical logs and support records as needed for troubleshooting, security, requests and legal obligations; contact us for information about retention relevant to your request.
Your choices and requests
You can use browser-only planning without signing in, edit supported account and profile fields, change build and character visibility, and use available build export controls. Revoking Google or Discord access through the provider prevents future authorization through that grant; it does not itself delete your ForeverBuilds account or browser copies.
To request access, correction or deletion of account information, contact the privacy address above. We may need to verify that you control the account. Depending on where you live, applicable law may give you additional rights, including objection, restriction, portability or a complaint to a privacy regulator. We will consider requests under the laws that apply.
Children
ForeverBuilds is not intended for children under 13, or a higher minimum age required where they live. If you believe a child has supplied personal information contrary to this policy, contact us so we can investigate and take appropriate action.
Changes and contact
We will post updates here with a revised effective date and provide additional notice when required. Questions and privacy requests can be sent to the privacy contact listed above.