Gizlilik Politikası

1. Controller

MUHtion Media e.K., owner Dominik Schaller, Joditzer Straße 21, 95180 Berg, Germany, email [email protected].

2. What the bot processes

When Doorman is on a Discord server it receives data from Discord that is needed to provide its functions (Art. 6(1)(b) and (f) GDPR — providing the Service to the server operator and our legitimate interest in operating it):

• Discord IDs of servers, channels, roles and members, usernames and display names;
• message content, only to run the functions the server has enabled (automod, custom commands, levels, starboard, tickets). Messages are checked when they arrive and are not stored; stored are only the results (e.g. XP, a moderation entry with its reason, a starboard reference);
• data the functions need to keep: levels/XP, economy balances, moderation history (warnings, timeouts, bans with reason), tickets (opener, topic, status), reminders and their text, birthdays (day and month), giveaway entries, invite tracking (who invited whom), achievements, notification feeds configured by the server, suggestions and votes, accepted rules versions, AFK status, appeals, and which member a modmail conversation belongs to (the conversation itself stays in the server's Discord channel);
• statistics as numbers only: messages per day and channel, number of active members per day, member count;
• backups of the server structure (roles, channels, permissions — no messages), daily and on request;
• images uploaded in the dashboard (welcome card and rank card backgrounds), until they are replaced or deleted;
• if the server uses a custom bot: the bot's token, encrypted with a key that exists only on our server, and the bot's avatar and banner, until the custom bot is removed;
• if the server uses the verification mode Doorman Shield: when a member verifies on doorman.bot we process the member's IP address and a few browser characteristics (screen size, time zone, language, browser name) to detect VPN/proxy/Tor/data-centre connections and duplicate accounts. We store only keyed hashes of these values, never the plain IP address or browser data, together with the member's Discord ID and the result of the check, for 30 days (Art. 6(1)(f) GDPR — protecting the server from bots and abuse). The lists of VPN and data-centre networks are downloaded from public sources; no data about the member is sent to them;
• if the server turns on the shared ban list: the Discord ID of each member the server bans, the time and (if the server allows it) the ban reason, visible to other Doorman servers that take part, until the member is unbanned or the server withdraws its entries (Art. 6(1)(f) GDPR — protecting servers from repeat offenders). Servers that check new members see only the number of other servers and the reasons, never which servers;
• if the server turns on translation: the text a member asks to translate (flag reaction, message menu or /translate) is sent to DeepL SE, Cologne, Germany, to produce the translation (Art. 6(1)(f) GDPR — the member's request; DeepL does not store the text for its API customers). Doorman keeps only character counters per server and day and a keyed hash of the text with its translation for 7 days (so repeated requests don't cost quota), never the text itself;
• if the server turns on AI-assisted moderation: the text of each message by a regular member (not moderators, not excluded channels or roles) is sent to Anthropic, PBC (USA; EU data-transfer safeguards per Anthropic's terms, no training on API data) to classify it against the server's rules (Art. 6(1)(f) GDPR — the server's interest in keeping its community safe). Doorman keeps only the category, the score, the action taken and the message, channel and member IDs for 30 days, never the message text;
• if the server turns on inactive members cleanup: the time of each member's last message on that server (no content), while the feature is switched on and until the member leaves or the server turns it off, to find members who have been inactive for the chosen number of days (Art. 6(1)(f) GDPR — the server's interest in an active community);
• if the server uses the FAQ assistant or ticket summaries: a member's question (/ask, a mention of the bot or a question in a chosen help channel) together with the server's FAQ text, or the messages of a closed ticket, is sent to Anthropic, PBC (USA; EU data-transfer safeguards per Anthropic's terms, no training on API data) to produce the answer or the summary for the team (Art. 6(1)(f) GDPR — the member's request and the server's interest in efficient support). Doorman keeps only daily counters, never the question, the answer or the ticket text;
• if the server makes its leaderboard public: usernames, avatars, levels and XP of the members listed there are visible on the public leaderboard page; the server can exclude this page from search engines.

Logs of deleted or edited messages and ticket transcripts are posted into the server's own Discord channels (or sent as a DM to the member who opened the ticket); we do not keep a copy.

Every member can download and delete their own data on a server with /mydata export ve /mydata delete.

The server's administrators decide which functions are active; for the processing on their server they are responsible towards their members.

3. Dashboard

Log-in uses Discord OAuth2 with the scopes identify ve guilds: we receive your Discord ID, username, avatar and the list of servers you are on, to show you the servers you can manage. We do not receive your email address or password. A technically necessary session cookie (valid 12 hours) keeps you logged in, and a cookie remembers the language you chose (1 year); there are no tracking or advertising cookies.

4. Payments

Premium is paid through Stripe Payments Europe Ltd., Dublin, Ireland. Stripe processes your payment and billing data (name, address, email, VAT ID, payment method) as an independent controller; see stripe.com/privacy. We store only the Stripe customer and subscription IDs and the server the subscription belongs to, and receive invoices for our accounting (Art. 6(1)(b) and (c) GDPR).

Paid memberships that a server sells through Monetize are paid on the server owner's own Stripe account (Stripe Connect); for that payment data the server owner and Stripe are responsible. We store the Stripe subscription and customer IDs, the member's Discord ID, the plan, its status and end date, to give and remove the roles of the membership (Art. 6(1)(b) GDPR). For server owners we store the ID of their connected Stripe account; as a platform operator we may have to report data about sellers and their sales to the tax authorities (DAC7, Art. 6(1)(c) GDPR).

5. Recipients and processors

• Hosting: WorldStream B.V., Naaldwijk, Netherlands (servers in the EU);
• Cloudflare, Inc. (DNS, TLS, protection against attacks) — for transfers to the USA based on the EU-U.S. Data Privacy Framework / standard contractual clauses;
• Discord Inc. operates the platform on which the bot runs and processes data under its own responsibility.

6. Storage period

Data about a server is kept while Doorman is on that server. Server administrators and members can ask us by email to delete their data; we then delete it unless statutory retention periods (e.g. tax records for payments, up to 10 years) require otherwise. Web server logs (IP address, time, requested page) are kept for security reasons and deleted after 7 days at the latest.

7. Your rights

You have the right of access (Art. 15), rectification (16), erasure (17), restriction (18), data portability (20) and objection (21 GDPR), and the right to lodge a complaint with a supervisory authority (Art. 77), e.g. the Bavarian Data Protection Authority (BayLDA).