Privacy Policy

This is a convenience translation. Only the German version is authoritative.

For the Discord bot “SnapCord” and this website (snapcord.de). Last updated: 5 November 2026.

1. Who is responsible

Raik Krause
Contact: raikkrause08@gmail.com

2. Logging in to this website

Login goes through Discord. In the process, Discord provides the bot with your user ID, your name, your profile picture and the list of your servers (scopes identify and guilds). The site uses this to show the servers where you are an administrator. The access token from Discord is not stored.

After login, the site sets a single cookie that keeps you logged in. Login does not work without this cookie. The session expires after 12 hours or ends when you click “Log out”. There are no advertising or analytics cookies, no tracking, and no fonts or scripts from third-party servers.

3. Logs

On every login, the web service writes the Discord ID and the IP address to its log. The upstream web server logs requests with IP address, time and the address requested. The logs are used only for troubleshooting and for preventing abuse.

The bot also keeps an activity log that only the operator can see: which command was used when, by which user ID, on which server (without free-text reasons or notes), logins and form actions on this website, results of backups and restores, anti-nuke alerts and the bot joining servers. It contains no IP addresses. It is used for troubleshooting, detecting abuse and usage figures. Entries are deleted automatically after 90 days.

Live view for the operator: Every open page checks in every 30 seconds with a random identifier that only lives in that browser tab (no cookie), the page being viewed and whether the tab is visible. Device (phone, tablet, PC) and browser are roughly derived from the browser's user agent. For signed-in users, the operator also sees the Discord name and user ID. Each check-in is deleted after 70 seconds; only the highest simultaneous count per day is kept, without any link to people.

4. What a backup contains

A backup is created by an administrator of a Discord server, either manually or automatically. Depending on the settings and the rank, it contains:

• server settings, roles, channels, permissions, emojis, stickers and AutoMod rules,
• messages with their content, time, the authors' name, ID and profile picture link, plus links to attachments or the attachments themselves,
• the ban list with user IDs and reasons,
• the members' user IDs together with their roles.

The sole purpose of a backup is to restore or transfer the server at the request of its administrators. Backups are stored on a server run by the operator, not with a cloud provider.

For how long: Manually created backups are kept until their creator deletes them (/backup delete or on this website). Of automatic backups, only the most recent ones are kept; how many depends on the rank. Before every “Replace”, the bot creates a safety backup; of these, the last 3 per server are kept.

Precaution: If Anti-Nuke is on and someone gets the Administrator permission or a bot joins the server, the bot immediately saves the server's structure (roles, channels, permissions, without messages) and starts a backup like an automatic one. The last 6 of these are kept per server. Who granted the permission and who received it is recorded with the user ID in the activity log (90 days). After automatic backups the bot can post a list of changes (role and channel names, permissions) to the server's moderation log.

As a file: The creator can download a backup (optionally as a ZIP with the saved attachments). The file is then with them, outside the operator's control. If someone uploads such a file, the bot stores its content – including messages, names and IDs of other people – as that user's backup, trimmed to their rank and kept for the same time as one of their own backups. Downloads and uploads are recorded in the activity log with size and counts, but without content.

5. Other stored data

• Jobs: server ID, user ID of the person who triggered it, type, time and result of backups and restores.
• Moderation: warnings with server, user ID, moderator ID, reason and time.
• Anti-nuke: the per-server settings and the user IDs on the exemption list.
• Ranks and blocks: user ID, assigned rank with expiry date; blocked user or server IDs with the reason.
• Templates: submitting a template stores a copy of a backup's structure (roles, channels, permissions, emojis, stickers – without messages, members, bans, server name and icon) with name, description, the creator's user ID and the number of uses. Once approved, structure, name and description are public in the gallery; the creator is not named there. Reports store the template, the reporter's user ID, the reason and the time. A template stays until its creator or an operator deletes it.
• Recycle bin: when a channel, category or role is deleted on a server, the bot remembers what it looked like (name, settings, permissions including the user IDs in them; for roles, the user IDs of the members who had it), plus the user ID of whoever deleted it and the time. Messages are not stored. Entries are deleted after 7 days, at most 200 per server. The server owner can turn the recycle bin off with /trash off; everything collected so far is then deleted immediately.
• Tickets: when a server sets up tickets, the bot remembers the category, team role, log channel and the channel with the button. The bot does not store ticket contents: a ticket is a channel on the server, and on closing the bot puts the transcript (messages with user names and IDs) as a file into the server's log channel. Opening and closing are recorded with the user ID in the activity log. For statistics the bot keeps, per ticket, the server, the user IDs of the opener and of whoever closed it, the type, the times and – if given – the rating (1–5 stars) with a comment. Answers to a ticket type's form are only in the ticket channel itself. For deadlines the bot keeps the time of the opener's and the team's last message, plus who claimed the ticket. If a server sets up forwarding, the bot copies a ticket's messages (display name, text, links to attachments) into a thread on the given team server and replies from there back into the ticket; it does not store the contents. If a server chooses tickets as a private thread, the thread is not deleted on closing but locked, and stays readable on the server for the opener and the team until the server deletes it. For each ticket the bot also keeps the running number, a reason given on closing and an open close request (who, reason, expiry).
• Raid protection: only if a server turns it on. The bot counts joins in memory (time, user ID, account age) for the length of the time window. If it kicks or bans during a raid, it keeps the affected user IDs for 7 days so that “Unban all” can undo a false alarm.
• AI in tickets: only if a server turns it on with its own key from Google (Gemini) or Anthropic (Claude). The bot then sends the ticket opener's answers, the AI's questions, the server profile and the server name to that provider – on behalf of and billed to the server, under its terms. The key is only stored encrypted and is never shown or logged. The bot keeps the conversation with the AI only while the ticket is open; it is deleted on closing, and the summary is in the ticket transcript. If the bot leaves the server, key and profile are deleted. The ticket shows a notice about the AI, and “Straight to the team” skips it. If the AI answers questions from the server's knowledge base (in a ticket, a help channel or on mention), the question and the matching entries go to the provider. Questions the knowledge doesn't cover are kept without user ID for 30 days so the team can add entries.
• Spam protection: only if a server turns it on. The bot checks new messages and keeps in memory, for at most one minute, when someone wrote and – simplified – what, to spot the same message in several channels. Only a hit (user ID, rule, action) is stored in the activity log (90 days).
• Verification: the bot stores the server's role, channel and mode and – if it locked the server – @everyone's previous permissions. Every verification is recorded with user ID and time in the activity log (90 days).
• Announcements: the bot stores scheduled announcements with server, channel, text, mention, time, repeat and the creator's user ID until they are deleted; one-off ones stay paused in the list after sending until someone deletes them. Uploaded images and sender pictures are kept in the bot's storage until the announcement is deleted.

This data is kept until it is deleted, in the case of warnings for example by the server's moderators.

6. Legal basis

You use the login and the commands at your own request (Art. 6(1)(b) GDPR). Backups, moderation and logs are based on the legitimate interest of the server administrators and the operator in a secure, restorable server (Art. 6(1)(f) GDPR).

7. Disclosure

The data is not sold and not passed on to third parties. It comes from Discord and goes back there when a backup is restored. Discord itself is covered by its own privacy policy.

8. Your rights

You have the right of access, rectification, erasure, restriction of processing, data portability and objection. To exercise these rights, use the contact address above. If your messages or your ID are in the backup of someone else's server, that server's administrators can also delete the backup. You also have the right to lodge a complaint with a data protection supervisory authority.