“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.”
“If your organization uses DeepL through another AI tool (e.g.”
“How long we keep transcripts - If your organisation keeps transcripts, your admin sets the relevant retention periods (anywhere from 20 seconds to 30 days).”
“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.”
Downstream
Who's behind DeepL, as listed in its own subprocessor documents. No subprocessors identified · coverage incomplete: no subprocessor document is on file; the names below come from other documents, if any.
Model providers
- none listed
Hyperscalers
- none listed
Other subprocessors
- none listed
Reviewer notes
Extracted by deterministic rules (rules/v1), no language model. Coverage is limited to recognisable clauses and a gazetteer of common subprocessors; absent values mean 'not matched', not 'not present'.
Documents read
- privacy policy https://www.deepl.com/en/privacyHTTP 200 · 2026-10-13
- terms https://www.deepl.com/en/terms-of-useHTTP 200 · 2026-10-13
Document changes
- low 2026-10-13 · terms +1 / −1 lines
show diff
+ Start free trial− Log inStart free trialMenu - low 2026-10-13 · privacy policy +1 / −1 lines
show diff
+ Start free trial− Log inStart free trialMenu - low 2026-10-10 · privacy policy +3 / −1 lines
show diff
+ * Information about your payment method received from our payment service provider (token, card brand, last four digits, BIN, country of issue and card fingerprint)+ In addition, we use the payment orchestration services of Payrails GmbH, Zimmerstrasse 16, 10969 Berlin, Germany; AG Charlottenburg ("Payrails"). Payrails stores your payment method, processes your first payment and returns to us a token for the stored payment details. We use the stored payment method to collect the payments due under your subscription. Further information on data protection at Payrails and compliance with the requirements of Art. 44 GDPR can be found here. We have concluded a data processing agreement with Payrails, which allows Payrails to process the data solely in accordance with our instructions and not for its own purposes.+ Last update: October 2026− Last update: September 2026
Fact changes
No changes recorded yet. Changes appear here when a later reading differs from an earlier one.
Corrections
No correction requests. Anyone may dispute a fact with a source; requests and resolutions are public and ledger-entered.
Facts are as stated in DeepL's public documents on the date read. This is a record, not legal advice. Work for DeepL? Claim this profile · Something wrong? Request a correction.