Copy Bot

Privacy Policy

This policy explains what data Copy processes, what is stored, and how data can be managed.

Last updated: March 5, 2026

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.

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.

Message content is read in real time for configured features such as auto reactions, counting channels, and auto thread creation.
Presence/custom status data is processed for vanity role checks, and member update events are processed for boost and clan workflows.
Attachments referenced in emoji/sticker commands are read to upload or convert files, then sent to Discord APIs.
Copy does not intentionally persist full message text or attachment binaries in stored bot records as part of normal operation.

For clan tag features, Copy performs authenticated requests to Discord API endpoint /api/v9/users/{user_id} to read clan metadata.
For emoji and sticker copy/get features, Copy fetches media from Discord CDN URLs.
Copy does not sell personal data and does not intentionally disclose data to unrelated third parties.

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.

Configuration data is retained while the bot is in use, unless removed by command or operator action.
Not all tables are auto-purged immediately when a guild removes the bot; cleanup can require manual operator action.
Server admins may request removal of stored configuration related to their guild.

Access to owner-only modules is restricted by owner ID checks. Bot token and infrastructure security depend on host environment controls.

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

Server admins can disable or reset many features directly via bot commands (for example reaction, vanity, clan tag, and counting settings).
Removing the bot stops new processing in that server.
For complete data deletion requests, contact Ismaelpaulino32@gmail.com.

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

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

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