Privacy Policy

Last updated: July 3, 2026

This policy explains what data the BGMI Unofficial Discord Bot collects, why it is used, how it is stored, and how Discord users or server administrators can request removal.

1. Who this policy applies to

This policy applies when you add, configure, or use the BGMI Unofficial Discord Bot in a Discord server. The bot is an independent Discord utility bot and is not affiliated with Discord Inc. or KRAFTON/BGMI.

2. Information the bot may process

The bot may process the following information only when needed to provide its features:

• Discord IDs: user IDs, role IDs, channel IDs, guild/server IDs, message IDs, and invite IDs.
• Discord profile and server data: usernames, display names, avatars, roles, permissions, join dates, server names, and channel names.
• Command usage data: command names, command options, timestamps, the server/channel where a command was used, and success or error details.
• Message content: message text and attachments only for features that require message access, such as exports, reposting, cleanup filters, reaction tools, or forum post tools.
• Generated exports: CSV or similar files created by export commands, which may include the Discord data requested by the server administrator or authorized command user.
• Dashboard settings: bot configuration such as prefix, status text, log channels, error channels, and command definitions uploaded through the dashboard.

3. Why the bot uses this information

The bot uses information to:

• respond to slash commands and legacy command settings;
• moderate messages when authorized users run moderation commands;
• generate message, invite, member, forum, and reaction exports requested by authorized users;
• manage roles, repost content, create invites, and show server/user information;
• maintain command cooldowns, operational logs, error logs, and bot health statistics;
• store dashboard-managed commands and configuration.

4. Legal and user responsibility notes

Server administrators are responsible for configuring bot permissions appropriately and for ensuring their server's use of export, moderation, and logging features complies with Discord's Developer Terms of Service, Discord's Developer Policy, and any laws or community rules that apply to their server.

5. How information is stored

• Runtime command data may be kept in memory while the bot is running.
• Bot settings and command definitions may be stored in local configuration files or MongoDB, depending on deployment settings.
• Log files may be written to the server hosting the bot for debugging and security monitoring.
• Export files are generated only when an authorized command requests them and may be stored temporarily on the hosting server or sent directly through Discord.

6. Data sharing

The bot does not sell personal data. Data may be sent to Discord as part of normal bot operation and may be stored by infrastructure providers used to host the bot, database, logs, or dashboard. Export files are shared only in the Discord context where the command output is delivered, based on command permissions and Discord channel visibility.

7. Data retention

Data is retained only as long as needed for bot operation, troubleshooting, security, dashboard configuration, or requested exports. Server administrators should regularly delete old logs and export files if they are no longer needed. If the bot is removed from a server, stored server-specific configuration and logs can be deleted on request.

8. Your choices and deletion requests

• Users can ask a server administrator to stop using commands that process their data.
• Server administrators can remove bot permissions, remove the bot from the server, or request deletion of server-specific stored data.
• To request deletion or ask privacy questions, contact the bot owner via Discord (see contact details below).

9. Security

The bot should be hosted with restricted access to the Discord token, dashboard password, database credentials, generated exports, and logs. No system can be guaranteed perfectly secure, but reasonable steps should be taken to limit access to bot data and credentials.

10. Changes to this policy

This policy may be updated when bot features, data practices, hosting, or Discord requirements change. The "Last updated" date will be changed when the policy is revised.