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.
For Cloud Deployments, Customer may request data export during the Subscription Term or within thirty days of termination. Upon written request following termination, LangChain must delete all Customer Data within thirty days. No post-termination export right exists for No Charge Access users.
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 establishes the operational procedures and deadlines for Customer Data recovery and deletion following Agreement termination. The export right is limited to Cloud Deployments and requires a written request within thirty days; the deletion obligation requires a separate written request. Both rights are explicitly excluded for No Charge Access users.
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 must submit a written request to export data within thirty days of termination to preserve access to Customer Data on Cloud Deployments; after that window closes, no contractual export right applies. A separate written request triggers LangChain's obligation to delete all Customer Data within thirty days of termination.
Cross-platform context
See how other platforms handle Data Export and Deletion Post-Termination 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.
"During a Subscription Term or within thirty (30) days thereafter upon Customer's written request (subject to Customer's configured retention period), Customer may export Customer Data from Cloud Deployments as described in the Documentation. The thirty (30) day post-termination export right does not apply to No Charge Access. Within thirty (30) days of Customer's written request following termination or expiration of this Agreement, LangChain shall delete all Customer Data in its custody and control.Excerpt from LangChain's Terms of Service
(1) REGULATORY LANDSCAPE: GDPR Article 17 (right to erasure) and Article 20 (right to data portability) may impose statutory deletion and portability obligations on LangChain as a data processor for EU and EEA customers, independent of and potentially broader than the contractual mechanisms described here. The DPA incorporated by reference governs these statutory obligations for Personal Data. CCPA imposes deletion rights for California residents that may similarly operate independently of contractual timelines. (2) GOVERNANCE EXPOSURE: Medium. The thirty-day export window for Cloud Deployments creates a hard deadline that requires proactive action by Customer at the time of termination. Organizations with complex data environments or lengthy offboarding timelines should assess whether thirty days is operationally sufficient and whether contractual extensions can be negotiated in Order Forms. (3) JURISDICTION FLAGS: EU and EEA customers should verify that the DPA's data subject rights procedures address portability and erasure timelines consistent with GDPR requirements, as the base Agreement's thirty-day windows may not fully satisfy statutory obligations in all EU member states. (4) CONTRACT AND VENDOR IMPLICATIONS: Offboarding procedures for enterprise deployments should include written data export and deletion requests as standard steps at termination. Procurement teams should confirm whether Self-Hosted or BYOC Deployment customers face different data export procedures, as the export right is specified only for Cloud Deployments. (5) COMPLIANCE CONSIDERATIONS: Data retention policies should be reviewed for alignment with the thirty-day post-termination window, and offboarding runbooks should include the written request mechanism to trigger both export and deletion rights under this provision.
This provision establishes the operational procedures and deadlines for Customer Data recovery and deletion following Agreement termination. The export right is limited to Cloud Deployments and requires a written request within thirty days; the deletion obligation requires a separate written request. Both rights are explicitly excluded for No Charge Access users.
Under this clause, Customer must submit a written request to export data within thirty days of termination to preserve access to Customer Data on Cloud Deployments; after that window closes, no contractual export right applies. A separate written request triggers LangChain's obligation to delete all Customer Data within thirty days of termination.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by LangChain.