Privacy

What the bot stores

For each server the bot stores the server ID, the theme used, the IDs of the channels, categories and roles it created, the active license (plan and expiry date) and how many times some features were used, to apply plan limits.

When you use the other features the bot also stores: saved themes, backups of the server layout (names and permissions of roles, channels and categories, never message content), recurring event schedules, and each member's points, check-in streak and last check-in day, by Discord ID. When you buy a plan with /mua the bot stores the order: the plan, days, amount, status and the Discord IDs of the server and the person who ran the command.

Admin tools and the dashboard

When you use the welcome flow, AutoMod and tickets, the bot stores each tool's settings (the channel and role IDs you pick, the welcome text you write), the ID of each ticket channel with the IDs of who opened and closed it and when, and the health scores of recent checks. It stores no ticket content and no messages. AutoMod rules are enforced by Discord itself.

If you sign in to the web dashboard, the bot uses Discord sign-in to learn who you are and which servers you administer, then revokes that access token straight away. It keeps only a signed session cookie in your browser, never your password or your access token.

Protection, moderation and the log

When you use anti-raid, lockdown and the anti-nuke guard, the bot stores the settings (thresholds, action, alert channel) and the state of a running lockdown: the list of locked channels with @everyone's previous send permission and the old verification level, so it can put things back exactly. Counts of joins or deletions are held in memory and not stored.

When you use /canhcao, /timeout, /kick and /ban the bot stores one case per action: the ID of the member, the ID of the moderator, the kind of action, the reason the moderator typed (up to 300 characters), the time and the length of a timeout. Admins read them back with /hoso. The mod log writes to the channel you pick who was banned or unbanned, which role changed permissions, and which AutoMod rule blocked whom in which channel. The log never includes the text of a blocked message.

Activity points, giveaways, polls, role menus

When activity points are on, the bot stores per member (by Discord ID): points, the number of messages counted, minutes in voice rooms, and points earned today. It only knows who wrote in which channel and who is in which voice room, and never reads or stores any text.

Giveaways store the IDs of people who pressed Join and of the winners. Polls store the ID of each voter and their choice so everyone votes once; the poll message never shows who voted for what. Role menus store which roles a menu offers, not who took which role.

Temporary rooms, stats channels, scheduled messages, reminders, suggestions, blocked words

Temporary voice rooms: the bot stores the channel ID of each room it makes, the ID of the member who made it and the time, until the room is deleted. Stats channels store only settings (the channel ID, the kind of number, the name template) and nothing about members. Scheduled messages store the channel, the text an administrator wrote, the time and the ID of whoever created it. The custom blocked word list an administrator types is stored in the server's AutoMod settings, and the bot never receives or stores a blocked message because Discord does the blocking.

Reminders (/nhacviec): the bot stores the ID of the person, the text they typed (up to 300 characters), the due time, and the server and channel where it was made (to remind in the channel when direct messages fail). A delivered reminder is deleted after a month and every reminder after a year at most; people can delete their own with /nhacviec xoa. Suggestions (/gopy): the bot stores the ID of the sender, the text they typed (up to 500 characters), the staff decision with its note, and each vote by member ID (up or down); the suggestion message never shows who voted. The new-account filter only reads the creation date of the account that joins and stores nothing.

Anonymous counts

To learn where people drop off, the bot counts each step: invited, finished /batdau, built, tried, paid, left. Each count stores only the server ID, the name of the step and the time, with no user name or ID and no content. The weekly report uses the same counting for new members and AutoMod blocks.

The status page

The website's status page asks the bot directly from your browser. The bot answers with its version, how long it has run, a server count (rounded down to ten) and how fresh its heartbeat is, with no ID or name. The website does not store that answer.

AI design

When you use /thietke or /vietgiup, the description you type is sent to Google's Gemini service to create the design or the draft. For the plain-words explanation of a health check, the bot's own findings (never message content) are sent with it. Only that is sent, with no usernames or message content. The bot currently uses Google's free tier, so Google may use content sent through it to improve its products. Do not enter personal or secret information in the description.

Payments

Automatic payments go through Stripe (stripe.com, by card) or payOS (payos.vn, by Vietnamese bank QR code). You enter your card or bank details on the pages of Stripe, payOS and your bank, never on Discord or in the bot. The bot does not see or store your account or card number, only whether the order has been paid.

What the bot does not do

The bot does not read or store message content, does not ask for the Message Content permission and uses no privileged Discord intent. It only receives these events: messages (to know who wrote where and to see Discord's join notice, not to read text), voice room state (to make and clean up temporary rooms and to count voice points), bans and unbans, and AutoMod blocks. It does not sell or share data with third parties.

Permissions on your server

The bot needs permission to manage channels, roles and the server in order to build it. It only deletes channels and roles it created itself, and only after an administrator confirms.

Deleting data

An administrator can run /xoadulieu so the bot forgets the list of channels and roles it built and the settings. The license, usage counts and the trial mark are kept to apply the plan. The command also removes activity points, moderation cases, giveaway entries, poll votes, role menus, tickets, backups, saved themes, the custom blocked word list, temporary room records, scheduled messages, reminders made in that server, and suggestions with their votes for the server. To have one member's data deleted, message the bot owner. Removing the bot from the server stops all bot activity there.

Contact

For questions about data, message the bot owner on Instagram: instagram.com/nhaajt_hehee, or see nhaajt.com.