01 Scope and operator
This policy covers Mizuki Bot (formerly ミ✧みずきBot✧ミ) and its website, based on v1.4.1 source reviewed on October 28, 2026. Contact the operator through Discord Support below. Individual server settings may differ from the stated defaults.
Contact the Mizuki Bot operator through Discord Support ↗ (opens a new tab). Provide only the necessary User ID, Server ID, and request details. Never send passwords or Bot Tokens.
02 Data accessed and stored
- Discord data: Server, user, actor, channel, message, and role IDs; permissions; account names; avatars; join times; and account creation times as needed for commands and events. Not every accessed value is stored permanently.
- Case: Incident type, reason, time, mode, points, outcomes, errors, revocation information, and IDs of the people involved.
- Settings: Modes, rules, allowed/blocked domains, channel/role exemptions, log channels, and screening settings, separated by Guild ID.
- Channel locks: Original and applied permissions, potentially including member or role IDs, the actor, reason, expiry, and restoration status.
- Newcomers: User IDs, join times, account age when relevant, restriction reasons, timeout/review status, raid information, and related times.
- Operational logs: Time, command name, Guild ID and User ID for successful commands, status information, and errors. Configured tokens and credentials in certain URL types are redacted, but logs may still contain identifiable data.
03 Messages and DMs
When detection is enabled and permissions/Message Content Intent allow, the bot processes new and edited server messages for spam, mentions, and links. It must still read messages when excerpt storage is off. Text hashes, message IDs, and times are held in memory to compare repeated messages; it does not permanently archive all ordinary chat.
The default is storeContent: false. If staff enable store_content:true, up to 500 characters from detected messages are saved in cases and may appear in Security Log. Disabling it affects new incidents, not existing excerpts immediately. Staff-written reasons may contain personal information even when excerpt storage is off.
Commands are used in servers. There is no incoming-DM chat-reading feature. The bot may send warning or screening-instruction DMs according to settings.
04 Purpose and access
Data is used to execute commands, moderate members, detect rule violations, calculate points, prevent duplicate actions, restore channel permissions/timeouts, and troubleshoot. Primary records are stored in SQLite on the bot's host, separated by server.
The host operator may access the database and logs. Authorized server staff may view cases. Command replies are private to the caller, but announcements, waiting-room cards, Security Log, and Discord Audit Log are visible according to Discord permissions. The bot checks that the Security Log channel is staff-only before sending.
Operation involves exchanging data with Discord under Discord's Privacy Policy. No analytics, advertising, AI-provider transfers, or data-selling integrations were found in the reviewed source. No external bot-hosting provider is specified in this project.
05 Retention and deletion limits
| Category | Observed behavior |
|---|---|
| Cases and message excerpts | Default 30 days, configurable from 1–90 days. Expired records are pruned at startup and approximately every 60 seconds while running. |
| Member join events | Entries with seen_at older than 24 hours are removed during maintenance. |
| Newcomer holds | Records in approved, expired, left, external, or skipped states are removed when expires_at is over 30 days old. Pending or unresolved states remain until resolved. |
| Pre-lock permissions | Removed after successful restoration without conflicts. Records needing review may remain. |
| Settings, counters, and latest raid state | No automatic expiry was found for these tables. The host operator must manage them. |
| Operational logs / backups | No log retention, rotation, or backup-expiry management was found in the reviewed source. Actual retention depends on the host operator. |
Point expiry (24 hours by default) does not delete cases. Revocation retains evidence. Database pruning does not delete messages already sent to Discord channels, DMs, Audit Log, or backup copies.
Removing the bot from a server does not automatically delete every data category in this version. Pruning stops while the bot is offline and resumes on startup. These periods do not guarantee deletion of every copy on the same schedule.
06 Access, correction, and deletion requests
Contact the Mizuki Bot operator through Discord Support ↗ (opens a new tab). Provide only the necessary User ID, Server ID, and request details. Never send passwords or Bot Tokens.
Specify which data you want to access, correct, or delete. The operator may request necessary proof of account ownership or server authority. Ask staff for a private channel before sharing sensitive details; do not post personal evidence publicly.
There is currently no automatic personal-data deletion command. The host operator must review and handle requests manually. Server staff must manage log-channel messages, and Discord-held data must be handled with Discord. Disabling or removing the bot stops new events within the relevant scope but does not replace a request to delete existing data.
To appeal an action, contact your server's staff with the case number for human review.
07 Music, voice channels, and YouTube
Music uses Guild ID, voice channel, requester User ID, video URL/ID, title, thumbnail, duration, queue, and playback state in memory to check access, join, play, and display cards. No member speech-recording implementation was found in reviewed source. Voice join/leave states are monitored for playback management.
yt-dlp contacts YouTube from the bot host to retrieve metadata and audio. Links are normalized to one video URL. No browser cookies or user login are used. Thumbnails reference YouTube’s ytimg domains. External providers may process request information and the host IP under their own policies. No Discord User ID was found attached to video extraction commands.
Temporary audio files in .runtime/music are limited to 128 MiB per track with a 120-second download limit. Code attempts removal after conversion, cancellation, or errors. Forced termination or failed deletion may leave files behind; no startup sweep was found. Queues clear when sessions close or the bot restarts and are not stored in SQLite.
Music logs may contain Guild ID, voice channel, video ID, duration/elapsed time, end reason, voice states, and diagnostics with URLs/credentials redacted. No automatic log retention was found; the host operator must manage it. Standard command logs still include the caller’s User ID.
08 Anti-Nuke data and retention
Stores Audit Entry ID, Guild ID, actor/target IDs, event category, event/receipt times, and evidence confidence. Role-removal plans include role names/IDs, permission bits, managed status, removal/restoration outcomes, and errors. Trusted users are stored in server settings. Manage Server permits viewing status/incidents; the owner configures and confirms restoration.
antinuke_audits entries are pruned when received_at is over 24 hours old; antinuke_alerts use last_at with the same period. antinuke_incidents records and snapshots are pruned when created_at is over 30 days old except planned/enforcing states. Startup changes unfinished plans to review without automatically resuming actions. Associated cases retain their configured 1–90-day lifetime, separate from Anti-Nuke tables.
09 Website data
This static site has no data-entry forms, accounts, cookies, analytics, or external fonts. It stores your selected theme and language in this browser's localStorage only; these preferences are not sent to the bot. Command search runs on your device. Copy buttons write command text to your clipboard only when pressed.
Invite and Support links take you to Discord, which has its own policies. If hosted on Cloudflare Pages, the hosting provider may process IP addresses, request and device information to deliver and secure the site under Cloudflare's Privacy Policy. The operator must update this policy if analytics or other services are added.
10 Policy changes
When bot behavior, settings, or providers change, the operator should update this document and its revision date, announcing material changes through service channels.
Read more: Terms of Service
Talk to the operator
Contact the Mizuki Bot operator through Discord Support ↗ (opens a new tab). Provide only the necessary User ID, Server ID, and request details. Never send passwords or Bot Tokens.
Open Discord Support (opens a new tab)