Worth Knowing
LangChain Spells It Out, “Including Any Large Language Models”
LangChain’s May 20 ToS update is the kind of revision that reads as routine until you look at what each change does.
Three substantive moves. First: the training opt-out language in Section 4.2 picked up four new words. The prior clause read “LangChain agrees that it will not use Customer Data to train on, develop, or otherwise improve its products.” The updated clause adds: “…including any large language models.” On its face, the addition just closes a possible loophole — but those four words are a meaningful concession in an industry where “our products” and “models we train” have spent two years being negotiated as separate categories.
Second: a new deployment mode was carved out. The Hybrid Deployment definition was rewritten and narrowed to cover only customer-operated installations. The LangChain-managed-without-direct-data-access variant has its own new defined term: “Bring Your Own Cloud Deployment” or “BYOC Deployment” — “a deployment of the LangSmith Platform within Customer Infrastructure in which LangChain operates and manages the LangSmith Platform through cloud provider APIs, without direct access to Customer Data.” That’s a meaningful product distinction for regulated industries: BYOC lets LangChain run the platform without ever holding customer data. It’s now formally a tier.
Third: alongside the protective moves, LangChain also tightened its accuracy disclaimer. Section 6.3 added two words to the list of things LangChain explicitly does not warrant: the platform is no longer warranted to be “accurate, complete,” error-free, or uninterrupted. The first two are new. That is standard enterprise-warranty hygiene rather than a structural retreat, but it’s worth noting because it lands in the same revision as the user-protective changes.
Why this matters: Three changes, two of them creator-favorable, one of them a tightening of warranty language. The training language is now narrow enough to survive a contract review at a data-sensitive customer. The BYOC tier gives LangChain a story to tell financial-services and healthcare prospects who can’t ship customer data to a vendor. The accuracy addition just makes explicit what AS-IS clauses already implied. Worth tracking whether other agent-orchestration platforms follow the BYOC pattern as enterprise procurement teams push back on data-residency.
