Privacy Policy

Draft, not legal advice, have it reviewed by a lawyer before publication. (Entwurf, keine Rechtsberatung, vor Veröffentlichung anwaltlich prüfen lassen.)

Last updated: Oktober 2026

This privacy policy explains which personal data we process when you use Lizbot. Lizbot consists of a Discord bot, a web dashboard (https://lizbot.gg), public portals (support portal, appeal portal, verification), an API and a mobile app. The German version is legally binding; this English version is provided for convenience. zu prüfen

1. Controller

Korbinian Günther Dienstleistungen
Agnesstraße 47, 97833 Frammersbach, Deutschland
Email: [email protected]
Phone: +49 175 5095559

Data protection officer: dsb name und kontakt fehlt (only if appointed or legally required)

2. Two roles: controller and processor

a) We as controller. We are responsible for your account and your contract with us: login to the dashboard and app, subscriptions and payments, security and abuse prevention, communication with you, and technical logs of our servers.

b) We as processor for server owners. When a server owner uses Lizbot on their Discord server, they decide which modules are active (for example moderation, tickets, leveling, backups) and how they are configured. We process the members' data on that server on behalf of and on the instructions of the server owner (Art. 28 GDPR). The server owner is the controller. We provide a data processing agreement for this. Members with questions about moderation decisions, tickets or stored content should first contact the team of the respective server. We support the server owner in responding.

3. Data we process

3.1 Login to dashboard, app and API

Login uses Discord (OAuth2). We receive from Discord: user ID, username, display name, avatar, email address, locale and the list of your servers with your permissions there. Discord access tokens are stored encrypted (AES-256-GCM) to keep your server list up to date.

For your session we set a strictly necessary cookie (keeper_session) or, in the app, a login token. Sessions are stored only as a hash, together with user agent and IP address for abuse detection and so you can end active sessions.

API keys (Studio plan) are stored only as a hash with a short, non-secret prefix.

Legal basis: Art. 6(1)(b) GDPR (contract). Security data (IP, user agent): Art. 6(1)(f) GDPR, legitimate interest in secure operation.

3.2 Data on Discord servers using Lizbot (processing on behalf)

Depending on the enabled modules, the bot processes on behalf of the server owner:

• Member data: Discord ID, username, display name, avatar, roles, join date, account age.
• Moderation: cases (warnings, timeouts, kicks, bans, notes) with reason, moderator and time, member reports including the reported message content, ban appeals with the member's answers, quarantine status, join log with invite code and risk score (alt detection), reputation.
• AutoMod: message content is checked automatically for rule violations. Data is stored only on a match (rule, excerpt). If AI moderation is enabled (Studio plan), the message text is sent to Anthropic for assessment (see section 5).
• Logging: edited and deleted messages, role and nickname changes, voice joins, if enabled by the server owner.
• Tickets: all messages in ticket channels including attachments (as links), answers to ticket questions, ratings after closing, internal staff notes, HTML transcripts.
• Verification: time and method. For email verification the email address, a hash of it (to prevent reuse) and a hashed confirmation code. For web verification a captcha check via Cloudflare Turnstile.
• Community features: levels and XP, message count, voice minutes, birthdays (day, month, optionally year), poll votes, reminders, giveaway entries, economy balances and transactions, temporary voice room preferences.
• Statistics: daily counters per server (joins, leaves, message count, active members, voice minutes) without message content. To count active members, Discord IDs are cached briefly (at most 3 days).
• Backups: at the server owner's request, a snapshot of the server: roles, channels, permissions, bans with reason, member roles and optionally the last up to 100 messages per channel in up to 20 channels (Studio plan).

Legal basis: determined by the server owner as controller, usually Art. 6(1)(f) GDPR (legitimate interest in moderating and running a community). Our processing is based on the data processing agreement.

3.3 Public portals

• Support portal: users without Discord log in via a sign-in link sent to their email. We store the email address, a hash of it, the chosen display name, ticket content and a session cookie (keeper_portal, stored as a hash). Staff replies are sent by email (at most one email per ticket every 10 minutes).
• Appeal portal: banned members log in via Discord and submit an appeal. We store answers, status and decision.
• Verification portal: see section 3.2.

Legal basis: for the server owner as in 3.2; for our provision of the login process Art. 6(1)(b) and (f) GDPR.

3.4 Mobile app and push notifications

If you allow notifications, we store a push token of your device and a device name. Notifications are delivered via Expo (Expo, Inc., USA) and Apple Push Notification Service or Firebase Cloud Messaging (Google). You can disable push at any time.

Legal basis: Art. 6(1)(a) GDPR (consent via the operating system prompt) and Art. 6(1)(b) GDPR.

3.5 Payments and subscriptions

Paid plans are processed by Stripe (Stripe Payments Europe, Ltd., Ireland). Stripe does not share card numbers with us. We store the Stripe customer ID, subscription ID, plan, billing interval, status, period end and the Discord ID of the purchaser.

Legal basis: Art. 6(1)(b) GDPR and Art. 6(1)(c) GDPR (statutory retention obligations).

3.6 AI features (Studio plan)

If the server owner uses AI features (ticket summaries, reply suggestions, automatic categorisation, AI moderation, server building from a description), the required texts (ticket messages, the message to be checked, the description of the desired server and possibly names of existing roles and channels) are sent to Anthropic PBC (USA). We cache summaries to avoid repeated requests and count usage per server and day.

Legal basis: as in 3.2, determined by the server owner who enables the feature.

3.7 Social alerts, webhooks and integrations

At the server owner's request, the bot fetches public feeds (YouTube, RSS) or the Twitch API; no member data is transmitted. If the server owner configures outgoing webhooks, we send event data (for example new ticket, new case, report) to the address the server owner provides. The server owner is responsible for this transfer.

3.8 Server logs and error analysis

Our servers log technical events (time, request path, status code, error messages) for troubleshooting and attack prevention. If enabled, error reports are sent to Sentry (Functional Software, Inc., USA), with personal data removed as far as possible.

Legal basis: Art. 6(1)(f) GDPR (secure and stable operation).

3.9 Contact by email

If you contact us, we process your information to handle the request (Art. 6(1)(b) or (f) GDPR).

4. Recipients and service providers

5. Transfers to third countries

Some providers are located in the USA. Where they are certified under the EU-US Data Privacy Framework, transfers are based on the European Commission's adequacy decision (Art. 45 GDPR). Otherwise we use the Commission's standard contractual clauses (Art. 46(2)(c) GDPR) with supplementary measures. Using Discord technically requires a transfer to Discord. AI features are off by default and are only used if the server owner explicitly enables them.

6. Retention

7. Export and deletion by server owners

Server owners can export all data stored for their server and delete it completely in the dashboard at any time. Individual cases, tickets, backups, templates and other entries can be deleted selectively.

8. Cookies and local storage

We do not use tracking or advertising cookies or third-party analytics. We only set strictly necessary cookies: keeper_session (dashboard login) and keeper_portal (support portal login). Some convenience settings are stored locally in your browser. Legal basis: Section 25(2) No. 2 TDDDG.

9. Your rights

You have the right of access (Art. 15), rectification (Art. 16), erasure (Art. 17), restriction (Art. 18), data portability (Art. 20) and to object to processing based on legitimate interests (Art. 21 GDPR). You can withdraw consent at any time with effect for the future (Art. 7(3) GDPR).

For data we process on behalf of a server owner (section 3.2), please contact the team of the respective server. If you contact us directly, we forward the request to the server owner.

You also have the right to lodge a complaint with a supervisory authority, in particular in the Member State of your residence, workplace or the place of the alleged infringement. Our competent authority is Bayerisches Landesamt für Datenschutzaufsicht (BayLDA), Promenade 18, 91522 Ansbach.

10. Automated decisions

AutoMod rules, raid protection, alt detection and optionally AI moderation take automated actions (for example deleting a message or a timeout). Their scope is set by the server owner. Affected users can contact the server team; actions are logged and can be reviewed and reversed, and bans can additionally be challenged via the appeal portal. zu prüfen: assessment under Art. 22 GDPR

11. Changes

We update this policy when features or the law change. The version published here applies.