Langdock
AI tools · langdock.com · last read 2026-11-16
At a glance
- Is Langdock GDPR compliant?
- No tool is GDPR compliant on its own: compliance depends on what you process with it and how. What follows is what Langdock itself publishes, each answer linked to its source and the date we read it.
- Does Langdock have a data processing agreement (DPA)?
- Yes. Langdock publishes a data processing agreement at langdock.com. It gives 14 days' notice before a new subprocessor is added. It promises breach notification "without undue delay", with no number of hours. Source and date
- Which version of the Langdock DPA is current?
- On 2026-11-09, Langdock's DPA at langdock.com printed “Version 2.1”. Source and date
- Does Langdock have a SOC 2 report?
- Langdock states SOC 2 Type 2 on its own page, but does not say there how to get a report. In Langdock's words: “SOC2 Type II: Independently audited to ensure secure, reliable data handling.” We read this on 2026-10-08. Source and date
- Is Langdock ISO 27001 certified?
- Langdock states ISO/IEC 27001 on its own page, but does not say there how to get the certificate. We read this on 2026-10-08. Source and date
- Where is Langdock's trust center?
- Langdock publishes a page it calls “Trust Center” at trust.langdock.com. Some of its documents sit behind a request or sign-in: the page says “Request access”. Its text appears only after JavaScript runs: a client without it, as most tooling is, gets an empty page. The page mentions SOC 2, ISO 27001, subprocessors and a DPA. We read it on 2026-11-03. Source and date
- Does Langdock use your data to train AI models?
- For business plans (Langdock (Langdock-provided LLMs)): Inputs not used to train any AI when using Langdock-provided LLMs; with own API keys the customer manages the provider relationship. For business plans (Langdock Platform): Customer Content not used to develop, train or improve AI models; model providers contractually prohibited too. Source and date
- Does Langdock offer zero data retention?
- For business plans (Langdock Platform): Zero Data Retention agreed with OpenAI, AWS (Bedrock) and Mistral AI. Source and date
- Can Langdock process AI data in the EU?
- For business plans (Langdock): By default all data processed in the EU with EU-hosted models; admins can enable global-deployment models that may process outside the EU; data at rest always in Germany. For business plans (Langdock Platform): Customer can choose models that process and store data only in the EU; global-deployment models may process outside the EU. Source and date
- How does Langdock transfer personal data out of the EU?
- Langdock's agreement relies on the EU standard contractual clauses and the EU-U.S. Data Privacy Framework. We found no entry for Langdock on the official Data Privacy Framework List. Source and date
- Does Langdock offer EU data residency?
- The EU is the default region for this vendor. Source and date
- Who are Langdock's subprocessors?
- Langdock lists 7 third-party subprocessors; 0 of them name at least one processing country outside the EEA. We last read the list on 2026-10-08. Source and date
The same questions for any vendor, and the rule behind each: the vendor due diligence checklist.
Identity
| Legal entity | Langdock GmbH |
|---|---|
| HQ | DE |
| Parent company | — |
| Ultimate ownership | — |
| EU contracting entity | — |
| LEI | — |
| US CLOUD Act reach | Not determined from the sources read |
| Source | langdock.com · 2026-10-08 |
Langdock data residency
| Region | EU data location | Minimum plan | Source | Observed |
|---|---|---|---|---|
| EU | EU by default | — | langdock.com | 2026-10-08 |
EU: The document labels the standard multi-tenant SaaS deployment as "Hosted via Microsoft Azure on servers inside the EU." It names no extra cost, add-on or customer opt-in for this. It says hosting for most models is "configurable", and only the dedicated, own-cloud and on-premise deployments are tied to Enterprise seat thresholds.
The same question for every vendor: where SaaS vendors store EU data.
Langdock's subprocessor list names Microsoft for hosting or infrastructure. Which SaaS vendors run on which cloud, and the sovereign offerings of each: sovereign clouds.
Subprocessor chain
7 third parties · 0 with a country outside the EEA · all read 2026-10-08
| Subprocessor | Country | Purpose |
|---|---|---|
| Amazon Web Services (AWS) | EU | AI Provider |
| Cloudflare | EU | Protection against malicious traffic |
| Google Cloud | EU | AI Provider |
| Microsoft Azure | EU | Hosting & AI Provider |
| Mistral | EU | AI Provider |
| OpenAI Ireland Ltd | EU | AI Provider |
| Sentry | EU | Error tracking |
The count outside the EEA is arithmetic over the country column, not a judgement about lawfulness. A transfer outside the EEA can be perfectly lawful; whether this one is depends on your use, not on the vendor.
Every subprocessor in the registry, and which vendors name it: subprocessors.
Processing terms
From the vendor's data processing agreement · read 2026-10-09 · langdock.com
| Term | What the agreement says |
|---|---|
| Transfer mechanism | EU-U.S. DPF |
| Transfer mechanism | SCC (module not stated) |
| Transfer mechanism | Swiss FADP clauses |
| Transfer mechanism | other |
| Notice of new subprocessors | At least 14 days before engagement, by publication at https://trust.langdock.com/subprocessors and by email to those subscribed on that page |
| If you object to one | Written objection within 14 days of publication, on specific data protection grounds; otherwise deemed approved. If no agreement within 14 days of the objection, either party may terminate on 30 days' notice |
| Obligations passed to subprocessors | Contractually imposes on sub-processors data protection obligations corresponding to the level of protection under the Agreement |
| Breach notification | without undue delay after becoming aware of the breach |
| Deletion when the service ends | Deletes Controller Data no later than 30 days after termination of the Main Contract unless legally required to retain it longer; confirms deletion on request |
| Getting your data back | Controller may export its data during the term and until deletion; Processor provides export functions on request |
| Requests from data subjects | Assists the Controller via platform functionalities and reasonable measures; handles standard account rectification/deletion requests itself; forwards other requests received directly to the Controller without undue delay |
| Audit | Information on request; compliance shown primarily by independent attestations/certification audit reports (e.g., ISO 27001, SOC 2 Type II); inspections only on substantiated suspicion of breach or if reports are insufficient, preferably in writing/remote, during business hours with reasonable notice; third-party auditors must not be competitors and must sign NDA |
| Audit | Inspections may be carried out by a third party appointed by the Controller; that party must not be a competitor of the Processor and must sign a confidentiality agreement before the inspection |
| Processing on your instructions | only on Controller's documented instructions, unless required by Union or Member State law (Controller informed beforehand unless prohibited) |
| Confidentiality of staff | authorized persons committed to confidentiality or under a statutory obligation of confidentiality |
| Security measures | appropriate technical and organizational measures per Art. 32 GDPR, set out in Appendix 3 |
Terms as the agreement states them. Where it is silent on a term, there is no row; that is not a statement that the vendor does not offer it.
Which version applies
On 2026-11-09, the agreement printed: Version 2.1
at langdock.com
Version 2.1
This version is in our copies from 2026-10-09.
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 Langdock'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 Langdock (Langdock-provided LLMs) | Training on your data | Not used Inputs not used to train any AI when using Langdock-provided LLMs; with own API keys the customer manages the provider relationship | trust.langdock.com | 2026-10-28 |
| Business Langdock Platform | Training on your data | Not used Customer Content not used to develop, train or improve AI models; model providers contractually prohibited too | langdock.com | 2026-10-28 |
| Business Langdock Platform | Zero data retention | With its model providers Zero Data Retention agreed with OpenAI, AWS (Bedrock) and Mistral AI | langdock.com | 2026-10-28 |
| Business Langdock | EU processing | In the EU By default all data processed in the EU with EU-hosted models; admins can enable global-deployment models that may process outside the EU; data at rest always in Germany | trust.langdock.com | 2026-10-28 |
| Business Langdock Platform | EU processing | In the EU Customer can choose models that process and store data only in the EU; global-deployment models may process outside the EU | langdock.com | 2026-10-28 |
| Business Langdock Platform | Model providers | AWS Bedrock | langdock.com | 2026-10-28 |
| Business Langdock Platform | Model providers | Google Cloud Platform | langdock.com | 2026-10-28 |
| Business Langdock Platform | Model providers | Microsoft Azure | langdock.com | 2026-10-28 |
| Business Langdock Platform | Model providers | Mistral AI | langdock.com | 2026-10-28 |
| Business Langdock Platform | Model providers | OpenAI Ireland Ltd. | langdock.com | 2026-10-28 |
Assurance
Does Langdock have a SOC 2 report?
Langdock states SOC 2 Type 2 on its own page, but does not say there how to get a report. We read this on 2026-10-08.
- Claimed “ISO 27001 & SOC 2 Type II”
- Claimed “SOC2 Type II: Independently audited to ensure secure, reliable data handling.”
Source: langdock.com, 2026-10-08
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 Langdock ISO 27001 certified?
Langdock states ISO/IEC 27001 on its own page, but does not say there how to get the certificate. We read this on 2026-10-08.
- Claimed “ISO 27001 & SOC 2 Type II”
Source: langdock.com, 2026-10-08
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 |
|---|---|---|---|---|
| GDPR | Claimed | — | langdock.com | 2026-10-08 |
| ISO 27001 · ISO27001 | Claimed | — | langdock.com | 2026-10-08 |
| SOC 2 Type II · SOC2T2 | Claimed | — | langdock.com | 2026-10-08 |
| SOC2 Type II · SOC2T2 | Claimed | — | langdock.com | 2026-10-08 |
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
- ACN qualified cloud (Italy): checked 2026-11-16, no entry under Langdock; Langdock GmbH
- ISO 27001 on the basis of IT-Grundschutz (BSI, Germany): checked 2026-11-16, no entry under Langdock; Langdock GmbH
- CISPE Data Protection Code of Conduct (GDPR Art. 40): checked 2026-11-16, no entry under Langdock; Langdock GmbH
- DORA critical ICT third-party providers (ESAs): checked 2026-11-16, no entry under Langdock; Langdock GmbH
- Data Privacy Framework List (US): checked 2026-11-16, no entry under Langdock; Langdock GmbH
- ENS certificates of conformity (CCN, Spain): checked 2026-11-16, no entry under Langdock; Langdock GmbH
- EU Cloud Code of Conduct (GDPR Art. 40): checked 2026-11-16, no entry under Langdock; Langdock GmbH
- FedRAMP Marketplace (US): checked 2026-11-16, no entry under Langdock; Langdock GmbH
- GPAI Code of Practice signatories (European Commission): checked 2026-11-16, no entry under Langdock; Langdock GmbH
- SecNumCloud qualified services (ANSSI, France): checked 2026-11-16, no entry under Langdock; Langdock GmbH
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 |
|---|---|---|---|---|---|
| Langdock Desktop | — | Not declared | unknown | docs.langdock.com | 2026-10-11 |
Vulnerability reporting: no security.txt at the well-known path (read 2026-10-17)
How other vendors publish theirs: security.txt across the registry.
Documents
Where is Langdock's trust center?
Langdock publishes a page it calls “Trust Center” at trust.langdock.com. Some of its documents sit behind a request or sign-in. Its text appears only after JavaScript runs: a client without it, as most tooling is, gets an empty page. The page mentions SOC 2, ISO 27001, subprocessors and a DPA. We read it on 2026-11-03. Open trust.langdock.com
- Name “Welcome to Langdock's Trust Center”
- Request step “Request access”
Source: trust.langdock.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 |
| ai-2 | Public | full | 200 | 2026-10-28 |
| certifications | Public | full | 200 | 2026-10-08 |
| dpa | Public | full | 200 | 2026-10-09 |
| lifecycle | Public | full | 200 | 2026-10-11 |
| residency | Public | full | 200 | 2026-10-08 |
| subprocessors | JavaScript only | full | 200 | 2026-10-08 |
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.