• Last updated: 2026-06-25*

This Privacy Policy explains how the Discord bot named MirroBot ("the Bot", "we", "us") collects, uses, processes, and protects your data. This document has been drafted in compliance with the General Data Protection Regulation (GDPR) and the Discord Developer Terms of Service.

## 1. Data Controller

The Data Controller responsible for your personal data collected through the Bot is the entity specified in the "Contact" section at the bottom of this document.

## 2. Data Collection Points

To provide real-time machine translation services, the Bot processes specific data obtained via the Discord API. We categorize this data as follows:

### A. Permanently Stored Data (In the Database)

We securely store the following identifiers on our servers:

• Discord Server (Guild) ID*: To identify the server and verify permissions or entitlements (e.g., Premium subscriptions).
• Discord Channel ID*: To map which channels form translation groups.
• Discord Message ID*: To map original messages to their translated cross-posted counterparts. This is strictly necessary to synchronize message edits, deletions, and emoji reactions across linked channels.
• Under no circumstances do we permanently store message content, usernames, or any other data that directly identifies a natural person in our database.*

### B. Transiently Processed Data (In RAM)

To execute translations, the Bot temporarily analyzes the following data in memory:

• Discord User ID, Display Name, and Avatar URL*: To configure Webhooks that impersonate the original author during cross-posting.
• Message Content*: The text of the message sent by the user.
• Images/Attachments*: To perform Optical Character Recognition (OCR) on text embedded in images.
• Contextual History*: Recent messages from the channel are held in a short-term, temporary cache to understand the conversational context (e.g., to accurately resolve gender pronouns).

## 3. Third-Party Data Sharing (AI Processing)

MirroBot is an AI-integrated application. Consequently, the data listed in Section 2.B (Message Content, Images) is transmitted to third-party providers via secure API connections: