Privacy

When you log in with Discord we receive your Discord user ID, your username and the list of servers you manage (scopes identify and guilds). These live only in a signed session cookie in your browser until you log out. They are not written to our database. A member without manager rights can log in too, to hand in their own Torn API key: the site then asks Discord, with the bot's token, whether you are a member of that server. Nothing of that answer is stored.

Per Discord server: the server ID, the roles you chose as admin roles, the channels you put on the blacklist, the money goal (heading, amounts, note) and the custom bot lines you add together with the Discord ID of whoever added them.

The keys you submit (a faction can have several, from different accounts), each stored encrypted, plus the faction ID and name it belongs to, the Torn ID and name of the account that owns it, the Discord ID of whoever submitted it and the date. A key is never shown again and can be removed at any time. Keys can be submitted by a server manager or by an ordinary member of the server for their own account (marked as a member key, together with the submitter's Discord ID). Managers and the server owner never see the key of a member, only that it exists, the Torn account and faction behind it and the date, and they can remove it. A member can see and remove their own key on their own page.

Which products a server has booked and until when, whether renewal is cancelled, the server's Xanax balance with every movement on it (payment, booking, renewal, payout), and a record of each payment: the Torn log entry ID, the sender's Torn ID, the amount of Xanax, the time and, for payments the operator entered by hand, a short note. Payout requests are kept with the Discord ID of whoever made them.

While a chain watch runs, the bot keeps the queue of that server: Discord IDs, Torn IDs and names of the people who signed up and their hit counts. It also keeps, per server, the link between a Discord account and a Torn ID, taken from the Torn ID in a member's server nickname, from Torn's own Discord verification, or entered with /link.

When a chain ends with /chain-stop, its leaderboard is kept for that server: the display names, Discord IDs and Torn IDs of the people who took a slot, how many hits each was assigned and how many were detected, plus when the chain ran and how far it got.

The bot does not request Discord's message content intent. It only notices when someone mentions it directly and counts how many messages were posted in the chain channel, it does not read or store what people write.

Technical logs on the operator's server can contain Discord and Torn IDs and error messages. Torn API keys are masked before anything is logged.

To run the chain-watch bot for your faction, to let you manage its settings, and to manage subscriptions and payments. Nothing is used for advertising or sold.

Used only to read your faction's chain status, recent attacks and member list, and to identify the account behind the key so a payment from it can be matched to your server. Nothing else.

Discord and Torn, because the bot and this site talk to their APIs. The hosting provider of the operator's server technically processes everything stored there. Your data is not passed on to anyone else.

Deleted immediately when you press Remove key, or when you replace it.

The queue is deleted when the chain watch is stopped with /chain-stop.

Kept until a server admin deletes an entry on the History page or asks for it to be deleted. Only the latest 200 chains per server are kept, older ones drop out.

Kept until you ask for it to be deleted, since there is no self-service deletion for it yet. Payment records may have to be kept longer for bookkeeping. Backups of the database are rotated and expire on their own after a couple of weeks.

One functional cookie that keeps you logged in, deleted when you log out or close the session. There is no tracking, no analytics and no advertising cookie.

The pages load their typefaces from Google Fonts, which means your browser contacts Google's servers when a page loads.