Privacy Policy
This describes what the Hermes Games Discord bot actually stores, taken
from its database schema rather than from a template. If something is not
listed here, the bot does not keep it.
Last updated: 7 October 2026.
What is stored
| Data | Why |
| Your Discord user id |
To know whose entry, duel, turn and score is whose. It is the only identifier used. |
| Your display name at the time you entered |
So a bracket reads as it did when it was drawn, even if you rename yourself afterwards. It is a snapshot, not a live copy. |
| Tournament records — the tournament, its settings (including the price of an entry, if the host gives one, and what the prize is worth), the request to open it — who asked, who approved or rejected it and any reason they gave — its entries, every match and result, and (in an olympics) which dice game each match was dealt, and the game each finalist picked for the final |
They are the tournament. Without them there is no bracket to advance, and no way to point at the game a match was decided by. |
| Duel records — who challenged whom, the stake, the starting number, who won, how many games it was best of and the score between them, and what the game was played for if anyone said |
To run the duel, and to answer /roll history and the leaderboard. What a game is played for is whatever the player typed into item: — it is shown on the game's own cards and kept with the game. |
Plain rolls — who rolled with /roll dice, in which channel, the highest number they asked for, when, and which of the bot's cards published the roll's fingerprint beforehand |
So each roll can be held to the fingerprint posted before it. The number rolled is not stored — it is recomputed from the fairness record — and nothing else about the channel is kept. Kept indefinitely, like the fairness records below. |
| Poker night records — the night, its buy-in and payment detail as the host typed them, who joined, who was recorded as having paid and who recorded it, and where every player finished, along with who recorded each finishing position and when |
They are the night. The payment detail is free text the host typed into pay: — usually a link — and it is displayed on the night's cards and nowhere else. No payment is ever taken, verified or processed: the bot records only that a person pressed a button to say money arrived, and which person that was. |
| Adjustments to a poker record — the month, the change (nights played, finishing places, or participation points), the reason given, and the organizer who made it |
So a corrected count can be explained and undone. Corrections are added rather than overwritten, which is why the earlier value stays visible. |
| Score totals and a settlement ledger |
The notional profit-and-loss shown by /roll stats. Numbers only — see Terms. |
| Fairness records — for each game of chance, the secret it was played from, the fingerprint published beforehand, and the value your click contributed |
So any result can be recomputed and checked by anyone, months later. See Fairness. These are kept indefinitely: a game that stops being checkable stops being proven. |
| An audit log of organizer actions — who forced a result, voided an entry, or substituted a player |
So a contested tournament can be explained afterwards. It names the organizer who acted. |
| Server ids and settings — the organizer role, any per-game organizer roles and who last set them, and whether the server is approved |
To know who may run organizer commands, and whether to respond at all. A role id identifies a role, never a person. |
Message content
The bot does not read your messages. Every command is a
slash command, which Discord delivers as an interaction containing only
what you typed into that command. The bot does not hold Discord's
message-content intent, registers no message listener, and does not read
direct messages.
This changed in August 2026. Death Roll was previously played by typing
!dr, which required the message-content intent: the bot then
received the text of messages in servers it had been added to, checked each
for the !dr prefix, and dropped anything that was not a
command. That is no longer how the game is played, and the intent has been
given up. Nothing was retained from it — the only text ever kept was what a
command's own arguments carried, which is still the case.
Servers the bot has not been approved for are not processed at all.
What is never stored
- Message content beyond what is described above — including anything typed into
item:, which is a command argument like any other and is never read from a message.
- Payment details of any kind — no card numbers, account numbers, balances or transactions. A poker night's
pay: field holds whatever text the host typed, and the bot neither follows it nor knows whether anybody used it.
- Email addresses, IP addresses, or anything from outside Discord.
- Voice, attachments, images, or files.
- Your profile picture. An olympics card shows it beside your name, but it is looked up from Discord each time the card is drawn and never saved.
- Your Discord password or token — the bot never sees them and could not use them.
- Anything at all from a server that has not been approved.
The website
This site is static files. It sets no cookies, runs no analytics, loads no
fonts or scripts from anywhere else, and has no way to identify you. The
hosting provider keeps ordinary web server logs, as any host does.
Who can see it
The data lives in one database, controlled by the bot's operator, and is
not sold, shared or handed to anyone. What is visible in Discord is
visible to the people in that channel: brackets, results, duels and
leaderboards are posted publicly, because that is what a tournament in a
channel is.
Scores and records are per server. Nothing you do in one
server appears on another's board.
How long it is kept
Records are kept for as long as the bot runs, so that history and scores
remain meaningful. There is no automatic deletion. Removing the bot from a
server stops it collecting anything further, but does not by itself erase
what is already there — ask, and it will be.
Getting your data removed
Ask the operator. Press the Info button on any of the
bot's cards — it names the operator and how to reach them — and say which
server and what you want removed. A request to delete a player's records is
honoured; a tournament somebody else is still playing may keep an anonymous
seat where you were, so the bracket does not become unreadable.
Children
Discord requires its users to be at least 13, or older where local law says
so. This bot is not intended for anyone below Discord's minimum age and
collects nothing beyond what is listed above from anyone.
Changes
If what the bot stores changes, this page changes in the same release. The
date at the top is the last time that happened.