Privacy
Last updated:
The bot stores what it needs to work, keeps API keys encrypted, and does not sell or share data for advertising. Data goes to two other services only: Torn, and FFScouter for one feature. The full list is below.
The bot is run by --Phoenix-- [3656832].
What the bot stores
Section titled “What the bot stores”About a server
Section titled “About a server”- The Discord server’s ID and name, and the faction’s Torn ID and name.
- The settings the admins chose: admin and ping roles, channels, which modules are on, alert settings and the nickname format. These are role and channel IDs, not what is inside them.
- The server’s Torn API key, encrypted.
- The server’s credits: its balance, when it was last charged, and its payments and refunds.
About members
Section titled “About members”Only when a member uses a feature that needs it:
| Feature | What is stored |
|---|---|
| Verification | The member’s Discord ID, Torn ID and name, faction ID, name and tag, profile picture link, whether they are verified, and when they were last checked. |
A member’s own key (/key, joining a chain) |
The key, encrypted, with its owner’s Torn ID and name, which Torn sections it can read, when the member accepted the key terms, and whether Torn later rejected it. A member has one key, which every server running the bot uses, and /key removes it from all of them. |
| Chain | The roster of each scheduled or live chain: who joined, with their Torn name. A copy of each finished chain’s report from Torn, kept for the history. |
| Lotto | Each lotto’s prize, host, winner and status. Each entrant’s Discord ID and Torn name while the lotto runs and for a month after it ends. After that the list of entrants is deleted and only the result stays. |
| Reports | The case: kind, title, text, who filed it (filing anonymously only hides the name from your server’s leadership), its status, and when it was answered or closed. |
| Credits | Each payment: when it was credited, the sender’s Torn name, what was sent and how many credits it bought. |
The stat tracker adds, per member who uses it: their build, goal, daily training numbers and sharing choices (including which alerts and recap they asked for, and the last goal, stall and week they were told about), up to five saved jumps, and, for the faction view, a thin copy of their battle stat history (their latest total, and their last month and three months in thin form), replaced each day. A member’s total is shown to leaders only if they chose to share it.
Usage and logs
Section titled “Usage and logs”- A count of how many times each command was used on each day, for usage statistics. It is not linked to a server or a person.
- Technical logs of what the bot did, kept on the server it runs on so faults can be found. They are not shared.
What the bot does not do
Section titled “What the bot does not do”- It does not read or store the messages people write in your channels. It reacts to commands and button presses.
- It does not ask for passwords or for anything that gives control of a Torn account. A Torn API key can only read what the person chose to allow.
Who else receives data
Section titled “Who else receives data”| Who | What | Why |
|---|---|---|
| Torn | Every request the bot makes with a key, as any app would. | To look up who someone is, a faction’s members and chains, and the developer’s payment log. |
| TornStats (site) | A member’s own Torn key, when they use /progress, and the battle stat history it returns. |
/progress reads the member’s battle stat history from TornStats. The key goes in the request, and TornStats stores it on the member’s account there if they have one. |
| FFScouter (policy) | A member’s own Torn key, only after the member agrees and presses the button that registers it. | The Save chain button needs FFScouter’s target data, which FFScouter gives only to someone using their own key. |
| Discord | What any Discord bot sends: the messages, roles and nicknames it posts or sets. | The bot works through Discord. |
| The hosting provider | The encrypted database and the logs, as stored data. | To run the bot. |
Nothing is sold, and nothing is shared for advertising or profiling.
How keys are protected
Section titled “How keys are protected”Keys are stored encrypted in the database and are decrypted only at the moment they are used, inside the bot. They are never shown on screen and are sent nowhere except Torn’s own API, and FFScouter for the feature above. Each time a member’s key is used, the bot checks it against the Torn account the member verified with.
Keeping and deleting data
Section titled “Keeping and deleting data”- While you use the bot, your server’s data is kept.
- After you remove the bot, your server’s settings, credits and member records are kept, so that adding the bot back is easy. This includes the encrypted server key.
- To have a server’s data deleted, ask the developer with
/report, in the support server, or by Torn mail. A server admin can ask for the server’s data, and a member can ask for their own. - Members can remove their own key at any time with
/key. A server admin removes a verification in/members. - To cut off a key yourself, delete or regenerate it in Torn’s settings. The bot can no longer use it. Torn’s access log for the key shows every call made with it.
- Payment records are kept as long as refunds and disputes might need them.