Why every Disclos disclosure ships in 24 EU languages (and how our reviewers verify each one)
Article 50 of Regulation (EU) 2024/1689 does not specify a language. It specifies plain language, clear and distinguishable, accessible to vulnerable persons. The practice's read on that requirement is unambiguous: a disclosure shipped only in English will not satisfy plain-language obligations for a customer whose product is used in Athens, Lisbon, Riga, or Sofia. This piece explains how the practice handles the translation problem and why every audit ships disclosure code in all 24 EU official languages.
What Article 50 says about language
The relevant clauses are spread across Article 50 and Recital 132.
Article 50(1): "Providers shall ensure that natural persons are informed that they are interacting with an AI system." No language specified.
Recital 132: "The information shall be provided in a clear and distinguishable manner at the latest at the time of the first interaction... taking into account the specificities of vulnerable persons." Strong implication that 'clear and distinguishable' means clear in the language the user actually reads.
Charter of Fundamental Rights, Article 21: non-discrimination on grounds of language. Strong implication that an English-only disclosure to a Greek-speaking user is not 'clear' in the way the Act requires.
Our policy reviewers' working interpretation: a disclosure must be in the language of the surface the user is using. If your SaaS UI localises to Greek, the disclosure must localise too.
The 24 official languages the practice covers
Bulgarian (bg), Croatian (hr), Czech (cs), Danish (da), Dutch (nl), English (en), Estonian (et), Finnish (fi), French (fr), German (de), Greek (el), Hungarian (hu), Irish (ga), Italian (it), Latvian (lv), Lithuanian (lt), Maltese (mt), Polish (pl), Portuguese (pt), Romanian (ro), Slovak (sk), Slovenian (sl), Spanish (es), Swedish (sv).
Every disclosure snippet our practice delivers — chat banner, AI-content watermark, deepfake label, biometric notice, emotion-recognition notice, AI text byline, product-wide AI policy — ships with all 24 language strings already loaded.
How our reviewers verify each translation
The practice does not use machine translation as a final output. Every language string passes through a three-stage review.
Stage 1: reference translation. A baseline translation is produced from the verified-native English source. For five languages (English, French, German, Spanish, Italian), the lead reviewer's working knowledge is sufficient. For the remaining 19, a native-speaker reviewer in the practice's network produces the reference.
Stage 2: plain-language audit. The reviewer reads each string aloud and confirms it would be understood by a person without legal training. Recital 132's vulnerable-persons standard is the bar. If a string reads as legalese in the target language, it is rewritten.
Stage 3: change-control sign-off. The verified string is recorded in the practice's translations registry with the reviewer's review status (verified-native vs verified-translator). The registry ships with every deliverable so customers know which strings carry which level of review.
Why this matters for procurement and enterprise sales
Enterprise procurement teams across the EU are starting to ask for evidence of language coverage as part of AI procurement diligence. The practice has seen this from buyers in the Nordics, the DACH region, and France.
A SaaS that responds "we'll add other languages when we get traction in those markets" is at a clear disadvantage against a SaaS that responds "every AI disclosure in our product is already verified in 24 EU languages — here is the registry, here is the per-language reviewer status."
Our deliverables include the language registry by design. Customers can attach it to procurement responses, RFP answers, and security questionnaires without modification.
What the customer gets
The customer's bundle in folder 03-Code-Snippets/translations/ contains a single JSON file with all 24 languages. Each disclosure key maps to all 24 translations. The customer's engineering team imports the file and switches language by passing the lang prop to the snippet components.
``js <ChatDisclosureBanner lang="fr" variant="full" /> <ChatDisclosureBanner lang="de" variant="full" /> <ChatDisclosureBanner lang="el" variant="full" /> ``
The customer's frontend already knows which language the user is on. The disclosure follows.
The registry's metadata block records the review status per language so the customer can demonstrate, when a procurement team asks, exactly which translations are verified-native vs verified-translator.
Frequently asked questions
Do you support languages outside the 24 EU official?
Not as part of the standard audit. If a customer needs Norwegian (Bokmål or Nynorsk), Icelandic, Ukrainian, or Russian disclosures because of their specific user base, the lead reviewer arranges the work as a separate engagement with the practice's translation reviewers. The audit fee remains €997; non-EU-official language work is quoted separately.
How do you handle Maltese and Irish — small native-speaker populations?
Both Maltese and Irish are EU official languages and both ship in every standard deliverable. Reviewers in those languages are in the practice's network. Coverage is the same as for the larger languages.
What about regional variants — Belgian French vs France French?
The standard delivery uses the dominant variant of each official language (France French, Castilian Spanish, mainland Portuguese, etc.). If a customer's user base is concentrated in a specific variant, the lead reviewer flags it in the intake and the native reviewer adjusts. Costs the same.
Can the customer ship in fewer languages to save effort?
The customer can ship in any subset they want — the snippet's lang prop is a runtime choice. Our recommendation is to ship in every language the customer's UI already localises to, which removes the burden from the customer's frontend team while satisfying Article 50.
Does the practice keep translations updated?
Yes. When the EU AI Office publishes guidance, when the Act is amended, or when an upstream model provider changes its Article 53 disclosures in a way that affects our wording, the registry is updated and the new version is pushed to customers under the 30-day check-in window or, after that, as part of the €497 re-audit.
Sources
Last updated: 2026-05-30