Is DeepL: translate and write with AI safe?

Medium risk

DeepL is medium risk.

DeepL attaches a persistent installation ID and browser fingerprint to every analytics event it sends to its servers.

Each time the user interacts with the extension, a base analytics payload is assembled containing an installationId (a UUID stored in chrome.storage.sync that survives reinstalls), a sessionId, browserInstanceId, browser name, version, platform, language, and userAgent string. When the user is signed in, accountId and organizationId are added. A dapUid cookie read from deepl.com is included as webInstanceId, linking extension events to the user's DeepL website activity. All of this is transmitted to s.deepl.com/chrome/statistics with each analytics call.

team-browser-extensionsv1.108.0Extension ID cofdbpoegempjloogbagkncekinflcnjChrome Web Store
51Risk
Who publishes it

DeepL - no other listings under this identity, 3 shared hostnames

Publisher
team-browser-extensions
Declared legal entity
DeepL
Registered address
Maarweg 165, Köln 50825, DE
Registered contact
DeepL

Shared hosts - 3 hostnames

Hostnames hardcoded in this extension that few other listings call. That can mean one operator behind both, and it can equally mean a small shared vendor, so it is context rather than a conclusion. Hosts that many listings call are left out: they are services, not connections.

deepl.qualtrics.com
Also called by 2 other listings: DeepL, DeepL: AI translator and writing assistant
jira.deepl.dev
Also called by 2 other listings: DeepL, DeepL: AI translator and writing assistant
www-app.linguee.com
Also called by 2 other listings: DeepL, DeepL: AI translator and writing assistant
AI-assisted analysis.

DeepL findings

Translation requests send site context to DeepL analytics

MediumunwantedCWE-359Dynamic sandbox

Source-code analysis shows a completed translation builds an analytics event for DeepL's statistics endpoint: hostname, installation/session IDs, user type, language direction, character count and trigger.

What actually happens

You did this

You request a translation from the extension.

This can be inline text translation or another translation flow that completes through the service worker.

The extension did this

The extension prepares a translation analytics event for DeepL.

The event combines the page hostname with installation, session, browser, language, and character-count fields.

Fields placed in the translation analytics event

  • Page hostname
    de.wikipedia.org

    Shows which website was open when you translated text.

  • Installation ID
    d154b8e5-5f28-434b-beae-e816fa0d50b3

    Lets DeepL associate translation events from the same browser extension install.

  • Session ID
    session-20260712-8f4b2c

    Groups activity from the same browser session.

  • User type
    free account

    Describes whether the extension sees the account as anonymous, free, or paid.

  • Translation details
    German to English, 240 characters, inline translation

    Records the language direction, amount of text, and how the translation was started.

Captured request

POSThttps://s.deepl.com/chrome/statistics
Headers
Accept
application/json
Content-Type
application/json

The code that does this

The content script supplies the hostname and the service worker posts the analytics event

Readable version

Content script translation message

build/content.js
EA.update({  translationState: v.ongoingTranslation,  translatedSnippet: "",  originalSnippet: a,  itaTranslateTrigger: n ? C : E}), wH({  type: ty,  payload: {    sourceText: a,    targetLanguage: t,    domainName: window.location.hostname,    trigger: n ? C : E,    websiteLanguage: e.websiteData.websiteLanguage  }})

Translation analytics wrapper

background.js
function $b(event) {  return r(this, void 0, void 0, function*() {    return Gb(base => Object.assign(Object.assign({}, base), {      eventId: BS.EVENT_ID_TRANSLATION_REQUEST,      translationRequestData: Object.assign({        extensionVersion: "1.93.0",        domainName: event.domainName,        userId: event.installationId,        translationTrigger: tE(event.trigger),        translationData: {          sourceLang: event.websiteLanguage,          targetLang: event.targetLanguage,          sourceLength: event.characterCount        }      }, event.translationPerformance && { translationPerformance: event.translationPerformance }, {        nicheIntegration: TE(event.nicheIntegration || Mn)      })    }));  });}

Statistics endpoint sender

background.js
function Gb(buildEvent) {  return r(this, void 0, void 0, function*() {    const browser = Uo();    const clientExperiments = yield cR();    const baseEvent = Object.assign({      eventId: void 0,      extensionVersion: "1.93.0",      sessionId: sessionId,      installationId: installationId,      browserInstanceId: browserInstanceId,      userAgent: browser.userAgent,      platform: browser.platform,      browser: browser.browser,      browserVersion: browser.browserVersion,      browserLang: browser.browserLang,      clientExperiments    }, webInstanceId && { webInstanceId });    const event = buildEvent ? buildEvent(baseEvent) : baseEvent;    return fetch("https://s.deepl.com/chrome/statistics", {      method: "POST",      headers: { Accept: "application/json", "Content-Type": "application/json" },      body: JSON.stringify(event),      credentials: "omit"    });  });}

Destination contacted by this code path

    • s.deepl.com

    DeepL statistics endpoint receiving translation analytics JSON.

Selected page text is sent to DeepL translation endpoints

MediumunwantedCWE-200Dynamic sandbox

Source-code analysis shows that translating selected, input, or page text has the content script collect it and pass it to the service worker, which forwards it to DeepL's JSONRPC path.

What actually happens

You did this

You select text or ask the extension to translate page content.

The extension needs the source text to produce the translation result.

The extension did this

The extension sends the selected or collected page text to DeepL's translation service.

The request includes language settings and the page hostname.

Fields in the translation request path

  • Selected or page text
    Guten Tag, bitte ubersetzen Sie diesen Absatz.

    Contains the text you asked the extension to translate, which may include personal or work content if that text is on the page.

  • Page hostname
    de.wikipedia.org

    Shows which website the translated text came from.

  • Target language
    EN-US

    Shows the language you requested for the translation result.

  • Character count
    240 characters

    Records how much text was included in the translation request.

Captured request

POSThttps://www2.deepl.com/jsonrpc?client=chrome-extension,1.93.0
Headers
Content-Type
application/json

The code that does this

The content script collects text and the service worker forwards it for translation

Readable version

Content script request payload

build/content.js
const y = wj(p.map(e => e.text));v = o ? [yield kn({  action: fn.dlRequestImproveWriting,  payload: Object.assign(Object.assign({    requests: y.simplifiedHtml.map(e => ({ text: e })),    domainName: window.location.hostname,    websiteLanguage: f,    sourceLang: a  }, s && { isHtml: !0 }), { nicheIntegration: i })})] : yield kn({  action: yn.dlRequestInputTranslation,  payload: {    requests: y.simplifiedHtml.map(e => ({ text: e })),    domainName: window.location.hostname,    websiteLanguage: f,    targetLang: r,    platformBehavior: i  }});

Service worker translation handler

background.js
const QL = request => r(void 0, void 0, void 0, function*() {  return yield request.payload.isWriteRequest ? JL(request) : (request => r(void 0, [request], void 0, function*({ payload: { domainName, requests, targetLang, websiteLanguage, formality, platformBehavior, skipDapReporting } }) {    yield $N();    const { installationId, targetLanguageUserInput } = yield MN(["targetLanguageUserInput", "installationId"]);    const selectedTargetLanguage = targetLang || targetLanguageUserInput;    const response = yield DL({ sourceTexts: requests.map(e => e.text) || [], selectedTargetLanguage, formality });    const translatedTexts = response.processedTranslation.map(e => e.text);    const detectedSourceLanguage = response.processedTranslation[0].detected_source_language;    skipDapReporting || PN(() => $b({      installationId,      trigger: platformBehavior !== Mn ? D : C,      websiteLanguage: detectedSourceLanguage,      targetLanguage: selectedTargetLanguage,      characterCount: requests.reduce((sum, item) => sum + item.text.length, 0),      domainName,      nicheIntegration: platformBehavior || Mn,      glossaryTrackingInfo: response.glossaryTrackingInfo    }));    return [{ detected_source_language: detectedSourceLanguage, text: translatedTexts.flat().join(""), texts: translatedTexts }];  }))(request);});

Translation service destinations in the shipped configuration

    • www2.deepl.com

    DeepL free translation JSONRPC endpoint for extension translation requests.

    • api.deepl.com

    DeepL Pro translation JSONRPC endpoint for extension translation requests.

Opening the popup sends the page path to DeepL analytics

MediumunwantedCWE-359Dynamic sandbox

We observed the extension send an extension-opened event to DeepL when the popup opened: eventId 60007, the installation ID, fingerprint fields, and extensionOpenedData (domainName 'de.wikipedia.org', pathName '/wiki/Hauptseite').

What actually happens

You did this

You open the DeepL popup while viewing a webpage.

The observed case used the German Wikipedia homepage.

The extension did this

The extension sends an extension-opened analytics event containing the current page domain and path.

The request also includes extension installation and browser context fields.

Captured request

POSThttps://s.deepl.com/chrome/statistics

Request body was 3255 bytes and included browser fingerprint fields such as userAgent, browser, browserVersion, platform, and browserLang.

Headers
Accept
application/json
Content-Type
application/json
Body
JSON with eventId:60007, installationId:'d154b8e5-5f28-434b-beae-e816fa0d50b3', extensionOpenedData:{domainName:'de.wikipedia.org',pathName:'/wiki/Hauptseite',extensionOpenedFrom:0}

Fields observed in the extension-opened event

  • Current page domain
    de.wikipedia.org

    Shows which website was open when you used the extension.

  • Current page path
    /wiki/Hauptseite

    Shows the specific page path open at the time of the popup event.

  • Installation ID
    d154b8e5-5f28-434b-beae-e816fa0d50b3

    Lets DeepL associate popup-open events from the same browser extension install.

  • Browser details
    Chrome 126 on Linux, en-US

    Adds device and browser context to the event.

The code that does this

The service worker builds event 60007 with domain and path

Readable version

Extension-opened event wrapper

background.js
function Hb(event) {  return r(this, void 0, void 0, function*() {    return Gb(base => Object.assign(Object.assign({}, base), {      eventId: BS.EVENT_ID_EXTENSION_OPENED,      extensionOpenedData: {        extensionVersion: "1.93.0",        domainName: event.domainName,        pathName: event.pathName,        extensionOpenedFrom: event.extensionOpenedFrom      }    }));  });}

Dispatcher preserving domain and path

background.js
const nC = event => r(void 0, void 0, void 0, function*() {  yield PN(() => Hb({    domainName: event.domainName,    pathName: event.pathName,    extensionOpenedFrom: rE(event.extensionContext)  }));});

Statistics endpoint sender

background.js
function Gb(buildEvent) {  return r(this, void 0, void 0, function*() {    const browser = Uo();    const clientExperiments = yield cR();    const baseEvent = Object.assign({      eventId: void 0,      extensionVersion: "1.93.0",      sessionId: sessionId,      installationId: installationId,      browserInstanceId: browserInstanceId,      userAgent: browser.userAgent,      platform: browser.platform,      browser: browser.browser,      browserVersion: browser.browserVersion,      browserLang: browser.browserLang,      clientExperiments    }, webInstanceId && { webInstanceId });    const event = buildEvent ? buildEvent(baseEvent) : baseEvent;    return fetch("https://s.deepl.com/chrome/statistics", {      method: "POST",      headers: { Accept: "application/json", "Content-Type": "application/json" },      body: JSON.stringify(event),      credentials: "omit"    });  });}

Destination observed in traffic

    • s.deepl.com

    DeepL statistics endpoint receiving the extension-opened analytics event.

+4 more findings not shown

What DeepL can do

Permissions this extension asks for, as declared in version 1.108.0. Asking for a permission is not a finding on its own - it is what the extension can do if it chooses to.

  • Read and change your data on deepl.com

    *://*.deepl.com/*

  • Read and change your data on api-test.deepl.com

    https://api-test.deepl.com/v1/*

  • Read and change your data on api.deepl.com

    https://api.deepl.com/v1/*

  • Act on the current tab, but only after you click the extension

    activeTab

  • Store data in your browser

    storage

  • Add items to the right-click menu

    contextMenus

  • See the address and title of every tab you have open

    tabs

  • Block and redirect the requests your browser makes

    declarativeNetRequest

  • Sign you in with your Google account

    identity

  • Speak text aloud

    tts

  • Schedule its own background tasks

    alarms

  • Watch every request your browser makes

    webRequest

  • Read and change cookies, including the ones that keep you signed in

    cookies

  • Show a panel beside the page

    sidePanel

DeepL version history

  1. 1.73.0

    Mar 4, 2026

  2. +19 more

  3. 1.106.0

    Nov 2, 2026

  4. 1.107.0

    Nov 9, 2026

  5. 1.108.0

    Nov 17, 2026

Where DeepL sends data

  • s.deepl.com

    Found in its code · only this extension

Chrome Web Store listing

Versions
1.108.0 latest of 23 seen since March 4, 2026
Store rating
4.5 from 12,664 ratings
Last updated
October 19, 2026
Size
55.25 MiB
Privacy policy
www.deepl.com
Updated November 20, 2026