Privacy Policy

Effective Date: July 3, 2026

This Privacy Policy explains how ProKameron Bot collects, uses, stores, shares, and deletes information when the Bot is added to a Discord server, used through Discord commands, or configured through the dashboard. This Policy applies to the Bot and dashboard only. Discord separately processes information under Discord's own Privacy Policy.

1. Information the Bot Receives from Discord

When the Bot is in a server or a user interacts with it, Discord may provide the Bot with information needed to operate, including Discord user IDs, usernames, tags, display names, avatars, server IDs, server names, channel IDs, role IDs, role names, message content visible to the Bot, message metadata, command inputs, interaction data, member join and leave events, member updates, role updates, channel updates, invite events, voice-state events, emoji and sticker events, scheduled event updates, webhook updates, and other Discord gateway or API data permitted by the Bot's permissions and intents.

2. Information Stored by the Bot

The Bot stores only the information it needs for configured features and operation. Depending on server configuration, stored data may include:

• Server settings: language, prefix, feature toggles, log channel ID, welcome channel ID, welcome, bot welcome, leave, bot leave, and DM welcome messages, join role IDs, role-saving settings, locked role settings, honeypot settings, server stats settings and channel IDs, slur filter settings, extra blocked terms, warning messages, and custom command definitions.
• Dashboard sessions: Discord OAuth access tokens, refresh tokens, token expiration times, Discord user profile data needed to identify the dashboard user, manageable guild data returned by Discord, session IDs, creation time, refresh time, and last active time.
• Moderation cases: case ID, action type, target user ID and tag, moderator user ID and tag, reason, duration where applicable, and timestamp.
• Saved roles: user IDs and role IDs saved for role restoration when role saving is enabled.
• Locked member memory: user IDs, locked role IDs, and timestamps for members who leave with the configured Locked role so the role can be restored if they rejoin.
• Temporary snipes: deleted message author ID, author tag, avatar URL, message content, first attachment URL, channel ID, and timestamp, stored in memory for up to 3 hours and limited to recent deleted messages per channel.
• Operational logs sent to Discord channels: if logging is enabled, log messages may include deleted or edited message content, moderation actions, member joins and leaves, role or profile changes, voice activity, channel changes, thread changes, role changes, invite changes, webhook changes, emoji and sticker changes, scheduled event changes, server setting changes, and AutoMod events.

3. Information Not Intentionally Collected

The Bot does not intentionally collect payment card data, government identification numbers, health records, biometric data, precise geolocation, Discord account passwords, private Discord DMs between users, voice call audio, video call content, or screen-share content. The Bot may receive message content in servers where it has permission and where Discord provides that content for commands, filters, moderation, snipes, or logs.

4. How Information Is Used

Information is used to provide and secure the Bot, including command execution, moderation, logs, slur filtering, custom commands, role saving, locked-role restoration, join roles, welcome and leave messages, DM welcome messages, server stats channels, honeypot enforcement, dashboard authentication, server configuration, localization, troubleshooting, abuse prevention, and compliance with Discord rules and legal obligations.

5. Legal Bases Where Applicable

Where data protection law requires a legal basis, the Bot processes information as necessary to provide the requested service, based on the legitimate interests of operating and securing the Bot and Discord communities, based on Server Administrator configuration and user interaction, and, where required, based on consent or legal obligation. Server Administrators are responsible for ensuring they have a lawful basis to enable optional features in their communities.

6. Dashboard Cookies and OAuth

The dashboard uses a signed session cookie to keep a user logged in. Dashboard sessions are stored locally and include Discord OAuth tokens so the dashboard can refresh access and show manageable servers. Sessions are pruned after 7 days of inactivity. Logging out deletes the dashboard session. The dashboard does not use advertising cookies.

7. Sharing and Disclosure

The Bot does not sell personal information. The Bot may disclose information in the following ways:

• To Discord, because the Bot operates through Discord and sends configured messages, logs, moderation actions, channel updates, role updates, and command responses through Discord.
• To server channels selected by Server Administrators, such as log channels, welcome channels, honeypot channels, locked-role channels, and server stats categories or channels.
• To users who invoke commands or view command responses, moderation history, snipe results, custom command responses, or dashboard pages they are authorized to access.
• To service providers or libraries used to operate the Bot, host the dashboard, process OAuth, perform translation, or provide infrastructure, only as needed for Bot functionality.
• When required by law, legal process, security investigation, abuse prevention, or to protect the rights, safety, and integrity of the Bot, users, Discord communities, or the Operator.

8. Data Retention

Server settings, custom commands, moderation cases, saved roles, locked-member memory, and dashboard sessions are stored until deleted, overwritten, disabled, pruned, or no longer needed. Dashboard sessions are removed after 7 days of inactivity. Temporary snipe data is kept in memory for up to 3 hours and is lost on restart. Discord log messages sent to server channels remain in Discord according to that server's retention and moderation practices. Backups, if any, may retain data for a limited period until rotated or deleted.

9. Server Administrator Controls

Server Administrators can disable optional features in the dashboard, including logs, role saving, locked role, honeypot, welcome messages, DM welcome messages, leave detection, join roles, custom commands, slur filter options, and server stats. Removing the Bot from a server stops future Bot processing in that server, but may not automatically delete existing local records or Discord messages already sent by the Bot.

10. User Choices and Requests

Users may ask a Server Administrator to review, correct, or remove server-specific data visible to that server, such as moderation records or roles. Users or Server Administrators may also contact the Operator through the available support or contact channel to request access, correction, deletion, or restriction of data stored by the Bot. Requests may require verification of Discord identity and server authority. Some information may be retained where needed for security, abuse prevention, dispute resolution, legal compliance, or legitimate moderation records.

11. Children

The Bot is not directed to children under 13 and should not be used by anyone who is not allowed to use Discord. If the Operator learns that the Bot has knowingly collected personal information from a child under 13 in a way that requires deletion, the Operator will take reasonable steps to delete that information.

12. Security

The Operator uses reasonable technical and organizational measures to protect stored Bot data, including local JSON data stores and signed dashboard sessions. No system is perfectly secure. Server Administrators should grant only the permissions the Bot needs, keep dashboard access limited to trusted users, and avoid placing sensitive personal information into custom commands, welcome messages, filter terms, or moderation reasons unless necessary.

13. International Processing

The Bot may be hosted and operated in the United States or other locations. By using the Bot, you understand that information may be processed outside your country and may be subject to different data protection laws than those in your jurisdiction.

14. Changes to This Policy

The Operator may update this Privacy Policy as Bot features, laws, or practices change. Continued use of the Bot after an update means you acknowledge the updated Policy. If you do not agree, you should stop using the Bot and remove it from your server.