Privacy Policy

1. Scope

This policy applies to the Copy Discord bot as currently implemented in the active codebase loaded by main.py.

It covers bot behavior in Discord servers and limited owner-only operations.

2. Data Stored by the Bot

• Server and config identifiers: guild IDs, guild names, channel IDs, role IDs, and module settings.
• Counting module state: channel ID, current number, last user ID, and high score fields.
• Auto reaction settings: trigger phrases and configured emoji lists per guild.
• Boost role settings and optional boost log channel IDs.
• Vanity and clan tag settings, including configured codes, role mapping, and embed templates.
• Support case metadata: case, guild, channel and opener IDs, subject, status, timestamps, and private archive message IDs. Raw case messages are not stored in the bot database.
• Live LFG data: voluntary enrollment and the current game/role assignment. Historical presence, status, and game records are not created.

3. Data Processed in Real Time

• Message content is read in real time for configured features such as auto reactions, counting channels, and auto thread creation.
• When a support case is closed, its channel history is processed in memory to generate a sanitized transcript that is posted to the server's private Discord archive.
• Attachments referenced in emoji/sticker commands are read to upload or convert files, then sent to Discord APIs.
• Presence/custom status data is processed for configured vanity roles. For Live LFG, Copy acts on Playing activities only for voluntarily enrolled members.
• Copy does not persist raw message text, support transcripts, attachment binaries, or presence history in its database.

4. External Requests and Data Sharing

• Copy uses Discord's official Gateway and API data to operate configured message, member, clan tag, support case, and Live LFG features.
• For emoji and sticker copy/get features, Copy fetches media from Discord CDN URLs.
• Copy does not sell personal data, use it for advertising or profiling, or use message or presence data to train AI or machine-learning models.

5. Logs and Diagnostics

• If logging module is enabled, command errors and bot events may be written to logs/bot.log on the host environment.
• Diagnostics may track aggregate traffic counts (messages, commands, presence updates, member updates) and general performance metrics.
• Diagnostics are restricted to owner-only admin commands.

6. Retention

• Configuration data is retained while the bot is in use, unless removed by command or operator action.
• Support transcripts remain inside the administrator-selected private Discord archive for 1 to 90 days and may be deleted earlier by an administrator.
• Live LFG active assignments are deleted when the activity ends or the member leaves LFG. Enrollment remains only until the member leaves the feature.
• Stored guild configuration is purged from the bot database when the bot leaves that guild.

7. Security

Access to owner-only modules is restricted by owner ID checks. Support archives must be private to @everyone, transcripts are HTML-sanitized, and each transcript includes an integrity hash.

No internet-facing security control can guarantee zero risk. Administrators should review granted permissions and logs regularly.

8. User and Server Controls

• Server admins can disable or reset many features directly via bot commands (for example reaction, vanity, clan tag, and counting settings).
• Members can leave Live LFG with /lfg leave. Server administrators control support retention and can delete archived case records.
• For complete data deletion requests, contact Ismaelpaulino32@gmail.com.

9. Children

Copy is intended for Discord users and communities that meet Discord minimum age and platform rules.

10. Changes to This Policy

This policy may be updated as features change. The latest version and date published here are authoritative.

11. Contact

For privacy requests or legal questions, contact the bot owner at Ismaelpaulino32@gmail.com.