Privacy Policy

Effective 2026-07-02. This covers the hosted MadHoney bot and the dashboard at madhoney.nomadsgalaxy.com, operated by Nomads Galaxy.

What we store

Two files, and that's the whole database:

Server configuration - for each server: the chosen role and channel IDs, your verify message, banner design settings, your per-channel gating choices, and whether ban sharing is on.

Ban log - when the honeypot bans someone (or an admin undoes a ban): the Discord user ID, username, server ID, channel name, and timestamp. Ban entries are what powers the log channel, the dashboard's ban list, and (only for opted-in servers) cross-server ban sharing.

What we don't do

The hosted bot does not read message content. The trap fires on where a message was posted, never on what it says, and the hosted instance runs with Discord's Message Content intent disabled. No analytics, no tracking pixels, no advertising, and we don't sell or share data with anyone. The captcha is generated by the bot itself; no third-party captcha service ever sees your members.

The dashboard

Logging in uses Discord OAuth with the identify and guilds scopes: we receive your Discord username, ID, avatar, and your server list with permission flags, and use them only to show you the servers you can manage. Sessions live in server memory and disappear on logout or when the bot restarts. The only cookie is a session ID; there are no tracking cookies.

The site is served through Cloudflare (their edge handles TLS and caching; their policy applies to that hop) and loads fonts from Google Fonts.

The universal ban list and your data

If a MadHoney honeypot bans you in any server, the record (your Discord user ID) lands on the universal ban list. Servers that opted in to the list may ban you when you join them. An admin unbanning you removes that effect everywhere. If you believe you're on the list wrongly, ask the server that banned you to undo it, or open a GitHub issue and we'll look at the record.

Retention and deletion

Server configuration persists so the bot re-arms if it's re-invited; kicking the bot stops all processing for that server. Ban log entries are kept so ban sharing and the Undo button keep working. To have your server's configuration or a specific ban record deleted, open a GitHub issue from an account that can prove server ownership.

Changes

If what we store ever changes, this page changes with it, along with the effective date above.