Get the weekly research letter
Companies change their terms quietly. We read every version and catch what actually changed. One email a week on the changes that matter and what they mean. No account.
Both parties must comply with U.S. export control and sanctions laws and regulations. Customer warrants it is not listed on U.S. restricted party lists, must screen Users accordingly, and may not use the platform to store, retrieve, or transmit ITAR-controlled technical data.
This analysis describes what LangChain's agreement states, permits, or reserves. It does not constitute a legal determination about enforceability. Regulatory applicability and practical outcomes may vary by jurisdiction, enforcement context, and individual circumstances. Read our methodology
This provision places affirmative compliance obligations on Customer regarding U.S. export control and sanctions screening, including ongoing representation that neither Customer nor its Users are on restricted party lists. The explicit ITAR prohibition is operationally significant for defense, aerospace, and dual-use technology sectors where Customer Data may include controlled technical data.
The updated terms introduce a new deployment architecture option (BYOC) alongside existing Cloud and Hybrid options, giving customers more control over infrastructure placement. LangChain's explicit commitment to not use customer data for large language model training now has clear written language in the Terms, whereas the prior version only referenced 'products' generically. However, the expanded non-warranty clause now states the platform is not warranted to be 'accurate' or 'complete,' which broadens the disclaimers of liability. Customers should review which deployment option aligns with their infrastructure and compliance requirements.
View change record →Under this clause, Customer is responsible for ensuring that all Users are screened against U.S. restricted party lists (including the SDN List and Entity List) and that no ITAR-controlled technical data is processed through the LangSmith Platform. Breach of export control representations is a material breach of the Agreement.
Cross-platform context
See how other platforms handle Export Control Compliance and similar clauses.
Compare across platforms →Monitoring
LangChain has changed this document before.
Receive same-day alerts, structured change summaries, and monitoring for up to 20 platforms.
"Each party will comply with all applicable Export Control and Sanctions Laws and Regulations in connection with providing and using the LangSmith Platform. Without limiting the foregoing, (a) each party represents that it is not listed on any list of entities or individuals who are restricted from receiving U.S. services or items subject to U.S. jurisdiction (including but not limited to the Specially Designated Nationals and Blocked Persons List and the Entity List) nor is it owned or controlled by any such listed entity; (b) Customer will not, and will ensure that Users do not, violate any Export Control and Sanctions Laws and Regulations, or cause any such violation to occur; and (c) Customer will not use or cause any person to use the LangSmith Platform to store, retrieve, or transmit technical data controlled under the U.S. International Traffic in Arms Regulations.Excerpt from LangChain's Terms of Service
(1) REGULATORY LANDSCAPE: This provision implicates the U.S. Export Administration Regulations administered by the Bureau of Industry and Security, the International Traffic in Arms Regulations administered by the Directorate of Defense Trade Controls, and U.S. sanctions programs administered by the Office of Foreign Assets Control. Non-compliance may result in civil and criminal penalties under applicable U.S. law, independent of contractual remedies. (2) GOVERNANCE EXPOSURE: Medium to High for organizations in defense, aerospace, and dual-use technology sectors. Customer's obligation to screen all Users and ensure no ITAR-controlled data is transmitted through the platform requires ongoing compliance programs, not merely a one-time representation at contract execution. (3) JURISDICTION FLAGS: Non-U.S. customers should assess whether re-export obligations under U.S. export control law apply to their use of a U.S.-provided service, particularly for BYOC or Hybrid Deployments that involve transmission of data to LangChain's cloud infrastructure. (4) CONTRACT AND VENDOR IMPLICATIONS: Procurement teams at organizations operating in defense, government contracting, or dual-use technology sectors should assess whether the LangSmith Platform has any export control classification or authorization requirements before processing technical data through the platform. (5) COMPLIANCE CONSIDERATIONS: Export compliance programs should include the LangSmith Platform in restricted party screening workflows covering User onboarding, and should assess whether any Customer Data processed through the platform constitutes ITAR-controlled technical data requiring separate handling.
This provision places affirmative compliance obligations on Customer regarding U.S. export control and sanctions screening, including ongoing representation that neither Customer nor its Users are on restricted party lists. The explicit ITAR prohibition is operationally significant for defense, aerospace, and dual-use technology sectors where Customer Data may include controlled technical data.
Under this clause, Customer is responsible for ensuring that all Users are screened against U.S. restricted party lists (including the SDN List and Entity List) and that no ITAR-controlled technical data is processed through the LangSmith Platform. Breach of export control representations is a material breach of the Agreement.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by LangChain.