Legal
Privacy Policy
Effective Date: September 4, 2026
Suurd Digital, trading as BabelBot, provides translation and related tools for Discord servers. This policy explains how we use personal data when you visit our website, use the dashboard, install BabelBot, or interact with it on Discord.
1. Who Operates BabelBot
Data controller: Suurd Digital, trading as BabelBot.
Guldenroedetuin 18, 7813 BH Emmen, The Netherlands
KVK number: 42099481
VAT ID: NL005492681B54
Email: [email protected]
Server administrators decide whether to install and configure BabelBot in their Discord servers. We act as the data controller for our dashboard accounts, billing, analytics, security, and service operations. Our role for Discord server content can depend on how a server administrator uses BabelBot.
2. Data We Use and Why
BabelBot receives data from Discord, dashboard users, server administrators, payment and service providers, and people who visit our website. We use the following data groups:
| Data group | Why we use it | Legal basis |
|---|---|---|
| Messages and attachments | Provide translations, language detection, media translation, replies, and bridge features. | Contract and legitimate interests in providing the service requested by the server administrator. |
| Discord accounts, server settings, and setting history | Apply server preferences and show authorized server managers who changed settings. | Contract and legitimate interests in operating the service. |
| Dashboard account and access data | Sign you in, confirm which servers you can manage, and protect dashboard access. | Contract and legitimate interests in account security and fraud prevention. |
| Usage and billing data | Apply quotas, manage subscriptions, provide support, prevent abuse, and keep accounting records. | Contract, legitimate interests, and legal obligations. |
| Diagnostics and analytics | Find service problems, provide support, protect the service, and understand product and website use. | Legitimate interests in reliability, security, support, and privacy-friendly analytics. |
| Translation feedback | Investigate translation problems, improve BabelBot, prevent duplicate submissions, and provide support. | Legitimate interests in service quality, reliability, and support. |
You must provide account, server-setting, and billing data when it is needed for the feature or plan you request. Without that data, BabelBot cannot provide the related feature, confirm your access, or manage the subscription. BabelBot does not make decisions that have legal or similarly significant effects based only on automated processing.
Message and attachment processing
BabelBot receives messages from Discord when it needs them to provide an enabled feature. A translation can include limited recent conversation context. Messages, context, and relevant attachments can be sent to external AI providers. BabelBot stores bridge message links and can retain quoted reply-preview text, author names, and message links to keep replies synchronized.
We also keep identifiers and operational records when needed to synchronize bridge messages, prevent duplicate actions, retry delivery, investigate errors, and support users. Authorized diagnostic exports can contain message content and related Discord information.
Translation feedback
If you select Bad response on a translation embed in a Discord thread, we collect the feedback you enter and any suggested correction. We also store Discord and service identifiers for the server, thread, messages, reporting user, and translation trace, together with your locale and submission time. The database feedback record does not copy the original message or translated text.
We use this information to investigate translation problems, improve BabelBot, prevent duplicate or abusive submissions, and provide support. Authorized BabelBot maintainers can review it. If configured, an optional private Discord support webhook receives the submitted feedback, any suggested correction, relevant Discord and translation identifiers, and a link to the translation. The link can let authorized maintainers open the translation in Discord, subject to their server access.
Please do not include passwords or other sensitive information in the form.
See Subprocessors and Data Details for technical data categories and current processing details.
3. Providers and Data Sharing
We use external providers for Discord access, AI translation, bot hosting, data storage, payments, and email delivery. Each provider receives the data needed for its service. AI providers can receive message text, recent context, and relevant attachment content for translation features.
Railway hosts our Discord bot and data storage in the European Union. We host the website, dashboard, and analytics on our own infrastructure.
Some providers process data outside the Netherlands or European Economic Area. Where the law requires a transfer safeguard, we use the safeguard that applies to the transfer, such as an adequacy decision or Standard Contractual Clauses.
Resend processes your email address, delivery details, and email content. We use its Ireland region to send emails. Resend stores customer data in the United States, including message content, delivery logs, webhook payloads, and account records. We use Resend for billing and account messages. We also use it for abandoned checkout and review request emails. Use the email link in the footer to ask us to stop these non-essential emails.
We do not sell or rent personal data. We may disclose data when the law requires it or when needed to protect BabelBot, its users, or other people from fraud, abuse, or security threats.
See Subprocessors and Data Details for the current provider list, purposes, data categories, and processing locations.
4. How Long We Keep Data
We keep personal data only while we need it for the purpose described below, or while the law requires it. These are the main retention rules:
| Data group | Retention rule |
|---|---|
| Recent message context | Kept for up to 15 minutes. |
| Bridge message links and recent translation records | New bridge message links and saved reply previews have no age-based expiry. Existing Redis bridge records keep their original expiry, normally 30 days after creation. Recent translation records cover 48 hours and expire after 72 hours without new activity. |
| Server setup and billing records | BabelBot keeps server settings, billing state, opt-outs, and bridge thread links while it is in the server. They expire 180 days after BabelBot leaves. If BabelBot rejoins during that period, BabelBot keeps the records while it remains in the server. |
| Dashboard setting history | The dashboard shows up to 500 successful entries from the last 90 days. Older service records can remain longer while needed for reliability and support. |
| Usage totals and saved target language | Daily usage and a member's saved target language expire after 180 days. Monthly usage expires 13 calendar months after the month ends. |
| Removal tasks and email limits | Records used to finish removing deleted channels and webhooks expire after 30 days. Email event limits and cancellation reason records expire after 400 days. Monthly checkout email limits expire 62 days after the month ends. |
| Dashboard and subscription records | Kept while an account or subscription is active and as needed for security, support, fraud prevention, and legal duties. |
| Translation feedback | Scheduled for deletion 90 days after submission. Copies in internal support tools follow the retention rules for those tools. |
| Accounting records | Invoices and other statutory administration records are kept for at least seven years where Dutch tax law requires it. |
| Analytics and lifecycle records | Kept for the period needed to measure service use, acquisition, reliability, and billing. Some categories have fixed expiry periods. |
Redis backups can contain data from the live service. BabelBot keeps frequent backups for 2 days and then keeps fewer backups for up to 365 days. Deleting data from the live service does not delete it from existing backups. That data remains until each backup expires. BabelBot uses backups only to restore the service.
See Subprocessors and Data Details for current retention periods and operational limits.
5. Your Choices and Rights
5.1 Stop Message Translation
Ask a server admin to add your Discord user ID under Ignored users in the BabelBot dashboard for that server. BabelBot will not process or send ignored users' messages to translation APIs. Admins can remove your ID from the same list to opt you back in.
5.2 Privacy Rights
If you are an individual Discord user, dashboard user, server administrator, or other data subject, you may have the right to:
- Access: Request a copy of personal data we store about you or, if you are an authorized server administrator, about your server.
- Deletion: Request deletion of personal data, dashboard account data, opt-out records, or server configuration where applicable, subject to retention requirements for billing, security, abuse prevention, and legal compliance.
- Restriction: Ask us to limit how we use your personal data where this right applies.
- Portability: Request your data in a structured, commonly-used format.
- Rectification: Correct inaccurate account, server, or billing information.
- Objection: Object to processing based on legitimate interests.
To exercise these rights, contact [email protected]. Include enough information for us to verify the request, such as your Discord user ID, dashboard account email, or server ID. We respond within one month unless applicable law permits an extension.
5.3 California Residents
California residents have the right to know, delete, and opt-out of the sale or sharing of personal information where the law applies. BabelBot does not sell personal information. To exercise California privacy rights, contact [email protected].
5.4 Removing BabelBot
Remove BabelBot from your server at any time through Discord server settings. This stops message translation and other live server processing. We record the removal time. Existing lifecycle, configuration, and billing records remain subject to Section 4.
6. Data Security
We use access controls, secure network connections, service monitoring, updates, and other technical and organizational measures to protect personal data. No system is completely secure, so we cannot guarantee absolute security.
7. Personal Data Breaches
If we discover a personal data breach, we assess its risk and notify the relevant authority or affected people when applicable law requires it.
8. Children's Privacy
BabelBot is not intended for children under 13 (or the applicable age of digital consent in your jurisdiction). We do not knowingly collect personal information from children. If you are a parent or guardian and believe we have collected data from a child, contact us immediately at [email protected].
9. Changes to This Privacy Policy
We update this policy when our data practices or legal duties change. We post the updated policy on this page with a new effective date. We provide any additional notice required by law.
10. Contact and Complaints
For questions about this Privacy Policy, data requests, or to report a privacy concern:
- Privacy inquiries and data requests: [email protected]
- General support: [email protected]
You can also complain to the Dutch Data Protection Authority or the supervisory authority in the country where you live or work.