Privacy
Last updated: September 13, 2026
This policy covers the BMO Discord bot and web dashboard operated at bmobot.bot. It describes data received from Discord, information you provide through commands and dashboard settings, and how that information supports community management. The bot operator can be contacted through the BMO support server.
Data the bot processes
- Server and member information: server, channel, role and user IDs; usernames, display names and avatar URLs; membership and account timestamps; roles, boosts and invite information. We use these for welcome messages, member screening, role management, moderation and server reports.
- Configuration and moderation records: settings entered by administrators, configured messages, warning and jail records, moderation reasons, moderator IDs, saved roles, reminders and temporary voice-channel ownership. These support configured features and continuity across restarts.
- Presence and custom status: when reputation-role features are enabled, online status and custom-status text help determine eligibility for configured reputation and media-access roles. Raw presence is processed in memory; derived qualification signals, role actions, user and server IDs, and event timestamps can be stored in analytics.
- Messages and attachments: the bot processes messages it can access, including text, links, attachment details, author and channel IDs, and edit/delete events, for invite and media rules, moderation, configured audit logs, deleted-message recall, text commands and game answers.
- Activity reports: stored records include join and leave events, introduction and first-activity timestamps, message counts by member and channel, voice participation duration, and daily server-level keyword counts derived from message text. Activity reports do not require a member to invoke a command.
The bot keeps operational caches in memory and saves configuration, moderation and analytics records on its host. Configured audit logs can copy edited or deleted message text, attachments and their links into Discord log channels. Deleted-message recall can also repost content publicly in a server, and can be available to qualifying reputation-role or booster members as well as moderators.
Dashboard sign-in and website use
Discord OAuth provides your user ID, username, avatar and server list, including permissions, so the dashboard can identify servers you manage. The session retains the manageable server list and OAuth access and refresh tokens in memory. A signed session cookie keeps you signed in. Sessions are valid for up to seven days from sign-in; logging out removes the active session and cookie. Expired session records are removed when accessed, and a service restart clears in-memory sessions.
Joining the BMO support server is optional and uses its separate invite link. Dashboard actions use the bot to make the changes you request. Signing in does not join servers or publish messages as your Discord account.
Public profile lookup displays Discord profile information for a supplied user ID, such as the username, avatar and public badges. The website processes connection information, including IP addresses, for serving requests and limiting abusive lookups. Operational logs can include request metadata, errors and Discord identifiers. Browser storage also keeps interface preferences and pending dashboard actions.
Optional AI and voice features
When AI commands are available and you use them, the question you submit is sent to OpenRouter and the model provider it routes the request to, together with the bot's instructions, to generate a response. AI-assisted games can send generated game instructions to those providers. General server conversation history is not included in these requests. BMO uses these models for inference and does not run a model-training pipeline. Requests require OpenRouter to exclude providers that collect user data and to use endpoints classified as having a zero data retention policy. Provider fallback is disabled; requests fail if an eligible endpoint is unavailable. These restrictions rely on OpenRouter's provider classifications and do not remove messages already posted to Discord. In the OpenRouter workspace used for BMO, prompt and response storage and external observability broadcasts are disabled. The account's separate option to let OpenRouter use inputs and outputs in exchange for a data-sharing discount is also disabled. Responses may be posted in the Discord channel where the command was used. Avoid including information in an AI prompt that you do not want sent to these providers.
If the optional voice-listening feature is enabled and started in a voice channel, it buffers audio and transcribes it locally to detect configured phrases. It can post transcripts and short audio clips, including recent channel context, to an administrator-selected Discord log channel. Transcript logging can be enabled separately. Voice-feature settings are stored on the bot host; audio buffers are held in memory, and posted clips and transcripts remain in Discord until removed there.
Who can access data
The bot operator and the hosting provider, DigitalOcean, process data to operate the service. Server staff can access applicable configuration, moderation and analytics through the bot and dashboard according to their permissions. People with access to a Discord channel can see bot messages, including logs, AI responses or recalled messages posted there. Administrators control the permissions of the channels they configure.
Discord processes bot interactions and content hosted on its platform under the Discord Privacy Policy. Optional AI processing involves the providers described above. Website resources, such as avatars, fonts and badge images, can be loaded from external content providers, which receive the associated web request. We do not sell your data or provide Discord API data to advertising networks.
Retention and deletion
Persistent configuration, moderation and activity records do not currently have a universal automatic deletion deadline and may be retained for longer than 30 days. They support continuing server configuration, moderation history and historical reports until removed by the operator or through the relevant feature. Leaving a server, revoking dashboard authorization or removing the bot does not automatically erase existing stored records.
Deleted-message recall uses a bounded in-memory cache with a ten-minute display window. That window is not an automatic erasure deadline: entries are removed during cache cleanup, eviction or a restart. Copies already posted to Discord, including audit logs and recalled messages, have their own lifetime and are not removed by that cache cleanup. Discord channel administrators manage those copies.
To request access, correction or deletion of data held by the bot, contact the bot operator through the BMO support server. Provide your Discord user ID, the relevant server ID if known, and the records or request involved. Ask support to arrange a private conversation before sharing sensitive details. We may need to verify your identity or authority over a server to prevent unauthorized access or deletion. For copies in your community's Discord log channels, also contact that server's administrators. There is currently no self-service command that deletes all data associated with a user.
Your choices
Server administrators can change feature settings, channel permissions and the bot's access, or remove the bot. You can choose whether to use optional AI commands and can revoke dashboard access under Discord → User Settings → Authorized Apps. The bot does not currently provide a general per-user opt-out from presence processing or message-content processing in servers it can access. Removing a qualifying custom-status token stops that qualification; it is not a general data-processing opt-out. Contact support about data requests and your community's administrators about the features enabled there.
Questions about this policy or reports about the bot's handling of data can be raised in the BMO support server. Changes to this policy will be published on this page with an updated date.