DeepL policy evolution
Before/after stance changes across captured policy versions, with exact citations. If no before/after delta is available yet, AIRIN shows the latest citation-backed stance events instead.
No before/after stance delta is available for this filter yet. Latest citation-backed stance events are shown below.
Jun 17, 2026privacymedium
data sharing
Latest stance: third party or vendor sharing
“8.1.4 Customer is obligated to keep, and shall procure that its Internal Users keep, the access credentials provided by DeepL secure and shall not disclose them to any third partys. Customer is not entitled to repackage or resell access credentials or its access to the Services to any third parties unless expressly agreed by DeepL in advance in writing. 8.1.5 Customer is obligated to observe all legal requirements for the collection, processing and use of data which is transmitted to DeepL and processed by DeepL for Customer in connection with the Services under this Agreement. Customer shall immediately enter into DeepL's data processing agreement (which shall be provided by DeepL) if Customer intends to transmit personal data to DeepL using the Services. Customer agrees not to collect, process or use any personal data in connection with the Services without the express consent of the data subject or without sufficient other legal authorisation. DeepL shall reasonably cooperate with Customer in order to assist Customer in implementing such required legal authorisations. 8.1.6 Customer shall defend, indemnify and hold DeepL harmless against any and all third-party claims (regulatory or judicial orders and claims) and all resulting losses, damages, fines and expenses (including court costs and reasonable legal fees), asserted against or incurred by DeepL arising out of or in connection with:”
Open citationJun 17, 2026privacymedium
data sharing
Latest stance: third party or vendor sharing
“8.3.5 In the event that a disclosure of access credentials to third parties is required for the contractually intended use of the API, Customer shall and is solely responsible to take adequate and effective precautions to protect the access credentials from misuse or unauthorised access. In particular, access credentials may not be stored in configuration files in plain text and may not be transmitted over unencrypted public network connections. 8.3.6 Customer is obligated to adhere to any security precautions, functional and other limitations of the API. In particular, Customer must not bypass, remove, defeat, avoid, deactivate or otherwise circumvent protection or authentication mechanisms or misuse API methods for purposes other than those intended or expressly documented. 8.3.7 To the extent reasonable and technically possible, Customer must take precautions during the implementation of the Application using the API to ensure that Customer’s Application will continue to work properly even if the API is not available, whether caused by DeepL’s or Customer’s fault. DeepL shall have no responsibility for any failure of the Application caused by any failure of the API. 8.3.8 Customer shall immediately inform DeepL if there are reasons to expect a significant increase in the number of API Requests for reasons such as an extraordinary surge in End Users, unusual marketing, promotions or other campaigns. 8.3.9 Customer acknowledges that DeepL may update the API from time to time.”
Open citationGenerated from live stance events. Informational only, not legal advice.