Join the UpQuest Discord · help, routes and updates Join now

Privacy policy

What UpQuest does with your data, in plain language.

Last updated:

The short version

  • Browsing and Premium activation do not require a website account. Advertisers sign in with Twitch; essential cookies maintain that session and protect sign-in.
  • Paid sponsor banners and cards can appear on the home page and on the Guild Hall, Workbook and Partners pages. We do not use third-party advertising trackers or sell visitor profiles.
  • Payment details are handled by our payment partner, which runs the checkout for UpQuest purchases. We can see the order information it provides to sellers.
  • When you activate Premium, your license key is processed only to verify it with our payment partner and create your import code. It is not stored.
  • The UpQuest addon never connects to the internet. A separate desktop program, the Hearth Relay, can publish guild chat and guild activity on the homepage. Members of the two guilds choose whether to run it.
  • Public guild messages include character names, message text and timestamps, with a limit of 200 messages from the last 24 hours. Guild event lines name a character with its class and level.
  • The welcome scroll contains the recorded story and two choices: a guild gold contribution and one sharing checkbox, each kept only when you press Save. Every local tool works whether or not you read it, and Begin your adventure turns on neither sharing nor gold. The sharing checkbox turns all five kinds of sharing on or off together. The Accord never reads or shows your BattleTag; with sharing on, the Watch feature can show it to authorized current-guild staff, never the public website. Fresh choices start off and current saved choices are preserved. Once you save a gold choice, your guild master and officers see it and the gold your game mailed. A configured member's relay can pass authorized information to this website even if you never run a relay.
  • A private guild archive retains the latest 1,000 guild messages. An authorized website administrator can request a human-reviewed moderation report that sends those messages, their character names and timestamps to OpenAI.

Who runs UpQuest

UpQuest is operated under the UpQuest name. You can reach the operator at FeebledGamer@gmail.com.

Purchases

UpQuest products and advertising are sold through Whop, our payment partner. When you buy, you check out on the partner's secure checkout page, and the partner collects and processes your name, email address, payment details and similar information under its own privacy policy, shown at checkout. We never see your full card details.

As the seller, we can see the order details the partner makes available to sellers, such as your username or email address and what you bought. We use them only to provide support, handle refunds and prevent abuse of licenses.

Activating Premium on this website

On the activation page you paste the license key from your order. Here is what happens to it:

  1. Your browser sends the key over an encrypted (HTTPS) connection to this website's activation service.
  2. The service asks our payment partner whether the key is valid for UpQuest Premium.
  3. If it is, the service creates a signed import code and sends it back to your browser.

The key is used only for that check. We don't save it, write it to logs or share it with anyone except our payment partner, and the page doesn't store it in your browser. Addon activation keeps no license database; the one record we keep for a Guild Hall licence is described below.

The import code identifies the purchased edition (Classic, Forever or All-Access), a code ID and its issue time. The code ID is a one-way fingerprint derived from your purchase; it does not contain your name, email or license key.

Twitch sign-in and advertising

When you sign in, Twitch provides your account ID, login name, display name and profile image. Twitch handles your password; UpQuest does not receive it. Essential secure cookies keep you signed in for 30 days after successful Twitch verification and protect the authorization callback. A new successful Twitch sign-in starts a fresh 30-day window; visiting the website does not extend it. Signing out clears the website session. Twitch sign-in does not subscribe you to promotional Whispers.

We store your Twitch account ID, application title, description, destination link, category, contact information, review decisions and campaign dates in Cloudflare storage. Approved advertisements are public when launched. Contact information and review records are available to you and the operator, not visitors browsing the sponsor card.

Whop processes advertising payments. To verify and maintain a campaign, we store the associated membership ID and payment-verification status. A sponsor license key is processed for verification and is not stored. Purchase checks and signed payment notifications can pause or remove a campaign after a refund, dispute or loss of access. Contact us to request access to or deletion of your advertising records; records needed to resolve a purchase or dispute may need to be retained.

Owner announcement tools

The owner dashboard can record an announcement, transcribe it with OpenAI, formulate an editable draft and post the reviewed text to the configured Discord channel. Recording starts only when the owner selects the microphone control. Audio is uploaded for transcription only on request and is not retained by this website. Notes are sent to OpenAI only when Formulate is selected, with response storage disabled. The OpenAI key is used for the selected request and is not stored by the server.

Draft writing may be saved locally in the owner's browser for later editing. The private Discord webhook is encrypted in Cloudflare storage and is never included in public pages or API responses. Posting requires a separate Post action. A private receipt records the request and message identifiers, timestamp and content fingerprint to prevent repeated sends; it does not retain the announcement body. Messages posted to Discord are visible to that channel's audience and follow Discord's own privacy and notification settings.

Hosting and technical data

We measure website visits, navigation destinations, product interest, download and checkout clicks, redirects issued by this website, and successful or failed activation attempts using our own service on this website. A random identifier in your browser tab expires after 30 minutes of inactivity; it is not linked to your Twitch account, payment identity or licence key. Only known page paths and destinations, product names, broad traffic-source categories and a fixed list of public campaign labels are accepted. Full URLs, query strings, form values, raw referrers, IP addresses and browser fingerprints are not stored in these analytics records. Do Not Track and Global Privacy Control preferences disable this optional collection. Signed-in administrator activity is excluded.

Short-lived session and event identifiers are stored as hashes for deduplication and expire after 30 minutes of inactivity. Aggregate daily figures are retained for up to 90 days and are available only through the owner dashboard. Server-verified activation results are counted separately from browser-reported clicks; activating an existing licence is not treated as a new purchase. The dashboard can also show cached aggregate sales totals from Whop, without exposing buyer information or attributing a payment to a particular browsing session.

When you click a known checkout or download redirect on this website, short-lived random identifiers may be added to that same-site request to connect the click to the redirect response. These identifiers and all other query parameters are removed before sending you to the external destination, and the redirect suppresses the referring URL. A redirect response confirms that this website issued the handoff; it does not establish that the destination finished loading.

The website runs on Cloudflare. Like any web host, Cloudflare processes technical information such as your IP address, browser type and the time of each request in order to deliver pages and protect the site from abuse, for example by limiting repeated activation attempts. See Cloudflare's privacy policy.

Application observability logging is currently disabled. Cloudflare still processes the operational information needed to serve and protect the site.

The featured items and the legendaries on the home page show their icons and, when you hover an icon, an in-game style tooltip provided by Wowhead. Your browser loads that script, the icons and the item data from wow.zamimg.com and nether.wowhead.com, which receive your IP address and browser headers like any web request. UpQuest sends them nothing else. See Wowhead's privacy policy.

Purchase availability

UpQuest may temporarily close new purchases. A private sales ledger on Cloudflare records product and payment identifiers, payment timestamps, verified amounts, refunds and dispute status to manage availability and purchase history. It does not store full card details or expose customer orders publicly. Existing purchased access and licence activation remain available during a sales closure.

Purchasing availability and the next eligible opening are shown on the website. There is no reopening reminder signup or email subscription. Optional funnel analytics distinguish a purchasing closure from a checkout failure without receiving payment identifiers.

The addon

The UpQuest addon runs inside World of Warcraft, which does not let addons use the internet. It saves its settings and your import code in the game's own SavedVariables files on your computer. Installing the addon alone does not upload these files.

The introduction is a welcome story. It opens by itself once, the first time you log in with a new version of it, and then plays the owner's supplied recording and scrolls in time with it. Nothing in the addon waits for it: guides, Catalog, tracker, map and every other local tool work whether or not it was read. Begin your adventure only closes the scroll and remembers that it was seen. Opening, listening, scrolling and closing do not turn on sharing or gold. The story and recording contain no sharing notice or account preview.

Settings → UpQuest Accord, /uq accord and /uq privacy reopen the parchment. It holds two separate choices, kept when you press its Save button: the guild gold contribution and one sharing checkbox. Its What is shared page is read-only and lists each kind of information the sharing checkbox covers, with its purpose, recipients and retention. Enabled guild chat can pass through a configured relay to the website's public feed for up to 24 hours and private latest-1,000-message archive until replaced or manually purged; an administrator may submit retained chat to OpenAI for a human-reviewed AI report.

The sharing checkbox turns five kinds of information on or off together: live guild/group location, coordination and requested gear or talents, account identity, external relay exports and guild activity. Sharing starts off, and unsaved edits do not enable anything. The Accord itself never reads or shows a BattleTag; with sharing on, the Watch feature can read your own BattleTag to show it to authorized current-guild staff reviewing a report about you. Turning sharing off stops the related new data and clears unsent work. A feature that needs several permissions requires each of them. Updated standard and Guild Hall relays enforce the relevant categories for their operator and every exported player. Plain chat needs external export permission; activity exports additionally need activity permission. All sharing can be off while local guides and independent gold remain available. Existing valid version 2026-10-21.5 choices are preserved; stale, withdrawn and staged records do not activate sharing. Turning sharing off cannot recall delivered copies or erase another archive. The game normally saves changed preferences at logout or UI reload.

In-game Watch gives authorized current-guild staff private incident, identity and discipline records for human review, retained for up to 180 days. Its five severity levels decrease by one after each 24 quiet hours. Level 5 calls for guild removal and blocks UpQuest invitations; native removal depends on current guild permissions and the game client's restrictions. A lower level does not automatically invite a removed character back. Current members can review their action and appeal in the addon; after removal, they must contact guild leadership to appeal because current-guild addon transport is unavailable. Moderation whispers wait for verified online presence. For an online Level 5 target, the final whisper is submitted before removal is requested; submission does not confirm delivery. These private Watch records are not automatically sent to the website or OpenAI.

An independent, voluntary guild gold contribution starts off on fresh installations, with a suggested 7% rate on the Accord parchment. You must explicitly enable and save it there; beginning the introduction or enabling data sharing does not enable gold. A valid, explicitly accepted existing gold preference is preserved. Change the percentage from 0 to 100 or turn it off at any time by reopening the Accord from Settings. Once you save a gold choice, your game sends a short record on the guild's addon channel at login, when the choice changes and once an hour: whether you contribute, your share, and the gold, parcels and date of the contribution mail it sent. Every UpQuest client in the guild receives it; only the guild master's and officers' games keep it (up to 500 members per guild), and a member who leaves the guild is removed from it. This record follows the gold choice, not the sharing checkbox. Contributions apply to confirmed enemy loot and native group loot shares. A group-share event does not identify the remote corpse, so the addon cannot distinguish remote enemy coins from a remote money-bearing container. Quest rewards, mail, trades and vendor proceeds do not count. Contributions accumulate in your character's Ledger and are sent automatically when you open a mailbox, after verifying the current guild leader, funds and mail availability. A leadership change updates the recipient of definitely unsent mail; submitted or uncertain mail is not resent. Opting out pauses future accrual and automatic sending. This choice does not affect addon access or sharing permissions and does not charge real money.

Optional public guild conversation and the Hearth Relay

The homepage can display Silver Chain Gäng and UpQuest guild-channel messages from Doomhowl, US Hardcore. They are sent by the Hearth Relay, a separate desktop program that members of those two guilds can download and run; several members may run it at the same time. After it is started once, the relay keeps running in the background without a window and starts again whenever that member signs in to Windows, until they switch that off or stop it in the relay's own window. A relay uploads guild chat only when the member running it has switched chat capture on in the game. By default it reads the addon's own export file, which the game writes at logout or UI reload. Optional live mode, which that member also switches on, reads a visible coded panel while WoW is in the foreground, allowing updates during play. The reader temporarily examines pixels from the WoW window to locate and decode that panel; screenshots are not saved or uploaded. Only validated guild-message text, the hearth values described below and capture metadata are sent. No mode uploads your full addon database, license code, officer chat or whispers. The relay never sends input to the game and never reads game memory.

A relay is recognised by a random identifier that the addon creates once for a game account. It is not an account name, a BattleTag or a license. With sharing on, the Guild Hearth can pass a one-way fingerprint of that identifier over the guild's addon channel inside the game, whether or not its user runs a relay. Other members' addons keep the fingerprint with the name of the character that sent it for up to 90 days; a relay with external sharing enabled can upload it. The website accepts uploads from a member's relay only after its fingerprint has reached the website in this way. Updated standard relays and paid Guild Hall relays require fresh current-Accord consent from the relay operator and each player whose records they export. The addon accepts these bounded consent notices only from direct native current-guild senders. Unknown, declined, withdrawn and older clients are excluded. Consent expires after three minutes without renewal, so old saved snapshots cannot authorize continuing uploads. A received withdrawal clears matching unsent records and temporarily blocks older proofs at the receiving service. Already delivered records keep their stated retention. These notices are relay assertions, not cryptographic proof of a player's account; modified clients cannot be fully prevented.

Cloudflare stores the fingerprint, up to ten character names it was seen with, when it was reported and by which relays, and whether the operator has switched it off. The identifier is the same for every character of a game account, so this record links those characters to each other. The record has no fixed expiry: the list holds at most 1,000 fingerprints, and when it is full the ones not seen for the longest time are removed first. A fingerprint the operator has switched off is kept so that it stays off. To ask for a record to be removed, contact us as described below. None of this is shown publicly.

The public page shows only chat lines, guild event lines and the fire. Messages published here are visible to anyone visiting the page. Cloudflare stores the character name, message text and message timestamp, for an event line also the character's class and level, plus connection and snapshot timestamps and a private note of which relay sent each line. The active feed retains at most 200 messages for up to 24 hours, event lines included. Duplicate and deletion identifiers may be retained for 24 hours to prevent removed messages from returning. Last-contact timestamps remain until the feed is reset. Copies already viewed or saved by other people cannot be recalled by this website.

Cloudflare's storage recovery system may retain historical database versions for up to 30 days after the active record changes. These versions are not served by the public feed.

Guild members should be told when publication is enabled. For a removal request, contact the UpQuest team through the UpQuest Discord or the contact address below. The operator can remove lines, clear the feed, pause publication, and switch a relay off and remove what it sent. Stopping a relay stops its future uploads; it does not automatically erase lines already published.

Private guild history and AI moderation

Alongside the bounded public feed, a separate private archive in Cloudflare retains the latest 1,000 guild-channel messages per guild from the relay. These private messages do not expire after 24 hours: they remain until newer messages replace them or an administrator purges them. The archive lets authorized website administrators review recent guild conversation even when a relay is offline. The private archive is not a public message API.

When an authorized administrator selects Generate report, the selected guild's retained message text, character names, timestamps and coverage information, together with the administrator's review instructions, are sent to OpenAI using that administrator's API key. The request disables OpenAI response storage. This website does not retain the key on its server. OpenAI processes the request under its own applicable service terms; disabling response storage is not a promise that no service-side processing or retention occurs.

The result is an editable review aid for a human moderator. It does not automatically warn, remove or punish players. Blizzard whispers, officer chat, raw BattleTags and private UpQuest Watch reports are not automatically included in the guild-chat export. Contact the operator about retained records or removal; stopping future capture or withdrawing consent does not erase an archive copy already delivered.

The Guild Hearth

The homepage also shows one guild fire for the same two guilds. Guild members' addons share with each other, inside the game, a character name, class, level and daily counts: quests turned in, experience earned, journey steps, and journeys and dungeon guides completed, plus a running experience total. They also share a level-up, and a character's death with its level and time. A relay uploads those values together with the number of consenting guild members online.

The page does not list these values. It shows the fire, which grows and sinks with how active the guilds are, and event lines in the chat list: a death and a level milestone, each with the character's name, class and level (the class is shown as the colour of the name), and a new level of the guild hearth. New uploads include only characters with fresh acceptance of the current Accord, including death and level notices. Players without updated consent are omitted, even if a native game event names them. No raw BattleTags, live map positions, license codes or quest names are sent in these relay records.

Daily counts older than 90 days and characters not seen for 90 days are removed as new data arrives, and the operator can remove a character or a line on request. So that an event is announced only once, the website also keeps a note of each death and of each character's latest level-up: the character's name, the level, the time and which relay reported it. This note outlasts the event line, which leaves the feed after 24 hours; it is removed after 90 days, when the next event arrives. Previously delivered records may include characters covered by earlier export rules; those copies retain the limits described here.

To keep your own counts out, turn the hearth off in game with /uq hearth off. Your addon then stops sharing your counts, your level-ups and your fingerprint. What it shared before stays until it runs out as described above or is removed on request.

Guild Hall

A guild master who buys a Guild Hall activates the licence key in the Relay program. This website then keeps one record for that licence: a one-way fingerprint of the guild's name, realm and region, the licence key itself, when it was activated and how many times, and when the purchase was last checked. The record exists so the Relay program can fetch hall updates: before a download, the website asks our payment partner whether the purchase still stands, at most once a day. The record is not shown publicly, and the licence key in it is sent nowhere except to our payment partner for that check.

The hall itself runs on the guild master's own Cloudflare account, not here. Whatever it stores, the roster, today's counts and guild chat lines if the guild master switched them on, lives in that account under Cloudflare's privacy policy. The guild master is the one to ask about it; only updates and the licence check come from this website.

Your choices and rights

For payment or order records, contact our payment partner through your order account or its support. For public guild messages or anything else, contact us at FeebledGamer@gmail.com. Depending on where you live, you may also have rights to access, correct or delete personal information, or complain to your local data protection authority.

Platform account eligibility

Purchases, Twitch sign-in and use of World of Warcraft are subject to those services' account eligibility and parental-permission requirements. Contact us if you have a concern about a child's information in the public guild feed or an advertising application.

Changes to this policy

If this policy changes, the new version will be posted on this page with a new "last updated" date.