Privacy Policy
Last updated: October 10, 2026
This Privacy Policy explains what data Support Bot ("BeaconBot", "we", "us") collects when you interact with the bot, the web dashboard, or the admin panel, and what we do with it. It applies alongside Discord's own Privacy Policy, which governs Discord as a platform.
1. Information We Collect
a) Through the bot, on servers where it is added
| Data | Why we collect it |
|---|---|
| Discord user ID, username/tag, server (guild) and channel IDs | Required to operate any Discord bot feature — identifying who did what, where |
| Message content, for messages that trigger the word filter or crisis-keyword detection | To apply the configured moderation action and, where enabled, to log a short excerpt for staff review (see Section 3) |
| Warnings, mutes, and moderation history | So staff can see a member's history and the bot can apply escalation rules |
| Ticket metadata (who opened it, when, which channel) and, for servers with that feature enabled, a transcript of the conversation | To run the support-ticket system and optionally provide a record of the conversation |
| Mood check-in scores (1–5) and timestamps | To power the mood check-in feature and let staff see patterns in a community's wellbeing, if enabled |
| Birthday (day and month only — not year) | To send an automatic birthday message, if enabled |
| Voice channel join activity and message activity (that you were active on a given day — not full voice recordings or full chat logs) | Used only to check eligibility for the optional "good behavior" reward, so an inactive member can't qualify by default |
| Anonymous messages sent via the anonymous-messaging feature | Forwarded to a staff channel without your identity attached in that forwarded message — see Section 4 |
b) Through the web dashboard
When you log in with "Log in with Discord," we receive your Discord user ID, username, avatar, and the list of servers where you have administrative permissions, so the dashboard can show you the servers you're allowed to configure. We request only the identify and guilds scopes — we do not request your email address or any other Discord data. Login is kept in a session cookie.
c) Through payments
Subscription payments are processed by Stripe. We never see or store your full card number. We do store your subscription status, the dates it covers, and identifiers Stripe gives us to manage your subscription (such as a customer ID). See Stripe's Privacy Policy for how Stripe handles payment data.
2. How We Use Information
- To operate the features a server administrator has enabled (moderation, tickets, mood check-ins, birthdays, reaction roles, etc.)
- To detect and respond to messages that may indicate a mental health crisis (see Section 3)
- To let server administrators configure and review the bot's activity through the dashboard
- To manage subscriptions and billing
- To maintain and improve the Service's reliability and security
We do not sell your data, and we do not use message content for advertising.
3. Crisis Detection — What Happens to Your Messages
If a server enables crisis detection and one of your messages matches a configured keyword, the bot removes the message, sends you a direct message with supportive resources, and shares the message content with that server's staff so a real person can follow up. This is a safety feature, not a surveillance feature for ordinary messages — it only activates on a keyword match.
This feature exists to get a concerning message in front of a human as quickly as possible; it is not a substitute for professional or emergency help. See Section 6 of our Terms of Service for more on the limits of this feature.
4. Anonymous Messages
Messages sent through the anonymous-messaging feature are forwarded to a staff channel without displaying your username or user ID in that message, and we do not separately log your identity against the anonymous message's content. Server staff cannot identify you through the bot based solely on an anonymous message.
5. Who We Share Data With
- Discord — as the platform the bot runs on; anything the bot posts or does is visible to Discord per its own terms
- Stripe — to process subscription payments
- Server staff — moderation-relevant data (warnings, flagged messages, ticket contents) is visible to the staff of the specific server it relates to, as configured by that server's administrators
We do not share your data with other third parties, and we do not sell it.
6. Data Retention
- General audit log entries (including message excerpts logged for word-filter or crisis-keyword matches) are automatically deleted after 7 days.
- Warnings, ticket records, mood check-in history, birthdays, and similar configuration data are kept for as long as the bot is used on that server, so that history and settings aren't lost if the bot is temporarily removed and re-added. Server administrators can delete specific records (for example, a member's warnings) at any time via the dashboard or relevant commands.
- Subscription and billing records are kept as required for accounting and legal purposes.
7. Data Security
We take reasonable technical measures to protect the data we hold, including restricting database and admin-panel access. No system is perfectly secure, and we cannot guarantee absolute security.
8. Your Rights
Depending on your location, you may have rights under data protection law (such as the GDPR) to access, correct, or request deletion of personal data we hold about you, or to object to or restrict certain processing. To make a request, email privacy@crashdesk.nl. Because most of the data we hold is tied to a specific Discord server, some requests (such as deleting your warning history) may be faster to resolve directly with that server's staff, who can also remove it via the dashboard.
9. Children's Privacy
The Service is only intended for use in line with Discord's own minimum age requirements. We do not knowingly collect data from children below that age beyond what Discord itself provides to bots operating on its platform.
10. Cookies & Sessions
The web dashboard and admin panel use a session cookie to keep you logged in. We do not use advertising or tracking cookies.
11. Changes to This Policy
We may update this Privacy Policy from time to time. Material changes will be reflected by an updated "Last updated" date above.
12. Contact
Questions about this Privacy Policy, or requests regarding your data, can be sent to privacy@crashdesk.nl.