Article 50 doesn't contain a language list. There is no "official language of the Member State" clause of the kind other EU rules have. What it requires is that people are informed, and the draft guidelines' whole approach judges disclosures by what a reasonably well-informed member of your actual audience would actually take in. A notice your user can't read informs nobody.
The practical rule that falls out: deliver the disclosure in every language your interface serves. If your product ships in German and French, an English-only "AI assistant" line is a gap in both. You've already told the Act, by localising, who your audience is. If your bot answers users in their own language, the disclosure should arrive in that language too; a bot that speaks fluent Italian but discloses only in English is hard to defend.
For the visible content labels under Article 50(4), the June 2026 Code of Practice eases the multilingual problem deliberately: the harmonised label is designed as a compact convention. "AI", with "KI" for German and "IA" for French and other Romance-language markets, is an icon in a fixed position rather than a paragraph needing translation. For spoken disclaimers on audio and video, use the language of the content itself.
Two audience notes from the same test: vulnerable groups count (simplify wording where children or low-literacy users are foreseeable), and accessibility is part of comprehension. A screen-reader-accessible label, not a colour cue.
Verified disclosure wording in English, German, and French (badge, first message, and voice opening) is what the free generator produces. For other languages, translate the same short patterns and have a native speaker check that the "you are dealing with AI, not a human" meaning survived.
Not sure how this applies to your specific setup? The free 2-minute check tells you which of the four Article 50 duty areas likely apply to your company. No email required.
Take the free check Generate disclosure text