Terms of Service
Updated 2026-04-26·8 sections
Scope
These terms govern your use of blau (also branded "bluejutzu"), which consists of the public web entry point, an authenticated dashboard for building Discord-server automations, and a Discord bot that executes those automations on your behalf. By using any part of the service you agree to these terms.
Eligibility and account linking
You log in by linking a Discord account via OAuth. You must have authority over the Discord account you link and over any Discord server in which you configure automations or invite the bot. You are responsible for everything that happens under your linked account, including actions performed by automations you create.
Configuring server-level automations or inviting the bot also requires the corresponding Discord guild permissions (typically MANAGE_GUILD or guild ownership). The dashboard checks these against the Discord API; if your permissions are revoked there, your access in our dashboard is revoked too.
Sessions and authentication
After OAuth we create a standard session that is kept for up to 30 days. That session record controls both the cookie lifetime in your browser and the server-side session TTL.
Session cookies are HTTP-only and, in production, marked Secure with SameSite=None so the dashboard subdomain can use them. Session handling does not anonymise your activity: every request is associated with your Discord ID server-side and may appear in operational logs.
Legacy incognito sessions may still exist until they expire naturally, but that mode is no longer offered for new logins.
You can also register one or more passkeys (WebAuthn credentials) to re-authenticate without going through Discord OAuth again. Passkeys can be removed from the dashboard at any time.
Acceptable use
- No unlawful or abusive use, and no attempts to bypass authentication, rate limiting, or other security controls.
- No misuse of OAuth tokens, session identifiers, passkey credentials, or automation features to gain unauthorised access to Discord accounts or servers.
- Automations you build run against the Discord API on your behalf. You must not configure them in ways that violate Discord's Terms of Service, Developer Policy, or Community Guidelines — for example, spam, mass DMs, harassment, or evading Discord moderation.
- We apply per-IP and per-user rate limits across login, passkey operations, and guild mutations to protect the service and the Discord API. Sustained attempts to circumvent them are themselves a violation of these terms.
Service availability
The service is provided on an "as available" basis. We may change, suspend, or discontinue features at any time for maintenance, security, or product reasons, and we do not currently offer an uptime SLA.
Liability
To the extent permitted by law we are fully liable for intent and gross negligence, and for injury to life, body, or health. For ordinary negligence, our liability is limited to foreseeable, typical damage from a breach of essential contractual obligations (Kardinalpflichten), except where mandatory law provides otherwise.
We are not liable for damage caused by Discord platform outages or Discord API changes, nor for the consequences of automations that you yourself configured (for example, a rule you set up that bans the wrong member).
Termination
You can stop using the service at any time by removing the bot from your Discord servers, deleting your sessions and passkeys from the dashboard, and unlinking your Discord account. We may suspend or terminate access for serious violations of these terms, of Discord's policies, or of legal requirements.
If you remove the bot from a server, we generally keep that server's automation data for up to 30 days so you can add the bot back without rebuilding everything from scratch. During that period, automations tied to the bot will not fire. If the server remains unused, we may delete the server-specific data after that 30-day period.
Where applicable law requires longer retention for specific records, we may keep the legally required subset for longer. Depending on the record type, German commercial and tax retention rules can require retention periods of 6, 8, or 10 years.
Governing law
To the extent legally permissible, German law applies. Mandatory consumer protection rules of your country of residence remain unaffected.