Privacy Policy

We only process data that is required to run the bot, provide translations, and manage your server settings. This also includes operational/error logs and short-lived caches to prevent abuse and keep latency low.

• Server and role IDs, channels, translation and verification options, and limits from your configuration (e.g., welcome flows, auto roles, logging).
• Operational and error logs contain metadata such as guild, channel, and user IDs, command names, locale, and message IDs. For critical errors the bot owner may be notified via DM with guild and user IDs.
• Language and timezone preferences plus poll- and ticket-related settings so responses and notifications use the right locale; language history is stored to respect your previous choices.
• For polls we store the poll message (ID), server and channel IDs, the question/answers, and submitted votes (user ID + option) to calculate results.
• For translations we calculate text length, derive a hash of the cleartext, and store the hash, detected language, and usage/cost metrics in caches and log tables. The cleartext is sent to the translation provider unless a cache is available.
• Support requests via email and subscription metadata (plan, limits) where required to provide and support the service.
• Contact and identity details of guild owners (e.g., owner ID, username/global name, avatar URL, DM channel ID) to reach out and manage the bot join process.
• Event templates and instances with title, description, channel and role IDs, announcement/reminder timings, target languages, plus reminder status and error history.

• Operating the Discord bot, including translations, welcome and verification flows, and polls. Legal bases: Art. 6(1)(b) GDPR (contract performance) and Art. 6(1)(f) GDPR (legitimate interest in a reliable service).
• Abuse prevention and stability (rate limits, error logs, caches) to keep the service reliable. Legal basis: Art. 6(1)(f) GDPR.
• Communicating about support and billing requests and maintaining server and user settings. Legal bases: Art. 6(1)(b) and (f) GDPR.

• Configurations, user preferences, and poll data remain stored while your server uses the bot or until you remove them in the dashboard.
• Translated content only lives in memory during processing; hash-based caches for language detection/translation expire automatically after a short period (e.g., 24 hours).
• Operational and error logs are stored temporarily for troubleshooting and abuse detection and deleted once the purpose ends or statutory retention periods expire.
• Billing and payment data (e.g., Stripe transactions, plans, and limits) are retained in line with statutory tax and commercial retention periods.

• Discord Inc. as the communication platform: slash commands, messages, and interactions are processed via the Discord API.
• Fly.io as the hosting environment (multi-regional setup with dedicated worker processes), Neon as Postgres database provider, and Upstash as Redis service for caching and locks. These vendors act as processors.
• External LLM provider (e.g., Groq) for language detection and translations. Message content may be transmitted for processing; hashes and usage metrics are stored for cache control and billing.
• Internal billing processes to sync plans and limits; errors and status codes are logged for monitoring.
• Data may be transferred to non-EU countries when services are hosted abroad. In such cases we rely on appropriate safeguards (e.g., EU Standard Contractual Clauses).

• Right of access to stored data and processing details (Art. 15 GDPR).
• Rectification of inaccurate or incomplete data (Art. 16 GDPR).
• Erasure or restriction of processing unless legal obligations require retention (Art. 17, 18 GDPR).
• Data portability in a structured, commonly used format (Art. 20 GDPR).
• Objection to processing based on legitimate interests (Art. 21 GDPR).
• Right to lodge a complaint with a supervisory authority.

For privacy requests or to exercise your rights, email info@mecks-translator.com.

To improve stability and user experience we use self-hosted Matomo. Data is processed exclusively on our server and never shared with third parties.

• We measure page views, feature usage (e.g., dashboard navigation), and technical events like errors or load times to detect issues quickly.
• Matomo sets a cookie to recognise returning devices. You can disable tracking at any time via the opt-out below.
• IP addresses are automatically truncated (IP anonymisation) so they cannot directly identify you.
• Your opt-in/opt-out choice is stored in the browser. After clearing cookies you may need to set your preference again.

Based on the dependencies listed in package.json we rely on the following vendors as processors or infrastructure:

• Authentication via NextAuth using the Discord OAuth flow; we receive basic Discord account details (e.g., user ID, username) to sign you in.
• Stripe for payment processing and subscriptions. Payment details are handled directly by Stripe; we receive status and metadata for contract management.
• AWS S3 to store generated files or uploads where necessary, accessed via pre-signed URLs.
• Resend for transactional emails (e.g., confirmations, support communication).