Privacy
Community contribution
HFTR community sync is designed around loot observations from supported rares. The server stores a one-way hashed installation identifier for deduplication and statistics. The server does not need character chat, BattleTag or Battle.net login credentials.
What may be uploaded
Rare/NPC identifiers, content pack, loot policy, relevant item identifiers and quantities, addon/client version, queue revision and observation timestamps needed for community aggregation.
What is not required
Battle.net password, BattleTag, personal chat messages or gameplay-control data are not required for HFTR community loot statistics.
Rare Research
When HFTR marks a specific rare encounter as still needing technical validation, the addon may store a small anonymous research observation for Companion to deliver after World of Warcraft closes. These observations are limited to encounter identifiers, map/position, relevant HFTR state transitions, specifically attached phase/event requirement signals, addon/build versions and other technical context needed to understand that rare. The Rare Research system does not require character names, guild information, chat content, BattleTags or Battle.net credentials. After the server explicitly acknowledges an observation, Companion removes that delivered observation from the local HFTR SavedVariables queue.
Companion activity
Companion v0.6.7 and newer generate a random local installation identifier and send a lightweight heartbeat while the app is running. The server stores only a one-way hash of that identifier, the Companion version and first/last-seen timestamps. The public website exposes only aggregate active-client counts.
Issue Tracker affected signals
The public Issue Tracker can record an anonymous one-way hash derived from the connection when a visitor clicks I have this issue too. It is used only to reduce duplicate affected signals; the public page shows only an aggregate count.
Community statistics
Public statistics are aggregate values. Observed drop percentages are community estimates and not official Blizzard drop rates.
Debug reports
Debug Tracker is off by default. A diagnostic session is recorded only after the player explicitly starts it and stops when the player ends the session. Submitting a completed debug report is a separate explicit action through the Companion or website. Reports are intended to contain HFTR versions, runtime state and diagnostics, not Battle.net passwords, BattleTags or chat history. Companion Diagnostic Packages can additionally include operating-system architecture and installed addon folder names to help identify compatibility problems; packages are created only when the player explicitly asks for one. Raw diagnostic reports remain private to HFTR administration, while the public Issue Tracker shows sanitized summaries and status only.