Translation plugin data paths
Where WordPress translation plugins send your page content
Some translation plugins keep translations on your WordPress host. Others send page text to an outside translation service so visitors can read another language. This table summarizes the documented setups below. Your settings can change where text goes.
Based on plugin documentation, not tests of your site. Your settings can change what loads. This is not legal advice or a compliance rating.
Scan your siteHow we group translation plugins
We compare the translation setups named below. A plugin can store translations on your server and still send text to an outside service. Some features must be enabled in plugin settings. We have not tested when requests start relative to cookie consent or assessed how long data is kept.
Translation plugins
No paid placement. On your server first, then outside translation services, then plugins not yet reviewed. Names are alphabetical within each group.
| Plugin | Documented behavior | Receiving domains | How long data is kept | Before consent | Links | Source |
|---|---|---|---|---|---|---|
| Loco Translate Documented default edits translation files on the WordPress host. Optional third-party translation APIs are settings features, not the default path reviewed here. | On your server | None in the documented default path. | Not assessed | Not tested |
| |
| Polylang Documented default stores language assignments and translated posts in the WordPress database. No cloud machine-translation endpoint in that path. | On your server | None in the documented default path. | Not assessed | Not tested |
| |
| GTranslate GTranslate docs describe cloud machine translation for translated pages. The linked listing does not name a verified content-receiving endpoint. | Outside translation service | Endpoint not verified | Not assessed | Not tested |
| |
| TranslatePress (Google/DeepL enabled) With Google Translate or DeepL enabled, page text is sent to the selected service and translations are stored in your WordPress database. Manual-only translation and TranslatePress AI are outside this row's scope. | Outside translation service | translation.googleapis.com, api-free.deepl.com, api.deepl.com | Not assessed | Not tested |
| |
| Weglot Weglot API docs: page strings are sent to api.weglot.com for translation. Translations are also stored on Weglot servers per the WordPress plugin listing. | Outside translation service | api.weglot.com | Not assessed | Not tested |
| |
| WPML (automatic translation) This row covers WPML automatic translation (PTC, DeepL, Google, or Microsoft). The linked guide does not name a verified content-receiving endpoint. Manual translation-only setups are not covered here. | Outside translation service | Endpoint not verified | Not assessed | Not tested |
|
What this table does and does not prove
This table describes the named translation setups. It does not show what loads on your site. Local storage and outside processing can both apply. We have not tested consent timing, and we have not assessed how long data is kept.
Documentation snapshot: Sep 28, 2026. Sources are linked in each reviewed row.
Scan your site/wp-translation-plugin-privacy