Skip to content
English
MineOS Platform
  • There are no suggestions because the search field is empty.

Languages & Translations in the Privacy Center

When setting up your Privacy Center in multiple languages, it's important to understand which fields have pre-defined translations, which require manual translation, and how translations work across different components.

Enabling Languages

Before you can translate content in your Privacy Center, you need to enable the languages you want to support.

To enable languages across the portal:

  1. Navigate to DSR setup → Languages
  2. Select and enable the languages you want to make available throughout the MineOS portal

Image 04-02-2026 at 14.51

To enable languages specifically in the Privacy Center:

  1. Navigate to Privacy Center → Form details & languages
  2. Scroll to the "Supported languages" section
  3. Toggle on/off the languages you want to support in your Privacy Center

Languages enabled in the Privacy Center must first be enabled in the DSR setup Languages section.

Image 04-02-2026 at 14.50

Defining translations

Navigate to DSR -> Privacy Center -> Form details & languages to define translations to the following fields in the article.

Image 04-02-2026 at 14.41

Title Field

Translation requirement: Mandatory manual translation

The title field must be manually translated for each language enabled in your Privacy Center. There are no pre-defined translations for this field.

To translate:

  1. Select the language from the dropdown at the top of the Form details section
  2. Enter the translated title for that language
  3. Repeat for each language you've enabled
  4. Click "Save changes" button on the top-left side of the page

Description Field

Translation requirement: Partial pre-defined translations available (editable)

The description field has pre-defined translations for select languages (contact support to confirm which languages are included). These translations can be edited to match your specific messaging.

Important notes:

  • Editing the description in one language does not affect other languages
  • If you want custom messaging, you must translate it manually for all enabled languages
  • If no pre-defined translation exists for a language, the field will display in English using the default English translation

To customize:

  1. Select the language from the dropdown at the top of the Form details section
  2. Modify the pre-defined text or add your own translation in the Description field
  3. Repeat for each language where you want custom messaging
  4. Click "Save changes" button on the top-left side of the page

Required Fields

Translation requirement: Pre-defined translations (not editable)

Required fields (such as First name, Last name, Email, Country, State, Address, Mobile number, URL) have pre-defined translations that cannot be edited.

Important limitation: When MineOS customers (you and your team) view the Privacy Center through the MineOS portal, field names will always display in English. However, when data subjects (end-users) fill out the form on your public Privacy Center, they will see field names in their selected language if pre-defined translations are available for that language. If no pre-defined translation exists, data subjects will see the field names in English.

Data Subject Type

Translation requirement: Mandatory manual translation

The "Data subject type" field is optional but recommended for identifying the relationship between the requester and your company.

To translate:

  1. Select the language from the dropdown at the top of the Form details section
  2. Manually enter the translation for the data subject type question and options
  3. Repeat for each enabled language
  4. Click "Save changes" button on the top-left side of the page

If not translated, this field will display in English.

Custom Questions

Translation requirement: Complete manual setup per language

Custom questions must be configured separately for each language. When you add a custom question in one language, it does not automatically carry over to other languages.

What needs to be set per language:

  • The question text
  • The question type (Open question, Single choice, or Multiple choice)
  • All answer options (for choice-based questions)

To add custom questions for each language:

  1. Select the language from the dropdown at the top of the Form details section
  2. Scroll to the "Add custom question" section
  3. Define the question type (Open question, Single choice, or Multiple choice)
  4. Enter the question text in the selected language
  5. If using Single or Multiple choice, add all answer options in the selected language
  6. Repeat steps 1-5 for each enabled language
  7. Click "Save changes" button on the top-left side of the page

Important: If a custom question is not defined for a specific language, it will not appear on the form when users select that language.

Country Selection Dropdown

Translation status: Always displayed in English

The country selection dropdown in the Privacy Center always displays in English, regardless of which language is selected. This is a system limitation and cannot be customized.

Privacy Rights Names

Translation location: DSR Setup (not Privacy Center setup)

To translate the names of privacy rights (such as "Delete my data," "Access my data," etc.):

  1. Navigate to the DSR setup section
  2. Select the specific right you want to translate
  3. Go to the General tab in the sidebar menu
  4. Scroll down to the "Appearance & translations" section
  5. Change the language using the dropdown
  6. Enter the translation for that language
  7. Click "Update" to save
  8. Repeat steps 2-7 for each right you want to translate

Translation availability:

  • Some rights have pre-defined translations that you can edit
  • Some rights do not have pre-defined translations
  • If no pre-defined translation exists, the right name will display in English
  • You can identify whether a pre-defined translation exists by switching languages in the "Appearance & translations" section—if text appears in that language, a pre-defined translation is available

Image 04-02-2026 at 14.37

Best Practices for Multi-Language Privacy Centers

  1. Plan your languages: Enable only the languages you can fully support with translations
  2. Test each language: Preview your Privacy Center in each enabled language to ensure all content displays correctly
  3. Document custom translations: Keep a record of your custom translations for Title, Description, Data subject type, and Custom questions
  4. Regular reviews: Periodically review your translations to ensure they remain accurate and aligned with your privacy policy
  5. Coordinate Rights translations: Remember to translate rights names in the DSR setup section, not in the Privacy Center configuration