01
Translate the player layer first
Prioritize limits, odds, help information, game explanations, and required disclosures—the content people need to act safely. Translate marketing pages only when the core experience can ship with them.
Languages
Translate the experience, not just the words.
Playbook RG is English-first today, with multilingual player resources in selected formats. We publish language coverage explicitly so teams can distinguish a translated asset from a fully maintained local experience.
Current coverage
What is available now.
AreaLanguagesStatusNotes
Website and framework
English
Source language
The navigation, product pages, evidence summaries, and implementation guidance are maintained in English.
Player website template
English, Japanese, Simplified Chinese, Arabic
Available
The Arabic template includes right-to-left layout support. Deployments should still receive native-speaker review.
Player collateral and myth feed
English, Japanese, Simplified Chinese, Arabic
Varies by item
Check the individual asset before deployment; translated variants should stay paired with the same source version.
Academy
English, French, Spanish, Japanese, Simplified Chinese
Course dependent
Language availability is listed by course. A translated title does not imply that every course asset is translated.
Jurisdiction modules
English
Reference layer
Modules document local requirements in English. Operators localize player-facing material during implementation and approval.
Translation standard
A language is ready when the experience is ready.
02
Treat localization as adaptation
Do not translate word for word. Preserve the meaning, reading level, tone, number and currency formats, examples, and local regulatory language.
03
Keep versions together
Every translated asset should name its source version, locale, review date, and reviewer. When the source changes materially, its translations return to review.
04
Require human review
Machine translation can support a draft, but a fluent reviewer should approve player-facing language. A local compliance reviewer should approve regulated statements and help information.
Why no global switcher yet?
Partial translation creates false confidence.
A language option in the main navigation signals that the whole service is available in that language. Adding one before the core pages, disclosures, forms, and support paths have matching coverage would make the site harder—not easier—to use.
The site-wide switcher should launch one locale at a time, after that locale has complete core navigation, essential product information, translated metadata, a tested fallback, and named owners for content and regulatory review.
Want to improve a translation or propose the next locale? Open an issue in the public Playbook repository or email info@gamblingpolicy.com.