Privacy Policy

The Hangout Family · Torn City · Last updated: 16 October 2026

This policy explains what data The Hangout Family's services handle and why. It covers The Hangout Revive Bot, The Hangout Merc Bot, and the pages and panels on thehangout.site. We collect the minimum needed to run them. We do not sell your data, we do not use it for advertising, and we do not profile you.

The Hangout's services run on the same server and the same software as b0torn, which has its own policy for the faction war panel at b0torn.com. This page is about the Hangout services listed above.

Who this is for

These services are for Torn City players. They are not directed at anyone below the minimum age required to use Discord (13) or Torn. Please do not use them if you do not meet those requirements.

What we collect

Discord account: when you sign in to a panel we use Discord OAuth with the identify scope only, which gives us your Discord user ID and username. We do not read your messages, your email address, or your other servers. In Discord itself the bots see the IDs, nicknames and roles of members in the servers they are added to, so they can route requests and grant the reviver and merc roles.
Torn account details: we map your Discord ID to your Torn account using Torn's official verified-Discord lookup, which returns your Torn player ID, name, faction and position.
Torn API keys: members who want to take paid revive or merc work, and factions that take out a contract, add a Torn API key voluntarily. We use it to read the data needed to confirm work — for revivers, the revive feed; for mercs, your own attack log, so we can see which of your attacks landed on a contract's target faction, how they ended, and which weapon bonuses applied. We read nothing from your key that is not used for this.
Request and contract records: revive requests and merc contracts, with who opened them, who worked them, timestamps, the contract's own terms (target faction, work type, activity rules, excluded player IDs, Stricken requirement, start and end time), the attacks counted against them, the price agreed, and whether a manager has marked the contract paid.
Public Torn data about targets: for a contract's target faction we read public information through the Torn API — member list, level, status and last-action time — so we can apply the contract's own activity and exclusion rules.
Session cookie: signing in sets one signed cookie holding your identifiers (Discord ID, Torn ID, faction, role) so the panel remembers you. It is cryptographically signed and we use no advertising or third-party tracking cookies.

How we use it

Only to run the services: routing revive requests and merc work, working out what a contract is owed and what a worker has earned, showing a contract owner what was delivered, granting and checking the reviver and merc roles, and deciding who may see which panel. We do not sell, rent, or share your data with third parties for their own purposes.

Who can see what

A contract's owner sees that contract's own records.
A worker sees the contracts they may work and their own earnings.
Hangout managers and the service operator see the contracts and records they manage, in order to agree payment and handle disputes.
An API key you add is never shown to other users, and is used only to read data on your behalf.

Third-party services

Discord — login and bot operation. Your use is subject to Discord's own Privacy Policy.
Torn (torn.com) — the source of all game data, read through the official Torn API with keys you provide. Your use is subject to Torn's terms and privacy practices.
Google Fonts — the web font these pages use is loaded from Google's servers, which receives your IP address as part of that request.

Everything else is stored on a private server run by the operator and is not shared further.

Keeping and deleting data

API keys and settings are kept while we are serving you. You can remove a key you added at any time, which stops further use of it.
Contract and request records are kept so that contracts can be settled and disputed afterwards, and are pruned periodically once they are settled and old.
You can ask us to delete your stored identifiers and records — see Contact. Removing the bot from your server and removing your key stops further collection.

Security

Keys and records live on a private server, and session cookies are signed so they cannot be tampered with. No storage or transmission is ever completely secure, so add the lowest-access Torn API key that still lets the feature work and never a key with more access than you are willing to share.

Changes

We may update this policy as the services change. The "last updated" date above reflects the latest revision, and continuing to use the services after an update means you accept it.

Contact

Questions and data requests: message b0rjara on Discord, or ask in The Hangout's Discord server.