Privacy Policy🔒

Kuma Bot is a moderation and community bot, so it processes some of your server's activity to do its job. Here's what that involves, and what we keep:

• Identifiers: Your user ID on the platform you use us on (Stoat, Discord or Fluxer), username, server nickname, avatar, and role IDs. We keep a small cache of usernames, avatars, and role names so past actions still show a real name instead of a raw ID, even after someone leaves or a role is deleted.
• Message processing: To provide AutoMod, the content filter, leveling/XP, keyword alerts, counting, ghost-ping detection, and (where a server has connected a channel to a bridge) relaying your messages to the linked channels on other platforms, Kuma Bot reads messages in real time in channels it can see. This processing (including use of Discord's Message Content intent) is required for those features; it is never used for advertising, profiling, or sale.
• Stored message content: Kuma Bot does not keep a copy of your messages. When server logging is enabled, the content of edited and deleted messages, messages that trigger an automatic moderation action, and the transcript of a purge are written to your server’s own log channel on the platform, where your moderators already control them. Kuma Bot stores only a pointer to that log post, and reads the text back from it when a moderator views the dashboard. If the log post is deleted, or logging was never switched on, the text is gone and the dashboard says so rather than producing a copy.
• Chat Snapshots: When a report is filed or a punishment happens, Kuma Bot records which messages were in that channel, storing their IDs and nothing else. We do not keep a copy of the messages. When a staff member opens a snapshot on the dashboard, the text is fetched live from the platform at that moment. A snapshot reports what was said at the time of the event: if a message was edited or deleted afterwards, Kuma Bot reads what it originally said out of your server’s own log channel, and an edited message is shown as it stood at the time and labelled as edited. A message that is gone from both the channel and your logs is simply reported as unavailable. Snapshots are a moderation record, kept for the server, and the stored IDs are automatically deleted after 60 days. Server owners can delete any individual snapshot from the dashboard at any time, or turn snapshots off entirely with !snapshots off or from the dashboard.
• Verification: If a server turns on web verification, new members complete a captcha (Cloudflare Turnstile) on our verify page. Cloudflare receives your IP address to run that check, and their privacy policy applies to it. Kuma Bot itself stores only that you verified and when (so you aren't asked again), and we do not store your IP address. With smart routing on, a join is scored from signals already visible to the server (account age, whether you have an avatar, name/raid flags, prior cases here); if you're held for review, that score and the reasons are shown to the server's staff and kept with the server's moderation records until resolved. Where a server enables the anti-VPN option, when you complete the captcha your IP is checked against a reputation service (proxycheck.io) for VPN/proxy use, and Kuma Bot keeps a one-way, per-server hash of your IP (never the address itself) solely to spot multiple accounts joining from the same network. These hashes cannot be reversed to an IP and are automatically deleted after 30 days.
• Moderation records: Cases, warnings, mutes, bans, the reasons and appeal text attached to them, and private moderator notes about members.
• Engagement & configuration: Leveling XP, economy balances and purchases, message counts, command usage, channel IDs, timestamps, and your server's settings, toggles, reaction roles, custom commands, keyword lists, giveaways, and feeds.
• Community roadmap: If you post on the public roadmap, we store what you write (your idea or comment, plus the display name, emoji avatar and colour you chose) and a random identifier your browser keeps so your votes only count once and your own posts are marked as yours. There is no account, email or password; the name is whatever you type, so it need not be your real one. Please treat anything you post there as public: ideas and comments are visible to everyone, and new ideas are read by staff before they appear. Clearing your browser storage loses the link to your past posts (they stay up under the name you used). To have a post removed, ask us (see your rights below).
• Website & dashboard: Support tickets (their subject, messages, the contact you provide, and any files you upload), dashboard and staff login sessions, a record of dashboard actions, diagnostic snapshots from the !debug command, and careers applications submitted on the site.
• Cross-platform bridging: If a server admin connects a channel to a bridge, Kuma Bot copies new messages in that channel (their text, attachments, and your username and avatar) to the linked channels on the other platforms (Stoat, Discord, Fluxer), where they are re-posted through a webhook or masquerade so they appear under your name. To keep the copies in sync, Kuma Bot stores a short mapping of the original and relayed message IDs, so an edit or deletion on one side is mirrored on the others. Bridging is off until an admin sets it up, and webhooks are only created in the channels they authorize for it.
• Cross-platform punishments & account linking: If linked communities enable cross-platform punishments, a moderation action (such as a ban) in one community can be applied to the others; to do this, your user ID and the action are shared with the linked servers' Kuma Bot instance. Separately, if you choose to link your own accounts with the !link command, Kuma Bot stores the mapping between your Stoat, Discord, and Fluxer user IDs so your profile and settings follow you across platforms. You can unlink at any time, and this mapping is included in the data you can view and erase from the privacy hub.
• What we don't do: Kuma Bot only reads DMs to handle commands you send it (such as a game's private actions), never your personal conversations, and DM content isn't stored. We don't read channels Kuma Bot isn't in, collect off-platform data or credentials, or use any of the above to build advertising profiles.

• Technical maintenance: Aki Works staff may access the database strictly to fix bugs, investigate crashes, or respond to abuse and security issues.
• No monetization: We never sell, rent, or trade your data to third parties.
• Service providers: Data is hosted on Railway, and messages are delivered through the platform your server is on (Stoat, Discord or Fluxer). A few optional features send specific data to a third party only when you use them: image content scanning sends posted images to Google's Vision API to check for gore/explicit content, AniList profile linking sends the AniList username a member provides to AniList, and Letterboxd profile linking sends the Letterboxd username a member provides to Letterboxd to check the profile and link to it. We don't share your data with anyone else.
• Linked communities you connect: Where a server enables bridging or cross-platform punishments, the specific data those features need (relayed message content and your name/avatar for bridging; user IDs and moderation actions for punishments) is shared with the other communities that server has linked to on Stoat, Discord, and Fluxer. This only happens between communities an admin has explicitly connected, and never with anyone else.
• Legal & safety: We may disclose data only where required to comply with a valid legal request, or to report serious abuse to the relevant platform's staff (Stoat, Discord or Fluxer) or the relevant authorities.