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: 23 August 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, its entries, every match and result |
They are the tournament. Without them there is no bracket to advance. |
| Duel records — who challenged whom, the stake, the starting number, who won |
To run the duel, and to answer !dr history and the leaderboard. |
| Score totals and a settlement ledger |
The notional profit-and-loss shown by !dr stats. Numbers only — see Terms. |
| 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, and whether the server is approved |
To know who may run organizer commands, and whether to respond at all. |
Message content
Death Roll is typed as !dr, so the bot holds Discord's
message content intent and does receive the text of
messages in servers it has been added to. What it does with them:
-
Every message is checked for the
!dr prefix.
A message that is not a !dr command is dropped
immediately — not stored, not logged, not inspected further.
-
For a message that is a command, what survives is what the bot
parsed from it: the mention, the numbers, and which command you meant.
The text itself is not kept as a record.
-
One exception, stated because it is true: if a
!dr command fails with an unexpected error, the text of that
command is written to the operator's error log so the fault can be
diagnosed. This applies only to messages beginning with !dr,
and only when something has gone wrong.
Messages in servers the bot has not been approved for are not processed at
all, and the bot does not read direct messages.
What is never stored
- Message content beyond what is described above.
- Email addresses, IP addresses, or anything from outside Discord.
- Voice, attachments, images, or files.
- 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.