Does your website use third-party services? Get GDPR compliant in minutes.
Try FlowConsentFree plan · 10-min setup
GTranslate is a website translation tool, available as an app for WordPress, Shopify and other platforms, that adds a language switcher and translates content using Google Translate. The free widget loads Google scripts and sets a language cookie, sending page text and visitor data to Google servers in the United States. Paid plans translate server side. Under the GDPR and the ePrivacy Directive, loading the Google powered widget generally requires prior consent.
GTranslate is a website translation service offered as a plugin or app for platforms such as WordPress, Shopify, Wix and Joomla. It adds a language selector to a site and translates the content automatically, in its most common configuration using Google Translate. It is used by businesses that want a multilingual site without manually translating every page.
In its free, client side mode GTranslate loads the Google Translate library in the visitor browser. That library sends the text of the page being translated, together with the visitor IP address and browser information, to Google servers. GTranslate also sets a cookie named googtrans that stores the chosen language so the preference persists across pages and visits.
Because the free widget loads a Google script that processes page content and device data, it involves a third party that may act on personal data. Storing the language cookie is governed by Article 5(3) of the ePrivacy Directive; while a pure language preference can be functional, the Google integration that accompanies it generally requires consent. Paid server side plans change this analysis by keeping translation on GTranslate own infrastructure.
Get GDPR compliant in 10 minutes
Free plan available · No credit card required
For the Google powered widget, block the script and obtain consent before it loads, presenting the choice through a Consent Management Platform. If you use a server side plan where no third party script runs in the browser, the language cookie alone may qualify as strictly necessary or functional. Always document which mode you use and reflect it in your consent banner.
When GTranslate uses Google Translate, page text and visitor data are transferred to Google LLC in the United States, a transfer that must rely on Standard Contractual Clauses or the EU US Data Privacy Framework with a Transfer Impact Assessment. Paid GTranslate plans process translations on GTranslate servers, which the vendor locates in the European Union and the United States depending on the subscription.
Decide whether the free Google based widget or a server side plan best fits your privacy posture, then disclose the relevant cookies and recipients in your cookie policy. Gate the Google widget behind consent, document your transfer safeguards, and avoid sending pages that contain user entered personal data to the free translation service. Review the setup when GTranslate or Google change their integration.
Websites using GTranslate must obtain user consent under GDPR regulations.
DPIA considerations
GTranslate in its free, client side mode loads the Google Translate library, which receives the text of translated pages along with the visitor IP address and browser data. Key DPIA considerations: (1) page content and visitor data are processed by Google LLC in the United States; (2) the googtrans cookie stores the selected language and is read on each visit; (3) third party Google scripts may set additional identifiers; (4) paid server side plans keep translation on GTranslate infrastructure, reducing exposure to Google. A DPIA is advisable where translated pages may contain personal data entered by users.
Sample consent text
We use GTranslate to offer our site in your language. In its free mode GTranslate relies on Google Translate, which processes the page text and your device data on Google servers in the United States and sets a language cookie. You can withdraw your consent at any time through our cookie settings.
Third-party domains contacted
gtranslate.netcdn.gtranslate.nettranslate.google.comtranslate.googleapis.comCookies placed
| Name | Type | Duration | Purpose |
|---|---|---|---|
| googtrans | Functional | Session | Stores the language selected by the visitor so translated pages are shown consistently. |
| gt_language | Functional | 1 year | Remembers the preferred language across visits on GTranslate paid plans. |
| NID | Advertising / Functional | 6 months | Google cookie that may be set by the embedded Google Translate service to store preferences and security information. |
GTranslate uses cookies for user preferences — inform visitors with a consent banner.
GTranslate sets a cookie named googtrans that stores the visitor selected language so the choice persists. In its free mode it also causes Google Translate scripts to run, which can read device data. The language cookie may be functional, but the Google integration generally calls for consent.
For the free, Google powered widget, yes. It loads a third party Google script that processes page content and device data, so under the GDPR and the ePrivacy Directive you should obtain consent before it runs. A server side plan that uses only a language cookie may not need consent for that cookie alone.
A strictly functional language preference cookie can rely on the user request or legitimate interest, but the Google Translate integration that processes personal data needs consent under Article 6(1)(a) GDPR together with Article 5(3) ePrivacy for any non essential storage. Choose the basis according to the mode you deploy.
Yes in free mode. Google Translate processes the page text and visitor data on Google servers in the United States, so transfers must be covered by Standard Contractual Clauses or the EU US Data Privacy Framework with a Transfer Impact Assessment. Paid server side plans keep translation on GTranslate infrastructure.
A DPIA is advisable when the translated pages can contain personal data that users enter, such as account or form pages, because that data would be sent to the translation service. For a simple marketing site translated in free mode, a lighter assessment of the Google transfer is usually sufficient.
If you need maximum privacy, use a GTranslate server side plan so no Google script runs in the browser. Otherwise load the free widget through a CMP that blocks it until consent, disclose the googtrans cookie and Google as a recipient, and document your transfer safeguards. Test that the switcher still works after consent.
Alternatives include Weglot, ConveyThis, TranslatePress and Lokalise, some of which offer server side or human translation that avoids a browser side Google script. A fully manual or server side translation reduces third party exposure, while any Google based machine translation carries the same transfer considerations.
Note in your cookie policy that GTranslate sets the googtrans language cookie and, in free mode, that page content is sent to Google Translate in the United States. List the GTranslate and Google domains involved and keep the entry consistent with whether you run the free or server side plan.