Keys, permissions & verification
Login uses Torn's user profile and key-information endpoints to check your player ID, name, faction membership and key access level. The HUB requires Minimum Access or higher for login; individual tools may need additional selections or faction permissions. A key does not make unavailable Torn data accessible, and login alone does not guarantee that every tool can collect data with it.
Where saving is enabled, the HUB retains your submitted key for verification and the enabled API-powered tools. More than one submitted key can remain in the store; replacing a key does not automatically remove an earlier one. Existing sessions can periodically recheck membership using a saved key.
The reviewed Torn integrations read data. They do not use your key to spend money, move items, train, travel, perform revives or execute organized crimes in Torn. The HUB does not ask for your Torn account password.
Membership & shared member directory
Purpose: verify access and keep member names/IDs consistent across tools. Login reads your profile and key information. Faction roster calls cache member IDs, names, current-membership flags and observation timestamps; the shared cache can also retain the original roster record, including status/activity fields supplied by Torn.
Key source: your submitted key for login; an eligible saved or configured faction key for roster refreshes. A faction roster can include members without their own saved key.
Revive data & personal revive history
Purpose: show revive performance, personal records and faction comparisons. Saved member keys read profile/personal statistics (revive skill, revives given and received) and personal revive/revive-full history. An eligible saved key can also read faction revive logs.
Stored records include reviver and target IDs/names/factions, timestamps, success/failure, chance and, when returned, hospital reason, early discharge and target last-action information. Targets and other participants may be outside UFD. Recent polling and older-history backfill can run while you are not visiting the HUB; history availability depends on Torn and key permissions.
Monthly competitions
Purpose: calculate progress, standings and prizes for the selected event. A designated polling account's saved key reads the faction roster and the configured source: faction contributions (such as training energy), armory news (such as Empty Blood Bag fills), or selected member user-stat fields.
Examples include racing points, flights, crime counts, attacks, revives and training-energy totals. Custom selections/field paths are supported, so events are not limited to that list. The HUB stores member IDs/names, baseline/current/final values, snapshots, differences, ranks, prize opt-outs and pause/excluded-progress records, with competition archives retained for review.
Attack Respect competition
Purpose: rank faction attack participation and respect earned. A separately configured, encrypted competition polling key reads faction identity, members and attack records. The competition stores qualifying attack IDs, attacker IDs, attack-end timestamps and positive respect gain, together with member names and current-membership flags; leaderboards aggregate hit counts and respect.
This is a faction-data collector, not a process that requires every member's personal key.
Chain Audit & faction resource accountability
Purpose: compare chain participation with faction resources used. An authorized operator's saved key or the designated polling account reads faction members, chain reports, attack records and armory news. Stored armory evidence can include original news text/records, member identity, resource quantities, actions and timestamps.
Reports derive hits, losses, respect, Xanax/points usage, expected participation, gaps and flags. The HUB also keeps return obligations/credits and manually entered member notes. These are operational estimates and records, not a claim that Torn directly reports every conclusion.
OC Travel Holds
Purpose: identify members travelling or abroad when their planning OC is ready. A configured faction key reads planning crimes and the member roster. The tool stores member/OC/role identifiers, ready/expiry times, travel-status descriptions/details, last-action information, observation snapshots, incident durations/counts and resolution reasons; snapshots can retain original member and slot records.
The overview and member history support follow-up on delays. Configured Discord alerts can include the member name/ID, OC and role, travel status, last action, observed duration and incident count. This is not a general-purpose log of every member's complete travel history.
OC CPR database
Purpose: let authorized UFD leadership and tool operators view observed CPR percentages by member, OC and distinct role, with measurement dates and gaps. Under UFD's HUB key-use policy, submitting a key to use the HUB while in the faction authorizes automatic CPR collection with that saved key; there is no separate member opt-in. The collector remains disabled by default until production enablement. Publishing this page does not start collection.
When enabled, the collector reuses saved member keys, verifies key ownership/faction, and reads personal organized-crime observations, the public OC catalog, faction members and faction crime assignments. Personal observations cover the empty recruiting roles Torn exposes, not every possible role. Current assignments and a bounded completed-OC backfill (up to six calendar months, subject to availability) provide additional snapshots.
It stores member/membership history, OC/role definitions, observed CPR, source/measurement timestamps, assignment references and changes, not raw keys or complete API responses. Missing data stays missing rather than becoming a zero. Departed members stop individual collection after a successful roster sync and are hidden from current-member matrices. CPR observations, change history and membership history are retained indefinitely for all recorded members, including departed members. Daily CPR database backups contain the full retained history; backup snapshots older than five days are automatically deleted after a new backup succeeds. This does not delete history from the live CPR database.
Flushie market, Points Market & Buyback requests
Purpose: show market trends and calculate member-submitted buyback quotes. The legacy Flushie collector and separate Points Market collector use configured operator keys to read market listings, not the HUB's saved member-key store. Local market databases hold listing prices, quantities, identifiers, timestamps and summary/history statistics; Flushie snapshots also retain selected listing records.
Buyback quantities are entered by the member; this flow does not inspect your private inventory. Quotes store your verified name/ID/faction, requested items and quantities, price snapshots, totals, notes, status and timestamps. Configured Discord notifications send quote identity, item/price details, totals, status and a HUB quote link; the Points collector can send market-listing summaries to Discord. These tools do not execute a Torn trade or payment.
Storage & retention
Saved keys are held server-side, with encryption enabled by default for the HUB login-key store and encrypted storage for the Attack Respect polling key. Protection also depends on deployment configuration and server access; encryption does not prevent the HUB from using a key for its configured tasks.
Data collected from Torn is stored in the HUB's SQLite databases and server-managed files to support the features described above. Some roster, armory, OC Travel and market records retain original API records alongside displayed summaries and historical results.
There is no HUB-wide automatic expiry or deletion period. Key history, revive/OC history, cached member records, quotes and competition archives can remain until a tool-specific reset or an operator-reviewed retention/deletion action. Logging out, quote expiry, a competition prize opt-out or leaving the faction does not automatically erase them. Backups and Discord copies need separate consideration.
UFD HUB