This analysis describes what DeepL's agreement states, permits, or reserves. It does not constitute a legal determination about enforceability. Regulatory applicability and practical outcomes may vary by jurisdiction, enforcement context, and individual circumstances. Read our methodology
The updated terms explicitly state that audio files are now included in the definition of 'Content' and that all Content is processed by DeepL's machine learning infrastructure. This formalizes what may have been implicit practice and clarifies the scope of data subject to machine learning processing. The terms also introduce a new access method through third-party AI assistant applications via DeepL's Model Context Protocol endpoint; usage through this pathway counts toward your subscription's usage limits and volumes. You can review the Service Specification for details on how third-party application access operates.
View change record →How other platforms handle this
Customer acknowledges and agrees that Cohere may monitor Customer's use of the Cohere API and that Customer will not block or otherwise interfere with Cohere's monitoring.
This includes the right to use OpenAI's API to integrate the Services into Customer Applications and to make Customer Applications available to End Users.
You will not exceed...any limit on calls per second set forth in any Specifications...and you will not send files to or from Creators API or PA API that are greater than 40KB without our prior written approval.
"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.Excerpt from DeepL's Terms and Conditions
Get the weekly coverage letter
Companies change their terms without announcing it. We capture governance documents, compare each new version with the last, and publish what changed, with the source text behind it. One email a week on what we found and what we could not reach.
The clause states: “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.”
ConductAtlas has identified this type of provision across 102 platforms. See the full comparison.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by DeepL.