> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://help.omegatheme.com/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# Consentik Wix: Data Requests in multiple languages

Show the privacy-request flow in the language your visitor is browsing in
## Overview
* If your store sells in more than one language, a visitor reads German pages and accepts a German cookie banner — but the moment they ask what data you hold about them, everything switches to the single language you typed into DSAR Setup.
* This feature fixes that. Every language you have configured in **Translations** gets its own copy of the Data Requests content, so the visitor stays in their language from the trigger link to the final reply.
* You don't have to write that content. Each language you add is pre-filled with a complete translation — 64 languages are covered, the same list the cookie banner uses. Edit only what you want to change.
* What stays the same for every language: your colors, popup position, trigger placements, and the notification email that comes to you.
> New to Data Requests? Read [**Data Subject Access Request (DSAR) Consentik Wix**](https://help.omegatheme.com/en/article/consentik-wix-data-request-13ypbms/) first — this article covers only the language layer on top of it.
![](https://storage.crisp.chat/users/helpdesk/website/-/8/3/8/3/8383e5404a31c000/image_1h0iss.png)

## What you need
* The **Advanced plan** (for Data Requests)
* **Multiple Language** enabled on your plan
* At least one language configured in **Translations**
Nothing extra to buy and nothing extra to switch on — when those are in place, the language selector appears in DSAR Setup.

## How it works for your visitor
* A visitor browsing your French pages gets the trigger link, the request-type cards, the form and the submitted screen in French. The request remembers the language it came in, so the verification email, the confirmation page and your final response email are all in French too.
* Your own notification email is not translated — it stays in your words, in one language.
* Arabic, Hebrew, Persian and Urdu display right-to-left, the same as the cookie banner.

## Setting it up
### 1 · Add your languages in Translations
Open **Translations** and add the languages your site speaks, with one set as the default. That is the only place languages are configured — Data Requests follows it automatically.
As soon as a language is added, its Data Requests content is filled in for you: trigger text, all five request types, every form label, the submitted screen, the confirmation page and both customer emails.
![](https://storage.crisp.chat/users/helpdesk/website/-/8/3/8/3/8383e5404a31c000/image_z5uz5l.png)

### 2 · Choose the language to edit
Go to **Data Requests → DSAR Setup**. The **Edit language** card at the top of the tab controls all three sub-tabs below it.
* Start typing to search; the list shows the languages you configured in Translations.
* Your default language carries a **Default** badge.
* Switching language swaps every field *and* the live preview at once.
With only one language configured there is no selector — just a note telling you which content you're editing and where to add more languages.
![](https://storage.crisp.chat/users/helpdesk/website/-/8/3/8/3/8383e5404a31c000/image_ruz6oo.png)


### 3 · Edit and save, one language at a time
Each language is saved on its own: editing French never changes German or English.
Two things to expect:
* **Save or discard before switching languages.** The selector is locked while you have unsaved changes, so nothing gets left half-finished.
* **On any language other than the default, shared settings are locked.** Colors, popup position, trigger placements, confirmation-page toggles, store name, back-URL and the notification email apply to all languages. They stay visible but greyed out — switch to your default language to change them.
![](https://storage.crisp.chat/users/helpdesk/website/-/8/3/8/3/8383e5404a31c000/image_1vtvaml.png)

### 4 · Send yourself a test
**Send test email** delivers the sample in the language you're currently editing, so you see exactly what you just wrote.
![](https://storage.crisp.chat/users/helpdesk/website/-/8/3/8/3/8383e5404a31c000/image_1xfoc8a.png)

## What is translated
| Translated into the visitor's language | Shared across all languages |
| ---- | ---- |
| Trigger link text | Colors |
| The five request-type cards | Popup position and trigger placements |
| Form labels, placeholders, checkbox, submit button | Confirmation-page toggles, store name, back-URL |
| Submitted screen | Processing checklists and internal notes |
| Verification email, including the confirm button | **New Request Notification** (the email to you) |
| Final response email |  |
| Confirmation page, all four states |  |

The popup's built-in messages — validation errors, *Copy*, *Done*, *Back* — are translated for you and aren't editable.
The notification email is intentionally left out: you are the one reading it, and translating it per visitor would fill your inbox with a different language every morning.

## Important notes
* **Removing a language deletes its content.** If you remove a language from Translations and add it back later, it starts fresh from the template and **your edits to that language are lost**. Copy your wording somewhere safe before removing a language you've customized.
* **Your default language and your original content are separate.** Your existing wording is carried over when you first turn languages on, so nothing disappears. After that they're independent: saving a translation never changes your original content, and vice versa.
* **Review the wording before you go live.** Translations are pre-written and automatically checked for correct placeholders and formatting, but they're generic. Read through the languages that matter most to your market and adjust anything that doesn't sound right — especially the emails.
* **If your plan loses Multiple Language.** The selector disappears and your site falls back to your original content right away. Your translations are kept, not deleted, and return if you upgrade again.
* **Not legal advice.** A translated flow helps you communicate, but deadlines and obligations still vary by country and by law. Confirm your setup with your own legal counsel.