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
How other platforms handle this
Customer is responsible for ensuring any login credentials to a Customer User Account...are: (i) kept secure, (ii) only provided to and used by Permitted Users, and (iii) not shared between more than one unique Permitted User.
if your authorization from that user expires or is revoked, you will immediately stop accessing or acting under that user's account.
Customer shall promptly notify Perplexity if Customer becomes aware of any unauthorized access to, or use of, an Authorized User's account.
"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.Excerpt from DeepL's Terms and Conditions
Get the research letter
Companies change their terms quietly. We read every version and catch what actually changed. One email a week on the changes that matter and what they mean.
The clause states: “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.”
ConductAtlas has identified this type of provision across 267 platforms. See the full comparison.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by DeepL.