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

Terms of use

Status: 21 November 2026

This is an English translation provided for convenience. In case of discrepancies, the German version prevails (§ 13(4)).

§ 1 Provider, scope

(1) The provider of ControlBay is Ioannis Antoniadis, c/o Impressumservice Dein-Impressum, Stettiner Str. 41, 35410 Hungen, Germany, email: kontakt@ioannisdev.de (hereinafter "I" or the "Operator").

(2) These terms apply to the use of the Discord bot ControlBay and the web panel at controlbay.me (together "ControlBay") by server teams and other users of the panel (together "Users"). "Server team" means the owners and administrators of a Discord server and the persons they authorise who use ControlBay on that server.

(3) Members of a Discord server who merely interact with the bot, without adding it or using the panel, do not enter into a contract with me. The Privacy Policy applies to them.

§ 2 Description of the service

(1) ControlBay is a Discord bot with a web panel for managing server modules, permissions, messages, moderation and optional additional services (for example welcome messages, role assignment, tickets, logs, XP systems, games, giveaways, votes, game-server status and integrations of external services). Which modules are available may change.

(2) The server team sets up the features for each server itself. The server team determines which modules are active and which data is processed as a result.

(3) ControlBay is provided free of charge and in line with the current state of the art. I endeavour to ensure trouble-free operation but do not owe any particular availability. Individual features may be temporarily unavailable, for example due to maintenance or disruptions at the hosting provider, at Discord or at integrated services. There is no entitlement to support or to particular response times.

§ 3 Conclusion of contract and start of use

(1) By adding the bot to a Discord server, or by logging in to the panel for the first time after the User has agreed to these terms by ticking the box provided, a free-of-charge contract for the use of ControlBay is concluded between me and the User. The User thereby confirms having read these terms and having taken note of the Privacy Policy. The mere public availability of this page does not create a contract.

(2) The panel is intended for adults or for minors acting with the consent of their legal representatives. Discord's age limits and rules of use remain unaffected.

(3) Anyone who sets up ControlBay for a server warrants that they are authorised to do so on that server.

§ 4 Access and permissions

(1) A Discord account is required for the panel. Users may only manage servers and features for which they are authorised on Discord or by the server team.

(2) The owner of a server always has all rights for that server in the panel. The owner and the persons the owner authorises for this purpose determine who may use and configure which modules in the panel. The server team is responsible for these assignments.

(3) Access credentials, sessions and bot tokens must not be passed on to third parties. Any suspicion of unauthorised access must be reported to me without delay.

§ 5 User obligations, prohibited use

(1) Users must comply with applicable law, the rights of third parties, and Discord's terms of service and community guidelines.

(2) In particular, it is prohibited to

  1. use ControlBay for spam, harassment, fraud, the distribution of unlawful content, or to circumvent measures taken by Discord or other server teams,
  2. circumvent ControlBay's protective measures, exploit security vulnerabilities, or burden the service with excessive or automated access outside the intended features,
  3. gain unauthorised access to the data or servers of others,
  4. use features in a way that monitors or deceives members contrary to applicable law.

(3) Support requests must not contain passwords or bot tokens.

§ 6 Responsibility of server teams, data protection

(1) The server team is responsible for the content it distributes or stores through ControlBay and for the integrations it activates. This also applies to embedded links, images and texts.

(2) Where the server team processes personal data of members with ControlBay, it is the controller under data protection law. In particular, it must

  1. have a legal basis for the features it activates,
  2. inform its members appropriately (for example in the server rules), in particular about logging, moderation files, tickets and XP systems,
  3. activate only the modules, and set retention periods only as far, as necessary for its purposes,
  4. answer members' requests about their data.

(3) I process this data as a processor under the agreement in Annex 1, which becomes part of the contract upon its conclusion under § 3. My own processing is governed by the Privacy Policy.

§ 7 Prices

(1) Use of ControlBay is currently free of charge. Prices, premium entitlements and a payment system are not activated. No subscription is required.

(2) Should I introduce paid offers ("Pro") in the future, they will be presented separately in advance with prices, scope of services, payment method and term, and will only take effect after a separate, express booking decision by the User. Existing free use will not automatically become chargeable.

§ 8 Changes to and discontinuation of the service

(1) I may further develop, change or remove features insofar as this is reasonable for Users.

(2) I may discontinue the service as a whole with at least 30 days' notice. Notice is given in the panel and on controlbay.me. The right to extraordinary termination under § 10 remains unaffected.

§ 9 Suspension

In the event of breaches of § 5, I may restrict features and suspend individual Users' access or a server's use. In doing so I take into account the seriousness of the breach and the User's legitimate interests and, where possible, announce the suspension beforehand. Where there is imminent danger, for example attacks on the security of the service or unlawful abuse, immediate suspension is permitted.

§ 10 Term, termination, consequences of termination

(1) The contract runs for an indefinite period.

(2) The User can end it at any time by removing the bot from the server and no longer using the panel. Notice by email is not required.

(3) I can terminate the contract with 30 days' notice in text form (for example in the panel or by Discord message). Either party's right to terminate for good cause remains unaffected.

(4) Removing the bot ends use on the server. At the server team's request (email to kontakt@ioannisdev.de), I will delete the server's data without undue delay and at the latest within 30 days. Without such a request, I will delete it at the latest 90 days after the bot is removed. Copies in backups are overwritten as they rotate (at the latest after 90 days); copies at Discord are not covered by deletion. Statutory retention obligations remain unaffected.

§ 11 Liability

(1) I am liable without limitation for intent and gross negligence, for injury to life, body or health, for fraudulently concealed defects, for guarantees given, and under the German Product Liability Act.

(2) In cases of slight negligence, I am liable only for breach of essential contractual obligations (obligations whose fulfilment is what makes proper performance of the contract possible in the first place and on whose observance the User may regularly rely) and limited to the foreseeable damage typical for this type of contract. Otherwise, liability for slight negligence is excluded.

(3) Liability under Art. 82 GDPR and mandatory statutory consumer rights remain unaffected. I do not promise uninterrupted availability of ControlBay (§ 2(3)).

(4) I am not liable for content, settings and decisions of server teams, for the actions of members on Discord servers, or for services provided by Discord and other third parties, unless I am at fault myself.

§ 12 Changes to these terms

I may change these terms if the service, the law or case law changes, or if gaps in the provisions have to be closed, and insofar as this is reasonable for Users. I will announce material changes at least 30 days before they take effect, in the panel and on controlbay.me, and will point out the consequences. The User may end use under § 10(2) before the period expires. If the User continues to use ControlBay after the period has expired, the amended terms apply for the future. Changes that shift the core of the service to Users' disadvantage require their express consent.

§ 13 Final provisions

(1) German law applies, excluding the UN Convention on Contracts for the International Sale of Goods. For consumers habitually resident in another state, mandatory consumer protection provisions of that state remain unaffected.

(2) For consumers, the statutory places of jurisdiction apply. Against merchants, legal entities under public law and special funds under public law, the place of jurisdiction is the Operator's location stated in the Legal Notice.

(3) If individual provisions are invalid, the validity of the remaining provisions is not affected.

(4) These terms are also available in English. In case of discrepancies, the German version prevails.

More information: Legal Notice · Privacy Policy


Annex 1 – Data Processing Agreement under Article 28 GDPR

This Annex governs the processing of personal data by me ("Processor") on behalf of the server team ("Controller"), insofar as the server team uses ControlBay to process personal data of members of its Discord server. Under § 6(3) it becomes part of the contract of use upon its conclusion and is concluded in text form under Art. 28(9) GDPR.

1. Subject matter and duration. The subject matter is the operation of the ControlBay features activated by the Controller. The duration corresponds to the term of the contract of use (§ 10).

2. Nature and purpose of processing. Collecting, storing, retrieving, displaying in the panel, linking, backing up and deleting data in order to provide the features set up by the Controller (§ 2(1)) on its server.

3. Type of data and categories of data subjects. Data: Discord identifiers and display names, server settings, moderation cases, tickets and transcripts, event logs, logs of changes made in the panel, XP, level, message and voice-time counters, game, giveaway and voting data; message content only insofar as it arises in tickets, moderation evidence or activated logging features. Data subjects: members of the Discord server, panel users of the server, and persons who interact with the bot on the server.

4. Instructions. I process the data only on the Controller's documented instructions. Instructions are this Annex and the settings made in the panel; the Controller gives supplementary instructions by email. I will inform the Controller without delay if I consider an instruction to be unlawful; I may suspend carrying it out until the matter is clarified. I process the data beyond this only where I am required to do so by Union or Member State law, and will inform the Controller of this in advance unless that law prohibits it. For my own purposes (security, abuse prevention, enforcement of the Terms of Use) I am a controller myself (see Privacy Policy, Section 3.7).

5. Confidentiality. I am the sole operator and undertake to maintain confidentiality. Only persons whom I expressly authorise and bind to confidentiality have access to the data.

6. Technical and organisational measures (Art. 32 GDPR).

  • Encrypted transmission between browser and panel (TLS).
  • Login via Discord, permission checks per server, separation of data by server ID.
  • Session identifiers are stored only as hashes; I never receive Discord passwords.
  • Access to production systems and databases is restricted to me and persons whom I expressly authorise.
  • Automatic security updates of the operating system; the application and container images are updated when security vulnerabilities become known.
  • Logging of changes made in the panel (for example to configuration, group permissions and warnings); access logs rotate (Privacy Policy, Section 5).
  • Encrypted external backups on a separate system, local backups with short rotation.

I will further develop the measures in line with the state of the art without falling below the agreed level of protection.

7. Sub-processors. The Controller consents to the use of STRATO GmbH, Otto-Ostrowski-Straße 7, 10249 Berlin, Germany (hosting). A contract imposing the same data protection obligations is in place with it. I will use further or other sub-processors only if I announce this at least 14 days in advance in the panel or on controlbay.me. The Controller may object for good cause; if it objects and no solution is possible, it may end the contract under § 10(2). Third-party integrations activated by the Controller (for example Twitch, YouTube, GitHub, DeepL) are not my sub-processors; the Controller decides on their use under its own responsibility.

8. Assistance. I assist the Controller with appropriate technical and organisational measures in responding to data subjects' requests (Arts. 12 to 22 GDPR) and in meeting its obligations under Arts. 32 to 36 GDPR. If a data subject contacts me directly and the Controller is identifiable, I will forward the request.

9. Personal data breaches. I will notify the Controller without undue delay by email or panel message of any personal data breach that comes to my knowledge and, as far as known, state its nature and scope, possible consequences and the measures taken.

10. Deletion and return. After the contract of use ends, I delete the data in accordance with § 10(4). On request, I will first make the data of its server available to the Controller in a commonly used, machine-readable format, insofar as this is possible without disproportionate effort.

11. Evidence and audits. On request, I will provide the Controller with the information necessary to demonstrate compliance with this Annex and will allow audits, including inspections, conducted by the Controller or an auditor mandated by it. Audits must be announced with reasonable notice and must not disrupt operations disproportionately.

12. Responsibility of the Controller. The Controller is responsible for the lawfulness of its instructions and of the processing it activates (§ 6(2)).

13. Liability. Art. 82 GDPR applies to liability; § 11 applies between the parties.

ControlBay