ControlBay
Legal notice · Privacy information · Terms of use · Status · Deutsch

Privacy information

Editorial revision: 17 November 2026

Privacy information – draft awaiting review of legal bases, processing responsibilities, service providers and international transfers. The technical statements below are based on the deployed ControlBay application; this is not a legally approved final policy.

1. Controller and contact

Ioannis Antoniadis · c/o Impressumservice Dein-Impressum, Stettiner Str. 41, 35410 Hungen · kontakt@ioannisdev.de

For privacy enquiries, access requests or deletion requests about this installation, please contact the address above.

The ControlBay operator determines the technical operation of this website, its Discord OAuth login, panel sessions and infrastructure security. Server owners choose which optional modules to enable and configure access rights, moderation, tickets, event logging and retention settings within the available technical limits. These decisions can affect different processing activities and the personal data of server members who never sign in to this panel.

The legal roles must be assessed separately for each activity: the ControlBay operator and a Discord server owner may act as independent controllers, joint controllers or in a controller-processor relationship, depending on who actually determines purposes and essential means. A server owner enabling a module does not automatically make them solely responsible, nor does it automatically establish a data processing agreement or the consent of every member. These allocations and any required Article 26 or 28 GDPR arrangements are not yet finally determined.

Information for Discord server members

You do not need to sign into the ControlBay web panel to be affected by enabled server functions. Server owners may enable tickets, moderation, server event logging, XP/levels, community games and optional integrations. Depending on those settings, Discord identifiers, server events, message excerpts, ticket transcripts, sanctions and statistics may be processed. Ordinary message-content logging is disabled by default, but ticket transcripts and moderation evidence can still contain messages.

For supported XP/statistics, use /privacy optout on the Discord server. /privacy delete removes selected user data for that server, not all ticket or moderation records, Discord copies or backups. For broader access or deletion requests, contact the operator listed above. Ask your server administrators which modules are enabled and whether they publish separate server-specific privacy information.

This member information is not a request for blanket consent. Actual responsibility and the legal bases for each operation remain subject to review.

2. Access to the website, Discord login and security

When using the website, technical requests reach the web server. The application can log the request method, requested path and IP address for operation and error diagnosis. The Apache/Virtualmin reverse proxy stores separate access and error logs for this website and rotates them weekly, keeping up to five rotated files under the current server configuration. The application and database container logs have size-based rotation limits (up to four files of 8 MiB each per container); this is not a fixed retention period in days. These settings may change when the infrastructure is updated.

Logging in uses Discord OAuth2 with the “identify” and “guilds” scopes. The application reads your Discord user ID, display name, avatar and server list so it can show only your permitted servers and controls. It stores a login session containing a pseudorandom identifier in hashed form, the account and eligible server IDs, a CSRF protection value and an expiry. It does not store your Discord password.

A technically required “haven_session” cookie remains valid for up to seven days (HttpOnly, Secure on the HTTPS production site, SameSite=Lax). The temporary “haven_oauth” cookie for signing in expires after ten minutes. Signing out ends the stored session.

3. Discord server functions and optional modules

Depending on the modules enabled by each server owner, ControlBay processes server, channel, role, message and member IDs, configurations and administrator actions. Optional features include reaction roles, welcome/leave messages, tickets, moderation, anti-spam, game server information, feeds, music queues, reminders and community games.

Moderation records may contain affected users, moderator IDs/names, reasons, sanctions, timestamps and evidence links or saved evidence excerpts. Ticket features may store the participant’s name/ID, messages, attachments, closing reason and transcripts; authorized support roles and explicitly enabled panel managers can access the relevant ticket data.

With the level/statistics module enabled, counters for messages, reactions, XP and voice participation time can be stored. ControlBay does not record voice audio. Server event logging can record member/role/channel events; saving message text in this logging module is disabled by default and can be enabled by the server owner. Ticket transcripts and evidence excerpts are separate functions and may contain message text even when ordinary message-content logging is disabled.

4. Browser storage and externally loaded images

The website stores preferences locally in your browser, such as language, light/dark theme, selected Discord server, dashboard module pins, preview state and loading animation preference. These values are used for display and can be removed through your browser’s website data controls.

Profile pictures, thumbnails and album covers may be loaded from external image hosts such as Discord’s CDN, YouTube or SoundCloud. The browser can transmit technical connection data, including its IP address, to the relevant image provider. Exact provider use depends on the displayed content.

5. External services and recipients

Discord provides the login service and bot infrastructure. Only if the relevant function is configured and used, the server may also contact Twitch, YouTube, GitHub or Gitea, RSS providers, Epic Games/GamerPower, Minecraft/Mojang, other game servers, Uptime Kuma, DeepL or APIs explicitly configured by a server administrator. Such requests can involve identifiers, queries, message excerpts, media URLs or the requested text, depending on the feature.

The application and database run on a server administered by the ControlBay operator and hosted by STRATO GmbH, Otto-Ostrowski-Straße 7, 10249 Berlin, Germany. STRATO provides the hosting infrastructure and may process technical connection data for hosting, operations and security. The operator has concluded a data processing agreement (DPA) under Article 28 GDPR with STRATO for the relevant STRATO customer relationship. The operator has confirmed that the ControlBay server is hosted under the same STRATO customer account covered by that DPA. The actual use of individual subprocessors and any international transfers still require a separate review.

Encrypted offsite backups are transmitted over a private connection to a separate self-hosted backup system. Any third-country transfers arising from Discord, external image hosts or enabled integrations and their safeguards must be assessed separately.

STRATO privacy information · STRATO data processing agreement

6. Retention and deletion periods

  • Login sessions: up to 7 days; OAuth login states: 10 minutes.
  • Server logging: adjustable from 1 to 365 days, with a default of 30 days. The actual duration depends on each server’s configuration.
  • Closed tickets and stored ticket logs: adjustable from 1 to 365 days after closure, default 30 days. Discord channel deletion has a separate timer (default 24 hours), and posted copies or exports may persist in Discord.
  • Moderation cases: adjustable from 30 to 3,650 days, default 365 days; warning validity is configured separately (default 90 days).
  • Daily XP counters: adjustable from 1 to 730 days, default 365 days; individual recorded XP reactions are cleared after approximately 30 days.
  • Panel change logs: up to 365 days; completed scheduled job history: about 7 days; data of a server removed from the bot: generally cleaned after approximately 30 days.
  • Local backups: generally about 14 days, but at least the latest three snapshots. Encrypted offsite backups retain 14 daily, 8 weekly and 6 monthly restore points. Therefore data deleted from the active database may remain temporarily in backups.

Additional stored records, exported transcripts and logs outside the application may have different or not yet fully documented retention rules. These require a separate operational check; the intervals above do not promise universal immediate deletion.

7. Data protection controls and requests

On a Discord server where ControlBay is installed, /privacy optout prevents further collection of supported XP/statistics, /privacy optin enables it again, and /privacy delete removes certain stored statistics, virtual economy, birthday, reminder and similar user records for that server and sets the XP opt-out flag.

Importantly, /privacy delete does not automatically remove all moderation cases, ticket messages, access logs, panel audit records or copies in Discord and backups. Please contact the operator above for a broader access, rectification or deletion request, stating the affected Discord server if possible.

8. Legal bases – still under assessment

For each processing purpose, the relevant legal basis under GDPR Article 6 must be determined and documented. This includes assessing whether processing is necessary for a service, whether legitimate interests apply, or whether a separate consent is required for optional functions. No blanket consent or universal legal basis is claimed here.

The use of automated spam protection or moderation features and any decisions with legal or similarly significant effects require a separate review; no automatic decision-making exemption is asserted.

Proposed purpose-based assessment (not yet legally approved)

  • Website operation, access logs, abuse prevention and backups: legitimate interests under Article 6(1)(f) GDPR may apply where the processing is necessary and a documented balancing test supports it.
  • Discord sign-in, panel permissions, settings and user-initiated commands: Article 6(1)(b) GDPR may apply where necessary for an agreed service; otherwise a separately assessed legitimate interest may be relevant. The contractual relationship and roles must first be clarified.
  • Server moderation, tickets, event logs and member statistics: the responsible entity, concrete necessity, information to members and any legitimate-interest balancing must be assessed by purpose. An administrator enabling a module does not by itself constitute every member’s GDPR consent.
  • Optional external integrations and forwarding texts or identifiers: legal basis, recipients and potential international transfers depend on the feature and must be clarified before activation. Where consent is required, it must be specific and withdrawable.

These are transparent review proposals, not a final declaration that every operation is lawful under the listed legal basis. The operator must confirm the actual allocation, any required balancing tests and transfer safeguards before replacing this draft with a final privacy notice.

9. Your rights

Where the statutory conditions apply, you may request access, rectification, erasure, restriction of processing, data portability or object to processing. Any consent given may be withdrawn for the future. You may lodge a complaint with a competent data protection supervisory authority. Requests are reviewed individually, including where other people’s rights or legal retention duties are affected.

Privacy requests can be made in German or English to the operator contact above. Please describe the affected Discord server and your request without sending passwords or access tokens. Under Article 12(3) GDPR, requests are generally answered within one month, subject to the applicable statutory conditions and extensions.

General Data Protection Regulation (GDPR) · Discord privacy policy

10. Items still requiring final approval

The actual legal bases and legitimate interests, other processors, international data transfers and safeguards, complete record-specific retention rules, any legally required data protection officer, and the responsibilities of individual Discord server owners still need review. The Discord Developer Portal already links to this privacy information, but that does not mean its legal contents have been approved.

ControlBay