Privacy Policy

Overview

This Privacy Policy explains how the Discord bots Coco and Tygrys process data.

Coco and Tygrys are private Discord bots created and operated exclusively for one Discord server. They are not public multi-server bots, are not listed for public installation, and are not intended to be installed or operated by other communities.

1. Summary

Applies to both bots

Coco and Tygrys process Discord data only as necessary for server safety, moderation, anti-abuse protection, audit logging, staff review, and bot operation.

The bots do not sell user data, do not rent user data, do not disclose user data to data brokers or advertising networks, do not use user data for advertising, do not profile users for unrelated purposes, and do not use message content to train, fine-tune, evaluate, improve, or operate AI or machine learning models.

Coco-specific summary

Coco processes message content and attachment metadata in real time to detect unsafe links, invite spam, suspicious scam phrases, repeated spam, mass mentions, attachment spam, and image spam patterns.

Coco does not store full message content in an application database. Coco moderation action logs are posted and retained only in the server’s dedicated Discord moderation/log channel. Coco may temporarily keep recent anti-spam metadata in application memory for a short detection window.

Tygrys-specific summary

Tygrys processes and stores data needed for moderation commands, audit logs, message delete/edit logs, attachment evidence, member join/leave logs, role-change logs, voice-channel logs, invite protection, blocked-term moderation, and moderation case history.

Tygrys stores some moderation and audit data in an application-side SQLite database and may store downloaded attachment files for deleted/edited message evidence. Tygrys includes configurable retention settings and an administrator-only command to delete local stored data for a specific user.

2. Data Processed by Both Bots

Depending on the event or command, Coco and/or Tygrys may process:

• Discord user ID;
• username, display name, global name, nickname, or user tag;
• server/guild ID;
• channel ID;
• message ID;
• timestamps;
• role IDs and role names;
• moderation reason;
• moderation action result;
• command input provided by authorized staff;
• relevant Discord permission or role information;
• error information needed to operate or troubleshoot the bots.

3. Coco-Specific Data Processing

Coco may process the following data:

• message text, only where needed for URL/domain extraction, invite detection, suspicious phrase detection, repeated-message detection, and rule-based scoring;
• extracted URLs, domains, and hostnames;
• trusted-domain and blocked-domain match results;
• message timestamp;
• channel ID;
• user ID and user tag;
• attachment count;
• image attachment count;
• attachment filename, MIME type, and file size when included in moderation logs;
• anti-spam score;
• detection reasons;
• action taken, such as deletion, cleanup, or timeout;
• number of deleted messages;
• number of scanned channels/threads;
• timeout status;
• temporary in-memory anti-spam history.

Coco uses this data to detect and stop unsafe links, compromised-account spam, spam bots, Discord invite spam, suspicious scam messages, repeated messages, mass mentions, attachment spam, and image spam.

Coco does not inspect, OCR, classify, or analyze the visual content of images. Coco identifies image spam only from Discord attachment metadata and posting patterns.

Coco may download public external blocklists and cache them locally. Message content is not sent to blocklist providers for checking.

4. Tygrys-Specific Data Processing

4.1 Moderation cases

Tygrys may store case ID, server/guild ID, moderation action type, target user ID and tag, moderator user ID and tag, channel ID where applicable, reason, timeout duration where applicable, message count where applicable, and creation timestamp.

This data is used to maintain moderation history and allow authorized staff to review prior moderation actions.

4.2 Message snapshots and message audit logs

Tygrys may store message ID, server/guild ID, channel ID, author ID and tag, original message content, current or edited message content, before/after content for edits, attachment metadata, creation timestamp, last seen timestamp, deletion timestamp, and message jump URL where applicable.

This data is used to log deleted messages, edited messages, and attachment changes so authorized server staff can review moderation-relevant activity.

4.3 Attachments

Tygrys may download and store message attachments, especially image attachments, when needed to preserve audit evidence for deleted or edited messages.

Stored attachment data may include attachment ID, filename, content type/MIME type, file size, original Discord URL or proxy URL where available, local stored file path or storage reference, and skip reason if the attachment was not downloaded.

Stored image attachments may be re-uploaded to the Discord moderation/log channel as evidence for authorized staff.

4.4 Member events

Tygrys may process and store user ID and tag, account creation timestamp, join timestamp, leave timestamp, display name, nickname, username, global name, roles at the time of leaving, and role IDs/names added or removed.

This data is used to log member joins, leaves, and role changes.

4.5 Voice events

Tygrys may process and store user ID and tag, voice channel ID and name, join timestamp, leave timestamp, and duration of the voice session.

Tygrys logs only voice channel joins and leaves. Tygrys does not record, transcribe, analyze, or store voice audio.

4.6 Invite protection

Tygrys may process message content to detect Discord invite links. It may check whether the invite points to another server, delete prohibited invite messages, warn the user, create moderation cases, count repeated invite violations, and apply automatic timeout after repeated violations.

4.7 Blocked-term moderation

Tygrys may process message content to detect configured blocked terms. If a configured term is detected, Tygrys may delete the message, send a configured moderation response, and create a moderation case.

4.8 YouTube notifications

If enabled, Tygrys may fetch public YouTube RSS feed data for a configured YouTube channel. It may store YouTube video ID, source YouTube channel ID, video title, video URL, publication timestamp, and announcement timestamp. This data is public YouTube data and is used only to avoid duplicate Discord notifications.

5. Why Message Content Is Processed

Applies to both bots

Message content is processed only where required for moderation, safety, audit logging, and bot functionality.

Users cannot individually opt out of these checks while posting in the server because message checks are required to protect the server and its members. Users may stop this processing by not posting in the server or by leaving the server.

Coco-specific reason

Coco requires message content to detect unsafe links, domains, Discord invite spam, suspicious scam phrases, repeated spam messages, mass mentions, and spam patterns. These messages are usually posted directly in public channels and are not addressed to the bot, so slash commands cannot replace real-time message checks.

Tygrys-specific reason

Tygrys requires message content to log deleted and edited messages, preserve moderation evidence, detect prohibited Discord invite links, detect configured blocked terms, and support staff review of moderation incidents.

6. Data Storage and Retention

6.1 Coco-specific storage and retention

Coco does not store full message content in an application database.

Coco may temporarily keep recent anti-spam metadata in application memory for a short detection window. This temporary data is used for spam detection and is not intended as permanent storage.

Coco moderation action logs are posted and retained only in the Discord server’s dedicated moderation/log channel. These logs remain in Discord until deleted by authorized server staff or according to server moderation practices.

Coco may cache public blocklists locally. These blocklist caches do not contain Discord user message content.

6.2 Tygrys-specific storage and retention

Tygrys stores moderation and audit data in an application-side SQLite database.

Tygrys may store attachment files on the bot host for moderation/audit evidence.

Tygrys uses configurable retention settings controlled by the operator. Unless changed by the operator, the intended default retention periods are:

• message snapshots: up to 30 days;
• locally stored attachments: up to 30 days;
• audit events: up to 90 days;
• voice session logs: up to 90 days;
• moderation cases: up to 365 days;
• YouTube announcement records: up to 365 days.

Retention periods may be changed by the operator depending on server safety needs, legal requirements, Discord requirements, or abuse-prevention needs.

A retention period of 0 for a specific category may disable automatic deletion for that category. This should only be used where longer retention is necessary for server safety, moderation history, legal compliance, or abuse prevention.

Tygrys may retain some records longer if they are needed for an active moderation review, abuse investigation, dispute handling, legal compliance, or protection of the server and its members.

7. User Data Deletion and Modification Requests

Users may request information about data related to them, correction of inaccurate stored data where technically possible, deletion of stored local data related to them, review of a bot moderation action, or reporting of false positives or bot misuse.

Requests should be sent to:

The request should include enough information to identify the relevant data, such as Discord user ID, server name, approximate date/time, channel, message ID, or moderation case number if known.

Coco-specific deletion

Coco does not keep a local application database of full message content. Coco moderation logs are stored only as Discord messages in the server’s dedicated moderation/log channel. Requests involving Coco logs should identify the relevant user, date, channel, or moderation event so authorized staff can review and delete or modify relevant Discord-side logs where appropriate.

Tygrys-specific deletion

Tygrys includes an administrator-only local privacy deletion function that can delete local stored data for a specified Discord user ID from the SQLite database and delete locally stored attachments associated with that user where technically possible.

This local deletion may include message snapshots, audit events, moderation cases where the user was the target or moderator, voice sessions, and locally stored attachments linked to those records.

Some data may be retained where necessary for server safety, active moderation review, abuse prevention, dispute handling, legal compliance, or protection against misuse. If data cannot be deleted immediately, the operator will explain the reason where appropriate.

8. Data Sharing

Applies to both bots

The bots do not sell, license, rent, or commercialize Discord API Data.

The bots do not disclose Discord API Data to data brokers, advertising networks, analytics networks, or monetization-related services.

The bots may share or process data only in these limited ways:

• within Discord itself, such as posting moderation logs to a restricted moderation/log channel;
• with authorized server staff who need access for moderation and safety;
• with infrastructure or hosting providers necessary to operate the bots;
• if required by applicable law, regulation, legal process, or Discord;
• if the user expressly directs the operator to share their data.

Coco-specific sharing

Coco downloads public blocklists from external sources, but does not send message content or user data to those blocklist providers for checking.

Tygrys-specific sharing

Tygrys may fetch public YouTube RSS feed data if YouTube notifications are enabled. Tygrys does not send Discord user message content to YouTube for this feature.

9. AI and Machine Learning

Coco and Tygrys do not use message content to train, fine-tune, evaluate, improve, or operate AI models, machine learning models, language models, classifiers, recommendation systems, advertising systems, or profiling systems.

The bots use rule-based checks, Discord moderation events, Discord audit events, and server configuration.

10. Security

The operator uses reasonable administrative, technical, and operational safeguards to protect bot data, including limiting access to bot configuration, databases, logs, attachments, and credentials.

Bot tokens, API keys, passwords, and other credentials must not be published or shared publicly.

Access to moderation logs, databases, and attachment storage should be limited to authorized server staff or the operator.

Where local storage is used, the operator should protect stored data against unauthorized access, including through server access control, restricted file permissions, secure backups, and encryption or equivalent protection where available.

If unauthorized access to relevant bot data is discovered, the operator will take reasonable steps to investigate, mitigate, and notify affected users and/or Discord where required.

11. Children and Minimum Age

Coco and Tygrys are not directed to children under 13 or to users below the minimum age required by Discord or applicable law.

Users must meet Discord’s minimum age requirements to use the server and interact with the bots.

12. Changes to This Privacy Policy

This Privacy Policy may be updated when bot functionality, data practices, Discord requirements, server rules, or applicable laws change.

The latest version should be made available through the server’s information channel, bot profile, website, or another accessible location.

13. Contact

For questions, privacy requests, deletion requests, security concerns, or moderation review requests, contact: