// legal / privacy
Privacy policy
What the bots keep, why, where it lives, for how long, and how to have it deleted.
Who this covers
The Discord bots made and run by hunnaG: TicketBot, EventBot, GiveawayBot, RoleReactionBot, MafiaBot, ScribeBot and DBDBot. They are free and run as a hobby. This page is about what the bots themselves keep. Discord's privacy policy covers what Discord does.
In short
- The bots keep as little as they can: the IDs Discord gives to servers, channels, roles, messages and people, the settings a server's admins choose, and the few things listed per bot below.
- Nothing is sold, shared, or used for advertising, profiling or AI training. The bots run no analytics.
- It all lives on one Raspberry Pi run by hunnaG, and is not copied to any other service.
- Two bots read message text: TicketBot inside a ticket when it closes, and ScribeBot in a channel an admin asks it to copy or export. Neither keeps that text on the Pi.
- Two bots see a server's member list: MafiaBot to start a game and match votes to players, and RoleReactionBot to give an auto-role to people who join. Neither stores the list.
What every bot keeps
- Its settings for each server: which roles count as its admins, and the channels and options an admin picked. These are what the bot needs to work in that server.
- How many servers it is in: just the number. That number, and whether the bot is online, is published on the status page. No server names or IDs are published.
- Error logs: when something goes wrong, a bot writes a line to the Pi's system log, which can include a server, channel or user ID, or a username. That log is held in memory only and is wiped each time the Pi restarts.
Per bot
TicketBot
- Keeps
- Per server: the Tickets category, the log channel, the admin and notify roles, the ticket categories, a ticket counter, and the role that stops someone opening tickets.
- While a ticket is open: its number, its category, the user ID of the person who opened it, and who claimed it. This is removed when the ticket closes.
- Reads
- The messages inside a ticket, once, when it closes, to build the transcript (this needs the Message Content intent).
- Where it goes
- The transcript (each message's time, the author's username and the text) is posted in the server's own log channel and, if the server turned it on, sent by DM to the person who opened the ticket. The bot keeps no copy: a long transcript is written to a file for the moment it takes to upload, then deleted.
- Kept
- Settings: until deleted (see below). Open-ticket records: until the ticket closes.
EventBot
- Keeps
- Each event: title, type, channel, sign-up deadline, team sizes, its sign-up questions and its log channel.
- Each sign-up: your user ID and, if the event asks, your yes/no answer and your written answer. For team events, the team name and the user IDs of the crew.
- Per server: the timezone and the admin roles.
- Where it goes
- Sign-ups show on the event post, and in the log channel if the event has one.
- Kept
- 30 days after the event's time, or sooner if an admin deletes the event or its post is deleted. An old event whose time the bot can't read stays until it is deleted. Un-sign removes your sign-up at any time.
GiveawayBot
- Keeps
- Each running giveaway: title, prizes, channel, message and end time.
- Per server: the admin roles, and a blacklist of user IDs that admins add.
- Where it goes
- It does not keep a list of entrants: entering is a 🎉 reaction, which stays on Discord. When a giveaway ends the bot reads the reactions, draws the winners, announces them and forgets the giveaway. A pool giveaway is drawn the moment it is made and never stored. It DMs you to confirm an entry and if you win, when your DMs are open.
- Kept
- Giveaways: until they end. Blacklist and admin roles: until deleted.
RoleReactionBot
- Keeps
- Per server: which message, emoji and role belong together, the channel, and the admin roles.
- The auto-role, if an admin sets one: one role ID per server.
- Reads
- Who joins the server, and who accepts the rules where the server uses rules screening (the Server Members intent), to give the auto-role. If an admin asks for the auto-role to go to the members already there, it goes through the member list once. Nothing about members is stored: no IDs, names or join times.
- Where it goes
- Nothing about members: it hands out or takes back a role as each reaction happens, and gives the auto-role as people join. Bots never get it, and where the server uses rules screening a member gets it only once they accept the rules.
- Kept
- Until an admin deletes the post or the pairing, or turns the auto-role off.
MafiaBot
- Keeps
- Per server: the game settings and the admin roles.
- Per player, per server: your user ID, your username, and game counts (games played and won, the roles you played and won as, and similar tallies such as saves as Doctor or correct votes). Older numbers from before stats were per server are kept apart and shown nowhere.
- Reads
- The server member list (the Server Members intent), to start a game from the people in a voice channel and to match votes to players. The list itself is not stored.
- Where it goes
- A game in progress lives in memory only. /mafiabot mystats shows you your own numbers; /mafiabot stats shows server totals only.
- Kept
- Until the server owner deletes it from /mafiabot privacy, or you ask. The older numbers belong to no server, so they go only when you ask.
ScribeBot
- Keeps
- Per server: the admin roles, the message ceiling per job, whether author-style copies are on, and the IDs of the servers it is linked with for cross-server copies.
- Saved presets (up to 50 per server): a name, the source channel, the destination (and its server, for a copy into another server), and the filters, which can include user IDs and words to search for.
- Reads
- The messages in a channel when an admin runs a copy or an export, only in channels that person can read (this needs the Message Content intent). For a copy into another server, it also looks up whether that person is a member and an admin there; the lookup is not stored.
- Where it goes
- A copy is posted to another channel in the same server; with author-style copies on, it is posted through a webhook under each original author's name and avatar. A copy can also go into another server, but only one an owner or administrator of both servers linked with a one-time code, only when the person running it is a ScribeBot admin in both, and always as plain posts with each author's name in front, never as the original authors. An export comes back as files (text, Markdown or JSON, with attachments if asked) posted in the same server. All of it is built in memory and never saved on the Pi.
- Kept
- Settings, links and presets: until an admin deletes them or asks. A link also goes when either server removes it.
DBDBot
- Keeps
- Nothing beyond the server count every bot keeps.
- Kept
- Nothing to keep.
Where it lives, and who sees it
In plain files on one Raspberry Pi run by hunnaG, reachable only by hunnaG. The bots talk only to Discord (ScribeBot also fetches images from Discord's own file servers when it copies an embed). The data is not shared with anyone or sent to any other service. If hunnaG keeps a backup copy, it stays private to hunnaG and a deletion covers it too.
How long
- Running giveaways last until they end; open-ticket records until the ticket closes.
- Transcripts, copies and exports are not kept by the bots at all.
- Error logs last until the Pi next restarts.
- Events and their sign-ups are deleted 30 days after the event's time.
- 30 days after a bot is removed from a server, everything it keeps for that server is deleted. Adding the bot back before then cancels it.
- Until then, the rest (server settings, blacklists, presets, reaction posts, Mafia stats) is kept until an admin deletes it with the bot's commands, the server owner deletes it all (below), or you ask.
Deleting your data
Some of it you can remove yourself, right now:
- Your event sign-up: the event's Un-sign button.
- Your giveaway entry: take back your 🎉 reaction.
- Server admins:
/event delete,/giveaway delete,/giveaway removeblacklist,/rolereaction deletepost,/rolereaction autorole off,/scribebot preset delete,/scribebot link remove, and each bot'sadmins removeand setup commands. - Server owners: every bot but DBDBot (which keeps nothing) has
/<bot> privacy, for example/eventbot privacy. It shows what that bot keeps for your server, with a button that deletes all of it at once. The bot stays in the server; its setup has to be done again.
For anything else (your MafiaBot stats, a blacklist entry, or anything you can't remove yourself), open a private ticket in #help on the hunnaG Discord server. No email, and nothing beyond the Discord account you already use with the bots. Say which bot, and give your user ID, or the server's ID if you own or run the server. The data is deleted within 30 days, usually much sooner, and the ticket gets a reply when it is done.
Age
The bots are for people old enough to use Discord: 13, or older where local law says so. They do not ask anyone's age or collect anything more about anyone.
This website
This site uses Cloudflare Web Analytics, which counts page views without cookies and without identifying visitors. The live status badges are fetched from a public file on GitHub.
Changes
If this page changes, the date below changes with it, and real changes get a line in the log.
Contact
A ticket in #help on the hunnaG Discord server, as above, or through GitHub: github.com/hunterg2.
Effective 2026-11-13. See also the terms.