Localisation

Localisation in DataGuard CPM allows you to tailor all Citizen-facing text to meet the specific language and locale requirements of your audience. This feature ensures that your consent collection and preference management processes are accessible and understandable to users in any region.

Localising Citizen-Facing Text

• Complete Localisation: All Citizen-facing text within DataGuard CPM can be localised to suit your needs. This includes every aspect of a template, giving you full control and flexibility to display text in any language or locale required.

• Template Localisation: Every element of a template can be localised, including the main text, labels, and instructions. This ensures that users interact with content that is clear and relevant to their language and cultural context.

• Template Child Objects: In addition to templates, supporting template objects such as rules, permission statements, and preferences can also be fully localised. DataGuard CPM enforces rules around localisation, ensuring that all sub-objects maintain consistent translations with the main template, providing a seamless experience for users.

• Manual Translation: It’s important to note that you must perform the translation of all these elements yourself. DataGuard CPM provides the framework for localisation but relies on your organisation to supply the translated content.

Localisation for Privacy Policies

• Privacy Policy Options: To support localisation of your Privacy Policies, you have two options:

  • Separate Policies: Create a different Privacy Policy for each language or translation required.

  • Combined Translations: Alternatively, you can add all translations to the same Privacy Policy file, depending on your organisational needs.

Using a Localised Template in the Widget

When using a localised template in a widget, you need to specify the locale in the widget configuration to ensure the correct language and region are displayed to the user. Here's how to do it:

• Widget Configuration: The locale is set in the widget configuration by including the locale parameter. For example:

StatefulWidget.load({
  …
  locale: 'en-UK',
  …
});

• Locale Code: The locale code must be provided by your website. The code can be determined based on the language shown in the CPM UI. You should convert the language and country text into a locale code. For instance:

  • English (United Kingdom) becomes en-UK

  • German (Switzerland) becomes de-CH

• Fallback to Default: If the specified locale is not available in the template, the widget will default to the template's default translation.

Summary

Localisation in DataGuard CPM empowers you to customise all aspects of your Citizen-facing content, ensuring that your communications are accessible and relevant to users in any language or locale. With full support for localising templates, supporting objects, and Privacy Policies, you can provide a consistent and culturally appropriate experience for your global audience.