This document sets out exactly what data the Kirby Discord bot keeps, why, for how long, and how to have it deleted. It describes how the service actually works, not a generic template.
1. What the bot does
Kirby offers 97 commands and 9 right-click menus. Each area keeps different data, listed in the next section:
- Music — voice channel playback, queue, playlists, favourites, lyrics, audio filters, 24/7 mode, and an Activity playable inside Discord.
- Moderation — ban, kick, timeout, warnings, message purge, channel lock, slowmode, role and nickname management.
- Anti-raid — eight automatic protections: join flood, anti-nuke, join gate, captcha, anti-spam, webhook monitoring, mass-DM detection, username filter.
- Crypto (read-only) — live prices, conversion, balance of a public address, transaction details, price alerts, address watching.
- Wallet — a custodial wallet for Litecoin, Ethereum, Solana and USDT (Polygon and BNB Chain). See section 3, devoted entirely to it.
- Giveaways — draws, entries, winners, voice giveaways.
- Mudae — character collection game: rolls, claims, kakera, wishes, harem and leaderboards.
- Invite tracking — which invite link brought each member in, inviter leaderboard, staff adjustments.
- Utilities — server, member and role cards, polls, reminders, tags, translation, QR codes, calculator, AFK, avatars and banners, support tickets.
- Settings — language, colour, emojis, autorole, welcome and leave messages.
- Fun — dice, coin flip, jokes, would-you-rather, image captions.
Two ways to install the bot
The application installs on a server — where it is granted permissions and its commands are visible to every member — or on your account. In that second case about thirty commands (crypto, wallet, utilities, fun) follow you everywhere: into your direct messages, and even into servers where the bot is not present. Replies there are visible only to you, and the host server receives nothing. An account installation grants no moderation permission whatsoever.
Either installation can be removed at any time from Discord: Settings → Authorized Apps for an account, or by removing the bot from the server.
2. What we keep
| Data | Why | Retention |
|---|---|---|
| Discord IDs (user, server, channel, role) | Tie settings, wallet and history to the right account | As long as the service is used |
| Server settings: language, colour, emojis, log channels, autoroles, welcome messages, anti-raid configuration | Run the bot as configured | 30 days after the bot is removed from the server |
| Music: tracks played, favourites, playlists, player settings | Queue, resume after restart, server statistics | Periodic automatic purge |
| Moderation: warnings, tickets, anti-raid logs | Tools requested by server administrators | Until deleted by an administrator |
| Support tickets: for each ticket, who opened, claimed and closed it, when, its panel, priority, labels, closing reason and rating (1 to 5); for each participant, the number of their messages and the time of the first and the last; the timeline of actions (who, what, when); the blacklist (member or role, reason, expiry). Never the text of messages: Kirby does not read it and makes no transcript. Answers to the opening form, the files attached to it and the written comment after a rating are posted in the channel the server chose, not kept by Kirby (files pass through memory only, long enough to be reposted). | Running tickets (limits, reminders, automatic closing), server statistics, exporting your data | Until deleted by an administrator, and at most 30 days after the bot is removed from the server |
| Applications (a ticket panel of the “application” type): who applied, on which panel, when, the state (pending, accepted, denied), who decided, when, and the reason given. The form answers are posted in the server's review channel, not kept by Kirby. On-call staff: your ID and since when. | Reviewing applications, the delay before applying again, adding on-call staff to new tickets | Until deleted by an administrator, or until you leave on-call duty; at most 30 days after the bot is removed from the server |
| Dashboard: change log (your ID, the part changed, the field names, the date — never their values); temporary access links (a hash of the link, who created it, who it bound to, expiry). | Knowing who changed what; opening the Tickets tab for a while to a trusted person | Log: one year. Links: 7 days after they expire |
| Outgoing webhook (if an administrator sets one): the address and the signing secret, encrypted. For each chosen event, Kirby sends the ticket or application metadata (number, panel, IDs, times, message counts, rating) to that address — never the text of messages nor form answers. What happens to that data next is up to the administrator who chose the address. | Connecting the server's tickets to its own tools | Until the webhook is deleted; at most 30 days after the bot is removed from the server |
| Giveaways: entries and winners | Running the draw and verifying it | Until the giveaway is deleted |
Voice giveaways (/giveaway voice): for each entrant, a
possible elimination, its reason (left voice, microphone or headset
off, left the server…) and its time. The conditions are checked live;
time spent in voice is not saved. Never the audio: no
listening, no recording, no transcription. Past automatic editions
(/giveaway auto, removed on 18/10/2026) keep their
entries (luck coefficient, eligibility, reason for a
disqualification); the voice time they counted has been erased |
Keep the draw for members who stayed in voice with microphone and headset on | Like other giveaways |
| Mudae: characters you own (and the nicknames or notes you give them), wishes, game counters (rolls, kakera, badges, tower), display preferences | Running the game and its leaderboards | Until you ask for erasure (section 6) |
| Invites: who invited whom, the code used, join and leave dates, staff-granted bonuses | Inviter leaderboard, requested by administrators | Until /invites clear, or 30 days after the bot
is removed |
| Reminders, tags, polls, AFK status (if Kirby added “[AFK]” before your nickname, your previous nickname, to give it back) | Give back what you saved | Until due or deleted by you |
Top.gg votes (/vote): date of the last reward claimed,
number of votes, streak, and whether you want a reminder |
Rewarding you (XP, badge) and reminding you when to vote again | As long as the bot exists; on request to support (section 9) |
| Kirby Premium granted for free (vote, 7-day free trial, referral): the source, the start and end dates, and for a referral the server concerned. For referrals, when the bot joins a server it reads the "bot added" entry of that server's audit log to know who added it — nothing else | Unlocking the perks for the granted time, offering the trial only once and each server only once, reminding you the day before the trial ends | Votes: 90 days after they end; trial and referral: as long as the bot exists (so they are not granted twice); on request to support (section 9) |
| Daily counters, without Kirby Premium: how many times today you used the "Translate" and "Convert" right-click menus — one number per day, never the translated or converted text | Applying the free daily limits of these menus | 2 days |
| Command usage measurement: per day, the command used, the server and your ID — the latter only to count distinct people. Never the content of options | Knowing which commands are actually used: Discord caps an application at 100 commands | 60 days, then erased automatically |
| Crypto: price alerts, watched addresses | Notifying you; these addresses are public on the blockchain | Until you remove them |
Server tags (/tag server): name, text, member who
created it, number of uses |
Reply library written by the server's staff | Until deleted, or 30 days after the bot is removed |
Levels (/level), only on a server that turned them on:
XP, number of messages counted, minutes in voice, reactions counted,
XP of the current week and month, and who holds the top spot.
Never the text of a message: only the fact that one
was sent. If the staff made the leaderboard public, the
top 100 (name, avatar, level, XP) are visible to everyone on the site's
/top page; if they import levels from MEE6, Kirby reads
MEE6's public leaderboard (each member's ID and XP) |
Computing the level, the leaderboards (overall, week, month) and reward roles | Until /level reset, when you leave the server if the
staff chose so, or 30 days after the bot is removed |
Reputation (/rep): your point total on each server, and
the log of points given and received (who, to whom, how many, when).
No reason and no text |
Showing the total and the leaderboard, enforcing the delay between two points, giving reputation roles | The log: 90 days; totals: until /rep reset, or
30 days after the bot is removed |
Roles on join (/autorole): if the staff set a delay,
which roles to give you and when; if they turned on « roles given back
on return », the list of roles you had when leaving. For the reaction
to your first message (/greet extras), Kirby remembers
in memory only, for 24 hours, that you just joined |
Giving roles at the planned time, giving your roles back if you return, reacting to your first message | The queue: until the role is given or you leave; kept roles: 30 days, or until you return |
Birthdays (/birthday): day and month that you save
yourself, never the year |
Wishing you a happy birthday on that server | Until /birthday remove, or 30 days after the
bot is removed |
Moderation (/warn auto, timed /ban,
/role temp): automatic sanction levels, and for a temporary
ban or role, who and until when |
Applying the sanction chosen by the staff, lifting the ban or removing the role on time | Until it expires or the staff removes it, or 30 days after the bot is removed |
Supporters (/supporters): who got the role because they
display the server tag, and since when. The tag is read on the public
profile; custom statuses are never read |
Giving the role, and removing it only if Kirby gave it | While the tag is displayed, or 30 days after the bot is removed |
Forms (/form): the form (title, questions, answers
channel). Answers are not kept: they are posted in the
channel chosen by the staff. For a “one answer per person” form, Kirby
remembers who answered and when (not the answer) |
Showing the form and passing the answers on | Until /form delete, or 30 days after the bot
is removed |
/snipe: for each channel, the last deleted message —
author, times, number of attachments, who deleted it and
its text (1,800 characters at most), shown only to
the staff (“Manage Messages” permission) — in memory only, never
written to disk or to a log |
Answering /snipe |
One hour, never written to disk |
Channel settings (/channel): automatic reactions,
auto-publish; /automod: banned words and the other rules
are kept by Discord (AutoMod), not by Kirby. If the staff turned it on,
a message blocked by a Kirby rule adds a warning whose reason is the
name of the rule, never the blocked text;
/channel sticky: the text of the message kept at the
bottom, written by the staff |
Reacting to a channel's messages, publishing announcements | Until removed, or 30 days after the bot is removed |
Server log (/logs): only the setting (channel, chosen
categories). Events (joins, leaves, sanctions, roles, channels,
deleted messages — author, channel and time, never the
text) are posted in the channel chosen by the staff and are
not kept by Kirby |
Keeping the server's staff informed of what happens there | Until /logs disable, or 30 days after the
bot is removed |
Suggestions (/suggest): the text you type in the command,
the votes (who voted what), the staff's decision and its reason |
Showing the suggestion, counting votes, telling you the decision | 30 days after the bot is removed |
Moderation cases (/case): for each sanction (ban, kick,
timeout, warning, and lifting them), a number, the member, the
moderator, the reason written by the moderator, the duration and where
its card was posted. If the staff turned it on, sanctions done by hand
in Discord are read from the server's audit log (who, on whom, what,
the reason typed). Staff notes on a member: the text written by the
staff in /case note add. The cases and notes about you are
in your data export |
Moderation tools requested by the server's administrators | Until deleted by an administrator, or 30 days after the bot is removed |
Feeds (/feed): the feed address or the name of the
channel, subreddit or account followed, the channel, the role to
mention, the chosen message, who added it, and a fingerprint
of the latest items seen (never their title or text). Kirby reads these
public feeds from its server (YouTube, Reddit, Bluesky, GamerPower for
free games, or the chosen site): no member data is sent to them |
Posting in the channel what was just published, never twice | Until /feed remove, or 30 days after the bot
is removed |
Starboard (/channel starboard): for each message that
reached the wall, its channel, its author and its number of stars
(never its text, which Kirby does not read) |
Updating the card's counter, showing the leaderboard | One year, or 30 days after the bot is removed |
Automations (/automation): the rules written by the staff
(when, if, then). They act on members — give a role, post a message,
send a DM — without keeping anything about them; Kirby sees that a
message arrives, never what it says |
Doing what the staff asked, at the right time | Until deleted, or 30 days after the bot is removed |
| Problem log (the dashboard's “Problems” tab): what Kirby could not do on the server (feature, reason, ID of the channel or role involved, number of times) — no member, no text | Showing the staff what blocks and how to fix it | 14 days without happening again, or cleared by the staff |
Ban appeals (the site's /appeal page): that you appealed, on
which server, when, and the staff's decision (who, when, their reason,
the invite created if the appeal is accepted). Your answers
are posted in the server's staff channel and are not kept by Kirby |
Checking that you are banned, passing on the appeal, showing the decision, avoiding endless appeals | 180 days, or 30 days after the bot is removed |
Server backups (/backup): the structure of the server
(settings, roles and their permissions, categories and channels with
their per-role permissions), the server name and the account that made
it. Never messages, members or their roles. A backup
belongs to the person who created it, not to the server. The trap
channel and automatic channel purge only keep their setting |
Reloading the structure on this server or another one, on request | Until /backup delete; an automatic backup replaces the
oldest one; all are erased after one year |
Games (/game, /blindtest): each member's points
per month and per game, the champions' hall of fame; quiz questions
written by the server's staff; for the blind test world tournament,
the server's points per day (shown with its name to other servers in
/blindtest world). Badges and the profile
(/profile) are computed from this data and levels; nothing
more is stored |
Leaderboard, seasons, champion role, question of the day | 30 days after the bot is removed |
| Community server settings: temporary voice channels and their owner, role panels, scheduled announcements (text typed by the staff) | Running these tools | Until deleted; a temporary channel is forgotten as soon as it is empty; a one-off announcement is erased once sent |
Payment requests (/pay): seller, channel, amount,
displayed address, note, status and the transaction found on the
blockchain |
Showing the payment card and updating it when the payment arrives | 7 days after the request ends (paid, expired or cancelled) |
| Wallet: encrypted recovery phrase, hashed PIN, addresses, movement history | Running the custodial wallet | Until /wallet delete |
| Encrypted Discord access tokens (Music Activity and dashboard) | Authenticating you in the Activity opened from Discord, and on the website dashboard | Deleted after 60 days of inactivity |
| Kirby Premium: your settings (colour, badge, banner, AFK GIF, theme, visibility), the history of your latest calculations and conversions (50 at most), your favourites, your monthly counters | Providing the subscription perks and the “Your month on Kirby” card | Until Erase my settings; counters erased after 13 months |
| Kirby Premium subscription: the item purchased, its scope (account or server), the start and end dates, and any refund | Knowing who is entitled to the perks, and until when. Discord passes these entitlements to us; we never see your payment method | Kept, including after a refund or Erase my settings: it is the accounting record of the purchase. No setting and no history is attached to it |
| Images you upload: banner, AFK GIF, tag or poll image | Showing them where you placed them. A copy is kept because Discord links expire after 24 hours | Until replaced, removed, or the tag is deleted |
| Kirby Premium linked role: encrypted Discord access tokens | Updating your linked role when your subscription changes | Until Erase my settings, or until you remove the app in Discord |
The server data listed in section 6 is also erased 30 days after the bot is removed from that server, whatever the period above.
The website dashboard
If you sign in at dash.kirby-tickets.com, Discord gives us your
id, name, avatar and the list of your servers — only to show you
the ones you can configure. That list is not stored: it is requested from Discord
on each visit and kept in memory for one minute, long enough to draw the page.
Your browser receives a cookie (kdash) holding
nothing but a session number: it keeps you signed in from one visit to the next,
and does nothing else. No analytics, no advertising tracker, no third-party
service. Signing out destroys the session server-side — deleting the
cookie alone would not. You can also revoke access at any time from
Discord → Settings → Authorized apps.
Kirby Premium: what becomes public, and only if you ask
Three switches in the My perks panel, all off by default, make
information visible beyond your servers. The supporters wall
(dash.kirby-tickets.com/supporters) shows your name, avatar, badge
and seniority. Your public page shows the same, plus the tags
you mark public and your highest-valued Mudae characters, without server
names. The bot's status can thank you by name, in every server
it is in. Turning the switch off, or the end of the subscription, removes them
at once.
Message content and online status
Discord only sends these two pieces of information to applications it has approved (the “Message Content” and “Presence” privileged intents). Here is exactly what the bot does with them:
- Message content, for anti-spam. Only in a server where anti-spam is turned on: the bot compares each message from a member with the ones they just sent, to spot the same text repeated. The comparison happens in memory, over 50 messages at most per member; the text is forgotten at the end of the detection window (5 seconds by default, set by the server). It is never written to disk or to a log: the log channel shows the sanction and its reason, never the message.
- Message content, for AFK. When a message mentions someone who is away, the bot sends them a direct message with the author, the channel and the link of the message, plus its first 300 characters only if they can see that channel; it keeps no copy. For a Kirby Premium subscriber, it sends no direct message: it keeps the author, the channel, the time and the link (25 mentions at most, never the text) for their return summary, and erases them when they come back.
- Message content, for
/snipe. When a message is deleted, the bot keeps its text (1,800 characters at most) in memory only, for one hour at most, one message per channel (the next one replaces it)./snipeonly shows it to members with the “Manage Messages” permission. It is never written to disk or to a log, and the log channel (/logs) does not show it. - Online status. It is only used to show a member's
status (online, idle, do not disturb, offline) on their
/userinfocard, when someone asks for it. The bot only keeps the last status received, in memory: it is never written to disk or to a log, and no history is kept — the bot does not know when you were online. Your activities (game being played, music being listened to, custom status) are not used.
None of this is sold, shared with a third party, used for advertising or used to train an artificial intelligence model.
What we do not keep
- The content of your messages: no message text is ever saved, except the one you choose yourself to keep as a tag (the Save as tag right-click menu). Your conversations are not stored.
- Your online status and its history.
- Your IP addresses, beyond the web server's technical logs, kept briefly for security and diagnostics.
- Your email, phone number or payment details: the bot never asks for them.
3. The wallet: what you need to know
The wallet is custodial
Your private keys are generated and held on our server, tied to your Discord ID. They are encrypted (AES-256-GCM) and your PIN is never stored in clear text: it is hashed with a salt unique to your account.
In plain terms: the service operator has technical access to your funds. Only use this wallet if you accept that dependency, and do not leave amounts on it that you could not afford to lose.
You can retrieve your private keys and recovery phrase at any time with
/wallet export_keys: they are sent to you by direct message and
remain usable in any external wallet. The bot does not erase them on its side —
for that, use /wallet delete.
4. Who can see what
- Server administrators see the configuration and moderation data of their server. They have no access to your wallet or your keys, and cannot withdraw funds on your behalf.
- Replies to sensitive commands (PIN, private keys, backup code) are sent by direct or ephemeral message, never in a channel.
- Some commands are public by nature: wallet balance, deposit address, history, withdrawal, address balance, transaction, and server, member and bot cards. Do not run them in a channel if you would rather that information were not visible there.
5. Third-party services
To work, the bot queries outside services. It sends them the bare minimum — never your Discord identity:
- Discord — the platform itself (Discord's policy).
- Blockchain explorers and nodes — receive an address or a transaction ID to look up. A blockchain address is public by nature.
- Price providers (CoinGecko, Coinbase, Kraken, Binance, alternative.me for the fear & greed index) — receive a coin name, no personal data.
- Audio and lyrics sources — receive a search term or a link.
- Translation service — receives the text you explicitly ask to translate.
/funservices (Open-Meteo, PokéAPI, Kitsu, TheCatAPI, Dog CEO, xkcd, Useless Facts, Advice Slip, nekos.best) — receive the search typed (city, Pokémon, title), no personal data.- Top.gg — receives the bot's server count, aggregated.
6. Seeing and deleting your data
Seeing it, and taking a copy
Sign in to the dashboard: the bottom of the page lists what the bot keeps about you, section by section, with the number of entries. One button downloads a full copy as JSON — tags, reminders, alerts, giveaway entries, invites, liked tracks, tickets, Kirby Premium settings and history, and the non-sensitive parts of your wallet.
What this export does not contain: your private keys and
recovery phrase. Those come out only through /wallet export_keys,
by direct message, after entering your PIN. A web download must not become a
shortcut to the funds of someone who left a session open.
Deleting it
- Your wallet:
/wallet delete(PIN + typed confirmation). Permanently erases the recovery phrase, the PIN and the addresses. Use/wallet export_keysfirst if funds remain on your addresses: after deletion, the bot can no longer return them to you. - Your other personal data: reminders, tags, alerts and
watched addresses can be removed from their own commands. An administrator
can erase your invite entries with
/invites clear— in both directions: your own join and the ones you brought in. - Your Kirby Premium settings: the Erase my
settings button in the My perks panel (opened from
/help), including after your subscription ends. It erases the settings and their images, the history, favourites, monthly counters and the linked-role connection. - Your voice time: it is no longer counted since
/giveaway autowas removed (18/10/2026), and what had been saved has been erased. - Your Mudae data: contact us (section 9).
- A server's data: remove the bot from the server. 30 days later, the following is erased for that server: settings, anti-raid, warnings, tickets, server tags, payment requests, levels, birthdays, suggestions, server log, role panels, scheduled announcements, game points and questions, invites, giveaways, the Mudae game (characters and counters), music (including its members' playlists and favourites), reminders to be posted on the server and usage measurement. If the bot comes back before then, nothing is erased: a mistaken kick costs nothing. Your wallet, your personal data that does not depend on any server, polls (stored with no link to the server) and the proof of purchase of a server subscription (section 2) are kept.
- Any other request: contact us (section 9). We handle every request within 30 days.
7. Security
- Recovery phrases encrypted with AES-256-GCM; the encryption key is not stored in the database.
- PINs hashed (scrypt, unique salt per account), compared in constant time, and temporarily locked after repeated failures.
- Site served over HTTPS with strict security headers.
No system is flawless. We cannot guarantee absolute security, and we would rather say so than imply otherwise.
8. Minors
The service follows Discord's terms: it is not intended for people below the minimum age Discord requires in their country.
9. Contact
For any question or deletion request, write to us on the Discord support server. It is the fastest route, and the only one we monitor consistently.
10. Changes
This policy may change along with the service. The date at the top shows the latest revision; significant changes will be announced on the support server.