Google Translate (Website Translator)
How to configure Google Translate (Website Translator) at different risk levels and map it in the Consenter Manager.
This work is licensed under CC BY-SA 4.0
Typical processing purposes: Unlock additional website features
Overview
This guide explains the status of the Google Translate Website Translator widget and how to reflect any remaining use in the Consenter Manager.
At a glance
Service status — retired. Google stopped issuing the Website Translator widget to new websites in 2019. Google has since announced that the widget is no longer supported from 1 October 2026 and points site owners to the Cloud Translation API. No configuration guide is provided for a retired product.
What to do.
- Search your templates and plug-ins for
translate.google.com/translate_a/element.js,google_translate_elementorgoogleTranslateElementInitand remove the widget. - If the site needs machine translation, assess the replacement (for example, a server-side integration of the Cloud Translation API, or a translation plug-in) as a separate recipient.
- Remove the Google Translate entry from the Consenter Manager once the widget is removed.
If the widget is still embedded. Until removal, load it only after consent and map it as follows.
| Consenter Manager field | Value to select | Basis and conditions |
|---|---|---|
| Processing purposes | Unlock additional website features | On-page translation. |
| Tracking method | No tracking | Not documented; re-assess if browser inspection shows cookies on Google domains. |
| Identifier | IP address | Transmitted with each request. |
| Data categories | IP address, Device characteristics, Browsing and interaction data | Page content is sent for translation. |
| Legal role of data recipient | Individual Controller | No processor terms exist for the free widget. |
| Personalisation model | No personalisation | — |
| Maximum storage duration | Not documented | — |
| Processing location | United States as potential processing and access location | Google LLC is subject to the US CLOUD Act. |
How is this guide?
Shape Consenter Together
Consenter is built on an open and participatory process that grows through community collaboration. Whether you share feedback, improve the documentation, or contribute to the Risk Configuration Guides or Technical Integration Guides, your expertise helps make Consenter more privacy-friendly, interoperable, and useful for everyone—including your own users and services: Get finally your benefits and control the risks when sharing personal data.
Need Help?
Last updated on