Localization Workflow

Last updated: October 4, 2026

CYBEXO supports multilingual banner deployments across regions. The direct Web product contains 60 UI catalogs, including supplemental consent disclosures and control labels. Catalog coverage does not establish 60 official TCF translations or completed linguistic qualification.

1. Configuration Flow

Set default language in dashboard.
Enable additional supported languages.
Publish configuration.
Verify the language actually delivered in both banner layers, including the TCF fallback below.

2. Fallback Rules

Language selection depends on the published property configuration and available content. Verify visitor-language and configured-default behavior on the actual installation.

For the direct Web TCF interface, the delivered official Global Vendor List language controls the primary UI language in both layers. If official text falls back to English, the TCF banner and preferences also use English, even when a product UI catalog exists for the requested language. For example, an Afrikaans request with an English GVL fallback presents the TCF interface in English and records ConsentLanguage=EN. An available German GVL presents the interface in German and records DE.

Official IAB text retains its delivered language metadata; product translations do not replace that text. The TC String records the language actually presented, not a language merely requested in configuration. Do not describe a catalog entry as a fully localized TCF experience without checking the delivered interface.

3. Translation Governance

define owner for legal copy translations
review translations with privacy/legal team
version-control translation changes with release notes

Native-speaker review of the expanded supplemental catalog is pending. Automated key, script and layout checks do not establish translation accuracy, legal approval, IAB approval or Google certification. We recommend appropriate human review for the languages you intend to deploy; this is a quality-control recommendation, not a claim that IAB or Google requires a separately named external linguist to sign each release. Official disclosure content and the language actually presented must still be correct.

4. RTL and QA

validate right-to-left layouts where supported
test long-string overflow and mobile wrapping