| Data storageYour Discord ID, Torn ID/name, hospitalization merit level, consent version, contract/claim records, matched action IDs, and unpaid earnings/payment records are stored. Contract and financial audit records are retained for dispute handling until the owner deletes the service; closed support tickets are deleted after 30 days. Full raw activity logs are not retained. Basic profile responses also contain public fields such as level, gender and status; merits responses contain all merit allocations. These extra fields are ignored and not stored. Verification abuse controls keep IP addresses in process memory for at most one minute; no IP access log is kept. | Data sharingTHLC's owner and designated staff can see order, target, payment, and audit details. Discord server administrators can access server messages through their administrative permissions. Verified server members can see active contract summaries and the Torn names/IDs and totals owed in Payouts. Claim target details are sent to the claiming worker. General Support messages are relayed to Uzumakikage. Discord receives messages and displayed data; API keys are entered on this HTTPS page, not sent in Discord messages. Hosting operators can administer the host. No data is sold or sent to other Torn tools. | Purpose of useVerify that your linked Torn and Discord accounts match; set your server nickname and THLC Verified role; read hospitalization merits for merc eligibility, refresh on reverify, and recheck before each merc claim to detect merit decreases (increases unlock higher tiers only after reverify); resolve requested targets' public names/IDs; verify exact bounty placements (target, reward, quantity, THLC reason, listing costs), hospitalization hits, losses, and escapes against your active claims; detect incoming payments from Uzumakikage [3716077] and reconcile unpaid earnings. THLC earns the advertised in-game service margin. No in-game actions or payments are performed by the bot. | Key storage and sharingYour key is transmitted over HTTPS to this bot, briefly used in server memory for authorized Torn API requests, and stored using AES-256-GCM encryption. The decryption key is held separately from the database. Encrypted backups may contain encrypted keys until backup expiry (14 days). Anyone controlling the running host and its secrets could access decrypted keys; no system can promise 100% security. No staff key-view command exists. Keys are never intentionally included in chat, audit messages, exports, or application logs. Use /deletekey to stop future checks, cancel pending verification links and remove the live encrypted key; a request already in flight may finish. Delete/revoke that dedicated key in Torn to invalidate any backup copy immediately. | Key access levelA dedicated Custom key only: user basic, discord, merits, and log; public torn logtypes metadata; the Bounties (157), Attacks outgoing (181), and Money incoming (17) log categories. Torn's current key builder grants category access, which can expose other events inside those three categories if the key is misused. The bot itself requests only bounty-place, attack-hospitalize, attack-lose, attack-escape, and money-receive event types. key/info checks permissions; extra selections, extra categories, and unrestricted logs are rejected. No battle stats, investments, net worth, inventory, faction banking, or unrelated log categories are requested. Only receipts from Uzumakikage are reconciled. Other unmatched action IDs are kept for two days for deduplication without target/amount data; sent notification copies are removed after seven days. |