Skip to content

Privacy Policy

SERIOUS
FIRST SEEN 2026-09-17 · VERSION 20260917_rev01 · COMPARED WITH 20260905_rev01

What changed, in plain language

How reviews are made

DeepL added a whole new sub-product, "DeepL Voice to Voice," to its privacy policy (section 5.2). It discloses that DeepL now processes live audio for real-time voice translation, that organization admins can set retention of transcripts/recordings from 20 seconds up to 30 days and download them, that a new "Speaker match" feature analyzes your voice characteristics (tone, speaking style) and can carry them into translated audio output so your voice is recreated in the translation, and that a third-party vendor (ElevenLabs) supplies backup voices for languages DeepL doesn't yet support natively. The rest of the diff is table-of-contents reorganization and section renumbering with no substantive change.

Changes that may affect you

DeepL can now clone your voice into translated audioSERIOUS
DATA COLLECTION

A new feature analyzes the tone and style of your voice and, if enabled, uses it to make translated speech sound like it's in your own voice. This is a new kind of sensitive biometric-style data collection that didn't exist in the prior policy.

“we may process the tone of your voice and speaking style and carry them into the translated voice output to enable your voice to be used in the translation output”

What you can do — Check your DeepL Voice to Voice settings and turn off voice matching, or select a pre-set voice instead of your own, if you don't want your voice characteristics used in translations.

Voice recordings can now be kept up to 30 days and downloaded by adminsMATERIAL
DATA RETENTION

Previously, DeepL Voice data was deleted right after the service was completed. Now, for DeepL Voice to Voice, your organization's admin can choose to store your transcripts and recordings for up to 30 days, and may be able to view and download them.

“your admin sets the relevant retention periods (anywhere from 20 seconds to 30 days)”

What you can do — Ask your organization's DeepL admin what retention period they've configured, since your conversations may be stored and downloadable for up to a month.

Audio may be sent to a new third-party vendor (ElevenLabs) for unsupported languagesMATERIAL
DATA SHARING

For languages where DeepL doesn't yet have its own voice, your audio is processed by ElevenLabs, an outside company, to generate the translated voice output.

“we use backup voices provided by our subprocessor ElevenLabs, who only processes this data on our instructions”

Changelog

  1. + ADDEDNew "DeepL Voice to Voice" product section added

    DeepL added a brand-new section describing a real-time voice-to-voice translation product and how it handles your audio, transcripts, and voice data.

    We use your audio to transcribe and translate it in real time. Once that's done, we delete the audio, the transcript, and the translation - unless one of the sections below applies.

  2. + ADDEDAdmin-controlled transcript retention (20 seconds to 30 days)

    Your organization's admin can now choose to keep transcripts of your voice conversations for anywhere from 20 seconds up to 30 days, and admins may be able to view and download those transcripts and recordings.

    your admin sets the relevant retention periods (anywhere from 20 seconds to 30 days)

  3. + ADDEDNew "Speaker match" voice-characteristic processing, including voice cloning into translations

    A new feature analyzes short samples of your voice to tell speakers apart, and if turned on, it can also copy your tone and speaking style into the translated audio so the output sounds like your own voice.

    we may process the tone of your voice and speaking style and carry them into the translated voice output to enable your voice to be used in the translation output

  4. + ADDEDNew third-party subprocessor (ElevenLabs) for backup voices

    For languages where DeepL doesn't have its own voice yet, your audio may be processed by ElevenLabs, an outside company, to generate a backup voice.

    we use backup voices provided by our subprocessor ElevenLabs, who only processes this data on our instructions

  5. + ADDEDTechnical logs and backups kept for security/recovery purposes

    DeepL notes it may keep some technical logs and backups related to Voice to Voice beyond the normal deletion point, for security and disaster-recovery purposes, without a stated time limit.

    we may retain some technical logs and backups as necessary for our legitimate interests to put in place security measures which enable troubleshooting and disaster recovery

  6. + ADDEDApp version, OS, and IP address noted for Voice app updates

    DeepL clarifies that when the Voice app updates, it may receive your app version, operating system, and IP address, and states this isn't a persistent ID tied to your usage data.

    for App updates we may receive data such as your app version OS, and IP address - as described in section 12. This isn't a persistent device ID and isn't linked to your usage data.

  7. ± CHANGEDTable of contents reorganized and sections renumbered

    The document's table of contents was restructured (e.g., "DeepL Voice" became "DeepL Voice Products" with subsections, and section numbers were adjusted) with no change to the substance of unrelated sections.

    [5\. DeepL Voice]()

    [5\. DeepL Voice Products]()

Full text changes — 20260905_rev01 to 20260917_rev01

COLOUR MARKS THE SEVERITY OF A FLAGGED CLAUSE · + AND − MARK ADDED AND REMOVED

11###### Table of contents
22
33- [1\. Data controller / Contact / Data Protection Officer]()
44- [2\. Scope of Data Protection]()
55- [3\. Texts, Translations and Improvements - DeepL Translator / Write (free version)]()
66- [4\. Texts and Improvements - DeepL Translator Pro / DeepL API Pro / DeepL Write Pro]()
7- [5\. DeepL Voice]()
7- [5\. DeepL Voice Products]()
8 - [5.1 DeepL Voice]()
9 - [5.2 DeepL Voice to Voice]()
810- [6\. Creating a DeepL account and Signing up for a DeepL Pro Subscription]()
911 - [6.1 Creating a DeepL account]()
1012 - [6.2 Signing up for DeepL Pro]()
1113 - [6.3 Processors involved in the DeepL Pro checkout process]()
1214 - [6.4 Processing of usage data]()
1315 - [6.5 Processing of the Submitted Texts and Translations / Improvements]()
1416- [7\. Translation of Documents]()
1517 - [7.1 Translation of Documents with DeepL Translator and DeepL Pro]()
1618 - [7.2 Temporary Storage of Metadata when Translating Documents]()
19- [8\. Customization Hub]()
1720 - [8.1 Translation Memories]()
1821 - [8.2 Translation Memory Generation]()
1922 - [8.3 Adaptive Translation]()
2023- [9\. Automatic Collection of Data via Website Access]()
2124- [10\. Use of Cookies and other Technologies on deepl.com]()
22- [10.1 Use of Cookies, Web Storage and other Technologies on deepl.com]()
25 - [10.1 Use of Cookies, Web Storage and other Technologies on deepl.com]()
2326- [Necessary]()
2427- [Performance]()
2528- [Functional]()
2629- [Marketing]()
2730- [11\. Analysis of User Behaviour]()
2831- [12\. DeepL Apps]()
9598When using our services DeepL Translator Pro, DeepL API Pro and DeepL Write Pro to translate or improve texts, the texts or documents you submit will not be permanently stored and will only be kept temporarily to the extent necessary for the production and transmission of the translation or improvement. After complete performance of the contractually agreed services all submitted texts or documents and their translations or improvements will be deleted. When using these services, your texts will not be used to improve the quality of our services. For further information on the processing of your data within a DeepL Pro subscription, please refer to section 6 of this privacy policy and our [Terms and Conditions](https://www.deepl.com/en/pro-license).
9699
97100Please note that using DeepL Translator Pro, DeepL API Pro and DeepL Write Pro for the translation or improvement of texts containing personal data of any kind is only permitted if there is a justification for this under data protection law. Therefore, our Ts&Cs provide for the conclusion of a data processing agreement (see section 8.1.4 of DeepL Pro [Terms and Conditions](https://www.deepl.com/en/pro-license)). To enter into such an agreement, please contact sales(at)deepl.com.
98101
99102Also note when you integrate our products into your tools for the purpose of document translation we may receive basic contact information from the third-party provider, e.g. Google, where you have consented to share this via the third-party platform. We do this as is necessary for our legitimate interests to facilitate a better user experience and a seamless integration with your key internal tools.
100103
101## 5\. DeepL Voice
104## 5\. DeepL Voice Products
102105
106### 5.1 DeepL Voice
107
103108When using the DeepL Voice services, the audio data of the users will be processed to provide our translation services. The processing includes the transcription and translation of the audio data.
104109
105110After complete performance of the contractually agreed services the audio data, their transcriptions and the translations will be deleted. For DeepL Voice for Conversations transcribed and translated audio data will be stored in the local storage on the customer's side to guarantee a seamless performance of the services. The content in the local storage will be deleted by closing the DeepL app. For further information on the processing of your data within a DeepL Pro subscription, please refer to section 6 of this privacy policy and our [Terms and Conditions](https://www.deepl.com/en/pro-license).
106111
107112When providing our Voice services to customers, we act in our capacity as processor. Your data will therefore be processed on the basis of the data processing agreement entered into with our customers. To enter into such an agreement, please contact sales(at)deepl.com.
108113
109114For DeepL Voice for Meetings we use third party cloud services to be able to integrate our bot application in the Microsoft Teams app. The cloud services are provided by Microsoft Ireland Operations Limited, One Microsoft Place, South County Business Park, D18 P521 Dublin 18, Ireland ("Microsoft") or Amazon Web Services EMEA SARL, 38 Avenue John F. Kennedy, L-1855 Luxembourg (AWS). The cloud services will only be used to host our bot application and forward the audio data to our infrastructure. Neither will the transcription or translation be happening on Microsoft or AWS servers, nor will we store any data on Microsoft or AWS servers for this purpose. We have concluded a data processing agreement with Microsoft and AWS and Microsoft and AWS may only process the data according to our instructions and not for its own purposes. Further information on the handling of personal data at Microsoft can be found [here](https://www.microsoft.com/en-us/privacy/privacystatement), at AWS it can be found [here](https://aws.amazon.com/privacy/).
110115
116### 5.2 DeepL Voice to Voice
117
118We use your audio to transcribe and translate it in real time. Once that's done, we delete the audio, the transcript, and the translation - unless one of the sections below applies.
119
120**How long we keep transcripts** \- If your organisation keeps transcripts, your admin sets the relevant retention periods (anywhere from 20 seconds to 30 days). Depending on your organisation settings, if you're an account admin you may be able to see and download transcripts, recordings and retention settings from your dashboard, so you can manage the service for your team.
121
122While a conversation is live, we may review the transcript on our backend systems for translation purposes. Where there is no host, or you have not set a retention period, we will default to the shortest option. Once a transcript expires, this is deleted permanently and we can't recover it. Please note we may retain some technical logs and backups as necessary for our legitimate interests to put in place security measures which enable troubleshooting and disaster recovery.
123
124**Speaker match** \- When you use Speaker match, we process your voice characteristics for a short period during a session (no longer than 30 seconds) to differentiate between speakers that are present during a conversation and label the transcript accordingly. We do this as necessary for our legitimate interests to provide you with Speaker match and the most advanced version of the DeepL Voice product. If actively enabled, we may process the tone of your voice and speaking style and carry them into the translated voice output to enable your voice to be used in the translation output. Please note you can update your settings at any time or change your selection. Please note that guests can opt out of voice matching or switch between your matched voice with pre-set voices that we have created for this product on a per-meeting basis - this is done via a DeepL hosted site. We keep this choice for the session duration only however we will not store any IDs as part of this selection.
125
126**Voices in other languages** \- For languages where we don't have our own DeepL voice yet, we use backup voices provided by our subprocessor ElevenLabs, who only processes this data on our instructions. Details can be found [here](https://support.deepl.com/hc/en-us/articles/26625846174364-DeepL-Voice-languages).
127
128Please note that for App updates we may receive data such as your app version OS, and IP address - as described in section 12. This isn't a persistent device ID and isn't linked to your usage data.
129
111130## 6\. Creating a DeepL account and Signing up for a DeepL Pro Subscription
112131
113132### 6.1 Creating a DeepL account
114133
115134You have the option of creating a DeepL account. You can use the DeepL Translator or DeepL Write via this account within the applicable [DeepL Account Terms and Conditions](https://www.deepl.com/pro-license) (please see also section [3]()). To create the account, the following personal data will be stored:
116135
227246Processing is carried out in accordance with Art. 6 para. 1 sentence 1 lit. f) GDPR based on our legitimate interest in improving the stability and functionality of our website. The data is stored for purely technical reasons. Website access data is used for error analysis, ensuring system security, logging access to DeepL Pro and for improving our translation or improvement services. Based on your IP address, we also use geolocation to determine the region from which you are visiting our website. We use this information to check whether we can offer you the DeepL Pro service in your region, which corresponds to our legitimate interests pursuant to Art. 6 para. 1 sentence 1 lit. f) GDPR. The storage of the full IP address for the users of the DeepL free version for a maximum period of 14 days is also justified by our legitimate interest in achieving the listed purposes, Art. 6 para. 1 sentence 1 lit. f) GDPR. The storage of IP addresses of users of the paid DeepL Pro subscription for the duration of the contract is justified by Art. 6 para. 1 sentence 1 lit. b) GDPR.
228247
229248Our website also uses services of Cloudflare, Inc, 101 Townsend St, San Francisco, CA 94107, USA ("Cloudflare"), which operates a so-called Content Delivery Network (CDN). To protect our website, the data transfer between your browser and our servers is routed through Cloudflare's infrastructure in order to analyze whether it is an abusive attack. As part of this analysis, your data is transmitted to Cloudflare in encrypted form, if necessary also to Cloudflare servers in the USA. However, since your requests and other customer data are encrypted between your end device and the DeepL servers, Cloudflare does not have any access to this data, but only to meta-data (such as your IP address). Only static resources (such as graphics) are loaded directly from Cloudflare-servers. In addition, Cloudflare determines a so-called bot score immediately before the login to DeepL, which is based on the analysis of the metadata of the client (browser) used. The use of Cloudflare is in our legitimate interest to secure the use of our website and to prevent and defend harmful attacks from outside, Art. 6 para. 1 sentence 1 lit. f) GDPR. We have concluded a data processing agreement with Cloudflare and Cloudflare may therefore only process the data according to our instructions and not for its own purposes. You can find more information about Cloudflare's handling of personal data [here](https://www.cloudflare.com/de-de/privacypolicy/).
230249
231250When you visit the DeepL Dialogues [website](https://deepldialogues.com/), we use Matomo Analytics to analyse the website traffic for purposes of understanding the use of and optimising our website. In this context we collect information relating to your website visit (e.g. signing up for events or newsletters) including your IP address, which is anonymized immediately on collection. This means we are not able to identify you.
232251
233## 10. Use of Cookies and other Technologies on deepl.com
252## 10\. Use of Cookies and other Technologies on deepl.com
234253
235254### 10.1 Use of Cookies, Web Storage and other Technologies on deepl.com
236255
237256These cookies may process personal data including data about your device, such as your IP address as set out in section 8 above. Where we use non-necessary cookies as set out below and process your personal data, we will only do so where you have provided us with your consent.
238257
239258We specifically use cookies or web storage objects in the following categories:
321340If you have contacted our Support team via the contact form, it is possible that we will subsequently inquire by email about your satisfaction with our customer service. In this case, we will process your data on the basis of our legitimate interests in accordance with Art. 6 para. 1 sentence 1 lit. f) GDPR in order to determine customer satisfaction and to continuously improve our service.
322341
323342### 14.3 Privacy Requests
324343
325344You also have the option of contacting privacy(at)deepl.com with questions or concerns about data protection at DeepL. We process your data in accordance with Art. 6 para. 1 sentence 1 lit. a) GDPR on the basis of your voluntarily given consent. We also use the Zendesk ticket system to respond to privacy enquiries, so please also note the above explanations in this regard under section 14.1.
326345
327## 15. DeepL Newsletter
346## 15\. DeepL Newsletter
328347
329348### 15.1 Product Newsletter
330349
331350If you have signed up for a DeepL account, for DeepL Pro or DeepL API Free, we will occasionally send you emails with news on our products, such as the launch of new languages and new features as well as on related products and services. This will also include information and tips on how to get the most out of DeepL Pro. We are entitled to use the email address you provided when signing up for a DeepL account, for a DeepL Pro/DeepL Free API subscription in this way under the legal conditions of § 7 para. 3 of the German Act against Unfair Competition (UWG). Given our existing contractual relationship, it is also in our legitimate interest to inform you as set out above (Art. 6 para. 1 sentence 1 lit. f) GDPR). If you do not wish to receive such emails from us, you can object to the use of your email address for this purpose at any time by sending an email to support(at)deepl.com. Of course, each of our emails contain an unsubscribe link at the end. For sending the newsletter, we use a service provided by HubSpot, Inc. ("HubSpot"), for more information see [1]()5.3.
332351
333352### 15.2 Marketing Newsletter and other marketing communication
443462Please note that it is also possible to participate in the webinar without having a Zoom account. In this case, the collection and processing of data is limited to the minimum necessary to be able to maintain the service for you. We have chosen settings so that the collection and processing of the communication content generally takes place on servers in the European Union. As Zoom is based in the USA, we cannot exclude the possibility that data processing (in particular meeting metadata) may also take place in the USA when using the service. A collection and processing of your data through the use of Zoom takes place on the basis of Art. 6 para. 1 sentence 1 lit. b) GDPR (participation contract). We store the data collected and processed by Zoom on our behalf for the duration of the Zoom webinar and subsequently for the duration of the statutory retention periods, if this is required. We have no influence on the duration of the data processed by Zoom under its own responsibility. Please contact Zoom directly for information in this regard.
444463
445464Automated decision-making pursuant to Art. 22 GDPR does not take place.
446465
447466Please note that we may record Zoom webinars and publish them afterwards on our website or social media channels. Participants will not be visible or identifiable in these recordings. As participants can only ask written questions, they will not appear visually in the recording. The answer to the participant's question will be part of the webinar recording. If, contrary to expectations, personal data of the participants is visible during the recording, it will be made unrecognisable before publication. The recording and storage of the webinar is based on Art. 6 para. 1 sentence 1 lit. f) GDPR, as these processing operations are in our legitimate interest to improve the quality of our webinars. When the webinars are published, no further processing of personal data will take place, as we will make them unrecognisable beforehand - if they can be viewed at all.
448467
449## 20. Job Applications
468## 20\. Job Applications
450469
451470We offer you the opportunity to apply for a position at DeepL via our [career page](https://www.deepl.com/en/careers). Please find further information on how we process candidate personal data in our [privacy notice for candidates](https://www.deepl.com/en/privacy-notice-candidates).
452471
453472## 21\. DeepL Partner Program
454473
455474DeepL uses a [Partner Relationship Management (PRM) platform](http://partners.deepl.com/) to administer its Partner Program, which includes resellers, distributors and other strategic partners. Through this platform we process the business contact details, first name, surname, email address and telephone number of our Partners, of DeepL's existing and prospective end customers, and of DeepL employees involved in partner activities, in each case in their professional capacity.