Generated by a model from the captured document; not read by a person
LowNeutral for users
Affected users
All usersEU usersUK usersGerman usersUsers accessing DeepL through third-party AI tools
DeepL restructured its privacy policy to clarify its corporate structure and complaint procedures. The policy now identifies DeepL as a group of legal entities across multiple countries (Germany, UK, Netherlands, Poland, US, Japan) rather than solely DeepL SE, and expanded complaint procedures to include specific contact information for German, EU, and UK regulators. The policy also added disclosure that when users access DeepL through third-party AI tools via MCP integration, DeepL receives user ID and organization name for authentication, and clarified that translated content is not stored.
Stay ahead of the changes
Track DeepL and hear on the next check after its terms change. We check daily where we can, and show you where we can't.
Generated by a model from the captured document; not read by a person
The updated policy clarifies that DeepL operates as a group of legal entities across multiple jurisdictions rather than a single entity. Users accessing DeepL through third-party AI tools (such as ChatGPT, Claude, or Cursor) via DeepL's MCP integration will have their user ID and organization name shared with DeepL for authentication purposes; translated content itself is not stored. The policy also establishes clearer complaint procedures: EU users can contact their local supervisory authority, German users can contact the Landesbeauftragte für Datenschutz und Informationsfreiheit Nordrhein-Westfalen, and UK users can contact the Information Commissioner's Office (ICO).
What you can do
→ If you access DeepL through third-party AI tools (ChatGPT, Claude, Cursor), review the updated disclosure regarding collection of your user ID and organization name.
→ If you are an EU, German, or UK user and wish to lodge a complaint, use the contact information provided for your respective regulator.
Key Clauses Affected
Generated by a model from the captured document; not read by a person
Data controller identification
Expanded to identify six legal entities across multiple countries as data controllers rather than solely DeepL SE.
Complaint procedures
Added specific contact information and procedures for complaints to German, EU, and UK regulators.
MCP integration disclosure
Added disclosure that accessing DeepL through third-party AI tools results in collection of user ID and organization name for authentication.
Full clause-by-clause analysis available with Insight.
ⓘ
This change record describes what was added, removed, or modified in the document. Analysis reflects what the updated agreement states or permits. It does not constitute a legal determination about enforceability. Applicability may vary by jurisdiction. Methodology
Wording edits to this record that do not change what it claims. Changes to a claim are published as corrections.
2026-10-11 · Feed summary edited · summary regenerated by summarize_events
Previous text Clarifies data controller structure across 7 legal entities in 6 jurisdictions; discloses ID and organization name sharing via ChatGPT/Claude/Cursor integrations.
2026-10-11 · Impact summary edited · summary regenerated by summarize_events
Previous text The updated policy clarifies that DeepL operates through multiple legal entities across Germany, the UK, Netherlands, Poland, the US, and Japan. Previously the policy identified only DeepL SE as the controller, but the revised terms now state that 'DeepL' refers to whichever group entity acts as the controller for your data. Additionally, the policy now discloses that when you use DeepL through ChatGPT, Claude, Cursor, or similar tools via DeepL's MCP (Model Context Protocol) integration, DeepL receives your user ID and organization name for authentication. This is a clarification rather than a new practice authorization; no specific action is required by users.
2026-10-11 · Summary edited · summary regenerated by summarize_events
Previous text DeepL updated its privacy policy to clarify its corporate structure and data controller responsibilities. Previously, the policy identified only DeepL SE as the data controller responsible for processing personal data. The updated policy now states that 'DeepL' refers to the entity within the DeepL group that acts as the controller, and lists seven legal entities across Germany, UK, Netherlands, Poland, US, and Japan that may process data. The policy also added language disclosing that when users access DeepL through third-party AI tools via DeepL's MCP integration, DeepL receives the user's ID and organization name for authentication purposes.
2026-10-07 · Change line edited · change line rewritten to the 2026-10-07 template: no detection date, no sentence counts
Previous text DeepL updated their DeepL Privacy Policy on June 21, 2026. Change detected: 10 sentence(s) added, 17 sentence(s) modified. Document contained 645 sentences after update.
Permanent archival reference. Stable identifier suitable for legal filings, compliance documentation, and research citation.
For legal and compliance teams
Institutional Analysis
Generated by a model from the captured document; not read by a person
Assessment
DeepL expanded its privacy policy to disclose its multi-country corporate structure and added explicit complaint procedures for EU and UK residents. The policy now identifies six legal entities across Germany, UK, Netherlands, Poland, US, and …
🔒Full institutional analysis
Regulatory exposure, obligation change, escalation trigger, board-ready language, and recommended action for legal and compliance teams.
ConductAtlas provides verified policy intelligence sourced directly from platform documents. All analysis is intended to support, not replace, legal and compliance review. Record CA-X-003132.
DeepL's privacy policy was restructured to add three new sections describing customization features: Translation Memories (8.1), Translation Memory Generation (8.2), …
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.
Stay ahead of the changes
Track DeepL policy changes
Get alerted when this policy changes again, including what changed and why it matters.