DeepL — privacy changed (review) DeepL updated its privacy policy to remove the sales(at)deepl.com contact address for data processing agreements under Art. 28 GDPR, directing users instead to privacy@deepl.com. The policy states that content uploaded to the free DeepL Translator and Write services, along with user corrections, is processed for a limited period to train and improve DeepL's neural networks and algorithms, and that free-tier users may not submit texts containing personal data of any kind under the Terms of Use. DeepL's privacy changed Privacy Policy DeepL Table of contents Protecting your privacy and personal data is very important to us. We therefore only use your personal data within the scope of legal regulations, in particular the General Data Protection Regulation "GDPR" and the German Federal Data Protection Act "BDSG" . With this privacy policy, we would like to inform you - regardless of whether you set up a DeepL account, use our DeepL Pro subscriptions, our various apps or visit our website - about the nature, scope and purposes of the collection, use and processing of your personal data by DeepL. 1. Data controller / Contact / Data Protection Officer Where we reference DeepL in this privacy notice we refer to the company in the group that acts as controller of, and is responsible for processing your personal data. The DeepL group is made up of different legal entities, which are: Germany: DeepL SE and DeepL AI GmbH of Maarweg 165, 50825 Cologne United Kingdom: DeepL UK Ltd of 6 th Floor, One London Wall, London, EC2Y 5EB Netherlands: DeepL NL B.V. of Weesperstraat 61-105, 1018VN Amsterdam Poland: DeepL PL SP. Z O. O. of Grabarska 1, Pegaz Building B, 3 rd Floor, Wroclaw, 50-079 United States of America: DeepL US Inc. of 2093A Philadelphia Pike, Suite 539, Claymont, DE 19703 Japan: DeepL Japan GK of Anderson Mori & Tomotsune, Otemachi Park Building 1-1 Otemachie 1-chome, Chiyoda-ku, Tokyo, 100-0004. REMOVEDIf you have any questions or concerns about privacy, please contact privacy at deepl.com. For the conclusion of a data processing agreement pursuant to Art. 28 GDPR see in detail section 4 and 5 and for general questions about our products, please contact sales at deepl.com. Further information on the data processing when contacting DeepL can be found in section 14 . ADDEDIf you have any questions or concerns about privacy, please contact privacy at deepl.com. For the conclusion of a data processing agreement pursuant to Art. 28 GDPR see in detail section 4 and 5 please contact privacy@deepl.com. Further information on the data processing when contacting DeepL can be found in section 14 . DeepL's external corporate Data Protection Officer, Dr. Christian Lenz, can be contacted at the following address: dhpg IT-Services GmbH, Bunsenstr. 10a, 51647 Gummersbach, via email to datenschutz at dhpg.de, or by telephone on +49 2261 8195 0. 2. Scope of Data Protection 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. 3. Texts, Translations and Improvements - DeepL Translator / Write free version When using our free services , 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. Please note that according to its 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 . 4. Texts and Improvements - DeepL Translator Pro / DeepL API Pro / DeepL Write Pro 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 . REMOVEDPlease 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 . To enter into such an agreement, please contact sales at deepl.com. ADDEDPlease 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 . To enter into such an agreement, please contact privacy@deepl.com . Also 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. 5. DeepL Voice Products 5.1 DeepL Voice 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. 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 . REMOVEDWhen 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. ADDEDWhen 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 privacy@deepl.com . 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 , at AWS it can be found here . 5.2 DeepL Voice to Voice 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. 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. While 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. 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. 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 . Please 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. 6. Creating a DeepL account and Signing up for a DeepL Pro Subscription 6.1 Creating a DeepL account You 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 please see also section 3 . To create the account, the following personal data will be stored: E-mail address Password IP address 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. 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. 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. 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. If your organization uses DeepL through another AI tool e.g. ChatGPT, Claude, or Cursor using DeepL's MCP integration, DeepL receives your user ID and your organization's name to authenticate your access. We process this to perform our contractual obligations with your organization. Your content sent for translation is only used for the translation and is not stored by DeepL. 6.2 Signing up for DeepL Pro 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 : First name, surname, and where applicable, company name Address Payment details Tax numbers where applicable Selected subscription option Possibly other, additional data you provided during the registration process. 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. 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. 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. 6.3 Processors involved in the DeepL Pro checkout process 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 and here . 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. 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. 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 . 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. 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. 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. 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/ . 6.4 Processing of usage data 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. 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. 6.5 Processing of the Submitted Texts and Translations / Improvements 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 where you ask us to store content in your account, for example by using the "saved translations" or glossary feature, or by using our customization features. In this case, content provided by you, including translations, will be stored for your account and kept accessible for you at all times, for details please see section 8 . When you use the "saved translations" feature in our mobile apps, your texts and translations are stored locally. 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. 7. Translation of Documents 7.1 Translation of Documents with DeepL Translator and DeepL Pro 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. 7.2 Temporary Storage of Metadata when Translating Documents Regardless of whether you use our paid or free service when translating documents, particularly the following data is stored for each translation process: Status/progress of the translation process Document file type Selected language pair for translation Estimates of time needed for the translation References to the applied glossary when using DeepL Pro Content of the applied glossary when using the free translator Number of characters calculated Errors that occurred during the translation process 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. 8. Customization Hub Our customization features allow you to store language assets in your account, such as saved translations, glossaries, style guides, Style Profiles and Translation Memories and to apply them to your translations. Information on saved translations and glossaries can be found in section 6.5. 8.1 Translation Memories You can create Translation Memories in your account and upload existing Translation Memories to it. A Translation Memory stores source segments together with their translations so that they can be reused in later translations. Content you store in a Translation Memory, including the translations, will be stored for your account and kept accessible for you at all times. It will be deleted when you delete the relevant entries, the Translation Memory or your account. 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. 8.2 Translation Memory Generation If you use our Translation Memory Generation feature, you can upload a source document together with its corresponding translated document. We process both documents solely to identify and align corresponding segments and to generate a Translation Memory from them. The uploaded source and translated documents are deleted immediately upon successful generation of the Translation Memory; they are not otherwise stored and are not used to train or improve our models. The resulting Translation Memory is then stored for your account in the same way as a Translation Memory you upload directly, as described in section 8.1. 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. 8.3 Adaptive Translation If you enable Adaptive Translation in a Style Profile, we use the Translation Memory and any reference documents attached to that profile to adapt your translations to your terminology, tone and style. Reference documents you upload are stored for your account. For this purpose we calculate numeric representations embeddings of that content and store them for your account, so that the closest-matching entries can be provided to our translation model as context at the time of translation. This content and the embeddings derived from it are used only within your own account, never for other customers, and are not used to train or improve our models. If you delete a Translation Memory or individual entries within it, delete reference documents, or if your account is deleted, the corresponding embeddings are deleted as well. You can deactivate the feature at any time in the relevant Style Profile. 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. 9. Automatic Collection of Data via Website Access 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 . The following data that you may send us will be stored: Date and time of access Browser type and version Operating system URL of the website previously visited Volume of data transmitted Requested domain Notification of successful data retrieval Search term when using a web browser Abbreviated/anonymized IP Full IP address Diagnostic information in the event of errors Processing 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. 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 . When you visit the DeepL Dialogues website , 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. 10. Use of Cookies and other Technologies on deepl.com 10.1 Use of Cookies, Web Storage and other Technologies on deepl.com 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. We specifically use cookies or web storage objects in the following categories: 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. This also includes the use of the Usercentrics Consent Management Platform provided by Usercentrics GmbH, Sendlinger Str. 7, 80331 Munich, Germany to manage and document your privacy choices. 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. 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. 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. 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 storing or sharing of hashed email addresses e.g. Reddit . 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. Where you are based in Japan we may also share your IP address e.g. to Sales Marker , to deliver content including via email, relevant to you, your interests and your organisation. 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 via our cookie banner or, as applicable depending on your jurisdiction the Usercentrics settings in our cookie banner by either i deactivating or activating the slide toggle next to the respective category; ii the button in the top right hand corner; iii or in the table below. Where you provide us with consent to place third party cookies provided by Google on your device as listed below , you can find out more information about how they store and process your personal data here . If you require additional information, please do reach out to us at privacy at deepl.com. Overview of the cookies and web storage objects used by DeepL: Necessary Context Description Technology Expiry Owner Site localization ID il Description Stores the interface language selected by the user. Technology Cookie Expiry 1 month Owner DeepL ID i18nextLng Technology Local Storage Expiry Persistent Data Privacy Settings ID privacySettings Description Stores the user's cookie-banner decision. You can change the settings here. Expiry 12 months Translator ID LMTBID Description 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. Expiry 6 months ID LMT Description Stores settings made explicitly by the user. E.g. preferred translation language or entries in the glossary. Write ID LMT write Description 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. Expiry 30 days ID LMT customization Description Stores if the reference to Write in the header menu was clicked. ID LMT preferredLangWeightsWrite Description Stores the weighting of the languages used by the user to allow accurate language identification of the text entered. ID productRecommendations Description Used for feature onboarding and discovery on the translator. Expiry 7 days ID userRecommendationFlags Description Used to store additional translator settings of the user. Discovery and Onboarding ID clickOnWordHint, LMT MessageBox, LMT onboarding, onboardingData, showAppOnboarding, AppOnboardingInfo, apiOnboarding Description Stores if the user has on-boarded with features to ensure that onboarding prompts are only displayed once. Expiry 1 to 6 months Checkout Process ID userCountry Description Stores the user's selected country during the checkout process. Technology Local Storage / Cookie Expiry Session ID newpro-checkout Description Stores the user's selected DeepL Pro plan during the checkout process. DeepL Pro-User Login/Session ID dl session Description 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. Expiry 100 years ID dl logo Description Temporarily stores a custom logo ID to avoid unnecessary loading times and flickering when loading the company logo as part of logging in to a subscription that has enabled the custom company logo feature. Technology Session Storage ID dl logoutReason Description 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. ID ep Description Ip-Based Enterprise Account login token. Checked once per session and deleted afterwards. ID user Description Stores the display name of logged-in users to display their name. Deleted if the user logs out. ID dl auth Description 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. Release process ID releaseGroups Description Used for gradual, controlled releases to ensure stability, quality and performance of our service and infrastructure. Technology Cookie/Local Storage ID dapGid Description Used for controlled rollout of features for logged users. ID DAP experimentation Session ID ID dapSid Description Session ID and timestamp. Automatically deleted after 30 minutes of inactivity. Owner DeepL & Usercentrics App Usage Statistics - only for DeepL Apps ID appUsageStats Description Remembers when the user last used the app. Sales Form Usage Statistics ID salesContactStats Description Remembers when the user submitted the form. Document translation ID LMT doctranslate client Description 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. ID LMT text translator usage free Description 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. Security ID dapUid Description User identifier to ensure correct operation of our systems, including to identify malicious bots and measure performance. ID dl clearance Description Used to prevent misuse of our services by using the Cloudflare bot score. Expiry 5 minutes ID dl camellia client Description Used to protect services from excessive use by individual users. This ensures that the service is not impacted for the remaining users. User Features ID dl featureSet Description Stores the features which are available to the user depending on the account or subscription. API documentation/GitBook ID gitbook cookie granted Description Third-party cookie used by GitBook documentation platform. Necessary for the operation of the service storage of user cookie preferences . Owner Third Party - GitBook ID session Description Third-party cookie used by GitBook documentation platform. Used for session management . Expiry 400 days Speech-to-text ID speechToTextConsent Description Stores the consent of the Free and DeepL account users when using the speech-to-text feature. Allocation of assets ID INGRESSCOOKIE Description Used to provide the user with the correct version of the assets Javascript, CSS, etc. when deepl.com is updated. ID gtm consent Description Stores user preference regarding Google Tag Manager consent. ID cf bm / Expiry 30 minutes after continuous inactivity of the user Owner Cloudflare Inc. ID Further details about Stripe 3rd party cookies can be found under https://stripe.com/cookies-policy/legal. Description 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. Technology Cookie 3rd party Expiry Session to 2 years Owner Third-Party - Stripe Technology Europe, Limited ID Further details about Riskified 3rd party cookies can be found under https://www.riskified.com/deco-terms-privacy/. Description Fraud detection and prevention for payments in the DeepL Pro check-out process. This is only applied if you enter the checkout process. Technology JavaScript Expiry n/a Owner Third-Party - Riskified Ltd. Chat Support / Zendesk ID ZD-widgetOpen Description Maintains the open/closed state of the chat Web Widget across page visits. Owner Zendesk ID