Data use, training & retention
How this is scored
What happens to prompts, uploaded files, connected data and outputs: whether any of it trains a model (the vendor's or a model provider's), how long it is kept and where logs live, whether zero-retention is available, and whether a data processing agreement covers it.
0 — No statement on training or retention; the privacy policy is a website policy that does not cover the product.
3 — A general statement that business data is "not used for training", with no word on retention, on the model providers behind the product or on logs.
5 — Business data excluded from training by contract, retention periods stated for chats and files, and a DPA offered to business customers.
8 — No-training commitments stated for the vendor and every model provider it routes to, retention configurable by the admin (including deletion of chat history), zero-data-retention terms with the model providers named, and abuse-monitoring retention described.
10 — Data use fully accounted for: training, retention, logging and abuse monitoring stated per model provider, customer-controlled retention and deletion with an audit trail, outputs and connected data treated as customer data in the DPA, and an independent audit (SOC 2, ISO 27001 or ISO 42001) covering the product.
The Skeptic
The binding terms state that neither Langdock nor any model provider it engages may train on customer content, the DPA is auto-concluded with deletion no later than 30 days after termination, and admins can set the chat retention period, with per-object deletion behaviour documented in the help pages. Zero-data-retention is evidenced for the Azure-hosted models' abuse monitoring, but I found no public information on abuse-monitoring or zero-retention terms for the OpenAI, Google or AWS models, nor an audit trail for deletions — the published SOC 2 Type II and ISO 27001 certificates lift this above a contract-only story, but not to the top. 4 5 7 9 10