Privacy policy

Last updated: October 2026

This English version is provided for convenience only. Only the German version is legally binding.

This policy applies to the Modario website and to the Discord bot “Modario”. It explains which personal data we process, for what purpose and for how long.

1. Controller

Stefan Rohrbach, DMNT Studio
c/o Online-Impressum 10950, Europaring 90, 53757 Sankt Augustin, Germany
Email: dmnt-studio@mail.online-impressum.de

No data protection officer has been appointed because there is no legal obligation to do so.

2. Website

Server log files

When you visit the website, the web server automatically stores:

• IP address of the requesting device
• date and time of access
• page requested, status code and amount of data transferred
• browser identifier (user agent) and, if transmitted, the previously visited page

The purpose is the secure and stable operation of the website, for example to detect attacks and errors. The legal basis is Art. 6(1)(f) GDPR. Log files are deleted after 14 days unless a specific incident needs to be investigated for longer.

Cookies and third-party services

The website does not set cookies, does not use tracking and does not load content from third-party servers (such as fonts or analytics services).

If you switch the sound on the home page off (default: on) or back on, or choose a language via the flag in the top right corner, your browser stores this setting locally (local storage) so that it is kept for your next visit. The setting is not transmitted to us and can be changed or deleted at any time via the switch, the language menu or your browser settings. The legal basis is Section 25(2) No. 2 TDDDG, because storing it is necessary for the function you requested.

Encryption

The connection is encrypted with TLS. The certificate is issued by Let's Encrypt. No visitor data is transmitted to Let's Encrypt in the process.

3. Discord bot “Modario”

Roles

Whoever uses Modario on their Discord server (server operator) decides what the bot is used for there. The server operator is the controller within the meaning of the GDPR for the data of that server's members. DMNT Studio processes this data as a processor under Art. 28 GDPR on the basis of a data processing agreement, which is concluded during setup with /modario setup. Members with questions about their data should therefore first contact the respective server operator.

DMNT Studio is the controller for the data of the server operators themselves (setup, contract, records).

Which data the bot processes

• Server settings: ID of the Discord server, IDs of channels and roles, selected settings (e.g. language, time zone, report channel, Modario area) and booked modules.
• Modario area (only if the server operator creates it): Only the IDs of the category, its three channels, two bot messages (control panel and status card) and the roles that see the area are stored. If someone changes the area's permissions, the bot resets them, looks up in the server's audit log who did it and names that person in the notice to the report channel; this is not stored.
• Setup (guided server setup): For each server, the answers of the setup, the chosen way and template, the IDs of the channels, categories and roles the bot created and, per category, the chosen level with the roles' permissions (the target) are stored. If someone changes these permissions, the bot reports it to the report channel and names who did it from the audit log; this is not stored. The setup stores no permissions of individual members and no other member data.
• User IDs: the Discord ID of people who use a bot command or trigger a function, where the function requires it.
• Record log: confirmations during setup (e.g. acceptance of the data processing agreement and its version, re-confirmation of new versions, confirmation that members have been informed), notices to the server operator, changes to channels (including who sees the Modario area) and modules, termination and deletion. The Discord ID of the acting person, the server and the time are stored.
• Events: title, description, start and end, selected voice channel, cover image (uploaded or as a link), a custom channel status text and the Discord ID of the person creating the event. For Discord's “Interested” the bot only reads the number, no names. Unfinished input (drafts, including an uploaded image) is kept briefly so nothing gets lost. Planning: if the server operator creates a series, the bot stores its rule (e.g. “every Friday at 8 pm”), title, description, cover image and the Discord ID of the person creating it, and creates the events of the next days from it. If the server operator adds the address of a calendar (ICS link, e.g. from Google Calendar), the bot fetches it regularly and takes over its dates as events or into the weekly overview; the address (shown shortened in the menu and never logged) and the state of the sync are stored. For a calendar subscription the bot creates secret addresses from which calendar apps fetch the server's dates; the address, the chosen starters and the time of the last fetch are stored – no IP address, no device information, no counter (section 2 applies to the server log files).
• Welcome (module “Willkommen”, only if the server operator switches it on): When someone joins or leaves the server, Discord sends the bot their Discord ID, user and display name, profile picture, join date and roles. The bot uses them only to show the welcome or farewell card (with these details if the server operator chooses) in the chosen channel – with the “Welcome+” add-on, if the server operator chooses, also as a direct message to the member – and to assign the configured roles; it stores nothing about the member. If the member doesn't allow direct messages in their Discord settings, the bot skips them. The bot loads the profile picture only to draw the card; it stores neither the profile picture nor the finished card (for the preview in the settings menu no more than 15 minutes in memory). Only the server's settings are stored (channels, roles, card texts and look, plus a background image if the server operator uploads or links one – the bot fetches it once, checks it and stores only the checked image, not the link). So that kicked or banned members don't get a farewell, the bot reads only kicks and bans from the server's audit log and keeps the result in memory for no more than two minutes. With “Welcome+” the server operator can set rules per template (period, weekday, time, member count, invite link). Only for the invite rule and only if the server operator grants the bot the “Manage Server” permission for it, the bot reads the server's invite list on join (link codes and counters, who created the link) to work out which link the member used; it keeps the counters in memory only and stores nothing about the member or the link. Clean-up: if the server operator sets a lifetime for the cards, the bot notes for each card sent only the message ID, the channel and the time of deletion – not which member it was for. So that the welcome card of a member who leaves again within ten minutes (short visit) can be deleted, the bot keeps the member-to-card mapping in memory for about ten minutes. If many members join at once, the bot welcomes them with one shared card; for that it keeps their Discord IDs in memory for about ten minutes. Ranks: Modario gives a rank on joining (guest, partner via an invite link chosen by the server, or member) and promotes guests by the server’s rule. The rank itself is not stored but read from the Discord roles. If the server chooses “notify the mods”, Modario stores the member’s Discord ID, the ID of the mod card and the next review date until a decision; the entry is deleted as soon as the member is accepted, leaves the server or loses the guest role. If a moderator demotes someone to guest while promotion is enabled, Modario stores the Discord ID and the time so that promotion counts from then – until the person is no longer a guest or leaves the server. Activity (only if the server operator switches it on in the Foyer): Modario gives activity levels as roles. For this the bot counts that someone writes a message, reacts, is in a voice channel with others, starts a game (from the Discord status) or votes in a poll – it does not evaluate any content. Per member only a point value with a timestamp and the points per source on the current day (for the daily limits) are stored, no individual events. For group searches and events the bot also counts who spent at least 15 minutes in the voice room (for events only those who clicked “Interested” on the Discord event) – the minutes and the “Interested” list in memory only, until the round ends. In memory the bot keeps events for at most 5 minutes, voice-channel minutes and game starts of the day for at most 2 days. Members only see their level, admins and mods a bar without a number. Every member can object at any time via “Don't track” in /profile (Art. 21 GDPR): the points are deleted immediately; Modario only keeps the Discord ID and the time of the objection so that it does not count again. The proof log records objection and withdrawal with the Discord ID. Profile: /profile shows a member their membership, level, join date and – with the moderation module – their active warnings with reason; admins and mods additionally see the bar and the number of cases for other members. Nothing extra is stored for this.
• Announcements (module “Frequenz”, only if the server operator switches it on): Only the announcements the server operator creates are stored: heading and text (with Announcement+ also further text variants), images (as a checked copy, not as a link), link buttons, the schedule, IDs of channel and roles (including the manager role that may run announcements without admin rights), the Discord ID of the person who creates the announcement, and the ID of the last message sent (so it can be replaced if wanted). The bot stores nothing about members and reads no one else's messages. Only for the option “only post if the channel is quiet” (Announcement+) does it check, before posting, when someone last wrote in the target channel: it uses only the time and sender ID of the latest messages, evaluates no content and stores none of it – only the time when a post was skipped for that reason. Placeholders (e.g. date, server name, member count, channel and role names) are only filled in when posting; the result is not stored. Creating, changing, sending and deleting is recorded in the record log without content. Weekly overview: per server Modario only stores the window settings (weekday, time, channel, ping role, intro) and the ID of the last overview post. The post shows the server’s upcoming events, calendar dates and group searches; calendars are read when posting and nothing of it is stored in addition. For the hint about many pings Modario counts per role and week how often it pings it (role ID and number only, 8 weeks). Live (only if the server operator switches it on): If a member adds their Twitch channel in /profile, the bot stores the Discord ID, the Twitch name and Twitch user ID, the approval status (waiting, approved, rejected, paused), the time and the Discord ID of the person who approves or rejects it. To check the channel, the bot asks Twitch whether the name exists; for approved channels it asks every 2 minutes whether they are live (on Twitch, see below). While a stream is running, it stores stream ID, start, title, game, the IDs of the live card and channel and the live role given. When the stream ends it deletes these details; the card stays as a normal message (“was live”). The bot gives the live role only for the duration of the stream. The record log contains adding, approving, rejecting and removing with the Discord ID, without content.
• Classes and class choice (server setting, only if the server operator creates classes; the choice only if they switch it on): The server operator creates classes (e.g. “Industry” – name, emoji, description and a Discord role) and, if wanted, subgroups (e.g. “Mining”) that modules such as the group finder use as slots. Members can choose a main class and side interests with a button; this is voluntary. Then the Discord ID, the chosen classes and the time are stored. Modario gives the member the roles of these classes and – with the main class – a level role (not if they objected to activity tracking). The level comes from a class points value per main class (participation in group searches on a slot of this class, stored like the activity points value and decaying over time); “No class” deletes it together with the choice. When someone looks for a group with class slots, Modario mentions up to 20 members with a matching class (with activity the most active ones); nothing extra is stored for this. When someone becomes a member (without ranks: on joining) and has no main class yet, the bot sends one direct message with the button if the server operator switched this on; if the person doesn't allow direct messages, it doesn't try again and stores nothing. The button is also available in /profile, below the welcome and on a card the server operator can post in a channel. “No class” deletes the choice immediately and removes the roles. Other members see the classes in /profile. The record log notes creating, changing and deleting classes and switching the choice on or off with the Discord ID of the acting person; members' choices are not in it.
• Group finder (module “Formation”, only if the server operator switches it on): The server operator's settings are stored: the chosen forum, the ID of the pinned starter post with its title, text and – if the server operator uploads or links one – an image (the bot loads it once, checks it and stores only the checked image, not the link), the IDs of the forum tags and of the category for the voice channels, and the templates (name, emoji, default text, group size, minimum, duration, optionally a cover image as a checked copy, not as a link, with the “Formation: Classes” plugin also the split of the slots into classes) with the Discord ID of the person who creates them, as well as the Discord ID of the person who set up the group finder. Once the starter is up, if someone creates a post of their own in the group finder forum, although planning there happens only through the starter, the bot removes it (posts by people who may manage posts there stay). So that nothing gets lost, it reads the title and text of that post once (for attachments only the file names) and sends them back to the person by direct message; none of it is stored. The same applies to messages in the pinned starter post itself, where searching happens only through the buttons: if someone who may not manage posts in the forum writes there, the bot removes the message, reads its text once for this (for attachments only the file names) and sends it back to the person by direct message – if someone writes a great many messages in a row, only for the first five per ten minutes; for this the bot keeps the times of these direct messages in memory for at most ten minutes. None of it is stored. The record log only notes that a post or message was removed, with the person's Discord ID and without content. If the person doesn't allow direct messages, the server operator gets a note in the report channel that mentions them. When a member looks for a group via the starter, the bot stores the search: title, text, time, duration, number of slots, the chosen template, the ID of the forum post and the creator's Discord ID – and the participant list, i.e. the Discord IDs of the members who click “Join” (with a split into classes also the chosen class, e.g. “Healer”; from a new time on also whether the person has answered yet, and the ID of the message with the question). They are visible on the card in the post. If the creator changes the time, the bot asks every participant by direct message whether they are still in; if someone doesn't allow direct messages, it asks in the post instead and mentions the person there. On a cancellation or hand-over it mentions the participants in the post. Input into the form is kept as drafts (see retention). The record log notes creating, changing, handing over and cancelling a search with the Discord ID of the acting person, without content. At the time of a search: one hour before the start the bot mentions the participants in the post and sends each of them a direct message with the time and a link to the post. If fewer people are in than the template's minimum, it asks the creator by direct message (in the post if they don't allow any) whether the run starts anyway, starts 30 minutes later or is cancelled; it stores the ID of that message until the question is answered or the run starts. 15 minutes before the start it creates a voice channel in the category chosen by the server operator that all members can see but only the participants can join (one permission per participant on the channel; the creator additionally receives moderation permissions there), sets a status under the channel (template, line-up) and creates a server-internal Discord event for it with title, time, link to the post and – if there is one – the template's cover image. The IDs of the voice channel, the Discord event and the reminder message are stored. After the end – as soon as the channel is empty, at the latest three hours after the planned end time – the bot deletes the voice channel and ends the Discord event; the post is archived and locked. Postponing and ending a run are noted in the record log with the Discord ID of the acting person. Latecomers: if someone clicks “Interested” on the Discord event of a run (or takes it back), the bot learns this with the person's Discord ID and creates a request: it stores the Discord ID, the search, where the request came from (Discord event, button, invitation), its state (waiting for the creator, waiting list, invited, declined) and the ID of the related message in the post. If the group is open, the bot mentions the person in the post with an invitation; with the plugin “Formation: Approval” it sends the request to the creator by direct message instead, who accepts or declines it (declined: no message to the person); if the creator does not accept direct messages, the bot mentions them in the post with a notice that does not name the person, and the creator decides via a button on the card whose answer only they can see. If the group is full, the person goes on a waiting list – also via the “Waiting list” button – and when a slot frees up, the bot mentions the next person or people in the post. “Invite interested” shows the creator the names of the interested people that Discord provides for the event, and the requests. The record log notes accepting and declining a request as well as collected invitations with the Discord ID of the acting person. Vote (with the plugin “Formation: Vote”): if the creator offers up to five dates to choose from, the bot stores the dates, the end of the vote and, per participant, which dates they ticked; the number of people per date is visible on the card. When the vote closes, the bot sends the creator the dates by direct message (if they don't allow any, in the post with a mention) and stores the ID of that message until the date is set. Once the date is set, everyone who ticked it gets a direct message (otherwise a mention in the post); anyone who hadn't ticked it is asked whether they are still in, as with a new time. The record log notes setting the date with the Discord ID of the acting person. “Again” and old crew: when a search ends or is cancelled, the bot stores a recipe for its creator so they can plan the same round again later with “Again”: template, title, text, the date and time of the last round (for “Again” only the time of day counts), duration, slots (including the split into classes and their own class), joining mode, the ID of the forum post and – as the “old crew” – the Discord IDs of the other participants. When the creator plans the round again, they can invite the old crew: the bot mentions the selected people in the new post with an invitation; each person has to join themselves. For the selection the bot asks Discord for these people's display names without storing them. The record log notes inviting the old crew (with the number) and deleting a recipe with the Discord ID of the acting person. Sidebar: if a member switches on “Sidebar” at the starter, the bot stores their Discord ID with the server ID and adds them as a follower to every open search post (so the post appears in their sidebar); once the group is full or running, it removes them again. For this it remembers which posts it added whom to. The bot deletes the system line Discord writes into the post when doing so. Switching on and off is noted in the record log.
• Own voice channels (module “Resonanz”, only if the server operator switches it on): The server operator's settings are stored: the IDs of the join channel and the category, the name pattern of the rooms, the user limit, the room type at start, the Discord ID of the person who set it up, and the time. When someone joins the join channel, the bot creates a voice channel, moves the person into it and stores, as long as the room exists: the channel ID, the owner's Discord ID, the room name (by the pattern usually with the display name on the server, e.g. “Anna's room” – that is also the channel name on Discord), the limit, the room type, the running number, the related join channel, the time and the ID of the menu card in the channel chat; in addition, what the owner sets via the menu card (or with /voice room): a status text, whether the room is locked, the Discord IDs of invited and kicked people and whether the owner renamed the room themselves. When the owner invites someone, the bot sends that person a direct message with the owner's display name, the room name, the server name and a link to the room; if they do not accept direct messages, it mentions them briefly in the room's chat instead (the line disappears after 2 minutes). Nothing is stored for this. When the owner leaves the room, it passes to the person who has been in it longest; for this the bot only remembers in memory since when someone is in the room. If the server operator's name pattern contains the placeholder {spiel}, the bot reads from the owner's Discord status which game they are currently playing and puts it into the room name – the game is only processed, not stored (only the resulting room name is stored, as long as the room exists). For this Discord reports status changes of all members to the bot; everything that does not concern the owner of such a room or – with Activity – the first game start of the day, the bot discards immediately. The bot deletes this data together with the room – at the latest when the bot leaves the server. “My room” (only with the Resonance+ plugin): If the owner clicks “💾 Keep” on the menu card, the bot stores per join channel their Discord ID, the room name (only if they chose it themselves), the limit, whether the room is locked and text only, the status text, the Discord IDs of invited people and the time of last use – so that their next room from this join channel starts the same way. Data is stored only on this click. “Forget” (in the reply to “Keep” or with /voice room) deletes the entry immediately; otherwise the bot deletes it when the person leaves the server (their Discord ID then also disappears from other members' invitation lists), when the server operator removes the join channel, when the bot leaves the server, and at the latest after 90 days without use. If Resonance+ expires, nothing is deleted; “My room” is simply no longer applied (the 90 days keep running). Only in memory and for a few minutes at most, the bot remembers when someone last wanted a room (waiting time of 30 seconds). If something does not work or the person has to wait briefly, a short notice mentioning the person appears in the join channel's chat and disappears after 60 seconds; if the bot is missing a permission, the message to the server operator (channel #modario-meldungen) names the person's display name or the room name. The record log contains setting up, changing and removing with the Discord ID of the person acting.
• Moderation (module “Garnison”, only if the server operator switches it on): The server operator's settings are stored (mod-log channel, mod roles, whether direct messages name the moderator, retention, reason templates, rules of automatic moderation with exceptions for roles and channels; with Garnison+ also custom words, patterns and allowed links). When a moderator or Modario itself takes action (warning, timeout, kick, ban), the bot creates a case: the Discord ID of the member concerned, type, duration, reason, the acting person (“Modario” for automatic actions), time and, where applicable, evidence (copied text or image link of the message concerned, with the channel). Before a kick or ban the member receives a direct message with server, action, duration and reason (with or without the moderator's name, depending on the setting); if the member files an appeal, the text entered (at most 1000 characters) is shown to the server operator in the chosen channel and stored with the case. When a member reports a post, the bot stores the evidence, the reason, the Discord ID of the reporting member (visible to moderators only) and the number of reports; image attachments of the reported message are downloaded immediately (Discord links expire) and shown only on the report card. If moderation dismisses a report, the bot counts it as a false report by the reporting member; after three false reports within 30 days it blocks that member from reporting for seven days. Automatic moderation (Discord AutoMod with rules Modario creates, plus flood detection) blocks messages before they are posted; Discord reports each hit to Modario with the Discord ID, the channel and the blocked text, from which a warning, evidence and a counter per rule are created. For flood detection the bot only counts message timestamps per member in memory, without content. Kicks, bans and timeouts made through Discord or other bots are read from the server's audit log and recorded as a case. Tickets (private threads between member and team): the bot stores the thread ID, the status and, on closing, a transcript (message text, attachments only as file names, at most 500 messages), which it can send by direct message on request. Warnings can delay the promotion to member.
• Error logs: technical details about bot actions. People appear in them only as a Discord ID.

Message content, i.e. what members write in channels: so that the group finder can return removed posts and messages to their authors, the bot has Discord's permission to receive message content (“Message Content Intent”). Discord therefore technically also transmits the content of other messages on servers the bot is on. The bot does not evaluate this content, does not keep it in memory and does not store it – it uses content only in the group finder case described above. Input into the bot's forms (e.g. an event title) is separate and described above. With the module Garnison the bot also receives message content for moderation: it uses it only to secure hits of automatic moderation and reported posts as evidence and to keep a ticket’s transcript; it does not evaluate or store other messages.

Purposes and legal bases

• Providing the bot and its functions to the server operator: Art. 6(1)(b) GDPR (contract); for member data on behalf of the server operator.
• Record log: Art. 6(1)(c) GDPR (accountability under Art. 5(2) and Art. 28 GDPR) and Art. 6(1)(f) GDPR (evidence towards authorities and in disputes).
• Error logs: Art. 6(1)(f) GDPR (secure, error-free operation).
• Moderation: on behalf of the server operator (Art. 6(1)(f) GDPR, the server operator’s legitimate interest in an orderly server).
• Activity: on behalf of the server operator (Art. 6(1)(f) GDPR, legitimate interest in an overview of who actively takes part), with objection by button in /profile.
• Class choice: on behalf of the server operator (Art. 6(1)(f) GDPR, legitimate interest in members finding suitable teammates); the information is voluntary and can be deleted at any time with “No class”.
• Live: Art. 6(1)(a) GDPR (consent – the member adds their channel themselves and can remove it at any time in /profile), on behalf of the server operator; for the query to Twitch in the USA Art. 49(1)(a) GDPR.

Storage period

• Server settings: until the bot is removed from the server or the contract ends, then deleted within 30 days.
• Events: 24 hours after they actually end, cancelled events immediately. Only a counter per server and month without personal reference remains. Series, calendar and subscription addresses until the server operator deletes or replaces them (a new subscription link invalidates the old one immediately); ended series 24 hours after ending.
• Classes: classes and subgroups like the server settings. A member's choice until “No class”, until 30 days after leaving (whoever returns earlier keeps it) or until the bot leaves the server.
• Welcome: the cards are normal messages in the channel and remain until the server deletes them – or until the lifetime set by the server operator (one hour, one day or seven days) expires; the bot deletes the noted message ID together with the card. Short-visit and group-welcome notes about ten minutes, in memory only. Direct messages sit in the member's chat with Modario; the bot does not store them and does not delete them later. A background image stays stored until the server operator replaces it, picks a Modario colour or deletes the template, at most as long as the other server settings. Kick/ban notes no more than two minutes, in memory only. Invite link counters (only with an invite rule) in memory only, until the bot's next restart. Ranks: an open promotion case (“notify the mods”) until the member is accepted, leaves or loses the guest role; a demotion note until the person is no longer a guest or leaves the server. Activity: point values (also per main class) until 30 days after leaving (whoever returns earlier keeps it); objection until withdrawn or until the bot leaves the server.
• Announcements: until the server operator deletes them or the bot is removed from the server (like the server settings). Sent announcements are normal messages in the channel. Weekly overview: settings like the server settings; ping counter per role 8 weeks. Live: the entry until it is removed in /profile, removed by a mod, the member leaves the server or the bot leaves the server; stream details until the stream ends. The live card is a normal message in the channel and stays until the server deletes it.
• Group finder: settings and templates until the server operator deletes them or the bot is removed from the server (like the server settings). The bot does not store the title and text of removed posts and messages; the direct message stays in the person's chat. Searches remain as records as long as the server operator runs the group finder; the bot deletes a search's participant list (including the dates ticked in a vote) 24 hours after its end or cancellation – likewise requests, the waiting list and the list of which posts it added whom to because of the sidebar. The “Sidebar” setting stays until the member switches it off or leaves the server. The forum post with the card remains a normal post in the forum until the server deletes it. The IDs of the voice channel, the Discord event and the reminder message stay with the search's record; the bot deletes its list of created voice channels as soon as the channel is gone. Recipes for “Again”: 90 days after their last use (a new round from them extends this), at most 10 per member and server – the oldest drops out; the old crew in it (the participants' Discord IDs) 30 days after the end of the round. A recipe goes earlier if the creator deletes it, leaves the server, or the round's forum post is deleted (the bot checks this within a day at the latest); anyone who leaves the server also drops out of other people's old crews – both as far as Discord reports the leaving to the bot. Drafts: 3 hours after the last input.
• Own voice channels: settings until the server operator removes them or the bot is removed from the server (like the server settings). The bot deletes the details of a room (including the owner's Discord ID) together with the room – as soon as it is empty, deleted by hand or the bot leaves the server. Notices in the join channel disappear after 60 seconds; messages in #modario-meldungen stay until the server operator deletes them. “My room”: until “Forget”, until the person leaves, until the join channel is removed or the bot leaves the server – at most 90 days after the last use (keeping it or a room that starts from it).
• Moderation: a case 12 months after the member’s last case; evidence including reporter, reason and ticket transcript 90 days; a ban entry as long as the ban lasts. The server operator can only shorten these periods. Downloaded image attachments of reported messages: at most 24 hours or until moderation decides. Report cards without a decision expire after 7 days. False reports: 30 days, a reporting block 7 days. Counters of automatic moderation (no personal data): until the bot leaves the server. Settings and lists: like the server settings.
• Drafts (including an uploaded image): 3 hours after the last input.
• Record log: for the duration of the contract and three years thereafter (regular limitation period under Section 195 BGB).
• Error logs: no more than 30 days.
• Backups: 14 days, then overwritten.

Discord

The bot works through the Discord platform. All data therefore also passes through Discord. For users in the European Economic Area this is Discord Netherlands BV, Schiphol Boulevard 195, 1118 BG Schiphol, Netherlands. Discord also processes data in the USA. According to its own statements, Discord participates in the EU-U.S. Data Privacy Framework. Which data Discord itself processes is described in Discord's privacy policy.

Twitch

For live notifications the bot queries public channel data from Twitch Interactive, Inc., 350 Bush Street, 2nd Floor, San Francisco, CA 94104, USA. Only the Twitch name or Twitch user ID is transmitted, never Discord data; Twitch thereby learns that the live status of this channel is being queried. As far as we know (October 2026), Twitch does not participate in the EU-U.S. Data Privacy Framework; there is therefore no adequacy decision for Twitch in the USA, and your data is not protected there to an equivalent level (for example against access by authorities). The query therefore only takes place if you add your channel yourself; the entry form points this out, and by submitting it you consent (Art. 49(1)(a) GDPR). “Remove Twitch” in /profile ends it immediately. The preview and profile images on the live card are links to Twitch that Discord loads; the bot does not load them. Which data Twitch itself processes is described in the Twitch privacy notice.

4. Hosting

The website, bot and database run on a server of Contabo GmbH, Welfenstraße 22, 81541 Munich, Germany. The data centre is located in the European Union (Lauterbourg, France) and is operated by Contabo France SAS. A data processing agreement under Art. 28 GDPR has been concluded with Contabo.

5. Contact by email or Discord

If you write to us by email or in the support channel, we process your details to answer your request. The legal basis is Art. 6(1)(b) GDPR where a contract is concerned, otherwise Art. 6(1)(f) GDPR. We delete the request once it has been dealt with and no retention obligation applies.

6. Your rights

You have the right to

• access your stored data (Art. 15 GDPR),
• rectification (Art. 16 GDPR),
• erasure (Art. 17 GDPR),
• restriction of processing (Art. 18 GDPR),
• data portability (Art. 20 GDPR),
• object to processing based on Art. 6(1)(f) GDPR (Art. 21 GDPR).

An informal message to the email address above is sufficient. You can also lodge a complaint with a data protection supervisory authority, for example the one responsible for us: Landesbeauftragte für den Datenschutz und die Informationsfreiheit Baden-Württemberg, www.baden-wuerttemberg.datenschutz.de.

7. Changes

If new functions are added, such as paid tiers or the news module, we will extend this policy before they become available. The data processing agreement (version 2.4) already describes these modules. The version published here applies.