Privacy Policy

blau (also branded "bluejutzu") provides Discord account linking, 30-day persistent sessions, optional passkey re-authentication, and a dashboard for configuring Discord server automations. This policy describes what personal data is processed in connection with that service and on what legal basis.

For access, deletion, or other data-subject requests, contact us through the public repository at github.com/Bluejutzu/site until a dedicated contact channel is published. A formal controller entity will be named here as soon as the operator structure is finalised.

The categories below correspond to fields actually written to our database, cache, or object storage. We do not collect data we don't use.

• Discord profile. Your Discord user ID, your global display name, and your avatar hash. We request the identify, guilds, and email OAuth scopes; email is used only for the OAuth handshake and is not stored.
• Discord OAuth tokens. The access_token, refresh_token, token_type, and expires_in returned by Discord. They are persisted so we can keep your account linked and enumerate the guilds you administer when you open the dashboard.
• Session records. A 64-character random session token (also held in your browser as an HTTP-only cookie); creation, expiry, and last-seen timestamps; the session mode (standard for current sessions, with legacy incognito records only where they still exist until expiry); an optional fingerprint hash; and optional device information consisting of your User-Agentstring and a derived label such as "Chrome on Mac".
• Passkey credentials (only if you register one). A credential ID, the public key, a signature counter, the device type, a backup flag, optional transport hints, the name you choose, and creation / last-use timestamps. We never receive your private key.
• Guild metadata. For guilds you administer: ID, name, icon hash, and whether our bot is present. Fetched from the Discord API on your behalf and cached transiently in Upstash Redis (see retention).
• Automation configurations.The triggers and action sequences you create in the dashboard, stored per Discord guild — not per user. The list of Discord IDs that have edited a guild's configuration is recorded so co-administrators can see who set up what.
• Operational data. Structured request logs (timestamp, log level, request context, your Discord ID where relevant) and product analytics events such as logins and session deletions.

• Account linking, sessions, passkeys, and dashboard functionality: Art. 6(1)(b) GDPR — performance of a contract.
• Rate limiting, abuse prevention, and operational logging: Art. 6(1)(f) GDPR — our legitimate interest in keeping the service available and secure.
• Product analytics: Art. 6(1)(f) GDPR — legitimate interest in understanding feature usage. The only user identifier sent to PostHog is your Discord ID (as distinct_id).

New sign-ins are always issued as standard sessions. The session record and its cookie are valid for up to 30 days. The cookie is HTTP-only, marked Secure in production, and uses SameSite=None so the dashboard subdomain can read it.

Legacy incognito sessions may still appear in internal records until they expire naturally, but that mode is no longer offered for new logins.

Sessions do not make your activity anonymous. All session data is associated with your Discord ID in our backend and may appear in operational logs. Your fingerprint hash, when collected, is only computed for standard sessions.

• Session records and cookies: deleted at the recorded expiresAt (normally 30 days for current sessions, or 24 hours only for legacy incognito sessions that still exist), or earlier if you log out or delete the session in the dashboard.
• Discord OAuth tokens: retained while your account is linked; removed when you unlink Discord or delete your account.
• Passkey credentials: retained until you delete them in the dashboard.
• Guild automation data and related server metadata: generally retained for up to 30 days after the bot is removed from that server or the server otherwise becomes inactive, so the setup can be restored if you add the bot back during that window. If there is no renewed use, the server-specific data may be deleted after that period.
• Cached guild list (Upstash Redis): 10 minutes per cache entry.
• Records subject to statutory retention duties: if a specific record must be retained to comply with applicable law, we keep only the required subset for the mandatory period instead of the standard deletion period. Under current German commercial and tax rules, that can mean retention periods of 6, 8, or 10 years, depending on the record type.
• Operational logs and analytics events: retained according to the retention policies of the respective processors (Axiom, PostHog).

We rely on the following processors. Where personal data leaves the EEA, transfers are covered by an adequacy decision or by Standard Contractual Clauses.

• Discord (Discord Inc., USA) — OAuth identity provider and Bot API used to enumerate guilds and execute your automations.
• Convex (Convex, Inc., USA) — primary application database for users, sessions, passkeys, guilds, and automations.
• Upstash (Upstash, Inc.) — Redis cache for guild lists, permission checks, and rate-limit counters.
• Axiom (Axiom Co., UK) — structured logs and OpenTelemetry traces. Active only when an Axiom token is configured for the deployment.
• PostHog (PostHog Inc., USA) — product analytics events. Active only when a PostHog key is configured for the deployment.

Under Arts. 15–22 GDPR you may request access, rectification, erasure, restriction, and portability of your personal data, and you may object to processing based on legitimate interests at any time.

The right to erasure is not absolute. If data is no longer needed for the service, we aim to delete it without undue delay, but we may keep data to the extent it is still necessary to comply with a legal obligation or to establish, exercise, or defend legal claims.

Most of these actions you can perform yourself from the dashboard: list active sessions, delete a specific session, delete all sessions other than the current one, remove a passkey, and unlink your Discord account.

You have the right to lodge a complaint with a data protection supervisory authority, including in your EU member state of habitual residence, place of work, or alleged infringement.