| Data storage | - Persistent: anonymous stat estimates of players you attacked, if you share attacks.
- Lists you make: the players on them with their names, levels, notes and, when it is known, their faction ID (saved when you add a whole faction or a player from a table that shows the faction, and when the userscript's side tab reads their faction and you turned on sharing there), and your name as owner, until you delete the list or it expires.
- In faction mode, also your name with your shared attacks for your faction, and the player you claim or reserve in the war room for a few minutes (a reservation for at most 20 minutes).
- For a faction's war room: whether it is on and who switched it.
- For a faction's Faction HQ: its name, who set it up and whether members are approved one by one, and for each member who asked to join or was let in: player ID and name, the status (waiting, approved, declined, removed or left), the HQ role (member or officer), when they asked and who decided and when.
- Left entries are deleted after 90 days; the others, declined ones included, stay until a leader, co-leader or officer changes them.
- For a company's Company HQ: its name, the player ID of the director who registered it and whether employees are approved one by one, and for each employee who asked to join or was let in: player ID and name, the status (waiting, approved, declined, removed or left), the HQ role (member or officer), when they asked and who decided and when.
- Left entries are deleted after 90 days; the others, declined ones included, stay until the director or an officer changes them.
- Whether you are a company's director or an employee, and which company, is read from Torn once with your key (the key is not stored) and kept only in a signed cookie in your browser for one hour; it is not stored on our server.
- Company employees, only if the company's director has an account, is in Company HQ and switches the tool on: the director's own browser reads the list of employees from Torn with the director's key (the key is not sent to us) and sends it, and we store, for each employee, their player ID, name, position, days in the company, when they were last active, their three working stats and their effectiveness (total, working stats and inactivity), with the time.
- The latest list is kept, plus one row per employee and day with the working stats and effectiveness, so the HQ can show what changed.
- History older than 90 days is deleted by the worker, an employee who is no longer in the list loses their history with the next one, and everything is deleted when the director switches the tool off.
- If you are an employee and delete your account, your own rows are deleted from the list and the history at once, and the next lists leave you out while the account waits to be deleted (once it is gone, a list adds you again while you work there).
- Wages and company value are not stored.
- Company stock, only if the director has an account, is in Company HQ and switches the tool on: the director's own browser reads the company's stock from Torn with the director's Limited key (the key is not sent to us) and sends it, and we store, for each product, its name, price, amount in stock and on order and amount sold today, with the time, plus the amount sold per product and day; it contains no player data, the daily sales are deleted by the worker after 90 days and everything is deleted when the director switches the tool off.
- Company job applications, only if the director has an account, is in Company HQ and switches the tool on: the director's own browser reads the applications from Torn with the director's Limited key (the key is not sent to us) and sends them, and we store, for each applicant, their player ID, name, level, their three working stats, when the application expires and its status (only open applications are kept, never the application's message), with the time.
- Only the latest list is kept, with no history; it is deleted by the worker 30 days after it was sent and at once when the director switches the tool off, and an applicant who asks to delete their account is taken out of it at once (the next lists leave them out while the account waits to be deleted).
- The Company HQ note, only if the director has an account, is in Company HQ and switches the tool on: one plain text note of at most 2000 characters that the director writes, with the time and the director's player ID, replaced each time it is saved; it is deleted when the director saves an empty note, switches the tool off or asks to delete their account (or their account is deleted after 12 months of not being used), and with the Company HQ.
- Which HQ tools a leader or co-leader (in Company HQ: the director) switched on for the faction, who the leader or co-leader chose to show members' shared battle stats to (leaders, co-leaders and officers, or every approved member), with their player ID and when they last changed each switch, until they change it again; the player ID is erased from it when that account is deleted.
- Shared battle stats, only if you have an account, are in Faction HQ and turn sharing on yourself in the HQ's Members page: your exact strength, defense, speed and dexterity (and so their total), read from Torn by your own browser with your key (the key is not sent to us), with the time it was sent.
- Only the latest reading is kept, no history.
- It is replaced with a fresh reading when you open the Members page of Faction HQ with sharing on and the last reading is more than an hour old.
- It is deleted when you turn sharing off, when you are removed from the HQ, when a leader or co-leader switches the tool off, and when you ask to delete your account.
- If you leave the faction, it is deleted the next time TornHelper sees you in another faction (when you turn on faction mode there).
- Whatever happens, it is deleted by itself 30 days after it was last refreshed.
- The numbers are read by your own browser, and TornHelper does not check that they are true.
- Help pings in the war room: who sent it (player ID and name; none for the warning the room sends by itself when the faction's chain timer is low, which has the chain length and the seconds left instead), whether it is for a target or the chain, the target's ID and name, and when, for 14 days.
- War room chat: the messages you write (the text, the channel, the ranked war it belongs to, the enemy from the board it names if you chose one, your player ID and name, and when), for 14 days, or until you or a leader or co-leader delete one, or you delete your account (an account that just goes unused does not take them with it); the mutes a leader or co-leader sets on you (your player ID, until when, who set it and when), until they run out; and the reports of a message, which are only a line in the war room log with no message text.
- The chain watch schedule: the hours you sign up for, with your player ID and name, until 14 days after the hour; and the chain warning a leader or co-leader sets for the faction (how much time is left on the timer when the room is warned, and the least chain length it is warned for); and, for the chat's war channel, when the faction's last ranked war started and when the room saw it end (the war's public times, no player data), so the war channel stays open for 24 hours after a war.
- The war room log: what happened in the room (a call, release, Help ping, someone joining or leaving, someone signing up for or leaving a chain watch hour, or the faction's chain timer going low or breaking), with the player ID and name of who did it, the ID and name of the enemy it was about, the chain length (or the hour of a chain watch block) and when, for 14 days; it has no free text and nothing from your attacks.
- The log also notes when a leader or co-leader deletes someone's chat message or mutes someone, and when a member reports a message (the report is shown to leaders and co-leaders only), with the player ID and name of who did it and of the message's author, never the message text.
- A leader or co-leader can add a Discord webhook for the faction: its URL is stored encrypted, with who added it and when, until it is removed, and used only to post Help pings.
- Temporary, in the server's memory only and gone at the latest within a day: who is in the war room, and the board that members' browsers read from Torn (the enemy members' public name, level, hospital, jail or travel status and last action, our own members' status and last action (whether they are online, idle or offline, from Torn's public members list), the ranked war score and the faction chain).
- Also temporary, in the server's memory only: the public status (okay, in hospital, jail, travelling or abroad, and until when) of players your browser checked, for at most 10 minutes, next to a scrambled code per reporter that cannot be turned back into your ID.
- The server uses it only to tell reports from different players apart, and it is gone on restart.
- Usage log: a pseudonym of your player ID (a keyed hash that cannot be turned back into your ID or matched to your shared attacks), the day, the tool you opened and whether it was the site or the userscript, once per tool per day, for 90 days, to count how many players use what; no name, key or IP address.
- You can switch it off in Settings.
- Your key, settings (an account also keeps most of them, see below), the players you tagged (at most five, only their IDs), the status of players you recently looked at and, for a minute, the answers to your Ready now searches and, for ten minutes, the times and the feature of your latest Torn requests (used to keep TornHelper within its limit of 75 requests a minute) stay in your browser, as does a short tag of the key the lists sign-in last ran for (not the key), so a changed key is signed in again once.
- The target filters you apply, and how you set up each player table (the column it is sorted by, rows per page, the Targets mode, levelling source and Baldr list you chose, and the bounty and attacker settings), are remembered in cookies in your browser until you change or reset them; they are sent to our server only as part of the page request and never anywhere else unless you have an account (see below).
- Accounts, if you create one: your player ID and name, when the account was made and when it was last used; its status and, if it was suspended, until when and a fixed reason code; for each device you are signed in on, a hash of its sign-in token (never the token itself), a short device name such as "Chrome on Windows" (never your browser's full identification), and when it signed in, was last used, expires and was signed out; and the faction and company roles your browser last reported (IDs, roles and when), read from Torn by your browser with your key, which our server does not check.
- Synced settings, if you are signed in, so they follow you to your other devices: your display and live-check preferences (including the Look studio and table defaults), your goals, the chain alert threshold and sound, whether the live strip is pinned, the players you tagged, your remembered target filters and table setups, whether Open my last tool directly and the war room Torn-reads switch are on, and whether you finished the tour.
- Each of these areas is stored as one small record (at most 16 KB) with a version number and the time it last changed, and goes when the account does.
- Your key, offline mode, request times, status cache and Discord webhook are never synced.
- Platform roles, for the people who run TornHelper: their player ID, the role (admin or moderator), who gave it and when, and a one-way hash (SHA-256) of the one API key they confirm themselves with on the admin page (never the key itself), kept until the role is removed or the account is deleted.
- An audit log of what admins and moderators do in the admin page (suspending or lifting a suspension, signing an account out everywhere, cancelling a deletion, giving or removing a role, changing a feature flag, registering an admin key): their player ID, the account it concerned, a fixed action name, a few codes or counts (never a key or a token) and the time, kept for 12 months.
- Feature flags, for trying a feature out with some people: which flag is on for whom, and an allowlist of player, faction and company IDs, with who changed it and when.
- A suspended account is kept, with the end date and a fixed reason code, until the suspension ends or is lifted, even past the usual deletion times.
- Re-checking a key for the admin page works like signing in: the key is sent once, used to read whose it is and what level it has, and not stored (for people with a platform role, only the hash above is kept, to tell whether it is the same key next time).
- You can download everything stored on your account as one file in Settings (the anonymous usage log is not in it, because it cannot be linked to you).
- The sign-in token itself is a random value kept in a cookie in your browser.
- A device is forgotten 7 days after it signs out or expires.
- Deleting your account signs you out everywhere at once and removes the account and what is stored on it after 30 days (signing in again within 30 days restores it), and an account that has not been used for 12 months is deleted.
- We have no email address for you, so we cannot send you notices.
|
|---|