Does Lokalise require consent on my website?

No consent is required for Lokalise's web translation service. Language preference storage is considered strictly necessary for maintaining the functional language setting the visitor has explicitly selected. Lokalise does not perform behavioral tracking or set advertising cookies.

What does Lokalise's script do on the page?

Lokalise's script scans the page DOM for translatable text, transmits text segments to Lokalise's translation API, and replaces content with translated versions in real time. The visitor's selected language is stored in a first-party cookie or localStorage entry to maintain the preference across page navigations.

How does ConsentStack handle Lokalise?

ConsentStack classifies Lokalise as functional and does not apply a consent gate to its translation scripts. Because language preference storage serves the visitor's explicit selection with no advertising or profiling component, it is treated as a necessary functional service.

What tracker domains does Lokalise use?

ConsentStack has catalogued tracker domains for Lokalise including lokalise.com. These are the network destinations Lokalise's scripts contact, which a consent platform blocks until a visitor agrees.

Lokalise - Translation & Localization Consent Info

Back to Vendor Library

Overview

Lokalise is a translation management system (TMS) that provides a live website translation feature enabling dynamic content localization. When detected on a website, Lokalise's scripts are powering real-time translation of page content, replacing visible text with translated versions based on the visitor's language preference. This allows websites to serve multilingual content without maintaining separate translated page versions or requiring a full page reload when switching languages.

What This Script Does

Lokalise's web translation scripts load from Lokalise's CDN and dynamically translate page content.

Scripts loaded: The Lokalise Live JS library loads from Lokalise's CDN, initializing the translation engine and language selector widget on the page
Translation flow: The script scans the page's DOM for translatable text content, sends text segments to Lokalise's translation API, and replaces the original text with translated versions in real time. Translations are cached after the first request.
Language selector: A language switcher widget is rendered on the page, allowing visitors to select their preferred language. The selected language is stored for persistence across page navigations.
Cookies set: First-party cookies or localStorage entries storing the visitor's selected language preference for consistent translation across page views
Data collected: The text content of the page is transmitted to Lokalise's servers for translation. Visitor language preference and page URL are stored. No personally identifiable browsing behavior is tracked.

Consent & Compliance

Lokalise falls under the functional consent category.

Under GDPR and ePrivacy, Lokalise's translation service serves a functional purpose — delivering content in the visitor's preferred language. Language preference cookies can be argued as strictly necessary for maintaining a functional language setting requested by the user. The page content transmitted for translation should not contain personal data in most cases, though dynamic pages displaying user-specific content would require data processing consideration under GDPR.

Under CCPA/CPRA, language preferences and page content transmitted for translation are minimal personal data processed for service delivery, not for advertising.

Should You Block This Without Consent?

No. Lokalise provides functional translation capabilities with minimal tracking impact. Language preference storage serves the user's explicit language selection. The service does not perform behavioral tracking or set advertising cookies. Blocking it would remove the multilingual capability from the website.

Is Lokalise GDPR compliant?

Lokalise typically loads functional trackers, which are not strictly necessary for your site to work. Under the GDPR and the ePrivacy Directive, non-essential cookies and trackers must stay blocked until a visitor gives clear opt-in consent. So Lokalise can be fully GDPR compliant, but only if your site holds its scripts until consent is granted and lets visitors decline just as easily. Compliance depends on how your site loads Lokalise, not on Lokalise itself.

Visit website