Legal

go~mus and the AI Act

go~mus provides agent interfaces but contains no AI system of its own. We use AI exclusively in software development, without processing customer data. The transparency obligations under Article 50 of the AI Act therefore do not apply to go~mus.

Below is the reasoning behind those three sentences, so it can be checked rather than taken on trust. Our stance on AI, as opposed to the legal position, is on how we use AI.

What applies from 2 August 2026

Regulation (EU) 2024/1689, the AI Act, has been in force since 1 August 2024 and applies in stages. From 2 August 2026 the transparency obligations in Article 50 apply. They attach to providers and deployers of AI systems, specifically:

  • AI systems intended to interact directly with people have to make clear that a machine is answering (Article 50(1)), the classic case being a chatbot
  • synthetic audio, image, video or text has to be marked machine-readably as artificially generated (Article 50(2))
  • emotion recognition and biometric categorisation require the affected people to be informed (Article 50(3))
  • deep fakes, and AI-generated text published to inform the public on matters of public interest, have to be disclosed (Article 50(4))

Whether any of this applies depends on one question: is there an AI system involved. Article 3(1) defines it as a machine-based system that infers outputs such as predictions, content, recommendations or decisions. Inference is the criterion, not the fact that software is modern or that a machine talks to it.

Our roles, per system

The regulation assigns duties per role and per system, so we list them separately:

  • go~mus, the product: contains no AI system. Ticketing, quotas, pricing, bookings, access control and the shop run on rules that we write and that a person can read. They compute, they do not infer. We are therefore neither provider nor deployer of an AI system here.
  • Agent interfaces: the documented REST API, the machine-readable documentation, llms.txt and our WebMCP trial on gomus.de expose functions to agents. None of them is an AI system: they infer nothing and decide nothing. An agent calls the same function a person calls in the browser.
  • AI tools in our development: here we do use AI systems, and for those we are a deployer within the meaning of the regulation. They work on source code, documentation and test data, not on customer data, and they ship nothing without human review.
  • Agents belonging to an institution: if a museum points its own agent at our API, that agent is the museum's AI system and the museum is its deployer. We provide the interface and the data-processing agreement. We do not operate that agent and we make no claim to control it.

Article 50: not applicable, and why

go~mus contains no AI system, so it is not a system that would have to disclose itself under Article 50(1). It generates no synthetic content under Article 50(2). It performs no emotion recognition and no biometric categorisation under Article 50(3). It produces no deep fakes and no AI-generated public-interest text under Article 50(4). No obligation under Article 50 arises for go~mus.

Deliberately not a chatbot in front of the product: the decision that keeps go~mus outside Article 50(1) is a product decision, not a legal reading after the fact.

Article 4: AI literacy

This one does apply to us. Because we deploy AI systems in development, Article 4 requires us to ensure a sufficient level of AI literacy among the people who work with them. It has applied since 2 February 2025. Internal rules and technical limits govern that use: no production data in development environments, and every change reaches a release only through human review.

If this changes

Should we ever build an AI component into go~mus, the obligations change and so does this page, before the feature ships rather than after. That is the point of dating and versioning it.

Scope of this statement

This is our own assessment, not an external certification, and it is not legal advice. It covers go~mus and the interfaces we deliver. It says nothing about what customers build with their own tools on top of them.

Contact

For procurement, questionnaires and conformity questions: sales@giantmonkey.de. General enquiries: kontakt@giantmonkey.de. Data protection, and our data protection officer: datenschutz@giantmonkey.de.

Version 1.0, as of 30 July 2026

Version history

  • 1.0, 30 July 2026: first published, ahead of Article 50 becoming applicable on 2 August 2026.