Terms of Service (TOS)

Last updated: October 11, 2025

Welcome to Beetle Discord Bot. By using our bot, dashboard, and related services, you agree to comply with and be bound by the following terms and conditions. Please read them carefully before using our services.

1. Discord Rules Policy

When using Beetle Discord Bot, you must adhere to the official Discord Terms of Service and Community Guidelines. By using our bot, you agree not to:
1. Engage in harassment or hate speech – including threats, discriminatory remarks, or targeted abuse against individuals or groups.
2. Share illegal content – such as pirated software, malware, or NSFW content in servers where it is prohibited.
3. Exploit or hack – using the bot to exploit bugs, spam commands, crash servers, or manipulate the bot for unfair advantage.
4. Disrupt other users – including spam, flooding channels, or performing actions that interfere with normal server operations.
5. Bypass Discord limitations – do not attempt to circumvent account restrictions, bans, or moderation actions. Violation of these rules may result in temporary or permanent restrictions from using the bot, at the discretion of the Beetle development team. Always respect the Discord community and server owners. Using Beetle responsibly ensures a safe and fun environment for everyone.

2. Message Intent

Beetle Discord Bot requires the Message Intent permission to function properly. This permission allows the bot to read messages in your server to enable automation and feature plugins, such as:
• Offensive Content Monitoring – detect prohibited words or phrases.
• Name Change Restrictions – prevent inappropriate username changes.
• Greeting & Farewell Automation – send welcome and goodbye messages automatically. Important:
• We do not store any sensitive message content.
• Messages are only processed temporarily to provide the bot’s features.
• The permission is required solely for the bot to perform its intended functionality safely and efficiently. By granting Message Intent, you allow Beetle to operate automation features while ensuring your private content remains secure.

3. Administrator Permission

Why Beetle asks for Administrator: Beetle requests the Administrator permission (or equivalent elevated permissions) to run moderation features reliably. This includes essential moderation commands such as kick, ban, mute, role management, and other actions that modify server state. Administrator-level access ensures Beetle can perform these tasks correctly across channels and roles and reduces the chance of command failures caused by missing sub-permissions. What we do with that permission:
• Execute moderation actions (kick, ban, timeout, role assignment).
• Manage plugin settings that require changing channel/role state for automation (e.g., mod logs, auto-moderation actions).
• Ensure commands run smoothly and consistently for moderators and automated systems. Safety & best practices:
• You can grant Beetle only the specific permissions it needs instead of full Administrator if you prefer — but missing permissions may prevent certain moderation features from working.
• We strongly recommend only trusted administrators grant these elevated permissions.

4. Channel Bypass

If you want Beetle to not act in a specific channel (for example, a private or announcement channel), use the bypass (blacklist) command to exclude that channel from moderation or automation checks.
How it works:
• When a channel is added to the bypass/blacklist, Beetle will ignore automation and moderation checks there (no auto-deletes, no greeting/farewell triggers, etc.), depending on the feature.
• This is useful for channels where you want free-form posting, sensitive discussions, or third-party integrations. Example usage (conceptual):
• !moderation bypass add #announcements — prevent moderation/automation in #announcements.
• !moderation bypass remove #announcements — re-enable features for that channel.
Notes:
• Bypassed channels are stored in your server configuration and persist until removed.
• Administrators and permitted staff can manage the blacklist as needed.

5. Data Usage

Beetle collects limited data only to ensure its features work properly within your Discord server. This includes:
• Guild ID — to identify and link your server with its plugin settings.
• User ID — to store user-related data for economy systems, moderation logs, leveling, and other plugin features.
• Plugin Data — information necessary for the correct operation of features (e.g., balances, stats, or configuration values).
We do not collect or store any personal information, message content, or sensitive user data unrelated to Beetle’s functionality. All stored data is used only to maintain and improve your experience with Beetle and is kept secure and private at all times. If you remove Beetle from your server, you may request deletion of all associated data at any time through our support server.

6. Data Retention & Deletion Policy

Beetle retains server data for up to 90 days of inactivity to allow server owners time to restore activity without losing configurations or progress.
• After 90 days of inactivity, Beetle will automatically send a notification to the server owner reminding them of the pending data deletion.
• If the bot remains inactive for an additional 7 days after this notification, all associated data — including plugin settings, economy balances, and user profiles — will be permanently deleted from our systems.
• Once deleted, the data cannot be recovered under any circumstances.
• Server owners can re-invite Beetle during the 7-day notice period to cancel the deletion and restore functionality immediately. This policy ensures both performance optimization and responsible data management, while giving server owners fair warning before any permanent removal occurs.