Privacy Policy
ARCHIVED 2025-04-01, DATE APPROXIMATE · VERSION 20250401_rev01 · COMPARED WITH 20250202_rev01
Full text changes — 20250202_rev01 to 20250401_rev01
COLOUR MARKS THE SEVERITY OF A FLAGGED CLAUSE · + AND − MARK ADDED AND REMOVED
| 13 | 13 | ## 2\. Scope of Data Protection |
| 14 | 14 | |
| 15 | 15 | Data protection applies to personal data as defined by the GDPR, i.e. all information relating to an identified or identifiable natural person. An identifiable natural person is deemed to be a natural person who can be identified directly or indirectly, in particular by means of assignment to an identifier such as a name, an identification number, location data, an online identifier or to one or more specific attributes. |
| 16 | 16 | |
| 17 | 17 | ## 3\. Texts, Translations and Improvements - DeepL Translator / Write (free version) |
| 18 | 18 | |
| 19 | When using our free services, please only enter texts that you wish to transfer to our servers. The transmission of these texts is necessary in order for us to provide the translation or improvement and offer you our service. We process your texts, the documents you upload and their translations or improvements for a limited period of time to train and improve our neural networks and algorithms. This also applies to corrections you make to our translation or improvement suggestions. The corrections are forwarded to our servers to check them for accuracy and, if necessary, to update the translated or improved text according to your changes. If you use the glossary feature and enter certain pairs of terms there, this data is only stored locally and is not forwarded to our servers. Therefore, you cannot use your glossary entries in another browser or on another device. | |
| 19 | When using our [free services](https://www.deepl.com/en/terms-of-use), please only enter content that you wish to transfer to our services. The transmission of this content is necessary in order for us to provide the translation or improvement and offer you our service. We process the content you upload and their translations or improvements for a limited period of time to train and improve our neural networks and algorithms. This also applies to corrections you make to our translation or improvement suggestions. If you use the glossary feature within our free services without a DeepL account and enter certain pairs of terms there, this data is only stored locally and is not forwarded to DeepL. Therefore, you cannot use your glossary entries in another browser or on another device. If you use the glossary feature while being logged into your DeepL account, glossaries may be forwarded to DeepL. | |
| 20 | 20 | |
| 21 | Please note that according to its Terms and Conditions, you may not use DeepL Translator / Write for the translation or improvement of texts containing personal data of any kind.The translation or improvement of personal data is only possible as part of a DeepL Pro subscription (please see sections [4]() and [5]()). | |
| 21 | Please note that according to its [Terms of Use](https://www.deepl.com/en/terms-of-use), you may not use DeepL Translator / Write for the translation or improvement of texts containing personal data of any kind.The translation or improvement of personal data is only possible as part of a DeepL Pro subscription (please see sections [4]() and [5]()). | |
| 22 | 22 | |
| 23 | 23 | ## 4\. Texts and Improvements - DeepL Translator Pro / DeepL API Pro / DeepL Write Pro |
| 24 | 24 | |
| 25 | When 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/). | |
| 25 | When 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). | |
| 26 | 26 | |
| 27 | Please 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.3 ofDeepL Pro [Terms and Conditions](https://www.deepl.com/en/pro-license/)). To enter into such an agreement, please contact sales(at)deepl.com. | |
| 27 | Please 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.3 ofDeepL Pro [Terms and Conditions](https://www.deepl.com/en/pro-license)). To enter into such an agreement, please contact sales(at)deepl.com. | |
| 28 | 28 | |
| 29 | 29 | ## 5\. DeepL Voice |
| 30 | 30 | |
| 31 | 31 | When 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. |
| 32 | 32 | |
| 33 | After complete performance of the contractually agreed services the audio data, their transcriptions and the translations will be deleted on our servers. 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/). | |
| 33 | After 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). | |
| 34 | 34 | |
| 35 | 35 | When 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. |
| 36 | 36 | |
| 37 | 37 | For 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/). |
| 38 | 38 | |
| 39 | 39 | ## 6\. Creating a DeepL account and Signing up for a DeepL Pro Subscription |
| 45 | 45 | - E-mail address |
| 46 | 46 | - Password |
| 47 | 47 | - IP address |
| 48 | 48 | |
| 49 | 49 | We process the email address and password on the basis of Art. 6 para. 1 sentence 1 lit. b) GDPR in order to perform the contract of use. Your IP address is processed in accordance with Art. 6 para. 1 sentence 1 lit. f) GDPR, as it is in our legitimate interests to match your IP address with IP addresses that have misused our service in the past for fraud prevention purposes. |
| 50 | 50 | |
| 51 | Please note that the creation of a DeepL account is a prerequisite for signing up for and using a DeepL Pro subscription (see section [6.2]()), but creating a DeepL account does not oblige you to purchase a paid subscription. Even if you do not sign up for a DeepL Pro subscription after creating the account, the DeepL account remains available and you can use it. You can delete your DeepL account at any time by sending an e-mail with your request to support(at)deepl.com. | |
| 51 | Please note that the creation of a DeepL account is a prerequisite for signing up for and using a DeepL Pro subscription (see section [6.2]()), but creating a DeepL account does not oblige you to purchase a paid subscription. Even if you do not sign up for a DeepL Pro subscription after creating the account, the DeepL account remains available and you can use it. You can delete your DeepL account at any time within the account settings or by sending an e-mail with your request to support(at)deepl.com. | |
| 52 | 52 | |
| 53 | If you use your business email address for creating an account with DeepL, we may share this email address with the holder of the company email domain associated with your email address. We will only do this, if the company has legitimate reasons to ask for this data e.g., is interested in purchasing DeepL Pro licenses for the whole company and has confirmed to us that email addresses under their company email domain may only be used for business purposes and may not be used for private purposes. In some cases, sharing of data may also include sharing of usage data associated with your account to allow the company to assess their specific need on DeepL Pro licenses. The sharing of this data is in DeepL's legitimate interest to best support our customers in the acquisition, roll-out and adoption of our paid services, Art. 6 para. 1 sentence 1 lit. f) GDPR. | |
| 54 | ||
| 53 | 55 | If your company uses Single Sign-On (SSO) to log in to DeepL, there is no need for a separate registration with DeepL. When you log in via Single Sign-On your company transmits your email address as well as your first and last name directly to us. We also process this data on the basis of Art. 6 para. 1 sentence 1 lit. b) GDPR. |
| 54 | 56 | |
| 55 | 57 | ### 6.2 Signing up for DeepL Pro |
| 56 | 58 | |
| 57 | 59 | If, after creating a DeepL account, you sign up for a DeepL Pro subscription, additionally the following personal data will be collected and processed for the purposes of concluding and fulfilling the contract (Art. 6 para. 1 sentence 1 lit. b) GDPR): |
| 58 | 60 | |
| 62 | 64 | - Tax numbers (where applicable) |
| 63 | 65 | - Selected subscription option |
| 64 | 66 | - Possibly other, additional data you provided during the registration process. |
| 65 | 67 | |
| 66 | 68 | Your payment details will also be processed by us if you initially sign up for a DeepL Pro subscription with a free trial period. Despite the free trial period, the processing of your payment details is already necessary at the time of the formation of the contract within the meaning of Art. 6 para. 1 sentence 1 lit. b) GDPR, as a DeepL Pro subscription is in principle a paid subscription and we only in some cases allow our customers to test our products free of charge for a trial period. However, if no cancellation is made within the aforementioned trial period, the subscription will automatically continue to be subject to payment and the method of payment specified by you will be debited at the time stated in the booking process. |
| 67 | 69 | |
| 68 | In order to process payments, we forward the necessary payment data to our authorized payment service provider Stripe Payments Europe Ltd., Block 4, Harcourt Centre, Harcourt Road, Dublin 2, Ireland. Where necessary, Stripe will transfer the data to Stripe, Inc., located in the USA. Further information on data protection at Stripe and compliance with the requirements of Art. 44 GDPR can be found [here](https://stripe.com/de/privacy) and [here](https://stripe.com/de/privacy-center/legal). We have concluded a data processing agreement with Stripe, which allows Stripe to process the data solely in accordance with our instructions and not for its own purposes. | |
| 69 | ||
| 70 | 70 | In addition to the aforementioned data, we process further (usage-)data relevant for the provision and billing of our service, such as subscription ID, date and time of the subscription conclusion, billing period, successful payment processing, logins, number of translated or improved characters and documents, upgrades and downgrades. The processing and storage of the aforementioned data is necessary for the conclusion of the contract as well as its performance and is therefore justified according to Art. 6 para. 1 sentence 1 lit. b) GDPR. If you yourself are not a party to the contract, but DeepL Pro is provided to you, e.g. by your employer or an organization to which you belong, we justify the processing of the data mentioned in section 6.1 and the aforementioned usage data via Art. 6 para. 1 sentence 1 lit. f) GDPR, as this is necessary for the performance of the business relationship with our customers, i.e. your employer or your organization. |
| 71 | 71 | |
| 72 | 72 | We store the data for the duration of the contract term and subsequently, if applicable, for the duration of statutory retention periods, insofar as these prescribe the retention for the respective types of data. We will delete your account if you wish to do so after canceling your subscription. Otherwise, we will maintain your account as DeepL account (see section [6.1]()) so that it is available to you in the event of a renewed subscription without you having to register again. This is in your as well as in our legitimate interests pursuant to Art. 6 para. 1 sentence 1 lit. f) GDPR. |
| 73 | 73 | |
| 74 | ### 6.3 Processors involved in the DeepL Pro checkout process | |
| 75 | ||
| 76 | In order to process payments, we forward the necessary payment data to our authorized payment service provider Stripe Payments Europe Ltd., Block 4, Harcourt Centre, Harcourt Road, Dublin 2, Ireland ("Stripe"). Where necessary, Stripe will transfer the data to Stripe, Inc., located in the USA. Further information on data protection at Stripe and compliance with the requirements of Art. 44 GDPR can be found [here](https://stripe.com/de/privacy) and [here](https://stripe.com/de/privacy-center/legal). We have concluded a data processing agreement with Stripe, which allows Stripe to process the data solely in accordance with our instructions and not for its own purposes. | |
| 77 | ||
| 78 | In addition, we use the fraud prevention services of Riskified Ltd, 30 Kalisher St., Tel-Aviv, 6525724, Israel ("Riskified"). Riskified's service helps us to detect and analyse fraud in online transactions. This enables us to prevent fraudulent activity and misuse of our services. | |
| 79 | ||
| 80 | When you purchase DeepL Pro services on our website, DeepL may transmit data like your first name, last name, billing address, email address, the DeepL service you booked, its price, your IP address, a truncated form of your payment data (for credit cards this is the BIN, the last four digits of the credit card and the bank issuing the card, for SEPA payments this is the bank code and the last 4 digits from your IBAN) to Riskified for verification purposes. Riskified also directly collects and processes your IP address and information on your device and on your behaviour in our checkout process as well as an identifier via its beacon, a Java script that is implemented in the DeepL check process. Riskified analyses these various data points and provides us with an assessment of whether a transaction is to be considered safe or likely to be fraudulent. More information on the logic typically involved in such an analysis can be found [here](https://www.riskified.com/learning/fraud/guide-fraud-score-scoring-models/). If Riskified assesses a payment as fraudulent, we may automatically decline your request to subscribe to DeepL Pro. This is justified, because this fraud analysis is necessary for entering into a contract with us. In case you receive an error message, but consider the decision not correct, you can reach out to support(at) deepl.com at any time and one of our support agents will review your case. | |
| 81 | ||
| 82 | We will also feed back user data to Riskified if Riskified has provided us with a positive assessment and we have concluded and executed the contract, but the transaction is subject to a chargeback or the debit on the specified means of payment is not successful after the end of the trial period. | |
| 83 | ||
| 84 | The inclusion of Riskified's fraud prevention services and the related data processing described above is necessary for our legitimate interest pursuant to Art. 6 para. 1 sentence 1 lit. f) GDPR for the prevention of fraud in order to verify the legitimacy of payments made via DeepL's checkout process. | |
| 85 | ||
| 86 | Riskified processes the data we transfer to them and the data they collect in our checkout process for their own purposes. The data may be transferred to the USA. You can find more information about Riskified's handling of personal data here: [https://www.riskified.com/privacy/](https://www.riskified.com/privacy/). | |
| 87 | ||
| 88 | ### 6.4 Processing of usage data | |
| 89 | ||
| 74 | 90 | In your account in the section "usage", you can also view data about your usage behavior e.g., - depending on your subscription - the number of characters translated or improved in the past or the number of documents translated. If you have a consumption-based subscription, such as the DeepL API Pro, you can also view the monthly costs incurred. We justify this data processing via Art. 6 para. 1 sentence 1 lit. b) GDPR, insofar as it is necessary for the performance of the contract, in particular for billing purposes or for managing the number of documents still available for translation. Insofar as the processing goes beyond what is necessary for the performance of the contract, we base the processing on our legitimate interests pursuant to Art. 6 para. 1 sentence 1 lit. f) GDPR, as we seek to meet our customers' wish to visualize information on usage behavior in a transparent manner. The graphical representation of the development of consumption over the contract period is considered to be also in the interest of our customers. |
| 75 | 91 | |
| 76 | If you yourself are not a party to the DeepL Pro subscription, but access to our products is provided to you by your employer or an organization to which you belong, it is possible that we share data about your usage of the subscription (e.g. number of translated characters and documents, last login date) with your employer or organization on request. Providing this data corresponds to our legitimate interests as well as the legitimate interests of our customers in receiving information about the use of the subscriptions they have paid for. | |
| 92 | If you yourself are not a party to the DeepL Pro subscription, but access to our products is provided to you by your employer or an organization to which you belong, we may share data about your usage of the subscription (e.g. number of translated characters and documents across the DeepL products, last session and last usage date) with your employer or organization. Providing this data corresponds to our legitimate interests as well as the legitimate interests of our customers in receiving the information they need about the use of the subscription they have paid for, Art. 6 para. 1 sentence 1 lit. f) GDPR. | |
| 77 | 93 | |
| 78 | ### 6.3 Processing of the Submitted Texts and Translations / Improvements | |
| 94 | ### 6.5 Processing of the Submitted Texts and Translations / Improvements | |
| 79 | 95 | |
| 80 | We process the texts you submit to DeepL Pro and their translations or improvements only temporarily, insofar as this is necessary for the creation and transmission of the translation or improvement. The processing is therefore justified by Art. 6 para. 1 sentence 1 lit. b) GDPR. Your texts and the translations or improvements will - within the framework of the contractual agreements and as stated in section [4]() and [5]() - not be stored permanently and will be deleted after the performance of the contractually owed service. The only exception is if you use the "saved translations" feature. In this case, texts selected by you, including translations, can be saved on DeepL servers and thus kept accessible at all times. When you use the "saved translations" feature in our apps, your texts and translations are stored locally. | |
| 96 | As contractually agreed, we process the content you submit to DeepL Pro and their translations or improvements only temporarily, insofar as this is necessary for the creation and transmission of the translation or improvement. This processing is therefore justified by Art. 6 para. 1 sentence 1 lit. b) GDPR. The content you submit and the translations or improvements will - within the framework of the contractual agreements and as stated in section [4]() and [5]() - will be deleted after the performance of the contractually agreed service. This does not apply, if you use the "saved translations" or glossary feature. In this case, content provided by you, including translations, will be stored for your account and kept accessible for you at all times. When you use the "saved translations" feature in our mobile apps, your texts and translations are stored locally. | |
| 81 | 97 | |
| 82 | If you use our glossary feature and store certain term pairs there, this data will be forwarded to our servers and stored for your account. If you want to use the glossary function as part of our service, the data processing that takes place in this context is necessary for the performance of our contract and is therefore also justified by Art. 6 para. 1 sentence 1 lit. b) GDPR. | |
| 98 | This data processing is necessary for the performance of our contract and is therefore justified by Art. 6 para. 1 sentence 1 lit. b) GDPR. | |
| 83 | 99 | |
| 84 | 100 | ## 7\. Translation of Documents |
| 85 | 101 | |
| 86 | 102 | ### 7.1 Translation of Documents with DeepL Translator and DeepL Pro |
| 87 | 103 | |
| 88 | 104 | You can translate documents in different file formats both with DeepL Pro (.docx, .pptx, .html, .pdf and .txt) as well as with DeepL Translator (.docx, .pptx and .pdf). When using document translation in DeepL Translator, section [3]() of this privacy policy applies. If you translate documents of the file types mentioned above while you are logged in to your DeepL Pro account, the texts you submit will only be processed temporarily and will be deleted after the completion of the translation process, including the translations themselves (see also section [4]() and [6.3]() of this privacy policy). With both DeepL Pro and DeepL Translator, the translation of your documents will be provided exclusively by DeepL and processed on our infrastructure in the EEA. |
| 101 | 117 | - Errors that occurred during the translation process |
| 102 | 118 | |
| 103 | 119 | This information is processed in accordance with Art. 6 para. 1 sentence 1 lit. f) GDPR based on our legitimate interest in improving the functionality of our products, as this makes it easier to identify any sources of error related to the translation process. The data is stored in a database that can only be accessed by selected employees and is automatically deleted after 14 days. |
| 104 | 120 | |
| 105 | 121 | ## 8\. Automatic Collection of Data via Website Access |
| 106 | 122 | |
| 107 | Regardless of whether you use our paid or free service, your device automatically transmits certain data for technical reasons when you access our website [www.deepl.com](https://www.deepl.com/). The following data that you may send us will be stored: | |
| 123 | Regardless of whether you use our paid or free service, your device automatically transmits certain data for technical reasons when you access our website [www.deepl.com](https://www.deepl.com/en). The following data that you may send us will be stored: | |
| 108 | 124 | |
| 109 | 125 | - Date and time of access |
| 110 | 126 | - Browser type and version |
| 111 | 127 | - Operating system |
| 112 | 128 | - URL of the website previously visited |
| 113 | 129 | - Volume of data transmitted |
| 123 | 139 | Our 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/). |
| 124 | 140 | |
| 125 | 141 | ## 9\. Use of Cookies and other Technologies on deepl.com and Analysis of User Behavior |
| 126 | 142 | |
| 127 | 143 | ### 9.1 Use of Cookies, Web Storage and other Technologies on deepl.com |
| 128 | 144 | |
| 145 | These 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. | |
| 146 | ||
| 129 | 147 | We specifically use cookies or web storage objects in the following categories: |
| 130 | 148 | |
| 131 | - Necessary: These cookies or web storage objects are necessary for our website to work properly, to enable smooth navigation and access our most important functions. This includes essential security and accessibility features and preferences such as interface and translator language as well as the handling of the checkout process for DeepL Pro. The collecting of data via the necessary cookies or web storage objects is justified according to § 25 para. 2 no. 2 TTDSG ("Telekommunikation-Telemedien-Datenschutz-Gesetz": German Telecommunications and Telemedia Data Protection Act). The further processing of this data is either necessary in accordance with Art. 6 para. 1 sentence 1 lit. b) GDPR for performing the contract or justified due to our legitimate interest in presenting our products and our company in accordance with Art. 6 para. 1 sentence 1 lit. f) GDPR. | |
| 132 | - Performance: These cookies or web storage objects measure how our site is used. We use this information to improve our website and services. With these cookies we measure, for example, how often users return and which functions they use. We and our external service providers use these cookies or web storage objects with your explicit consent in accordance with § 25 para. 1 TTDSG. The further processing of this data is also based on your consent, Art. 6 para. 1 sentence 1 lit. a) GDPR. | |
| 133 | - Functional: These cookies or web storage objects enable us to provide you with enhanced functionality and personalization on our website. For example, we can personalize your experience based on which pages you visited. In accordance with § 25 para. 1 TTDSG and Art. 6 para. 1 sentence 1 lit. a) GDPR, we only use these cookies or web storage objects and process the data collected from them with your explicit consent. | |
| 134 | - Marketing: These cookies and other technologies are used to deliver advertising more relevant to you and your interests. By selecting this category, you also consent to DeepL sending your data to third parties outside the EU (e.g., Google), including the sharing of hashed email addresses. In accordance with § 25 para. 1 TTDSG and Art. 6 para. 1 sentence 1 lit. a) GDPR, we only use these cookies, web storage objects and other technologies and process the data collected from them with your explicit consent. | |
| 149 | - Necessary: These cookies or web storage objects are necessary for our website to work properly, to enable smooth navigation and access our most important functions. This includes essential security and accessibility features and preferences such as interface and translator language as well as the handling of the checkout process for DeepL Pro. The collecting of data via the necessary cookies or web storage objects is justified according to § 25 para. 2 no. 2 TDDDG ("Telekommunikation-Digitale-Dienste-Datenschutz-Gesetz": German Telecommunications and Digital Services Data Protection Act). The further processing of this data is either necessary in accordance with Art. 6 para. 1 sentence 1 lit. b) GDPR for performing the contract or justified due to our legitimate interest in presenting our products and our company in accordance with Art. 6 para. 1 sentence 1 lit. f) GDPR. | |
| 150 | - Performance: These cookies or web storage objects measure how our site is used. We use this information to improve our website and services. With these cookies we measure, for example, how often users return and which functions they use. We and our external service providers use these cookies or web storage objects with your explicit consent in accordance with § 25 para. 1 TDDDG. The further processing of this data is also based on your consent, Art. 6 para. 1 sentence 1 lit. a) GDPR. | |
| 151 | - Functional: These cookies or web storage objects enable us to provide you with enhanced functionality and personalization on our website. For example, we can personalize your experience based on which pages you visited, , including when you interact with our chatbot and provide you with personalised DeepL solutions based on your interactions with our website. In accordance with § 25 para. 1 TDDDG and Art. 6 para. 1 sentence 1 lit. a) GDPR, we only use these cookies or web storage objects and process the data collected from them with your explicit consent. | |
| 152 | - Marketing: These cookies and other technologies are used to deliver content, offers and advertising more relevant to you and your interests. By selecting this category, you also consent to DeepL sending your data to third parties outside the EU (e.g., Google), including the sharing of hashed email addresses. In accordance with § 25 para. 1 TDDDG and Art. 6 para. 1 sentence 1 lit. a) GDPR, we only use these cookies, web storage objects and other technologies and process the data collected from them with your explicit consent. | |
| 135 | 153 | |
| 136 | 154 | The table below lists the different types of technologies that may be used on our website. Cookies or web storage objects are stored until the specified expiration time or until you delete them in your browser or, if it is a session cookie, until the session has expired. You can withdraw the consent you have given for the use of cookies, web storage objects and other technologies in the categories "Performance", "Functional" and "Marketing" or manage your settings at any time. You can do this by deactivating (or activating) the slide button in the top right-hand corner of the respective category in the table below. |
| 137 | 155 | |
| 138 | 156 | ### 9.2 Analysis of User Behavior |
| 139 | 157 | |
| 140 | 158 | In order to better understand how our products are used and to better tailor our products to the needs and desires of our customers, we analyze pseudonymized data about our customers' use of DeepL Pro products. The analysis allows us to understand general usage habits and derive different target and user groups. We can then address the identified user groups in a more specific way and, for example, point them to previously unused or unknown features of our products. In this way, we enable our customers to get to know and use all the features of their DeepL subscription and can thus improve the user experience of the DeepL products. This corresponds to our legitimate interests according to Art. 6 para. 1 p. 1 lit. f) GDPR. The data is processed exclusively on DeepL's servers in the EEA, the data is not transferred to the USA. No transfer of the data to third parties takes place. In case that users visit the website [https://developers.deepl.com](https://developers.deepl.com/) which is hosted by GitBook we use the services of Conva Ventures Inc. ("Conva Ventures" the corporation behind Fathom Analytics) to get basic insights about how our API documentation is being used. For the analysis, no cookie is set, and the analysis will only rely on the IP address and user agent of the user which will be hashed first. These pseudo-anonymized hashes will be anonymized after 24 hours. The data will be processed on servers in the USA. We have concluded a data processing agreement with Conva Ventures and Conva Ventures only processes the data in accordance with our instructions and not for its own purposes. You can find more information about Conva Ventures' handling of personal data [here](https://usefathom.com/blog/anonymization). |
| 141 | 159 | |
| 142 | 160 | Overview of the cookies and web storage objects used by DeepL: |
| 143 | 161 | |
| 144 | ### Necessary | |
| 145 | ||
| 146 | | Context | ID | Description | Technology | Expiry | Owner | | |
| 147 | | --- | --- | --- | --- | --- | --- | | |
| 148 | | Site localization | IDil | Description | |
| 149 | Stores the interface language selected by the user. | |
| 150 | ||
| 151 | | TechnologyCookie | Expiry1 month | OwnerDeepL | | |
| 152 | | Site localization | IDi18nextLng | Description | |
| 153 | ||
| 154 | Stores the interface language selected by the user. | |
| 155 | ||
| 156 | | TechnologyLocal Storage | ExpiryPersistent Data | OwnerDeepL | | |
| 157 | | Privacy Settings | IDprivacySettings | Description | |
| 158 | ||
| 159 | Stores the user's cookie-banner decision. You can change the settings here. | |
| 160 | ||
| 161 | | TechnologyCookie | Expiry12 months | OwnerDeepL | | |
| 162 | | Translator | IDLMTBID | Description | |
| 163 | ||
| 164 | Used to guarantee the origin of a request to the translator and protect from malicious visitors. This ensures that the service is not compromised for the remaining visitors. | |
| 165 | ||
| 166 | | TechnologyCookie | Expiry6 months | OwnerDeepL | | |
| 167 | | Translator | IDLMT | Description | |
| 168 | ||
| 169 | Stores settings made explicitly by the user. E.g. preferred translation language or entries in the glossary. | |
| 170 | ||
| 171 | | TechnologyLocal Storage | Expiry1 month | OwnerDeepL | | |
| 172 | | Write | IDLMT\_write | Description | |
| 173 | ||
| 174 | Stores settings made explicitly by the user for the preferred language or language variant, in order to make them available when Write is used again as well as whether the user has already seen the Intro Guide. In addition, the specific use of the alternative pop-up is noted in order to show customers the relevant alternatives in the future. Stores if pop-up announcing DeepL Write was shown. | |
| 175 | ||
| 176 | | TechnologyLocal Storage | Expiry30 days | OwnerDeepL | | |
| 177 | | Write | IDLMT\_customization | Description | |
| 178 | ||
| 179 | Stores if the reference to Write in the header menu was clicked. | |
| 180 | ||
| 181 | | TechnologyLocal Storage | Expiry30 days | OwnerDeepL | | |
| 182 | | Write | IDLMT\_preferredLangWeightsWrite | Description | |
| 183 | ||
| 184 | Stores the weighting of the languages used by the user to allow accurate language identification of the text entered. | |
| 185 | ||
| 186 | | TechnologyLocal Storage | Expiry30 days | OwnerDeepL | | |
| 187 | | Translator | IDproductRecommendations | Description | |
| 188 | ||
| 189 | Used for feature onboarding and discovery on the translator. | |
| 190 | ||
| 191 | | TechnologyCookie | Expiry7 days | OwnerDeepL | | |
| 192 | | Translator | IDrecommendationFlags | Description | |
| 193 | ||
| 194 | Used to store additional translator settings of the user. | |
| 195 | ||
| 196 | | TechnologyLocal Storage | Expiry6 months | OwnerDeepL | | |
| 197 | | Discovery and Onboarding | IDclickOnWordHint, LMT\_MessageBox, onboardingData, showAppOnboarding, AppOnboardingInfo, apiOnboarding | Description | |
| 198 | ||
| 199 | Stores if the user has on-boarded with features to ensure that onboarding prompts are only displayed once. | |
| 200 | ||
| 201 | | TechnologyLocal Storage | Expiry1 to 6 months | OwnerDeepL | | |
| 202 | | Checkout Process | IDFurther details about Stripe 3rd party cookies can be found under [https://stripe.com/cookies-policy/legal](https://stripe.com/cookies-policy/legal). | Description | |
| 203 | ||
| 204 | Fraud detection and security for check-out and payments. This cookie is only set if you enter the checkout process or view your account payment information. | |
| 205 | ||
| 206 | | TechnologyCookie (3rd party) | ExpirySession to 2 years | OwnerThird Party - Stripe | | |
| 207 | | Checkout Process | IDuserCountry | Description | |
| 208 | ||
| 209 | Stores the user's selected country during the checkout process. | |
| 210 | ||
| 211 | | TechnologyLocal Storage / Cookie | ExpirySession | OwnerDeepL | | |
| 212 | | Checkout Process | IDnewpro-checkout | Description | |
| 213 | ||
| 214 | Stores the user's selected DeepL Pro plan during the checkout process. | |
| 215 | ||
| 216 | | TechnologyLocal Storage | Expiry7 days | OwnerDeepL | | |
| 217 | | DeepL Pro-User Login/Session | IDdl\_session | Description | |
| 218 | ||
| 219 | Stores users login token to keep the user logged in on the site. Permanently stored when "remember me" is selected during the login, or expires after 30 minutes of inactivity if not. | |
| 220 | ||
| 221 | | TechnologyCookie | Expiry100 years | OwnerDeepL | | |
| 222 | | DeepL Pro-User Login/Session | IDdl\_logoutReason | Description | |
| 223 | ||
| 224 | When you get logged out accidentally, we will help you with an error message. We use this cookie to deliver this message to you so you can prevent this problem in the future. | |
| 225 | ||
| 226 | | TechnologyCookie | ExpirySession | OwnerDeepL | | |
| 227 | | DeepL Pro-User Login/Session | IDep | Description | |
| 228 | ||
| 229 | Ip-Based Enterprise Account login token. Checked once per session and deleted afterwards. | |
| 230 | ||
| 231 | | TechnologyLocal Storage | ExpirySession | OwnerDeepL | | |
| 232 | | DeepL Pro-User Login/Session | IDuser | Description | |
| 233 | ||
| 234 | Stores the display name of logged-in users to display their name. Deleted if the user logs out. | |
| 235 | ||
| 236 | | TechnologyLocal Storage | Expiry7 days | OwnerDeepL | | |
| 237 | | DeepL Pro-User Login/Session | IDdl\_auth | Description | |
| 238 | ||
| 239 | Stores the "login state" of a user, the account type and sets a reminder for login. When user gets logged out accidentally, user will be helped with an error message. | |
| 240 | ||
| 241 | | TechnologyLocal Storage | ExpiryPersistent Data | OwnerDeepL | | |
| 242 | | Release process | IDreleaseGroups | Description | |
| 243 | ||
| 244 | Used for gradual, controlled releases to ensure stability, quality and performance of our service and infrastructure. | |
| 245 | ||
| 246 | | TechnologyCookie | Expiry1 month | OwnerDeepL | | |
| 247 | | Release process | IDdapGid | Description | |
| 248 | ||
| 249 | Used for controlled rollout of features for logged users. | |
| 250 | ||
| 251 | | TechnologyCookie | Expiry1 month | OwnerDeepL | | |
| 252 | | Session ID | IDdapSid | Description | |
| 253 | ||
| 254 | Session ID and timestamp. Automatically deleted after 30 minutes of inactivity. | |
| 255 | ||
| 256 | | TechnologyCookie | ExpirySession | OwnerDeepL | | |
| 257 | | App Usage Statistics - only for DeepL Apps | IDappUsageStats | Description | |
| 258 | ||
| 259 | Remembers when the user last used the app. | |
| 260 | ||
| 261 | | TechnologyLocal Storage | ExpiryPersistent Data | OwnerDeepL | | |
| 262 | | Sales Form Usage Statistics | IDsalesContactStats | Description | |
| 263 | ||
| 264 | Remembers when the user submitted the form. | |
| 265 | ||
| 266 | | TechnologyLocal Storage | ExpiryPersistent Data | OwnerDeepL | | |
| 267 | | Document translation | IDLMT\_doctranslate\_client | Description | |
| 268 | ||
| 269 | Used to bind an ongoing document translation process to a user and protect the document translation feature from excessive use by individual users. This ensures that the service is not impacted for the remaining users. | |
| 270 | ||
| 271 | | TechnologyCookie | Expiry1 month | OwnerDeepL | | |
| 272 | | Document translation | IDLMT\_text\_translator\_usage\_free | Description | |
| 273 | ||
| 274 | Used to bind an ongoing text translation process to a user and protect the translation feature from excessive use by individual users. This ensures that the service is not impacted for the remaining users. | |
| 275 | ||
| 276 | | TechnologyCookie | Expiry1 month | OwnerDeepL | | |
| 277 | | Security | IDdapUid | Description | |
| 278 | ||
| 279 | User identifier to ensure correct operation of our systems, including to identify malicious bots and measure performance. | |
| 280 | ||
| 281 | | TechnologyCookie | Expiry12 months | OwnerDeepL | | |
| 282 | | Security | IDdl\_clearance | Description | |
| 283 | ||
| 284 | Used to prevent misuse of our services by using the Cloudflare bot score. | |
| 285 | ||
| 286 | | TechnologyCookie | Expiry5 minutes | OwnerDeepL | | |
| 287 | | Security | IDdl\_camellia\_client | Description | |
| 288 | ||
| 289 | Used to protect services from excessive use by individual users. This ensures that the service is not impacted for the remaining users. | |
| 290 | ||
| 291 | | TechnologyCookie | Expiry1 month | OwnerDeepL | | |
| 292 | | Product Support/Zendesk | IDzendesk | Description | |
| 293 | ||
| 294 | Third-party cookie used by our ZenDesk support tool. Necessary for the operation of the service (bot detection and session management). | |
| 295 | ||
| 296 | | TechnologyCookie | Expiry1 month | OwnerThird Party - Zendesk | | |
| 297 | | Product Support/HubSpot | IDhubspot | Description | |
| 298 | ||
| 299 | Third-party cookie used by our HubSpot sales tool. Used for session management and to prevent misuse. | |
| 300 | ||
| 301 | | TechnologyCookie | Expiry1 month | OwnerThird Party - HubSpot | | |
| 302 | | User Features | IDdl\_featureSet | Description | |
| 303 | ||
| 304 | Stores the features which are available to the user depending on the account or subscription. | |
| 305 | ||
| 306 | | TechnologyLocal Storage | ExpiryPersistent Data | OwnerDeepL | | |
| 307 | | API documentation/GitBook | ID\_\_gitbook\_cookie\_granted | Description | |
| 308 | ||
| 309 | Third-party cookie used by GitBook documentation platform. Necessary for the operation of the service (storage of user cookie preferences). | |
| 310 | ||
| 311 | | TechnologyCookie | ExpirySession | OwnerThird Party - GitBook | | |
| 312 | | API documentation/GitBook | ID\_\_session | Description | |
| 313 | ||
| 314 | Third-party cookie used by GitBook documentation platform. Used for session management. | |
| 315 | ||
| 316 | | TechnologyCookie | Expiry400 days | OwnerThird Party - GitBook | | |
| 317 | | Speech-to-text | IDspeechToTextConsent | Description | |
| 318 | ||
| 319 | Stores the consent of the Free and DeepL account users when using the speech-to-text feature. | |
| 320 | ||
| 321 | | TechnologyCookie | Expiry100 years | OwnerDeepL | | |
| 322 | | Security | ID\_\_cf\_bm | Description | |
| 323 | ||
| 324 | Used to prevent misuse of our services by using the Cloudflare bot score. | |
| 325 | ||
| 326 | | TechnologyCookie | Expiry30 minutes (after continuous inactivity of the user) | OwnerThird Party - Cloudflare | | |
| 327 | | Allocation of assets | IDINGRESSCOOKIE | Description | |
| 328 | ||
| 329 | Used to provide the user with the correct version of the assets (Javascript, CSS, etc.) when deepl.com is updated. | |
| 330 | ||
| 331 | | TechnologyCookie | Expirysession | OwnerDeepL | | |
| 332 | | Privacy Settings | IDgtm\_consent | Description | |
| 333 | ||
| 334 | Stores user preference regarding Google Tag Manager consent. | |
| 335 | ||
| 336 | | TechnologyLocal Storage | ExpiryPersistent Data | OwnerDeepL | | |
| 337 | ||
| 338 | ### Performance | |
| 339 | ||
| 340 | | Context | ID | Description | Technology | Expiry | Owner | | |
| 341 | | --- | --- | --- | --- | --- | --- | | |
| 342 | | Visit Count | IDdapVn | Description | |
| 343 | Stores how many times the user has visited the site. | |
| 344 | ||
| 345 | | TechnologyCookie | Expiry12 months | OwnerDeepL | | |
| 346 | | Page views | IDpv | Description | |
| 347 | ||
| 348 | Stores the page ID of the pages accessed by the user, including a timestamp indicating when this access was last made. Based on this, corresponding information is displayed to the user. | |
| 349 | ||
| 350 | | TechnologyLocal storage | ExpiryPersistent Data | OwnerDeepL | | |
| 351 | ||
| 352 | ### Functional | |
| 353 | ||
| 354 | | Context | ID | Description | Technology | Expiry | Owner | | |
| 355 | | --- | --- | --- | --- | --- | --- | | |
| 356 | | Translator | IDuserRecommendations | Description | |
| 357 | Used to personalise the users experience. | |
| 358 | ||
| 359 | | TechnologyCookie | Expiry7 days | OwnerDeepL | | |
| 360 | | Translator | IDrecommendationFlags | Description | |
| 361 | ||
| 362 | Used to store additional translator settings of the user. | |
| 363 | ||
| 364 | | TechnologyLocal Storage | Expiry6 months | OwnerDeepL | | |
| 365 | | Checkout Process | IDLMT\_resumeCheckout | Description | |
| 366 | ||
| 367 | Used to store checkout details of the user to help users resume the checkout process. | |
| 368 | ||
| 369 | | TechnologyLocal Storage | ExpiryPersistent Data | OwnerDeepL | | |
| 370 | | Product information | IDapiDocsVisited | Description | |
| 371 | ||
| 372 | Stores whether API documentation has been visited to help users select the correct package at checkout. | |
| 373 | ||
| 374 | | TechnologyLocal Storage | ExpiryPersistent Data | OwnerDeepL | | |
| 375 | ||
| 376 | ### Marketing | |
| 377 | ||
| 378 | | Context | ID | Description | Technology | Expiry | Owner | | |
| 379 | | --- | --- | --- | --- | --- | --- | | |
| 380 | | Conversion Tracking | ID | Description | |
| 381 | Records and evaluates conversions from DeepL's LinkedIn advertising campaigns | |
| 382 | ||
| 383 | | TechnologyTracking Pixel | Expiry Ongoing (until consent is revoked) | OwnerLinkedIn | | |
| 384 | | Conversion Tracking | ID | Description | |
| 385 | ||
| 386 | Records and evaluates conversions in connection with DeepL's advertising campaigns in Google services. | |
| 387 | ||
| 388 | | TechnologyServer-to-server tracking | ExpiryOngoing (until consent is revoked) | OwnerGoogle | | |
| 389 | | Conversion Tracking | ID | Description | |
| 390 | ||
| 391 | Records and evaluates conversions in connection with DeepL's advertising campaigns in Microsoft services, e.g. Bing search. | |
| 392 | ||
| 393 | | TechnologyTracking Pixel | Expiry Ongoing (until consent is revoked) | OwnerMicrosoft Ireland Operations Ltd. | | |
| 394 | | Conversion Tracking | ID | Description | |
| 395 | ||
| 396 | Records and evaluates conversions in connection with DeepL's advertising campaigns in Meta services. | |
| 397 | ||
| 398 | | TechnologyServer-to-server tracking | ExpiryOngoing (until consent is revoked) | OwnerMeta Platforms, Inc. | | |
| 399 | | Conversion Tracking | ID | Description | |
| 400 | ||
| 401 | Records and evaluates conversions in connection with DeepL's advertising campaigns in Naver services, e.g. Naver search. | |
| 402 | ||
| 403 | | TechnologyConversion Tracking Pixel | Expiry Ongoing (until consent is revoked) | OwnerNaver Corp. | | |
| 404 | | Conversion Tracking | ID | Description | |
| 405 | ||
| 406 | Records and evaluates conversions in connection with DeepL's advertising campaigns using B2B Digitalzone services. | |
| 407 | ||
| 408 | | TechnologyTracking Pixel | Expiry Ongoing (until consent is revoked) | OwnerDigitalzone, Inc. | | |
| 409 | | Conversion Tracking | ID | Description | |
| 410 | ||
| 411 | Records and evaluates conversions in connection with DeepL's advertising campaigns using Plug services. | |
| 412 | ||
| 413 | | TechnologyTracking Pixel | ExpiryOngoing (until consent is revoked) | OwnerPlug Media Ltd | | |
| 414 | | Conversion Tracking | ID | Description | |
| 415 | ||
| 416 | Records and evaluates conversions in connection with DeepL's advertising campaigns using Fifty services | |
| 417 | ||
| 418 | | TechnologyTracking Pixel | ExpiryOngoing (until consent is revoked) | OwnerFifty Technology Ltd | | |
| 419 | | Conversion tracking | ID | Description | |
| 420 | ||
| 421 | Records and evaluates conversions in connection with DeepL's advertising campaigns in Yahoo Japan services. | |
| 422 | ||
| 423 | | TechnologyServer-to-server tracking | ExpiryOngoing (until consent is revoked) | OwnerLY Corporation | | |
| 424 | ||
| 425 | 162 | ## 10\. Speech-to-text function for web |
| 426 | 163 | |
| 427 | 164 | For the web version of our DeepL Translator, we also offer a speech-to-text function, where the text to be translated can be dictated yourself. The recorded text is transcribed solely within DeepL's internal infrastructure. |
| 428 | 165 | |
| 429 | 166 | When using DeepL Pro, the recordings and the transcriptions will not be permanently stored and will only be kept temporarily to the extent necessary for the production and transmission of the translation. After complete performance of the contractually agreed services the recordings, their transcriptions and the translations will be deleted. This does not apply when using the speech-to-text function as part of the free version of DeepL translator or the DeepL account, where the recordings, their transcriptions and the translations are stored and processed for a limited period of time to train and improve our neural networks and translation algorithms (please see also section 3 of this privacy policy). The user will be informed of this before using the speech-to-text function for the first time and asked to give their consent. The consent does not cover the recording of the voices of third parties, which means, you are not permitted to record the voices of third parties. You can withdraw the consent you have given at any time with effect for the future. You do this by deleting the corresponding cookie set by the consent. For further information and explanation of the withdrawal process, please click [here](https://support.deepl.com/hc/articles/10422503124636). |
| 430 | 167 | |
| 454 | 191 | If you use our mobile apps, it is also possible to have the entered text and the translation or improvement read aloud or to dictate the text to be translated or improved yourself. The speech service installed on your device is used for this purpose. Please note that this may result in the transfer of the entered or spoken content to the provider of the speech service used by your device, possibly also to the USA. DeepL has no influence on this processing of your voice and audio data, therefore the privacy policy and terms of use of the speech service used by your device e.g. provided by Apple, Google or Samsung, but also those of other speech services that cannot be listed exhaustively, apply. |
| 455 | 192 | |
| 456 | 193 | No cookies are used in our mobile apps. However, a unique user ID (no cross-device ID) is used, which allows us to track, for example, the source and target language settings, how many characters are translated or improved, whether the copy button is used, and if so, how it is used. The processing of this data is based on our legitimate interest (Art. 6 para. 1 sentence 1 lit. f) GDPR) to better understand the needs of our users and to be able to adapt the app according to customer requirements. |
| 457 | 194 | |
| 458 | 195 | ## 12\. DeepL API Free |
| 459 | 196 | |
| 460 | In addition to the paid DeepL API Pro plan, we also offer a limited free version of our API (DeepL API Free). For further information, please see our [DeepL Pro Terms and Conditions](https://www.deepl.com/pro-license) and section [3]() on using the free version of DeepL. | |
| 197 | In addition to the paid DeepL API Pro plan, we also offer a limited free version of our API (DeepL API Free). For further information, please see our [DeepL Pro Terms and Conditions](https://www.deepl.com/en/pro-license) and section [3]() on using the free version of DeepL. | |
| 461 | 198 | |
| 462 | 199 | In order to use DeepL API Free, it is necessary to create a DeepL account (please see section [6.1]()). If you select the API Free option during the checkout process, further data, as specified in section [6.2](), will be collected. Although no costs are incurred when using DeepL API Free - subject to a (possible) upgrade - your payment data is collected in order to prevent improper use of API Free. Solely for this purpose, payment information is also passed on, in accordance with section [6.3](), to the payment service provider we have commissioned, Stripe Payments Europe Ltd. |
| 463 | 200 | |
| 464 | 201 | We process your data in order to perform the free-of-charge usage contract concluded between you and us on the basis of Art. 6 para. 1 sentence 1 lit. b) GDPR and on the basis of our legitimate interest in preventing misuse of the API Free, Art. 6 para. 1 sentence lit. f) GDPR. |
| 465 | 202 | |
| 466 | ## 13\. Contacting our Sales or Support Team | |
| 203 | ## 13\. Connecting with our Customer Team, including via our ChatBot | |
| 467 | 204 | |
| 468 | You have the possibility to contact us via various contact forms on our website. You can also contact us directly by email. | |
| 205 | You have various possibilities to connect with us, including via contact forms on our website, having calls with our customer team as well as by using our chatbot. You can also contact us directly by email. | |
| 469 | 206 | |
| 470 | ### 13.1 Sales and Support Requests | |
| 207 | We will process your personal data that you provide to us as part of these communications. This may include your name, email address and any other personal data you disclose to us. | |
| 471 | 208 | |
| 472 | If you would like to send us a sales enquiry in order to receive further information about our products and subscription plans or to start contract negotiations, you are welcome to use our sales contact form. In addition to your email address, you are required to provide your name and telephone number; all other information is optional. For the provision of our contact form, we use the HubSpot service (see section [14]()), where your request is pre-filtered and then forwarded to the ticket system of the provider Zendesk Inc. ("Zendesk"), 1019 Market Street, San Francisco, CA 94103, USA. We use Zendesk to process your enquiry and your further communication with us, we also use the service to manage our customer database. This may also involve the transfer of your contract data to the USA. We have entered into a data processing agreement with Zendesk and Zendesk may therefore only process the data in accordance with our instructions and not for its own purposes. Further information on the handling of personal data at Zendesk and on compliance with the requirements of Art. 44 GDPR can be found [here](https://www.zendesk.de/company/privacy-and-data-protection/) and [here](https://www.zendesk.com/blog/update-privacy-shield-invalidation-european-court-justice/). We also use the Customer Relationship Management System (CRM) of Salesforce.com Germany GmbH, Erika-Mann-Str. 31, 80636 München, Deutschland ("Salesforce CRM") to manage our customer database, which includes our existing and potential customers, and to organize sales and communication processes. Furthermore, Salesforce CRM enables us to analyse our customer-related processes. We have concluded a data processing agreement with Salesforce and Salesforce is therefore only allowed to process the data according to our instructions and not for its own purposes. The customer data is stored on servers in the EU. | |
| 209 | ### 13.1 Recording of dialer and Zoom calls | |
| 473 | 210 | |
| 474 | If you contact our support team with questions about your contract and its implementation via our contact form, it is necessary to provide a valid email address so that we know who the inquiry comes from and can respond to it. We also use the aforementioned ticket system Zendesk to respond to your enquiry. | |
| 211 | Our customer team is conducting dialer and Zoom calls with prospects and customers to provide them with general information about DeepL's services and to advise them according to their needs. In order to continue to provide excellent customer service and to continuously improve it, we may record and transcribe the dialer and zoom calls with prospects and customers in certain countries with their consent, using the Salesloft platform provided by Salesloft, Inc., 1180 West Peachtree St NW Suite 2400, Atlanta, GA 30309. We have concluded a data processing agreement with Salesloft and Salesloft is therefore only allowed to process the data according to our instructions and not for its own purposes. | |
| 475 | 212 | |
| 476 | For both support and sales enquiries including any subsequent correspondence , Art. 6 para. 1 sentence 1 lit. b) GDPR serves as the legal basis for the processing of your personal data, as the processing is necessary for the initiation of the contract or the conclusion and performance of our contract. Art. 6 para. 1 sentence 1 lit. b) GDPR also provides justification for the processing of personal data that may be contained in documents sent to our Support team. We will store your data for the duration of our business relationship and subsequently for the duration of the legal retention periods where this is required. The processing of your personal data as part of our customer database and the analyses of our customer-related processes is based on Art. 6 para. 1 sentence 1 lit. f) GDPR, as this is in our legitimate interest. | |
| 213 | Recordings of the calls, including transcriptions of these, are used for internal training and coaching as well as for documentation purposes. At the beginning of each dialer call, an automated message will inform the called party that the call is being recorded. If you do not wish to participate in a recorded call, you can end the call at any time. For Zoom calls, the Zoom invitation will inform you that the call is being recorded and that you can opt out when you join the call. | |
| 477 | 214 | |
| 215 | All recorded calls, including transcriptions, will be securely stored for a period of two years from the date of the call. After this period, the recordings will be automatically deleted from our systems. You also have the rights mentioned in section 20. | |
| 216 | ||
| 217 | ### 13.2 Sales and Support Requests | |
| 218 | ||
| 219 | If you would like to send us a sales enquiry in order to receive further information about our products and subscription plans or to start contract negotiations, you are welcome to use our sales contact forms. In addition to your email address, you are required to provide your name and telephone number; all other information is optional. For the provision of our contact forms, we use the HubSpot service (see section 14). | |
| 220 | ||
| 221 | We also use the Customer Relationship Management System (CRM) of Salesforce.com Germany GmbH, Erika-Mann-Str. 31, 80636 München, Deutschland ("Salesforce CRM") to manage our customer database, which includes our existing and potential customers, and to organize sales and communication processes. Furthermore, Salesforce CRM enables us to analyse our customer-related processes. We have concluded a data processing agreement with Salesforce and Salesforce is therefore only allowed to process the data according to our instructions and not for its own purposes. The customer data is stored on servers in the EU. | |
| 222 | ||
| 223 | If you contact our support team with questions about your subscription, for example via our contact form, it is necessary to provide a valid email address so that we know who the inquiry comes from and can respond to it. We use the ticket system provided by Zendesk Inc. ("Zendesk"), 1019 Market Street, San Francisco, CA 94103, USA We have entered into a data processing agreement with Zendesk and Zendesk may therefore only process the data in accordance with our instructions and not for its own purposes. Further information on the handling of personal data at Zendesk can be found [here](https://www.zendesk.de/company/agreements-and-terms/privacy-notice/). | |
| 224 | ||
| 225 | For both support and sales enquiries including any subsequent correspondence, Art. 6 para. 1 sentence 1 lit. b) GDPR serves as the legal basis for the processing of your personal data, as the processing is necessary for the initiation of the contract or the conclusion and performance of our contract. Art. 6 para. 1 sentence 1 lit. b) GDPR also provides justification for the processing of personal data that may be contained in documents sent to our Support team. We will store your data for the duration of our business relationship and subsequently for the duration of the legal retention periods where this is required. The processing of your personal data as part of our customer database and the analyses of our customer-related processes is based on Art. 6 para. 1 sentence 1 lit. f) GDPR, as this is in our legitimate interest. | |
| 226 | ||
| 478 | 227 | If 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. |
| 479 | 228 | |
| 480 | ### 13.2 Privacy Requests | |
| 229 | ### 13.3 Privacy Requests | |
| 481 | 230 | |
| 482 | 231 | You 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 [13.1](). |
| 483 | 232 | |
| 484 | 233 | ## 14\. DeepL Newsletter |
| 485 | 234 | |
| 486 | 235 | ### 14.1 Product Newsletter |
| 628 | 377 | - Process payments: We forward the necessary payment data to our authorized payment service provider Stripe Payments Europe Ltd., Block 4, Harcourt Centre, Harcourt Road, Dublin 2, Ireland. Where necessary, Stripe will transfer the data to Stripe, Inc., located in the USA. You can contact the company through duo(at)stripe.com. |
| 629 | 378 | - Secure the use of website: Our website uses services of Cloudflare, Inc, 101 Townsend St, San Francisco, CA 94107, USA ("Cloudflare"). 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. However, since your translation 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). You can contact the company through privacyquestions(at)cloudflare.com. |
| 630 | 379 | - Support enquires: If you send us a support enquiry, your request is forwarded to the ticket system of the provider Zendesk Inc. ("Zendesk"), 1019 Market Street, San Francisco, CA 94103, USA. We use Zendesk to process your enquiry and your further communication with us, we also use the service to manage our customer database. You can contact the company through privacy(at)zendesk.com. |
| 631 | 380 | - Manage customer database: We use the Customer Relationship Management System (CRM) of Salesforce.com Germany GmbH, Erika-Mann-Str. 31, 80636 München, Deutschland ("Salesforce CRM") to manage our customer database, which includes our existing and potential customers, and to organize sales and communication processes. You can contact the company through privacy(at)salesforce.com. |
| 632 | 381 | - Send newsletters and other marketing emails: For sending the newsletters and other marketing emails, we use a service provided by HubSpot, Inc. with headquarters at 25 First Street, 2nd Floor, Cambridge, MA 02141 USA. As part of this, your data may also be transferred to the USA. You can contact the company through privacy(at)hubspot.com. |
| 633 | 382 | - Conduct the customer satisfaction surveys: To conduct the customer satisfaction surveys, we use a service of Typeform SL, Carrer Bac de Roda, 163, local, 08018 Barcelona, Spain ("Typeform"), on whose platform the surveys are stored. Typeform uses different subcontractors, which are also partly located in third countries outside the EU. Therefore, in certain cases, there may be a transfer of your data to the USA. You can contact the company through GDPR(at)typeform.com. |
| 634 | - Conduct surveys: For the surveys we use a service of Qualtrics Ireland Limited, Costello House, 1 Clarendon Row, Dublin 2, DO2 TA43, Ireland ("Qualtrics"), on whose platform the surveys are stored. Qualtrics uses different subcontractors, which are also partly located in third countries outside the EU. Therefore, in certain cases, there may be a transfer of your data to the USA. You can contact the company through [\[email protected\]](https://deepl.com/cdn-cgi/l/email-protection#ea9a98839c8b8993c78e9998aa9b9f8b869e98838999c4898587). | |
| 635 | - Conduct surveys: We use a survey tool of Hotjar Ltd., Dragonara Business Centre, 5th Floor, Dragonara Road, Paceville St Julian's STJ 3141, Malta ("Hotjar"), on whose platform the surveys are stored. Hotjar uses different subcontractors, which are also partly located in third countries outside the EU.Therefore, in certain cases, there may be a transfer of your data to the USA. You can contact the company through [\[email protected\]](https://deepl.com/cdn-cgi/l/email-protection#bbdfcbd4fbd3d4cfd1dac995d8d4d6) | |
| 636 | - Conduct interviews: We use a service provided by UserTesting, Inc. 144 Townsend Street, San Francisco, CA 94107 USA to conduct interviews with you. UserTesting uses different subcontractors - such as Zoom - which are also partly located in third countries outside the EU. Therefore, in certain cases, there may be a transfer of your data to the USA. You can contact the company through [\[email protected\]](https://deepl.com/cdn-cgi/l/email-protection#5424263d2235372d1421273126203127203d3a337a373b39). | |
| 637 | - Host Webinars: We use a service provided by Zoom Video Communications, Inc. ("Zoom"), 55 Almaden Blvd. Suite 600, San Jose, CA 95113, USA, on whose platform the webinars are held. You can contact the company through [\[email protected\]](https://deepl.com/cdn-cgi/l/email-protection#bececcd7c8dfddc7fec4d1d1d390cbcd). | |
| 638 | - Job applications: In order to process your application data, it will be forwarded to the service provider Localyze UG (haftungsbeschränkt), Bäckerbreitergang 28, 20355 Hamburg, which carries out the Pre-Check on behalf of DeepL. You can contact the company through [\[email protected\]](https://deepl.com/cdn-cgi/l/email-protection#1b797473747e697f7e75767f7e776e757c5b7f7a6f7a7c6e7a697f357f7e). | |
| 639 | - Job applications: In order to process your application data, it will be forwarded to the service provider Recruitee B.V., Keizersgracht 313, 1016 EE Amsterdam, The Netherlands, which operates the application system. You can contact the company through [\[email protected\]](https://deepl.com/cdn-cgi/l/email-protection#e38b868f8f8ca391868091968a978686cd808c8e). | |
| 640 | - Job applications: In particular applications for developer positions, the applicant's name and email address may be forwarded to the service provider Codesse Ltd., FF28, Kao Hockham Building, Edinburgh Way, Harlow, Essex, CM20 2NQ, United Kingdom, which provides services regarding the provision and review of coding challenges during an application. You can contact the company through [\[email protected\]](https://deepl.com/cdn-cgi/l/email-protection#215348424a61424e45445252440f424e4c) | |
| 383 | - Conduct surveys: For the surveys we use a service of Qualtrics Ireland Limited, Costello House, 1 Clarendon Row, Dublin 2, DO2 TA43, Ireland ("Qualtrics"), on whose platform the surveys are stored. Qualtrics uses different subcontractors, which are also partly located in third countries outside the EU. Therefore, in certain cases, there may be a transfer of your data to the USA. You can contact the company through [\[email protected\]](https://deepl.com/cdn-cgi/l/email-protection#6616140f1007051f4b021514261713070a12140f05154805090b). | |
| 384 | - Conduct surveys: We use a survey tool of Hotjar Ltd., Dragonara Business Centre, 5th Floor, Dragonara Road, Paceville St Julian's STJ 3141, Malta ("Hotjar"), on whose platform the surveys are stored. Hotjar uses different subcontractors, which are also partly located in third countries outside the EU.Therefore, in certain cases, there may be a transfer of your data to the USA. You can contact the company through [\[email protected\]](https://deepl.com/cdn-cgi/l/email-protection#1074607f50787f647a71623e737f7d) | |
| 385 | - Conduct interviews: We use a service provided by UserTesting, Inc. 144 Townsend Street, San Francisco, CA 94107 USA to conduct interviews with you. UserTesting uses different subcontractors - such as Zoom - which are also partly located in third countries outside the EU. Therefore, in certain cases, there may be a transfer of your data to the USA. You can contact the company through [\[email protected\]](https://deepl.com/cdn-cgi/l/email-protection#acdcdec5dacdcfd5ecd9dfc9ded8c9dfd8c5c2cb82cfc3c1). | |
| 386 | - Host Webinars: We use a service provided by Zoom Video Communications, Inc. ("Zoom"), 55 Almaden Blvd. Suite 600, San Jose, CA 95113, USA, on whose platform the webinars are held. You can contact the company through [\[email protected\]](https://deepl.com/cdn-cgi/l/email-protection#a1d1d3c8d7c0c2d8e1dbcececc8fd4d2). | |
| 387 | - Job applications: In order to process your application data, it will be forwarded to the service provider Localyze UG (haftungsbeschränkt), Bäckerbreitergang 28, 20355 Hamburg, which carries out the Pre-Check on behalf of DeepL. You can contact the company through [\[email protected\]](https://deepl.com/cdn-cgi/l/email-protection#ef8d8087808a9d8b8a81828b8a839a8188af8b8e9b8e889a8e9d8bc18b8a). | |
| 388 | - Job applications: In order to process your application data, it will be forwarded to the service provider Recruitee B.V., Keizersgracht 313, 1016 EE Amsterdam, The Netherlands, which operates the application system. You can contact the company through [\[email protected\]](https://deepl.com/cdn-cgi/l/email-protection#fc9499909093bc8e999f8e8995889999d29f9391). | |
| 389 | - Job applications: In particular applications for developer positions, the applicant's name and email address may be forwarded to the service provider Codesse Ltd., FF28, Kao Hockham Building, Edinburgh Way, Harlow, Essex, CM20 2NQ, United Kingdom, which provides services regarding the provision and review of coding challenges during an application. You can contact the company through [\[email protected\]](https://deepl.com/cdn-cgi/l/email-protection#67150e040c27040803021414024904080a) | |
| 641 | 390 | |
| 642 | 391 | ## 22\. Changes to the Privacy Policy |
| 643 | 392 | |
| 644 | We reserve the right to amend this privacy policy. The current version of the privacy policy can be accessed at any time on our [website](https://www.deepl.com/privacy). | |
| 393 | We reserve the right to amend this privacy policy. The current version of the privacy policy can be accessed at any time on our [website](https://www.deepl.com/en/privacy). | |
| 645 | 394 | |
| 646 | Last update: November 2024 | |
| 395 | Last update: February 2025 |