DeepL
Translation · deepl.com · last read 2026-11-16
At a glance
- Is DeepL GDPR compliant?
- No tool is GDPR compliant on its own: compliance depends on what you process with it and how. What follows is what DeepL itself publishes, each answer linked to its source and the date we read it.
- Does DeepL have a data processing agreement (DPA)?
- DeepL publishes an agreement, but its site refuses automated readers, so its terms are not recorded here yet. Source and date
- Does DeepL have a SOC 2 report?
- DeepL says a SOC 2 Type 2 report is available on request. In DeepL's words: “Use this Trust Center to learn about our security posture and request access to our security documentation.” We read this on 2026-10-05. Source and date
- Is DeepL ISO 27001 certified?
- DeepL states ISO/IEC 27001 certification (2022 edition, as DeepL names it), and says the certificate or audit report is available on request. In DeepL's words: “DeepL Agent has successfully achieved ISO 27001:2022 certification.” We read this on 2026-10-05. Source and date
- Where is DeepL's trust center?
- DeepL publishes a page it calls “Trust Center” at trust.deepl.com. Some of its documents sit behind a request or sign-in: the page says “Get access”. The page mentions SOC 2, ISO 27001, subprocessors and a DPA. We read it on 2026-11-03. Source and date
- Does DeepL use your data to train AI models?
- For business plans (DeepL for business): Texts not used for model training without the customer's consent. Source and date
- What is DeepL's data retention for AI prompts and outputs?
- For business plans (DeepL for business): Texts not stored without the customer's consent. Source and date
- How does DeepL transfer personal data out of the EU?
- We found no entry for DeepL on the official Data Privacy Framework List. Source and date
- Does DeepL offer EU data residency?
- An EU location exists but only on the enterprise tier. Source and date
- How do you report a security vulnerability to DeepL?
- DeepL publishes a security.txt at www.deepl.com naming security@deepl.com. Source and date
The same questions for any vendor, and the rule behind each: the vendor due diligence checklist.
Identity
| Legal entity | DeepL SE |
|---|---|
| HQ | DE |
| Parent company | — |
| Ultimate ownership | DE |
| EU contracting entity | — |
| LEI | 391200R5PLBD11JIO417 |
| US CLOUD Act reach | No US company in the ownership chain on record |
| Source | deepl.com · 2026-10-08 |
Legal entity from the vendor's own terms. LEI, registered country and parent company from the Global LEI Index (GLEIF); ownership is left empty where GLEIF names no parent. The CLOUD Act row is arithmetic over those countries, not an assessment of risk.
DeepL data residency
| Region | EU data location | Minimum plan | Source | Observed |
|---|---|---|---|---|
| EU | Enterprise only | — | support.deepl.com | 2026-11-03 |
EU: The page names Europe among the regions DeepL operates in and says data residency is an add-on for sales-assisted customers on Team, Business and API for Business plans, included as standard in DeepL for Enterprise. By default, customer content may be processed in different regions.
The same question for every vendor: where SaaS vendors store EU data.
Subprocessor chain
Processing terms
The vendor's data processing agreement could not be read: the site refused our crawler.
These terms side by side for every vendor: data processing agreements compared. What vendors give you for a transfer impact assessment: transfer impact assessments.
AI and your data
What DeepL's own pages state about the data you send its AI products, plan by plan. Compared with other vendors on AI vendors and your data.
| Plans | Term | What the page says | Source | Observed |
|---|---|---|---|---|
| Business DeepL for business | Training on your data | Not used unless you opt in Texts not used for model training without the customer's consent | deepl.com | 2026-10-28 |
| Business DeepL for business | Data retention | Not stored Texts not stored without the customer's consent | deepl.com | 2026-10-28 |
Assurance
Does DeepL have a SOC 2 report?
DeepL says a SOC 2 Type 2 report is available on request. We read this on 2026-10-05.
- Available on request “Use this Trust Center to learn about our security posture and request access to our security documentation.”
- Claimed “DeepL has successfully achieved the C5 Type 2 attestation and renewed its SOC 2 Type 2 report”
Source: deepl.safebase.us, 2026-10-05
Of the 114 vendors in this registry whose own pages mention SOC 2, 57 say the report is available on request, 1 links to the report itself, and 56 state it without saying how to get it. The type is the one the vendor names.
Is DeepL ISO 27001 certified?
DeepL states ISO/IEC 27001 certification (2022 edition, as DeepL names it), and says the certificate or audit report is available on request. We read this on 2026-10-05.
- Available on request “DeepL Agent has successfully achieved ISO 27001:2022 certification”
- Claimed “Maintaining all current regulatory and compliance standards (including C5 and ISO 27001)”
Source: deepl.safebase.us, 2026-10-05
Of the 122 vendors in this registry whose own pages state ISO/IEC 27001, 16 link to the certificate, 43 say it is available on request, and 63 state it without saying how to get it. A certificate names the certification body, the scope and the expiry date: those are the three things to check.
| Scheme | Status | Scope | Source | Observed |
|---|---|---|---|---|
| C5 | Available on request | — | deepl.safebase.us | 2026-10-05 |
| C5 Type 2 · C5 | Claimed | — | deepl.safebase.us | 2026-10-05 |
| GDPR | Claimed | — | deepl.safebase.us | 2026-10-05 |
| HIPAA | Claimed | — | deepl.safebase.us | 2026-10-05 |
| ISO 27001 · ISO27001 | Claimed | — | deepl.safebase.us | 2026-10-05 |
| ISO 27001:2022 · ISO27001 | Available on request | DeepL Agent | deepl.safebase.us | 2026-10-05 |
| ISO/IEC 27001:2022 · ISO27001 | Available on request | — | deepl.safebase.us | 2026-10-05 |
| SOC 2 Type 2 · SOC2T2 | Available on request | — | deepl.safebase.us | 2026-10-05 |
| SOC 2 Type 2 · SOC2T2 | Claimed | controls related to security, availability, and confidentiality | deepl.safebase.us | 2026-10-05 |
Claimed means the vendor asserts the scheme on its own page and offers nothing further. Available on request means the report or certificate exists but sits behind a request, a login or an NDA. Neither is a certificate we have seen. That is a distinction an auditor makes, so we make it too.
SecNumCloud, C5, ENS and HDS for every vendor, with the pages for ISO standards, SOC 2 and TISAX: certifications compared.
Official registers
| Register | Offering, as the register names it | Status | Level | Valid until | Observed |
|---|---|---|---|---|---|
| Global LEI Index (GLEIF) | DeepL SE · DeepL SE | ISSUED | DE | 2027-02-09 | 2026-10-08 |
- ACN qualified cloud (Italy): checked 2026-11-16, no entry under DeepL; DeepL SE
- ISO 27001 on the basis of IT-Grundschutz (BSI, Germany): checked 2026-11-16, no entry under DeepL; DeepL SE
- CISPE Data Protection Code of Conduct (GDPR Art. 40): checked 2026-11-16, no entry under DeepL; DeepL SE
- DORA critical ICT third-party providers (ESAs): checked 2026-11-16, no entry under DeepL; DeepL SE
- Data Privacy Framework List (US): checked 2026-11-16, no entry under DeepL; DeepL SE
- ENS certificates of conformity (CCN, Spain): checked 2026-11-16, no entry under DeepL; DeepL SE
- EU Cloud Code of Conduct (GDPR Art. 40): checked 2026-11-16, no entry under DeepL; DeepL SE
- FedRAMP Marketplace (US): checked 2026-11-16, no entry under DeepL; DeepL SE
- GPAI Code of Practice signatories (European Commission): checked 2026-11-16, no entry under DeepL; DeepL SE
- SecNumCloud qualified services (ANSSI, France): checked 2026-11-16, no entry under DeepL; DeepL SE
What the authority publishes, not what the vendor claims. An entry covers the offering it names and nothing else: a FedRAMP authorisation for a government edition says nothing about the commercial service. No entry is not a finding about security - most vendors never apply - and an entry filed under a name not listed above would not have been found.
What an entry on the Data Privacy Framework List covers, and which vendors hold one: EU-US Data Privacy Framework.
Support window
| Product | Support period | State | SBOM | Source | Observed |
|---|---|---|---|---|---|
| DeepL desktop apps | — | Not declared | unknown | support.deepl.com | 2026-10-19 |
Vulnerability reporting: security@deepl.com (security.txt, expires 2026-12-01; read 2026-10-17)
How other vendors publish theirs: security.txt across the registry.
Documents
Where is DeepL's trust center?
DeepL publishes a page it calls “Trust Center” at trust.deepl.com. Some of its documents sit behind a request or sign-in. The page mentions SOC 2, ISO 27001, subprocessors and a DPA. We read it on 2026-11-03. Open trust.deepl.com
- Name “Welcome to DeepL's Trust Center. Our commitment to data privacy and security is embedded in every part of our business. Use this Trust Center to learn about our security posture and request access to our security documentation.”
- Request step “Get access”
Source: trust.deepl.com, 2026-11-03. Read from the page's text, without a model; every vendor's trust center.
| Document | Disclosure | Transcription | HTTP | Observed |
|---|---|---|---|---|
| ai | Public | full | 200 | 2026-10-28 |
| certifications | Public | full | 200 | 2026-10-05 |
| dpa | Refused | partial | 403 | 2026-10-09 |
| lifecycle | Public | full | 200 | 2026-10-19 |
| residency | Public | full | 200 | 2026-10-05 |
| residency | Public | full | 200 | 2026-11-03 |
| tia | Public | full | 200 | 2026-10-20 |
History
Nothing has moved since we started watching this vendor on 2026-10-28. Changes appear here only after a human has reviewed them.
Every reviewed change across the registry, newest first: vendor changes.