From 757cf0dd42d170aaa3da189dd6231987153e56e0 Mon Sep 17 00:00:00 2001 From: Marc Klingen Date: Thu, 25 Jun 2026 12:21:56 +0200 Subject: [PATCH 1/5] update privacy and some email addresses --- .../blog/2025-04-30-langfuse-april-update.mdx | 2 - .../fifteen-questions-langfuse-answered.mdx | 2 +- content/marketing/cookie-policy.mdx | 2 +- content/marketing/privacy.mdx | 37 ++++++++----------- content/marketing/terms.mdx | 2 +- content/security/compliance-faq.mdx | 2 +- content/security/dpa.mdx | 4 +- content/security/gdpr.mdx | 4 +- content/security/index.mdx | 6 +-- content/security/nda.mdx | 4 +- content/security/privacy-faq.mdx | 2 +- content/security/whistleblowing.mdx | 4 +- 12 files changed, 32 insertions(+), 39 deletions(-) diff --git a/content/blog/2025-04-30-langfuse-april-update.mdx b/content/blog/2025-04-30-langfuse-april-update.mdx index e10af82016..c05110c691 100644 --- a/content/blog/2025-04-30-langfuse-april-update.mdx +++ b/content/blog/2025-04-30-langfuse-april-update.mdx @@ -68,8 +68,6 @@ Being able to create custom dashboards on top of Langfuse data has been one of t We're excited to offer HIPAA-compliant Langfuse Cloud instances! This enables healthcare organizations to safely use Langfuse Cloud while ensuring patient data remains secure and confidential. -→ Reach out to hipaa@langfuse.com for access to the Langfuse HIPAA Cloud. - ## đŸ› ïž Tool Calling & Structured Outputs diff --git a/content/faq/all/fifteen-questions-langfuse-answered.mdx b/content/faq/all/fifteen-questions-langfuse-answered.mdx index 2053b6475c..087abc26de 100644 --- a/content/faq/all/fifteen-questions-langfuse-answered.mdx +++ b/content/faq/all/fifteen-questions-langfuse-answered.mdx @@ -65,7 +65,7 @@ As a fallback, you can always use [our API](/docs/api) to ingest data into Langf ## 7. Can Langfuse provide a DPA to its customers? -**Yes, Langfuse can provide customers with a DPA.** We are happy to enter into Data Protection Agreements with customers on our paid plans. Please navigate to our [Security Center](/security/gdpr) to review our DPA template. Please download it, sign it and send a signed version to privacy@langfuse.com. We will then counter-sign the DPA and send it back to you. +**Yes, Langfuse can provide customers with a DPA.** We are happy to enter into Data Protection Agreements with customers on our paid plans. Please navigate to our [Security Center](/security/gdpr) to review our DPA template. ## 8. Is Langfuse SOC2 Type2 certified? diff --git a/content/marketing/cookie-policy.mdx b/content/marketing/cookie-policy.mdx index 05780b9d14..33df31d513 100644 --- a/content/marketing/cookie-policy.mdx +++ b/content/marketing/cookie-policy.mdx @@ -72,7 +72,7 @@ The date at the top of this Cookie Policy indicates when it was last updated. ## Where can I get further information? -If you have any questions about our use of cookies or other technologies, please email us at legal@langfuse.com or by post to: +If you have any questions about our use of cookies or other technologies, please email us at legal@clickhouse.com or by post to: Langfuse GmbH
Oranienburgerstraße 91
diff --git a/content/marketing/privacy.mdx b/content/marketing/privacy.mdx index 3b26baafe2..d48d188521 100644 --- a/content/marketing/privacy.mdx +++ b/content/marketing/privacy.mdx @@ -4,14 +4,14 @@ title: Privacy Policy # Privacy Policy -**Last updated June 19th, 2026 | download as PDF** +**Last updated June 25th, 2026 | download as PDF** -This privacy notice for **Langfuse GmbH** ("**we**," "**us**," or "**our**"), describes how and why we might collect, store, use, and/or share ("**process**") your information when you use our services ("**Services**"), such as when you: +This privacy notice for **ClickHouse, Inc.** ("**we**," "**us**," or "**our**"), describes how and why we might collect, store, use, and/or share ("**process**") your information when you interact with our Langfuse-branded services ("**Services**"), such as when you: -- Visit our website at [https://www.langfuse.com](https://www.langfuse.com), use our Cloud Service or any website of ours that links to this privacy notice -- Engage with us in other related ways, including any sales, marketing, or events +- Visit our website at [https://www.langfuse.com](https://www.langfuse.com), use the Langfuse Cloud Service or any website of ours that links to this privacy notice +- Engage with us in other related ways, including any sales, marketing, or events for Langfuse products and services -**Questions or concerns?** Reading this privacy notice will help you understand your privacy rights and choices. If you do not agree with our policies and practices, please do not use our Services. If you still have any questions or concerns, please contact us at **legal@langfuse.com**. +**Questions or concerns?** Reading this privacy notice will help you understand your privacy rights and choices. If you do not agree with our policies and practices, please do not use our Services. Note that we maintain separate privacy policies and practices for ClickHouse-branded services (e.g., ClickHouse Cloud), which are different from those outlined in this Privacy Policy. For more information about those privacy policies and practices, visit: [https://clickhouse.com/legal/privacy-policy](https://clickhouse.com/legal/privacy-policy). If you still have any questions or concerns, please contact us at [**privacy@clickhouse.com**](mailto:privacy@clickhouse.com). ## Summary of Key Points @@ -146,7 +146,7 @@ The General Data Protection Regulation (GDPR) and UK GDPR require us to explain - **Legal Obligations.** We may process your information where we believe it is necessary for compliance with our legal obligations, such as to cooperate with a law enforcement body or regulatory agency, exercise or defend our legal rights, or disclose your information as evidence in litigation in which we are involved. - **Vital Interests.** We may process your information where we believe it is necessary to protect your vital interests or the vital interests of a third party, such as situations involving potential threats to the safety of any person. -In legal terms, we are generally the "data controller" under European data protection laws of the personal information described in this privacy notice, since we determine the means and/or purposes of the data processing we perform. This privacy notice does not apply to the personal information we process as a "data processor" on behalf of our customers. In those situations, the customer that we provide services to and with whom we have entered into a [data processing agreement](/security) is the "data controller" responsible for your personal information, and we merely process your information on their behalf in accordance with your instructions. If you want to know more about our customers' privacy practices, you should read their privacy policies and direct any questions you have to them. +In legal terms, we are generally the "data controller" under European data protection laws of the personal information described in this privacy notice, since we determine the means and/or purposes of the data processing we perform. This privacy notice does not apply to the personal information we process as a "data processor" on behalf of our customers. In those situations, the customer that we provide services to and with whom we have entered into a [data processing agreement](https://clickhouse.com/legal/agreements/data-processing-addendum) is the "data controller" responsible for your personal information, and we merely process your information on their behalf in accordance with your instructions. If you want to know more about our customers' privacy practices, you should read their privacy policies and direct any questions you have to them. ### If you are located in Canada, this section applies to you. @@ -197,7 +197,6 @@ We may share your data with third-party vendors, service providers, contractors, - Cloudflare - **Communicate and Chat with Users** - Slack - - Plain.com - Pylon - Inkeep - GitHub @@ -266,7 +265,7 @@ We have implemented appropriate and reasonable technical and organizational secu under 18 years of age. -We do not knowingly solicit data as data controller from or market to children under 18 years of age. By using the Services, you represent that you are at least 18 or that you are the parent or guardian of such a minor and consent to such minor dependent's use of the Services. If you become aware of any data we may have collected from children under age 18, please contact us at **legal@langfuse.com**. +We do not knowingly solicit data as data controller from or market to children under 18 years of age. By using the Services, you represent that you are at least 18 or that you are the parent or guardian of such a minor and consent to such minor dependent's use of the Services. If you become aware of any data we may have collected from children under age 18, please contact us at **[legal@clickhouse.com](mailto:legal@clickhouse.com)**. ## 10. What Are Your Privacy Rights? [#privacyrights] @@ -310,7 +309,7 @@ Please find more information on how to delete your account [here](/faq/all/delet Most Web browsers are set to accept cookies by default. If you prefer, you can usually choose to set your browser to remove cookies and to reject cookies. If you choose to remove cookies or reject cookies, this could affect certain features or services of our Services. For further information, please see our [Cookie Policy](/cookie-policy). -If you have questions or comments about your privacy rights, you may email us at **legal@langfuse.com**. +If you have questions or comments about your privacy rights, you may email us at **[privacy@clickhouse.com](mailto:privacy@clickhouse.com)**. ## 11. Controls for Do-Not-Track Features [#dnt] @@ -387,20 +386,16 @@ to be informed of how we are protecting your information. ## 14. How Can You Contact Us About This Notice? [#contact] -If you have questions or comments about this notice, you may email us at **legal@langfuse.com** or contact us by post at: +If you have questions or comments about this notice, you may email us at **[legal@clickhouse.com](mailto:legal@clickhouse.com)** or contact us by post at: -Langfuse GmbH\ -Oranienburgerstraße 91\ -10178 Berlin\ -Germany +ClickHouse, Inc. +c/o Goodwin Proctor LLP +601 Marshall St +Redwood City, CA 94063 +Attn: Privacy Practice Group -If you are a resident in the European Economic Area, we are the "data controller" of your personal information. We have appointed **Langfuse GmbH** to be our representative in the EEA. You can contact them directly regarding our processing of your information, by email at **legal@langfuse.com**, by visiting [https://langfuse.com](https://langfuse.com), by phone at **+49 0152 08459573**, or by post to: - -Langfuse GmbH\ -Oranienburgerstraße 91\ -10178 Berlin\ -Germany +If you are a resident in the European Economic Area, we are the "data controller" of your personal information. ## 15. How Can You Review, Update, or Delete the Data We Collect From You? [#review] -Based on the applicable laws of your country, you may have the right to request access to the personal information we collect from you, change that information, or delete it. To request to review, update, or delete your personal information, please submit a [data subject access request](/security/gdpr). +Based on the applicable laws of your country, you may have the right to request access to the personal information we collect from you, change that information, or delete it. To request to review, update, or delete your personal information, please submit a data subject access request to privacy@clickhouse.com. diff --git a/content/marketing/terms.mdx b/content/marketing/terms.mdx index 3936af035d..92cc513819 100644 --- a/content/marketing/terms.mdx +++ b/content/marketing/terms.mdx @@ -180,7 +180,7 @@ LIMITATION OF LIABILITY. EACH PARTY'S TOTAL AGGREGATE LIABILITY (TOGETHER WITH I 4. Publicity. Only with Client's prior consent, Langfuse may use Client's name and logo to identify Client as a customer on Langfuse's website and in marketing materials. Client may revoke consent at any time by notice. -5. Notices. Legal notices must be sent by email: to Client at the primary email associated with the account, and to Langfuse at [legal@langfuse.com](mailto:legal@langfuse.com). Notices are deemed given when the sending server records transmission. Operational and product notices (including price changes) may be given in‑product or by email to the account admin. +5. Notices. Legal notices must be sent by email: to Client at the primary email associated with the account, and to Langfuse at [legal@clickhouse.com](mailto:legal@clickhouse.com). Notices are deemed given when the sending server records transmission. Operational and product notices (including price changes) may be given in‑product or by email to the account admin. 6. Survival. Sections 3 (to the extent restricting use), 4 (Confidentiality), 6 (Client Data), 7 (Warranty – disclaimers), 8 (Liability), 9 (Indemnities), 11.4–11.6, and 12 (Miscellaneous) survive. diff --git a/content/security/compliance-faq.mdx b/content/security/compliance-faq.mdx index 5ed32977cd..801de1e395 100644 --- a/content/security/compliance-faq.mdx +++ b/content/security/compliance-faq.mdx @@ -7,7 +7,7 @@ description: Answers to common questions about Langfuse's compliance practices. This page addresses frequently asked questions and common compliance topics for Langfuse. Please refer to [security FAQs](/security/security-faq) for details on security topics. -If you don't find a solution to your issue here, try using [Ask AI](/docs/ask-ai) for instant answers or reach out to security@langfuse.com +If you don't find a solution to your issue here, try using [Ask AI](/docs/ask-ai) for instant answers or reach out to legal@clickhouse.com ## Compliance & Certifications diff --git a/content/security/dpa.mdx b/content/security/dpa.mdx index b9f355ec18..be8b7bd01e 100644 --- a/content/security/dpa.mdx +++ b/content/security/dpa.mdx @@ -142,7 +142,7 @@ Langfuse will provide at least 30 days' notice (via email) of any modification. ## 13. Notices -**Method of notice.** All legal notices under this DPA are to be sent (i) to Client at the primary email address associated with the account used to subscribe to the Solution, and (ii) to Langfuse at legal@langfuse.com. Notices are deemed received when the sending server records transmission. Notices are governed by the Main Contract's notice clause. +**Method of notice.** All legal notices under this DPA are to be sent (i) to Client at the primary email address associated with the account used to subscribe to the Solution, and (ii) to Langfuse at legal@clickhouse.com. Notices are deemed received when the sending server records transmission. Notices are governed by the Main Contract's notice clause. ## Execution @@ -210,7 +210,7 @@ Please refer to Section 4 of this DPA for further information on subprocessing. - **Data exporter:** the Client as identified in the Main Contract, including its legal name, registered address and contact details as recorded therein; role: Controller (and/or Processor for onward transfers as applicable). -- **Data importer:** Langfuse GmbH, Oranienburgerstraße 91, 10178 Berlin, Germany; privacy@langfuse.com; legal@langfuse.com; role: Processor. +- **Data importer:** Langfuse GmbH, Oranienburgerstraße 91, 10178 Berlin, Germany; privacy@langfuse.com; legal@clickhouse.com; role: Processor. _(Additional Langfuse entities and/or sub‑processors may accede pursuant to Clause 7 by executing an accession; no further Client action is required.)_ diff --git a/content/security/gdpr.mdx b/content/security/gdpr.mdx index 137c4087aa..2c4d5ff98a 100644 --- a/content/security/gdpr.mdx +++ b/content/security/gdpr.mdx @@ -15,10 +15,10 @@ More information: ## Contact -For questions regarding GDPR compliance or data privacy, please contact privacy@langfuse.com. +For questions regarding GDPR compliance or data privacy, please contact privacy@clickhouse.com. ## Data Subject Access Request (DSAR) Under applicable data protection laws, you may have the right to request access to and receive information about the personal data we maintain about you, to update and correct inaccuracies in your personal data, to restrict or object to the processing of your personal data, to have the information anonymized or deleted, as appropriate, or to exercise your right to data portability. -To submit a Data Subject Access Request, please email us at [privacy@langfuse.com](mailto:privacy@langfuse.com). We will respond to your request within the time limits established by applicable law. +To request to review, update, or delete your personal information, please submit a data subject access request to privacy@clickhouse.com. diff --git a/content/security/index.mdx b/content/security/index.mdx index 69f8cfa3ec..4a0f755d6f 100644 --- a/content/security/index.mdx +++ b/content/security/index.mdx @@ -55,9 +55,9 @@ Langfuse is [GDPR](/security/gdpr) compliant, and offers data retention, data ma ## Contact - Use [Ask AI](/ask-ai) to get instant answers to your questions. -- For security inquiries: security@langfuse.com -- For privacy inquiries: privacy@langfuse.com -- For compliance inquiries: compliance@langfuse.com +- For security inquiries: security@clickhouse.com +- For privacy inquiries: privacy@clickhouse.com +- For legal inquiries: legal@clickhouse.com ## General Information on Langfuse diff --git a/content/security/nda.mdx b/content/security/nda.mdx index 486ad46472..681ed25fe5 100644 --- a/content/security/nda.mdx +++ b/content/security/nda.mdx @@ -7,7 +7,7 @@ description: Request a NDA (Non Disclosure Agreement) with Langfuse ## Request an NDA with Langfuse -During procurement and onboarding, users sometimes request an NDA (Non Disclosure Agreement) with Langfuse. We have a standard NDA template that you can find below. You can request signature of this NDA by sending an email to legal@langfuse.com. Please include a few sentences about the purpose of the NDA. +During procurement and onboarding, users sometimes request an NDA (Non Disclosure Agreement) with Langfuse. We have a standard NDA template that you can find below. You can request signature of this NDA by sending an email to legal@clickhouse.com. Please include a few sentences about the purpose of the NDA. **Latest revision:** October 17th, 2025 | **download as PDF** @@ -20,7 +20,7 @@ This Mutual Non-Disclosure Agreement (the "Agreement") is entered into by and be **Party 1:**\ Langfuse GmbH\ Oranienburgerstraße 91, 10178 Berlin, Germany\ -Notices to: legal@langfuse.com +Notices to: legal@clickhouse.com **Party 2:**\ [Counterparty Name] \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ diff --git a/content/security/privacy-faq.mdx b/content/security/privacy-faq.mdx index 73d3e3bd38..9209a80fa8 100644 --- a/content/security/privacy-faq.mdx +++ b/content/security/privacy-faq.mdx @@ -7,7 +7,7 @@ description: Answers to common questions about Langfuse's privacy practices. This page addresses frequently asked questions and common privacy topics for Langfuse. -If you don't find a solution to your issue here, try using [Ask AI](/docs/ask-ai) for instant answers or reach out to privacy@langfuse.com +If you don't find a solution to your issue here, try using [Ask AI](/docs/ask-ai) for instant answers or reach out to privacy@clickhouse.com > **Do you use customer data to train AI models?** diff --git a/content/security/whistleblowing.mdx b/content/security/whistleblowing.mdx index 57a610749d..eb96a4b9b1 100644 --- a/content/security/whistleblowing.mdx +++ b/content/security/whistleblowing.mdx @@ -11,7 +11,7 @@ Langfuse encourages employees and third parties to report potential breaches of You can report concerns via: -- **Email:** [legal@langfuse.com](mailto:legal@langfuse.com) +- **Email:** [legal@clickhouse.com](mailto:legal@clickhouse.com) - **Postal Mail:** Address available [here](/imprint). ## Confidentiality & Anonymity @@ -24,4 +24,4 @@ For more detailed information, Langfuse employees can refer to the company's int ## Contact -For inquiries specifically related to whistleblowing, please use the channels mentioned above or contact legal@langfuse.com. +For inquiries specifically related to whistleblowing, please use the channels mentioned above or contact legal@clickhouse.com. From 9bbe0173dd92efc83759449ce980c9705ff89ad9 Mon Sep 17 00:00:00 2001 From: Marc Klingen Date: Thu, 25 Jun 2026 13:34:50 +0200 Subject: [PATCH 2/5] update legal links --- components/home/pricing/PricingTable.tsx | 2 +- components/inkeep/floating-ask-ai-bar.tsx | 1 - components/japan/JapanLanding.tsx | 6 +- content/handbook/chapters/why.mdx | 2 +- .../how-to-answer-support-questions.mdx | 6 +- content/marketing/meta.json | 1 - content/marketing/terms.mdx | 216 -------------- content/security/compliance-faq.mdx | 2 +- content/security/data-regions.mdx | 2 +- content/security/dpa.mdx | 269 ------------------ content/security/gdpr.mdx | 2 +- content/security/hipaa.mdx | 2 +- content/security/index.mdx | 4 +- content/security/meta.json | 6 +- content/security/privacy-faq.mdx | 2 +- content/security/subprocessors.mdx | 68 ----- content/security/toms.mdx | 177 ------------ lib/redirects.js | 22 ++ 18 files changed, 40 insertions(+), 750 deletions(-) delete mode 100644 content/marketing/terms.mdx delete mode 100644 content/security/dpa.mdx delete mode 100644 content/security/subprocessors.mdx delete mode 100644 content/security/toms.mdx diff --git a/components/home/pricing/PricingTable.tsx b/components/home/pricing/PricingTable.tsx index 2a4f2edca3..db4721df60 100644 --- a/components/home/pricing/PricingTable.tsx +++ b/components/home/pricing/PricingTable.tsx @@ -1233,7 +1233,7 @@ const sections: Section[] = [ }, { name: "Data processing agreement (GDPR)", - href: "/security/dpa", + href: "/dpa", tiers: { cloud: { Hobby: true, Core: true, Pro: true, Enterprise: true }, }, diff --git a/components/inkeep/floating-ask-ai-bar.tsx b/components/inkeep/floating-ask-ai-bar.tsx index 97d4d484ee..84b08ed0bf 100644 --- a/components/inkeep/floating-ask-ai-bar.tsx +++ b/components/inkeep/floating-ask-ai-bar.tsx @@ -33,7 +33,6 @@ const ASK_AI_BAR_HIDDEN_PATHS: ReadonlyArray = [ /^\/privacy(\/|$)/, /^\/terms(\/|$)/, /^\/cookie-policy(\/|$)/, - /^\/security\/dpa(\/|$)/, // App proxy /^\/cloud(\/|$)/, // Custom-designed regional / annual landing pages diff --git a/components/japan/JapanLanding.tsx b/components/japan/JapanLanding.tsx index 2b67160ad1..8248a60434 100644 --- a/components/japan/JapanLanding.tsx +++ b/components/japan/JapanLanding.tsx @@ -748,7 +748,7 @@ function Compliance() { DPA ↗ @@ -902,8 +902,8 @@ function FAQ() {

äž»èŠă‚”ăƒ–ăƒ—ăƒ­ă‚»ăƒƒă‚”ăƒŒïŒˆăƒȘăƒŒă‚žăƒ§ăƒłć†…ïŒ‰: AWS ず ClickHouse ă€‚ă©ăĄă‚‰ă‚‚æ—„æœŹă§çšŒćƒă—ăŠă„ăŸă™ă€‚æœ€æ–°ăźäž€èŠ§ăŻ{" "} - - langfuse.com/security/subprocessors + + langfuse.com/subprocessors {" "} ă«ă‚ă‚ŠăŸă™ă€‚

diff --git a/content/handbook/chapters/why.mdx b/content/handbook/chapters/why.mdx index 7b9c338bc5..cfdf4446dd 100644 --- a/content/handbook/chapters/why.mdx +++ b/content/handbook/chapters/why.mdx @@ -88,7 +88,7 @@ import EnterpriseCloudScale from "@/components-mdx/enterprise-cloud-scale.mdx"; - We take security and compliance seriously. - **Certifications**: Langfuse Cloud is [SOC 2 Type II](/security/soc2) and [ISO 27001](/security/iso27001) certified. -- **Privacy**: [GDPR](/security/gdpr) compliant with [DPA](/security/dpa) available. [HIPAA](/security/hipaa) aligned with BAA available. +- **Privacy**: [GDPR](/security/gdpr) compliant with [DPA](/dpa) available. [HIPAA](/security/hipaa) aligned with BAA available. - **Data Regions**: Choose between US, EU, or HIPAA-ready data regions on Langfuse Cloud—or [self-host](/self-hosting) anywhere. - **Data Control**: [Data masking](/docs/observability/features/masking), [data retention](/docs/administration/data-retention), and [data deletion](/docs/administration/data-deletion) capabilities. - More details in our [Security & Privacy Center](/security). diff --git a/content/handbook/support/how-to-answer-support-questions.mdx b/content/handbook/support/how-to-answer-support-questions.mdx index f628c51a96..816064428e 100644 --- a/content/handbook/support/how-to-answer-support-questions.mdx +++ b/content/handbook/support/how-to-answer-support-questions.mdx @@ -901,7 +901,7 @@ Best, **Triage steps:** -1. Direct the customer to [langfuse.com/security/dpa](https://langfuse.com/security/dpa), the PDF there is the executed version. +1. Direct the customer to [langfuse.com/dpa](https://langfuse.com/dpa), where the current DPA is published. 2. If they explicitly need a counter-signed copy on their template, route to the enterprise team. **Reply template:** @@ -909,9 +909,9 @@ Best, ```text Hi {name}, -Our DPA is auto-applied for all signups under the standard Terms. You can download the executed version directly here for your records: +Our DPA is auto-applied for all signups under the standard Terms. You can find the current version here for your records: -https://langfuse.com/security/dpa +https://langfuse.com/dpa If your procurement requires a counter-signed copy on your template, let me know and I'll loop in our enterprise team. diff --git a/content/marketing/meta.json b/content/marketing/meta.json index fefad1102f..0cf7eec5b6 100644 --- a/content/marketing/meta.json +++ b/content/marketing/meta.json @@ -21,7 +21,6 @@ "startups", "support", "talk-to-us", - "terms", "watch-demo", "wrapped" ] diff --git a/content/marketing/terms.mdx b/content/marketing/terms.mdx deleted file mode 100644 index 92cc513819..0000000000 --- a/content/marketing/terms.mdx +++ /dev/null @@ -1,216 +0,0 @@ ---- -title: Terms and Conditions ---- - -# Terms and Conditions - -See old T&C versions and Self-Hosting T&Cs at the [bottom](#archive) of this page. - ---- - -## Langfuse Cloud Terms and Conditions (T\&Cs) - -**Latest revision:** October 17th, 2025 | **download as PDF** - - - -**At a glance** — This is your main contract with Langfuse. It sets the rules for using our cloud solution: you pay for a subscription, we provide the service. You own your data; we use it only to deliver and improve the Solution. Some plans are free, most are paid, and fees/renewals are transparent. Either side can end the contract (you at the end of any billing cycle, us with notice or for cause). We keep confidentiality, protect your data, and commit not to sell or misuse it. Liability is capped, with standard exceptions. If we need to change terms, we'll give you 30 days' notice — you can walk away with a refund if you don't agree.\ -Most customers subscribe self-serve via the in-product checkout—no separate signatures are needed; enterprise customers may use a separately executed Order Form. - - - -### 1. GENERAL - -1. These Terms and Conditions ('**Agreement**' or '**T\&Cs**'), together with (a) the Data Processing Agreement ('**DPA**') available at [https://langfuse.com/security/dpa](https://langfuse.com/security/dpa) (incorporated by reference and applicable whenever Client provides Client Personal Data (as defined in the DPA) to Langfuse) and (b) if Client is provisioned on Langfuse's HIPAA instance and meets the eligibility requirements set out in the Business Associate Agreement ('**BAA**') available at [https://langfuse.com/security/hipaa](https://langfuse.com/security/hipaa) (incorporated by reference), form the entire contract between Langfuse GmbH ('**Langfuse**') and the respective client ('**Client**'). Langfuse and its Affiliates may perform obligations under these T\&Cs; Langfuse remains responsible for their performance. Engagement of Affiliates that process Personal Data is also subject to the DPA's subprocessor terms. - -2. Precedence. If there is a conflict on the same subject matter: (1) for PHI, the BAA controls; (2) for Personal Data (excluding PHI), the DPA controls; otherwise, these T\&Cs controls. Where information qualifies as both PHI and Personal Data, the BAA controls and the DPA applies only where not inconsistent with the BAA. - -3. The application of Client's terms and conditions is excluded. Deviating, conflicting or supplementary terms and conditions of Client shall only become part of the Agreement if and to the extent that Langfuse has expressly agreed to their validity in writing. This requirement of written consent also applies if Langfuse accepts Client's payments without reservation, provides the service without reservation and in full knowledge of Client's terms and conditions and in other similar circumstances. - -4. The Solution and associated services provided hereunder are exclusively intended for clients acting in a business capacity. By using the Solution, Client confirms that it acts in a business capacity. By signing up, accessing, or using the Solution, Client indicates its acceptance of this Agreement and agrees to be bound by the terms and conditions of this Agreement. The person accessing or using the Solution on behalf of the Client represents that they are authorized to accept this Agreement on behalf of the Client. - -5. Except as expressly permitted under the DPA (and, for PHI, under the BAA while provisioned on the HIPAA Cloud), Client will not intentionally submit: (i) Special Categories of Personal Data under GDPR Articles 9–10; (ii) Sensitive Personal Information as defined by the CPRA/CCPA; (iii) government‑issued identifiers, full financial account numbers, or precise geolocation; or (iv) data about children under 16 where parental consent has not been obtained. If Client submits such data in breach of this Agreement, Langfuse has no liability arising from such submission and may suspend processing of the affected data; this does not limit remedies under the DPA or BAA where applicable. - -6. Langfuse develops software, a material part of which is developed as open-source software and made available to the public via an open repository. In addition, Langfuse offers a software as a service (SaaS) Solution under this Agreement based on open-source software and, if applicable, additional functionalities or features. This Agreement exclusively establishes the rights and obligations associated with said SaaS Solution and is not intended to, and does not, limit any rights to open-source software code under the terms of any open-source license. - -7. **Global Definitions** - 1. 'Client Data' means any data or content submitted to or collected by the Solution from or on behalf of Client. - - 2. 'Client Personal Data' has the meaning given in the DPA and is a subset of Client Data. - - 3. 'PHI' has the meaning given in the BAA and is a subset of Client Data; for clarity, PHI may also constitute personal data under certain laws, but where information qualifies as both PHI and personal data, the BAA controls to the extent of any inconsistency. - - 4. 'Solution‑Generated Data' means usage, telemetry and metadata generated by the Solution; Solution‑Generated Data does not include Client Personal Data or PHI. - - 5. 'Billing Cycle' means the recurring subscription interval selected by Client (e.g., monthly or annual). - - 6. 'Affiliate' means any entity that controls, is controlled by, or is under common control with a party. - - 7. 'Order Form' means (a) for self-serve plans, the selections Client makes and confirms in the in-product checkout/upgrade flow (including plan, Billing Cycle, and any add-ons) as displayed at or after checkout; and (b) for enterprise plans, a separately executed order form, statement of work, or similar document signed by both parties. For self-serve plans, no separate signature is required. - - 8. Capitalized terms not defined here have the meanings given in these T\&Cs, DPA or BAA within their scopes. - -### 2. SOLUTION - -1. Langfuse operates a software as a service (SaaS) Solution which provides monitoring, analytics and development tools for businesses engaged in software development and operations pertaining to large language and other generative artificial intelligence (AI) and machine learning models (the '**Solution**'). Langfuse operates multiple instances of the Solution, including its U.S. cloud, HIPAA cloud, and EU cloud, each subject to the terms and governing law set out in this Agreement. Client may only use the Solution for its own business activities. If the Parties have agreed upon a specific number of authorised users, the Solution may only be used by the agreed number of users. - -2. During the Subscription Term, Langfuse will provide the services identified in the Order Form in accordance with the Documentation and if applicable the SLA. Langfuse may update or modify the services from time to time; however, Langfuse will not materially decrease the overall functionality or security of the services provided to Client during the then-current Subscription Term. Public website materials are descriptive and may change; material reductions will follow notice and termination rights. - -3. Langfuse may, at its own discretion, temporarily block Client's access to the Solution as a whole or to individual parts thereof if there are concrete circumstances indicating that Client is violating or has violated the terms of the Agreement, or if Langfuse has another legitimate interest in blocking the access. Langfuse shall give the legitimate interests of Client due consideration before blocking the access. Langfuse shall notify Client of any such blocking and restore access without undue delay if the corresponding circumstances justifying the blocking are no longer present. If Client repeatedly violates the terms of the Agreement despite being notified, Langfuse reserves the right to block access permanently and to terminate the Agreement without notice for good cause. - -4. Langfuse may, without being obliged to do so, update, amend and/or further develop the Solution (each, a '**Release**') at any time, in particular to reflect new legal, technical and/or other relevant developments. Langfuse shall take Client's legitimate interests into consideration when implementing such a Release and in each case in good time inform Client and/or in any other appropriate form disclose such Release, if the Client may reasonably expect such information and/or disclosure in consideration of the content, scope and/or impact of the Release. - -### 3. SUBSCRIPTION, FEES, AND INVOICING - -1. For self-serve plans, the Client's selections and confirmation in the in-product checkout/upgrade flow constitute the Order Form for purposes of these T\&Cs; no countersignature is required. If the parties separately agree on bespoke terms these shall take precedence over this agreement. The Solution is contracted and billed on a subscription basis ('**Subscription**'). A subscription terminates with the end of the term of the Agreement pursuant to section 11 (term and termination). - -2. **Taxes.** Fees are exclusive of taxes. Client will pay all applicable sales, use, VAT/GST and similar taxes (excluding taxes on Langfuse's income). - -3. A valid payment method, including credit card, is required to process the payment for Client's Subscription. Client shall provide Langfuse with accurate and complete billing information and a valid payment method. By submitting such payment information, Client authorizes Langfuse to charge all Subscription fees incurred through Client's account to any such payment instruments. Should automatic billing fail to occur for any reason, Langfuse will issue an electronic invoice indicating that Client must proceed manually to settle the full payment within fourteen (14) days as indicated on the invoice. - -4. Langfuse may update pricing effective on renewal of the then‑current Subscription term, with at least 30 days' prior notice. Mid‑term changes apply only to (i) add‑ons Client elects, (ii) usage‑based overages per published rates, or (iii) changes in taxes. If Langfuse must implement a material mid‑term change for legal or regulatory reasons, Client may terminate the affected Subscription within 30 days of notice and receive a pro‑rated refund of pre‑paid fees for the terminated portion. - -5. Free Tier and Free Trial. Langfuse may, at its sole discretion, provide either (a) a free subscription tier (e.g. currently the 'Hobby' plan), or (b) a time-limited free trial of certain paid plan features (each, a 'Free Offer'). - 1. Free Tier (Hobby Plan). The Free Tier is provided without charge and does not automatically convert into a paid subscription. Client will only incur charges if it affirmatively upgrades to a paid plan. - - 2. Free Trials of Paid Plans. For Free Trials of paid plans, Client may be required to provide billing information at registration. Billing will not occur until the Free Trial expires. Unless Client cancels prior to expiration, the subscription will automatically convert to the selected paid plan, and Client will be charged the applicable fees beginning on the final day of the Free Trial period. - - 3. Modifications and Disclaimers. Langfuse may modify or discontinue any Free Offer at any time and in its sole discretion, with or without notice. Free Offers are provided 'AS IS' and without warranty, support, indemnity, or liability by Langfuse. - -### 4. CONFIDENTIALITY - -1. The parties have exchanged or will exchange certain confidential information under this Agreement. Considering the foregoing, the parties agree to the rights and obligations set forth in this section (collectively, the '**Confidentiality Provisions**'). Confidential Information means any information in any form (e.g., oral, written, electronic) in the confidentiality of which the relevant party may have a legitimate interest (including, but not limited to, trade secrets, IP Rights, business strategies and/or plans) (collectively, '**Confidential Information**'). - -2. Unless otherwise expressly agreed in the Confidentiality Provisions, all Confidential Information exchanged between the parties shall be treated as strictly confidential. The parties agree to disclose Confidential Information in each case only for the purposes of this Agreement, with due care and to the extent necessary. - -3. Confidential Information shall not include information in respect of which the party invoking this exception can prove that (i) the information is or becomes part of the public domain through no breach of the receiving party, (ii) it has become aware of the information independently of the other party and without breach of confidentiality obligations and/or (iii) has been released in writing by the other party. - -4. Compelled Disclosure. Each party is entitled to disclose Confidential Information without the prior consent of the other party to the extent that it is required to do so by law, official order, or final court order and has (if permissible) informed the other party in writing of the intended disclosure and has taken reasonable precautions to keep the scope of the disclosure as narrow as possible. - -5. Each party shall protect the confidentiality of the other party's Confidential Information with at least the same degree of care it uses to protect its own confidential and sensitive information, and in no event less than a reasonable standard of care. Confidential Information will not be shared, sold, or used for any purpose other than fulfilling this Agreement. - -6. A party may disclose Confidential Information, without prior written consent, only to the extent reasonably necessary to perform its obligations under this Agreement and only to: - 1. its directors, officers, and employees who need to know the information and are bound by confidentiality obligations no less protective than those set forth here; - - 2. its affiliates and their respective directors, officers, and employees under equivalent confidentiality obligations; and - - 3. its professional advisors, service providers, or subprocessors (such as legal counsel, auditors, or consultants) who are subject to legal, professional, or contractual duties of confidentiality at least as protective as those in this Agreement. - -7. Each party shall at the request of the other party return, or at the option of the requested party evidence the destruction of all Confidential Information whether written or in any other form, without undue delay and together with all reproductions and copies thereof. Statutory retention obligations and electronic data backups carried out as part of proper business organization shall remain unaffected. Insofar as the Confidential Information is required to fulfill obligations under this Agreement, such request shall not be permissible before termination or expiration of this Agreement. Confidential Information shall be destroyed in an appropriate and reasonable manner. Any Confidential Information so retained will remain subject to the terms of the Agreement for so long as such Confidential Information is retained. - -### 5. CLIENT'S OBLIGATIONS - -1. Client shall use the Solution in accordance with the applicable documentation for the Solution ('**Documentation**') Langfuse may reasonably update, revise and/or amend the Documentation from time to time and in each case in good time and appropriately (i) inform Client and/or (ii) disclose such update, revision and/or amendment publicly. Such updated, revised or amended Documentation then constitutes the applicable Documentation. Client shall ensure its systems always meet the requirements set out in the Documentation at its own expense. - -2. Client is responsible for (i) the accuracy and completeness of all data introduced into the Solution by or on behalf of Client or Client's customers that is stored in or processed by the Solution (such data referred to as '**Client Data**'), (ii) determining the suitability of the Solution for its purposes, (iii) ensuring the processing configurations, settings and the administrative, technical and physical safeguards implemented by Client in connection with Client's use of the Solution are consistent with all laws applicable to Client. Client shall obtain or provide all necessary rights, consents, and notices for Langfuse to be able to use Client Data as necessary to fulfil its obligation under this Agreement. In addition, Client is obliged not to transfer, migrate and/or in any other way introduce any data to the Solution the use of which violates applicable law, official orders, third-party rights, or agreements with third parties. - -3. Client will not: (i) reverse engineer, decompile, or bypass technical controls; (ii) use the Solution to provide a competing service or resell the Solution without explicit permission given by Langfuse; (iii) conduct security/vulnerability testing without Langfuse's prior written authorization not to be unreasonably withheld; (iv) knowingly transmit malicious code, unlawful, or infringing content; (v) use for high‑risk activities where failure could lead to death or personal injury; or (vi) exceed agreed usage limits. Langfuse may suspend for violations. - -4. Suspension for Cause. Langfuse may suspend Client's access to the Solution upon: (a) undisputed invoices outstanding 30 days after due date; (b) material breach of the Agreement; or (c) security, availability, or integrity risk. Where practicable, Langfuse will give prior notice and will promptly restore access once the issue is resolved. Suspension does not relieve Client's payment obligations. - -5. Client must appropriately protect and store the credentials allowing access to the Solution transmitted by Langfuse against access by third parties. Client shall ensure that these access credentials are only used within the contractually agreed scope. Client must inform Langfuse immediately of any unauthorized access to the access data or the Solution as soon as reasonably practicable but in no event later than seventy two hours upon becoming aware of such unauthorized access. - -### 6. CLIENT DATA - -1. Client Data is and will remain owned exclusively by Client. Client hereby grants Langfuse a worldwide, limited-term, non-exclusive license to host, process, and transmit Client Data solely as necessary to provide, maintain, and support the Solution for Client under this Agreement or any other contract / Order Form between the parties. - -2. Langfuse may collect and use Solution-Generated Data from Client Data only as needed to operate, maintain, improve, and support the Solution. This includes purposes such as diagnostics, analytics, customer support, system performance, and reporting. Langfuse will not share this data externally unless it is (a) aggregated or anonymized with data from other clients, and (b) cannot reasonably be used to identify the Client, its Users, or any Client Data. - -3. Langfuse shall not access, analyze, or use Client Data to develop competing products or services, nor to reverse engineer, disassemble, or decompile Client Data in any way. - -4. Langfuse commits to not sell Client Data to third parties or train Artificial Intelligence Models utilizing Client Data. - -5. Client may, but is not required to, give Langfuse suggestions, feedback, or comments about the Solution or related offerings ('**Feedback**'), in which case Client gives Feedback 'AS IS'. Langfuse may use all Feedback freely without any restriction or obligation. - -6. During the Subscription Term, Client may export Client Data via the Solution's export features. Following termination, deletion of Client Personal Data is governed by DPA §9 and deletion of PHI is governed by BAA §10; all other Client Data is deleted under Section 11.4 - -### 7. WARRANTY - -1. Provided Client timely performs its obligations under the Agreement and reasonably cooperates with Langfuse, the Solution shall conform in all material respects with the requirements stated in the Agreement and the Documentation ('**Requirements**'). Any failure of the Solution to materially conform with its Requirements shall be a '**Defect**'. Client shall inform Langfuse of any Defect without undue delay and in appropriate detail. - -2. Except as expressly stated in the Agreement, the Solution and the Documentation are provided 'as is', and all other warranties, guarantees or any other statutory or contractual rights arising out of lack of quality, title, defects, or non-performance are, to the fullest extent permitted legally permissible, excluded from the Agreement. - -### 8. LIABILITY - -LIMITATION OF LIABILITY. EACH PARTY'S TOTAL AGGREGATE LIABILITY (TOGETHER WITH ITS AFFILIATES) UNDER OR RELATED TO THIS AGREEMENT SHALL NOT EXCEED THE FEES ACTUALLY PAID BY CLIENT TO LANGFUSE IN THE TWELVE (12) MONTHS PRECEDING THE FIRST EVENT GIVING RISE TO THE FIRST CLAIM. NEITHER PARTY (NOR ITS AFFILIATES) SHALL BE LIABLE FOR ANY LOST REVENUES, LOST PROFITS, LOSS OF BUSINESS, OR ANY INDIRECT, CONSEQUENTIAL, INCIDENTAL, SPECIAL, OR PUNITIVE DAMAGES, WHETHER BASED IN CONTRACT, STATUTE, OR OTHERWISE. THESE LIMITATIONS SHALL NOT APPLY TO DAMAGES CAUSED BY FRAUD, WILLFUL MISCONDUCT, OR GROSS NEGLIGENCE; TO LIABILITY FOR DEATH, PERSONAL INJURY, OR HEALTH DAMAGES CAUSED BY NEGLIGENCE; TO LIABILITY WHICH CANNOT BE LIMITED UNDER APPLICABLE LAW; OR EXPRESS WRITTEN GUARANTEES. EXCEPT FOR CLIENT'S PAYMENT OBLIGATIONS, NEITHER PARTY SHALL BE LIABLE FOR FAILURE OR DELAY DUE TO FORCE MAJEURE EVENTS INCLUDING STRIKES, RIOTS, EPIDEMICS, TERRORISM, WARS, FIRES, FLOODS, POWER FAILURES, OUTAGES, ACTS OF AUTHORITIES, OR ACTS OF GOD. WHERE THE INJURED PARTY'S OWN FAULT CONTRIBUTES TO THE DAMAGE, LIABILITY AND COMPENSATION SHALL BE DETERMINED BASED ON THE DEGREE OF CONTRIBUTION. - -### 9. INDEMNITIES - -1. Langfuse's indemnity obligation shall be to defend Client against any third-party claim alleging that the Solution infringes or misappropriates any patent, trademark, copyright, or trade secret enforceable under applicable law and pay the amount of any resulting adverse final judgment or settlement of such claim. Langfuse has no obligation to the extent a claim arises from: (i) combinations with items not provided by Langfuse; (ii) modifications not made by Langfuse; (iii) use not in accordance with the Documentation or this Agreement; (iv) non‑current versions where the claim would have been avoided by using a current version made available without material loss of functionality; or (v) Client Data. If the Solution is (or is likely to be) enjoined, Langfuse may procure continued use, modify and/or replace the Solution, or terminate the affected Subscription and refund prepaid fees for the remaining term.\ - Non-IP Indemnity. Langfuse will indemnify, defend, and hold harmless Client from any third-party claim to the extent arising from (a) Langfuse's breach of its confidentiality obligations under Section 4; (b) any Security Incident (as defined in the DPA) affecting Client Personal Data or PHI caused by Langfuse's failure to comply with the Agreement, the DPA, or, if applicable, the BAA; or (c) Langfuse's violation of Applicable Data-Protection Laws in its provision of the Solution, in each case to the extent caused by Langfuse. Langfuse's obligations are conditioned on Section 9.3 and exclude claims to the extent caused by Client's acts or omissions, instructions, or Third-Party Products.\ - The remedies provided in this section are the sole remedies for a claim of infringement or misappropriation hereunder. - -2. Client's indemnity obligation shall be to defend Langfuse against any claims asserted against Langfuse by or on behalf of Client's users, Client's customers and/or other third parties in connection with the misuse of the Solution by Client and pay the amount of any resulting final judgment or settlement of such claim, unless such claims are solely caused by Langfuse's breach of the Agreement. - -3. The obligations in this section are contingent upon: (i) the indemnified party, without undue delay, notifying the indemnifying party in writing of any claims for which it seeks indemnity, including all materials received by the party related to the claim and an identification of the relevant Solution; (ii) the indemnifying party having sole control over the defense and settlement of such claims; (iii) the indemnified party reasonably cooperating during defense and settlement efforts; and (iv) the indemnified party not making any admission, concession, consent judgment, default judgment or settlement of such claim or any part thereof, unless the indemnifying party has given consent to such actions (consent not to be unreasonably withheld). - -4. Notwithstanding the Limitation of Liability in Section 8, indemnity payments under this Section are capped at three (3) times the fees paid in the twelve (12) months prior to the claim. - -### 10. INTELLECTUAL PROPERTY - -1. Notwithstanding anything to the contrary, the rights and obligations pertaining to the use of any open-source software are exclusively governed by the terms of the applicable open-source license. Nothing in this Agreement shall prejudice these rights and obligations. - -2. The Solution (excluding Client Data) and its features and functionalities as well as the Documentation are and will remain the exclusive property of Langfuse and its licensors (collectively '**Property of Langfuse**'). Property of Langfuse is protected by copyright, trademark, and other laws pertaining to the protection of intellectual property rights. Langfuse's trademarks and trade dress may not be used in connection with any product or service without the prior written consent of Langfuse. - -3. Client may use the Solution and the Documentation exclusively in accordance with the Agreement and only in the ordinary course of its business. To this end, Langfuse grants Client the revocable, non-exclusive, and non-transferable right to use the Solution and Documentation for the term of the Agreement to the contractually agreed extent. Apart from this, Client does not acquire any right, title, or interest in, to or under, copyright, trademark, and/or other laws pertaining to the protection of intellectual property rights. - -### 11. TERM AND TERMINATION - -1. The Client may terminate without cause at any time during a running Billing Cycle with legal effect at the end of that Billing Cycle without observing a notice period. Langfuse shall observe a notice period of one (1) month to the end of a Billing Cycle for a termination without cause. - -2. Unless the Agreement is terminated by either party beforehand or otherwise agreed, at the end of each Billing Cycle the Client's Subscription will automatically renew for another Billing Cycle under the exact same terms. Client may terminate the Agreement and the corresponding Subscription through the online account management page or if that fails by contacting Langfuse's client support team at support@langfuse.com - -3. Either party may terminate this Agreement immediately for a material breach that cannot be cured, or upon 30 days' prior written notice if curable and not cured within that period. If Client terminates this Agreement for Langfuse’s uncured material breach, Langfuse shall refund any prepaid fees for the unused portion of the applicable Subscription Term following the effective date of termination. - -4. Langfuse will within thirty (30) days after termination or expiration of the Agreement close the account of the Client maintained on the IT systems of Langfuse and delete or destroy any Client Data in a manner designed to preserve its confidentiality, except to the limited extent retention is required by law or for the establishment, exercise, or defense of legal claims or persists solely in back-ups; any retained copies will remain subject to this Agreement and applicable data-protection terms and will be deleted in the ordinary course. For the avoidance of doubt the DPA shall govern the destruction or deletion of Client Personal Data and the BAA shall govern the destruction of PHI. - -5. Upon termination or expiration, all licenses granted under this Agreement terminate. - -### 12. SERVICE LEVELS (Enterprise Only) - -1. Only for Clients on an enterprise plan or with an Order Form that includes a Service Level Agreement (a 'SLA'). Langfuse will use commercially reasonable efforts to meet the target availability for core services stated in the Order Form, measured by Langfuse's production monitoring/status records. If the target is not met, Client may request service credits as specified in the Order Form; credits are Client's sole remedy and will not exceed fees for the affected period. Exclusions include scheduled/emergency maintenance, Client/third-party causes, beta/preview features, and force majeure. Langfuse may update this Section, but will not materially reduce commitments during the then-current term; any reduction applies only at renewal. - -### 13. MISCELLANEOUS - -1. Client is responsible for complying with import and export regulations applicable to using the Solution, in particular those associated with the United States of America. - -2. Amendments. Langfuse may update these T\&Cs prospectively by providing at least 30 days' prior notice (by email). If Client objects to a material change that adversely affects it, Client may terminate the affected Subscription before the effective date and Langfuse will refund any prepaid fees for the period after termination. Amendments to the DPA or BAA are governed by their own change clauses. - -3. The Agreement shall bind, benefit and be enforceable by and against Langfuse and Client and their respective permitted successors and assigns. Neither party may assign this Agreement without the other party's consent, except to an Affiliate or in connection with a merger, acquisition, corporate reorganization, or sale of all or substantially all assets (with notice). Any non‑permitted assignment is void. Except as otherwise set forth herein, the parties do not intend, nor shall there be, any third-party beneficiary rights for protection under the Agreement, and the rights of the parties to terminate, rescind or agree any variation, waiver or settlement under the Agreement are not subject to the consent of any other person. - -4. Publicity. Only with Client's prior consent, Langfuse may use Client's name and logo to identify Client as a customer on Langfuse's website and in marketing materials. Client may revoke consent at any time by notice. - -5. Notices. Legal notices must be sent by email: to Client at the primary email associated with the account, and to Langfuse at [legal@clickhouse.com](mailto:legal@clickhouse.com). Notices are deemed given when the sending server records transmission. Operational and product notices (including price changes) may be given in‑product or by email to the account admin. - -6. Survival. Sections 3 (to the extent restricting use), 4 (Confidentiality), 6 (Client Data), 7 (Warranty – disclaimers), 8 (Liability), 9 (Indemnities), 11.4–11.6, and 12 (Miscellaneous) survive. - -7. The Agreement states the entire agreement and understanding between the parties and supersedes all prior representations, agreements, and understandings, whether written or oral, relating to its subject matter. - -8. A determination that any provision of the Agreement is invalid or unenforceable shall not affect the other provisions of the Agreement and the provision that is held to be invalid or unenforceable shall be replaced by a valid and enforceable provision that would give the best legal and commercial effect to the intention of the parties. No modification of the Agreement, and no waiver of any breach of the Agreement, shall be effective unless in writing and signed by an authorized representative of the party against whom enforcement is sought. - -9. The Agreement and any dispute, difference, controversy, or claim arising, directly or indirectly, out of, relating to, or otherwise in connection with it or its subject matter or formation (including non-contractual disputes, differences, controversies, or claims) is governed by, and shall be construed and enforced in accordance with, the laws of: - 1. us.cloud.langfuse.com and hipaa.cloud.langfuse.com: the laws of the State of California, USA, with exclusive jurisdiction in the state and federal courts located in San Francisco, California, USA; - - 2. cloud.langfuse.com: the laws of the Federal Republic of Germany, with exclusive jurisdiction in the courts of Berlin, Germany; - - 3. any other current or future Langfuse cloud instances not listed above: the laws of the Federal Republic of Germany, with exclusive jurisdiction in the courts of Berlin, Germany. - -10. The United Nations Convention on Contracts for the International Sale of Goods (CISG) does not apply to the Agreement or its subject matter. The parties agree that any terms or laws referred to in this Agreement shall be construed to correspond to the applicable governing law as determined under this Section. - -**Optional countersignature.** _Self-serve subscriptions are formed upon completion of the in-product checkout/upgrade flow and do not require a separate signature._ - -_Upon Client's written request, Langfuse will provide a countersigned copy of these T\&Cs for record-keeping. The effectiveness of these T\&Cs does not depend on a separate signature._ - -## Archive of Cloud T&Cs & Self-Hosting [#archive] - -### Previous versions of Langfuse Cloud T&Cs - -- Langfuse Cloud Terms and Conditions (May 2024): [PDF](https://static.langfuse.com/files/legal_Langfuse_TCs_20240506.pdf) - -### Commercial Self-Hosted Licenses: Pro & Enterprise - -If you run the free, MIT licensed version of Langfuse (FOSS), you do **not** need an agreement with us. See our [repository's license](https://github.com/langfuse/langfuse/blob/main/LICENSE) for more. - -For Enterprise/Sales inquiries: [enterprise@langfuse.com](mailto:enterprise@langfuse.com). - -Legacy (Deprecated): [Langfuse Self Hosting Enterprise Terms of Service, May 2024](https://static.langfuse.com/files/legal_langfuse_self_hosting_terms_02_07_2024.pdf) diff --git a/content/security/compliance-faq.mdx b/content/security/compliance-faq.mdx index 801de1e395..8d43fd96aa 100644 --- a/content/security/compliance-faq.mdx +++ b/content/security/compliance-faq.mdx @@ -39,7 +39,7 @@ Langfuse maintains an inventory of all vendors and classify them by risk level b > **Which sub‑processors have access to customer data?** -The live list is published [here](/security/subprocessors). +The live list is published [here](/subprocessors). > **How does Langfuse manage its vendors?** diff --git a/content/security/data-regions.mdx b/content/security/data-regions.mdx index aa94e39a38..d276bf1ebd 100644 --- a/content/security/data-regions.mdx +++ b/content/security/data-regions.mdx @@ -83,7 +83,7 @@ Active tracing ingestion resumes once the replacement environment is live. S3 media buckets store uploaded media items referenced from traces. They are not replicated cross-region. **On the permanent loss of the primary AWS region, uploaded media items are not recoverable**, even where the referencing trace survives. -All secondary regions are within the same legal jurisdiction as their primary region (EU ↔ EU, US ↔ US, Japan ↔ Japan), so cross-region replication does not change the data-residency or cross-border-transfer posture declared in the [DPA](/security/dpa) and [HIPAA BAA](/security/hipaa). +All secondary regions are within the same legal jurisdiction as their primary region (EU ↔ EU, US ↔ US, Japan ↔ Japan), so cross-region replication does not change the data-residency or cross-border-transfer posture declared in the [DPA](/dpa) and [HIPAA BAA](/security/hipaa). **Protecting tracing data against a regional outage:** Since ClickHouse diff --git a/content/security/dpa.mdx b/content/security/dpa.mdx deleted file mode 100644 index be8b7bd01e..0000000000 --- a/content/security/dpa.mdx +++ /dev/null @@ -1,269 +0,0 @@ ---- -title: DPA -description: Data Processing Agreement for Langfuse services. ---- - -# Langfuse Data Processing Agreement (DPA) - -**Latest revision:** October 17th, 2025 | **download as PDF** - - - -**At a glance** — You (as _Controller_) remain in control of your data; Langfuse (as _Processor_) only uses it to run the Solution, keeps it secure under industry‑standard TOMs, and allows you to delete it or deletes it when you ask us to or leave us. If we need new subprocessors or make material changes, we will let you know 30 days in advance. - - - -## Applicability Notice - -This DPA is available for any Client of the Langfuse Cloud platform (EU Cloud at https://cloud.langfuse.com, US Cloud at https://us.cloud.langfuse.com, Japan Cloud at https://jp.cloud.langfuse.com, HIPAA Cloud at https://hipaa.cloud.langfuse.com) and any subscription tier (Hobby, Core, Pro, Teams, Enterprise). It forms part of and is incorporated by reference into the applicable T\&Cs or other agreement governing use of the Langfuse platform (the 'Main Contract').\ -References to specific statutes (e.g., GDPR Articles 32–36) apply where those laws govern. Where another Applicable Data-Protection Law applies instead, the Parties intend the provision to be interpreted to the materially equivalent requirement under that law. - -**Questions?** Email privacy@langfuse.com - -The current and past versions of this DPA are always available at [https://langfuse.com/security/dpa](https://langfuse.com/security/dpa) - -## 1. Preamble & Incorporation - -This Data Processing Agreement (**'DPA'**) describes how Langfuse GmbH (**'Langfuse'**, **'we'**, **'us'**) processes Personal Data on behalf of the Client (**'you'**). - -This DPA supplements and is incorporated by reference into Langfuse's Terms and Conditions ('**T\&Cs**') or other agreement governing use of the Langfuse platform (collectively, the **'Main Contract'**). - -It is intended to, inter alia, satisfy the requirements of: - -- **Regulation (EU) 2016/679** (_EU GDPR_), -- the **UK GDPR** as defined in the UK Data Protection Act 2018, and -- the **California Consumer Privacy Act of 2018** (together with the California Privacy Rights Act of 2020, the _CCPA_) -- and **any other national or U.S. State data‑protection laws** that implement or supplement the foregoing (collectively, **'Applicable Data‑Protection Laws'**). - -**Applicability.** This DPA applies to **all** Clients that Process Personal Data via the Solution. Sections on fees or cost‑sharing apply only where you have a paid subscription.\ -**Precedence.** If there is a conflict between this DPA and the Main Contract, **this DPA controls** for data‑protection matters. - -## 2. Definitions - -Capitalized terms not defined here have the meanings set out in the Main Contract or in the GDPR. - -- **'Client'** – the legal entity accepting the Main Contract (regardless of subscription tier). - Client's details (legal name, address, VAT/Tax ID) are captured during checkout and form part of the Main Contract. -- **'Solution'** – the hosted Langfuse platform and any associated support or professional service. -- **'Client Personal Data'** – the subset of 'Client Data' that constitutes personal data processed by Langfuse on behalf of Client via the Solution. -- **'EU Cloud' / 'US Cloud' / 'Japan Cloud' / 'HIPAA Cloud'** – the regional instance selected by Client (cloud.langfuse.com (EU) or us.cloud.langfuse.com (US) or jp.cloud.langfuse.com (Japan) or hipaa.cloud.langfuse.com (HIPAA \- US)). **Client is responsible for selecting the instance that satisfies its applicable data‑protection obligations.** -- **'Affiliate'** \- any entity that controls, is controlled by, or is under common control with a party. -- **'De‑Identified Data'** means data that cannot reasonably identify a natural person, Client, or Client account, taking into account reasonable technical and organizational measures. -- **'Controller'** and **'Processor'** – have the meanings given in the Applicable Data‑Protection Laws; Client is the Controller of Client Personal Data and Langfuse is the Processor. -- **'Applicable Data‑Protection Laws'** – the EU GDPR, UK GDPR, CCPA, and any other applicable national or U.S. state data-protection laws. - -_All other GDPR terms (Controller, Processor, etc.) shall have the meanings given in the GDPR._ - -## 3. Scope, Instructions & Responsibilities - -Langfuse will Process Client Personal Data **only**:\ -(i) to provide, maintain, secure and support the Solution for Client,\ -(ii) as documented in this DPA and the Main Contract, and\ -(iii) to comply with law or Client's documented instructions. - -Processing continues for the term of the Main Contract **and** until deletion of Client Personal Data in accordance with Section 9 (_Deletion & Return_). - -Langfuse may use Solution-Generated Data (as defined in the T\&Cs, i.e. data that cannot reasonably identify a natural person, Client, or Client account) to operate, analyze, and improve the Solution. Langfuse will not sell Client Personal Data to third parties and will not use Client Personal Data to train AI models or for advertising. - -**Processing on documented instructions.** Langfuse will process Client Personal Data **solely on documented instructions from Client**, unless Union or Member‑State law to which Langfuse is subject requires other processing; in such case Langfuse will inform Client of that legal requirement unless prohibited by law. If Langfuse reasonably believes an instruction infringes the GDPR or other Union‐or Member‑State data‑protection rules, it will promptly notify Client and may suspend execution until the instruction is confirmed, modified or withdrawn. - -**Client responsibilities.** Client is responsible for (a) ensuring that its instructions are lawful and that a valid legal basis exists for all Processing; (b) the accuracy, quality and legality of Client Personal Data; and (c) fulfilling controller obligations under Articles 33–36 GDPR. - -## 4. Sub‑Processors - -1. **Authorised List.** The current list of authorised sub‑processors for each instance of Langfuse is published at: [https://langfuse.com/security/subprocessors](https://langfuse.com/security/subprocessors) -2. **Affiliates.** Client authorizes Langfuse to engage its Affiliates as sub‑processors subject to written agreements imposing data‑protection obligations no less protective than this DPA. -3. **Notification & Objection.** Langfuse will notify Client (via email) at least **30 days** before authorising a new sub‑processor. Client may object on reasonable data‑protection grounds within that period. If the parties cannot resolve an objection, Client's **sole and exclusive remedy** for such objection shall be to cancel the Main Contract \- which it may do without notice period \- in which case Langfuse will provide a pro‑rated refund of any prepaid fees covering the period after cancellation. -4. **Data‑Transfer Mechanisms.** Transfers to sub‑processors outside the EEA/UK/Switzerland will rely on an approved transfer mechanism (e.g. EU SCCs, UK IDTA, or participation in the EU–US Data Privacy Framework). -5. **Same obligations & responsibility.** Langfuse shall ensure each Sub-Processor is bound by a written agreement that imposes the same data-protection obligations as set out in Article 28(3) GDPR (to the extent applicable to the Sub-Processor’s services), including appropriate technical and organisational measures. As between the Parties, Langfuse remains fully liable to Client for the performance of each Sub-Processor’s data-protection obligations, subject to the exclusions and limitations of liability in the Main Contract. - -## 5. Security Measures - -Langfuse will implement and maintain the technical and organisational measures ('TOMs') described in **Annex 2** (as updated from time to time). Material reductions will not be implemented without reasonable notice to Client, however Langfuse may add additional TOMs or increase the scope of protection at any time and without notice. - -**Personnel confidentiality.** All Langfuse employees and other recipients and subprocessor personnel who have access to Client Personal Data are bound by written confidentiality agreements or statutory duties of confidentiality **and receive regular privacy and security training appropriate to their role**. - -Langfuse may update or modify the TOMs, without invoking Section 12, provided that such updates do not materially diminish the overall security of the Solution. - -Langfuse maintains **ISO 27001** and **SOC 2 Type II** attestations. Further information on Langfuse's security posture & audit reports can be viewed or requested via https://langfuse.com/security. - -## 6. Data Subject Rights & Regulatory Cooperation - -Langfuse shall provide reasonable assistance (taking into account the nature of Processing and information available) for Client to respond to Data Subject requests or supervisory authority enquiries. - -Taking into account the nature of Processing and the information available to Langfuse, Langfuse will provide reasonable assistance to Client in ensuring compliance with Articles 32–36 GDPR/UK GDPR, including by providing available information about its Processing operations and TOMs to support data protection impact assessments (DPIAs) and, where required, the Client’s prior consultation with the competent supervisory authority (e.g., the UK ICO) under Article 36. - -Where available, self-service materials will be used; assistance beyond self-service may be provided on a time-and-materials basis and does not include legal advice. - -## 7. Security Incidents & Regulatory Support - -Upon becoming aware of a Security Incident affecting Client Personal Data, Langfuse will notify Client **without undue delay** (and in no event later than 72 hours). Where required, Langfuse will provide information sufficient to allow Client to meet its regulatory obligations.\ -Langfuse will provide reasonable assistance (at Client's cost where such assistance is non‑routine) for Client to notify data‑protection authorities or affected data subjects (e.g. in accordance with Articles 33 and 34 GDPR). - -## 8. Audits - -**Third‑Party Reports:** Annual SOC 2 (Type II) or ISO 27001 certificates shall ordinarily satisfy Client's audit rights to the extent permitted by Data Protection Laws. - -**Additional audits:** Only if required by an authority, a material issue, or if the reports referenced in Section 8.1 do not provide sufficient evidence of Langfuse's compliance with this DPA, Langfuse shall make available to Client all information reasonably necessary to demonstrate such compliance and, at Client's cost, allow for and contribute to audits—including on‑site inspections—conducted by Client or its appointed independent auditor. These audits must be strictly scoped to assess compliance with this DPA and are subject to: (i) at least 30 days' prior written notice, (ii) reasonable confidentiality and security safeguards imposed by Langfuse, and (iii) a limit of one on‑site audit in any rolling 12‑month period unless a material breach is reasonably suspected or as otherwise required by a competent supervisory authority. - -## 9. Deletion & Return of Data - -**Deletion requests during the Term.** Where the Solution includes self‑service deletion or data‑redaction features, Client shall use those features to delete Client Personal Data. Langfuse‑assisted deletion during the Term may be provided where such service is not available. - -**Deletion after termination.** No later than **30 days** following termination of the Main Contract (or earlier upon written request), Langfuse will delete or return (and thereafter delete) Client Personal Data, unless retention is required by law. - -Notwithstanding the foregoing, Langfuse may retain copies of Client Personal Data **(a)** in secure back‑up archives that are isolated from active systems and retained in the ordinary course of business and **(b)** as strictly necessary for the establishment, exercise or defence of legal claims or to demonstrate compliance with this DPA. Any Client Personal Data so retained will remain subject to this DPA and the confidentiality obligations of the Main Contract for so long as it is retained. - -## 10. International Transfers - -Langfuse will implement an appropriate transfer mechanism for each transfer, including the EU SCCs (Decision 2021/914) using Module 2 and/or Module 3 as applicable; the UK IDTA/Addendum; and the Swiss addendum. Where Langfuse relies on the EU‑US Data Privacy Framework, it will maintain self‑certification and, if DPF ceases to apply, the SCCs (with relevant addenda) will automatically govern. - -Data processed in the **EU Cloud** remains within the EEA (or equivalent adequacy jurisdictions) by default. Where Langfuse or its Affiliates must access or process such data from outside the EEA (for example, to deliver follow-the-sun support), it shall do so only under a valid transfer mechanism compliant with Chapter V GDPR and, where required by Article 46 GDPR, will inform Client in advance. - -Data processed in the **US Cloud** is primarily hosted in the United States; Langfuse relies on the EU Standard Contractual Clauses (Module 2 and/or 3\) and/or the EU–US Data Privacy Framework for such transfers. - -Data processed in **HIPAA Cloud**: PHI is hosted in a dedicated, HIPAA‑compliant environment in the United States. Transfers rely on the same mechanisms as the US Cloud, supplemented by the Langfuse HIPAA Business Associate Agreement (BAA). - -## 11. Main Contract Governance - -**Indemnity & Liability**: Each party's aggregate liability and indemnities relating to Processing are governed by the Main Contract. - -**Governing Law:** The governing law and forum/venue for any dispute arising out of or relating to this DPA are the same as those specified in the Main Contract (currently either California, San Francisco courts, or Berlin, Germany courts, as applicable under the Main Contract), excluding its conflict-of-laws rules. - -**Precedence:** If there is a conflict on the same subject matter: (1) for PHI, the BAA controls; (2) for Personal Data (excluding PHI), the DPA controls; otherwise, the T\&Cs control. Where information qualifies as both PHI and Personal Data, the BAA controls and the DPA applies only where not inconsistent with the BAA. - -**Termination:** This DPA is coterminous with the Main Contract and may be terminated only in accordance with the Main Contract (except where expressly provided herein, including Section 4). Upon expiry or termination, Processor will Process Client Personal Data solely to wind down the Solutions and to return/delete data per Section 9; Sections 5, 7–9, and 11 (and any provisions intended to survive) survive to the extent applicable. - -## 12. Changes to this DPA - -Langfuse may modify this DPA from time to time to reflect changes in applicable law, new Solutions or practices and/ or updated transfer clauses. - -Langfuse will provide at least 30 days' notice (via email) of any modification. Continued use of the Solution after the notice period constitutes acceptance. Client's sole and exclusive remedy if it objects to a modification is to cancel the Solution before the effective date, and Langfuse will refund any prepaid fees that relate to the period after cancellation. - -## 13. Notices - -**Method of notice.** All legal notices under this DPA are to be sent (i) to Client at the primary email address associated with the account used to subscribe to the Solution, and (ii) to Langfuse at legal@clickhouse.com. Notices are deemed received when the sending server records transmission. Notices are governed by the Main Contract's notice clause. - -## Execution - -**Acceptance & execution.** _This DPA is incorporated into the Main Contract and becomes effective upon the Parties' execution of the Main Contract or an Order Form (including via a legally valid electronic signature or click-accept). The Parties agree that such execution constitutes execution of Annex I.A of the EU SCCs (Decision (EU) 2021/914) and of the UK and Swiss addenda included in Annex 4, with the selections and Annexes completed herein. No additional signatures are required._ - -**Optional countersignature.** _Upon Client's written request, Langfuse will provide a countersigned copy of this DPA for record-keeping. The effectiveness of this DPA and the SCCs does not depend on a separate signature._ - -## Annex 1 – Details of Processing - -| Item | Description | -| ------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Purpose of processing | Contractual provision of the Langfuse platform | -| Scope of processing | Processing necessary to provide, secure, support, maintain and improve the Solution | -| Types of personal data | Names, email addresses and other identifiers of Client's users; Application content, prompts/outputs, traces, logs and identifiers provided by Client (collectively 'Client Personal Data') | -| Categories of data subjects | Client's employees and other users ('users'); Individuals referenced in communication content ('data subjects of the Client') | -| Special Categories / Sensitive Data. | Client will not submit Special Categories of Personal Data (GDPR Arts. 9–10) or Sensitive Personal Information under CPRA/CCPA to non‑HIPAA environments. For HIPAA workloads, PHI may be processed only in the HIPAA Cloud under the BAA. Any exception must be expressly agreed in writing and appropriately configured. | - -## Annex 2 – Technical and Organisational Measures (TOMs) implemented by Langfuse - -The below document supplements Section 5 of this DPA and fulfils inter alia Article 32 GDPR, UK GDPR Art 32 and Cal. Civ. Code § 1798.81.5. - -A current list of Langfuse's TOMs can be found at [https://langfuse.com/security/toms](/security/toms) - -A version history of this page can be found at: [https://github.com/langfuse/langfuse-docs/commits/main/content/security/toms.mdx](https://github.com/langfuse/langfuse-docs/commits/main/content/security/toms.mdx) - -## Annex 3 – Subprocessors - -A current list of Langfuse's subprocessors for each Langfuse instance can be found at [https://langfuse.com/security/subprocessors](/security/subprocessors). - -A version history of this page can be found at: [https://github.com/langfuse/langfuse-docs/commits/main/content/security/subprocessors.mdx](https://github.com/langfuse/langfuse-docs/commits/main/content/security/subprocessors.mdx) - -Please refer to Section 4 of this DPA for further information on subprocessing. - -## Annex 4 – International Transfer Pack (EU SCCs \+ UK & Swiss Addenda) - -#### 4.1 Incorporation and Application of EU SCCs - -**(a) Incorporation.** The Parties incorporate by reference the European Commission's Standard Contractual Clauses for the transfer of personal data to third countries under the GDPR, set out in Commission Implementing Decision (EU) 2021/914 of 4 June 2021 (the 'EU SCCs'), as if set out in full. The SCCs' text is not modified except to select modules/options and complete annexes. - -**(b) When they apply.** The EU SCCs apply only to the extent Client Personal Data is transferred from the EEA (or otherwise subject to the GDPR) to a country without an adequacy decision, including remote access to such data from such country, in connection with the Solution. - -**(c) Modules selected.** - -- **Module 2 (Controller → Processor):** Selected where Client (as controller/data exporter) transfers to Langfuse (as processor/data importer) outside the EEA. - -- **Module 3 (Processor → Sub‑processor):** Selected for transfers from Langfuse (as processor/data exporter) to its sub‑processors (data importers) outside the EEA. - -**(d) Options and clause selections.** - -- **Clause 7 (Docking clause):** Included. - -- **Clause 9(a) (Use of sub‑processors):** Option 2 (General written authorisation); notice period: 30 days (aligns with Section 4). - -- **Clause 13 (Supervisory authority):** As determined by Clause 13 for the data exporter. - -- **Clause 17 (Governing law):** German law. - -- **Clause 18 (Forum and jurisdiction):** Courts of Berlin, Germany, without prejudice to data subjects' rights under the SCCs. - -**(e) Transfer risk assessments and supplementary measures.** The Parties will perform and document transfer impact assessments as required by Clause 14 and implement supplementary measures where necessary. - -#### 4.2 EU SCCs – Annex I (completed) - -**A. List of Parties** - -- **Data exporter:** the Client as identified in the Main Contract, including its legal name, registered address and contact details as recorded therein; role: Controller (and/or Processor for onward transfers as applicable). - -- **Data importer:** Langfuse GmbH, Oranienburgerstraße 91, 10178 Berlin, Germany; privacy@langfuse.com; legal@clickhouse.com; role: Processor. - -_(Additional Langfuse entities and/or sub‑processors may accede pursuant to Clause 7 by executing an accession; no further Client action is required.)_ - -**B. Description of Transfer** - -- **Categories of data subjects:** Client's users; individuals referenced in application content/logs ('data subjects of the Client'). - -- **Categories of personal data:** As described in Annex 1 (e.g., names, email addresses, identifiers; application content, prompts/outputs, traces, logs and identifiers provided by Client). - -- **Special category/sensitive data:** Not intended for non‑HIPAA environments. For HIPAA workloads, PHI may be processed only in the HIPAA Cloud under the BAA. - -- **Frequency & nature:** Continuous and as necessary to provide, secure, support, maintain and improve the Solution (hosting, storage, retrieval, transmission, display, computation, logs/monitoring, backup/DR, support). - -- **Purpose:** Contractual provision of the Langfuse platform. - -- **Retention:** For the term of the Main Contract and until deletion/return per Section 9 (or as required by law). - -- **Subject matter & duration:** As above and coterminous with the Main Contract and post‑termination wind‑down/deletion period. - -**C. Competent Supervisory Authority** - -As determined by Clause 13 of the EU SCCs for the data exporter. - -#### 4.3 EU SCCs – Annex II (Technical and Organisational Measures) - -The TOMs in Annex 2 are incorporated here by reference as Annex II to the EU SCCs. - -#### 4.4 EU SCCs – Annex III (List of Sub‑processors) - -The sub‑processors in Annex 3 are incorporated here by reference as Annex III to the EU SCCs. - -#### 4.5 UK Addendum (UK GDPR) - -For restricted transfers under the UK GDPR, the Parties incorporate by reference the UK Information Commissioner's International Data Transfer Addendum to the EU SCCs (Version B1.0, in force 21 March 2022\) (the 'UK Addendum'). The UK Addendum varies the EU SCCs only as required by UK law. - -- **Table 1 (Parties):** Exporter \= the Client as identified in the Main Contract; Importer \= Langfuse GmbH, Oranienburgerstraße 91, 10178 Berlin, Germany. - -- **Table 2 (Selected SCCs):** EU SCCs (Decision (EU) 2021/914), Module 2 and/or Module 3; Docking clause included; Clause 9 Option 2 with 30 days; Clause 17 \= German law; Clause 18 \= courts of Berlin, Germany. - -- **Table 3 (Appendix Information):** Mirrors Annex 1–3 of this DPA. - -- **Table 4 (Ending the UK Addendum):** Mandatory clauses apply; no bespoke amendments. - -By executing the Main Contract or an Order Form (including via a legally valid e-signature or click-accept), the Parties are deemed to have executed the UK Addendum. No additional signatures are required. - -#### 4.6 Swiss Addendum (FADP) - -For transfers subject to Swiss data protection law, the Parties agree the EU SCCs are adapted as follows (the 'Swiss Addendum'): - -1. References to the 'GDPR' include the FADP where applicable; references to 'Member State' include Switzerland; references to the 'supervisory authority' include the FDPIC. - -2. For Swiss‑subject transfers, Clauses 17–18 are governed by Swiss law and the courts of Zurich, Switzerland, without prejudice to data subjects' rights. - -3. Swiss data subjects may exercise third‑party beneficiary rights in Switzerland under the SCCs as adapted. - -By executing the Main Contract or an Order Form (including via a legally valid e-signature or click-accept), the Parties are deemed to have executed the Swiss Addendum. No additional signatures are required. diff --git a/content/security/gdpr.mdx b/content/security/gdpr.mdx index 2c4d5ff98a..60b4bb7614 100644 --- a/content/security/gdpr.mdx +++ b/content/security/gdpr.mdx @@ -9,7 +9,7 @@ Langfuse is committed to complying with the General Data Protection Regulation ( More information: -- [Langfuse DPA](/security/dpa) +- [Langfuse DPA](/dpa) - [Managing processing of personal data (within Langfuse)](/security/manage-personal-data) - [Privacy Policy](/privacy) for details on how we handle personal data diff --git a/content/security/hipaa.mdx b/content/security/hipaa.mdx index 9a83780a42..9ea3786cfb 100644 --- a/content/security/hipaa.mdx +++ b/content/security/hipaa.mdx @@ -114,7 +114,7 @@ Langfuse will ensure that any Subcontractor that creates, receives, maintains or Langfuse remains responsible for each Subcontractor's compliance and is liable for their acts and omissions relating to PHI to the same extent as if performed by Langfuse. -Langfuse maintains a public list of Subcontractors that Process PHI in the HIPAA Cloud at [langfuse.com/security/subprocessors](https://langfuse.com/security/subprocessors) and will provide at least 30 days' prior email notice before adding or replacing any such Subcontractor. If Client reasonably objects on data‑protection grounds, Client may terminate the HIPAA Cloud subscription within that period and receive a pro‑rated refund of prepaid fees for the terminated remainder of the then‑current term. +Langfuse maintains a public list of Subcontractors that Process PHI in the HIPAA Cloud at [langfuse.com/subprocessors](/subprocessors) and will provide at least 30 days' prior email notice before adding or replacing any such Subcontractor. If Client reasonably objects on data‑protection grounds, Client may terminate the HIPAA Cloud subscription within that period and receive a pro‑rated refund of prepaid fees for the terminated remainder of the then‑current term. ### 7. Incident & Breach Reporting diff --git a/content/security/index.mdx b/content/security/index.mdx index 4a0f755d6f..73fd91d7a1 100644 --- a/content/security/index.mdx +++ b/content/security/index.mdx @@ -13,7 +13,7 @@ We take active steps to demonstrate our commitment to data security and privacy Langfuse is built with enterprise needs in mind, focusing on: - **Security Measures:** Robust [Encryption](/security/encryption), access controls, and regular [Penetration Testing](/security/penetration-testing). -- **Privacy Measures:** Protecting user data according to regulations like [GDPR](/security/gdpr). We offer a [DPA](/security/dpa), [BAA](/security/hipaa), and adhere to our [Privacy Policy](/privacy). +- **Privacy Measures:** Protecting user data according to regulations like [GDPR](/security/gdpr). We offer a [DPA](/dpa), [BAA](/security/hipaa), and adhere to our [Privacy Policy](/privacy). - **Transparency:** Open-source core and clear information on [software dependencies](/security/dependencies). - **Reporting:** Clear channels for [Responsible Disclosure](/security/responsible-disclosure) and [Whistleblowing](/security/whistleblowing). @@ -50,7 +50,7 @@ import { ShieldCheck, BadgeCheck, HeartPulse, FileLock } from "lucide-react"; ## Privacy -Langfuse is [GDPR](/security/gdpr) compliant, and offers data retention, data masking and data deletion capabilities to [manage the processing of personal data](/security/manage-personal-data). You can enter into a [DPA](/security/dpa) with Langfuse. +Langfuse is [GDPR](/security/gdpr) compliant, and offers data retention, data masking and data deletion capabilities to [manage the processing of personal data](/security/manage-personal-data). You can enter into a [DPA](/dpa) with Langfuse. ## Contact diff --git a/content/security/meta.json b/content/security/meta.json index 302cf4eb81..b64b9641c2 100644 --- a/content/security/meta.json +++ b/content/security/meta.json @@ -17,7 +17,7 @@ "penetration-testing", "vulnerability-management", "security-faq", - "toms", + "[TOMs ↗](/toms)", "---Compliance---", "policies", "soc2", @@ -25,8 +25,8 @@ "hipaa", "compliance-faq", "---Privacy---", - "dpa", - "subprocessors", + "[DPA ↗](/dpa)", + "[Subprocessors ↗](/subprocessors)", "gdpr", "manage-personal-data", "privacy-faq", diff --git a/content/security/privacy-faq.mdx b/content/security/privacy-faq.mdx index 9209a80fa8..2024ccc1a0 100644 --- a/content/security/privacy-faq.mdx +++ b/content/security/privacy-faq.mdx @@ -15,7 +15,7 @@ No. Langfuse does not train or fine‑tunes ML/LLM models on Client Data. See [t > **Can we enter into a Data Processing Agreement (DPA)?** -Yes. You can enter into a [DPA](/security/dpa) with Langfuse. +Yes. You can enter into a [DPA](/dpa) with Langfuse. > **How long is data retained?** diff --git a/content/security/subprocessors.mdx b/content/security/subprocessors.mdx deleted file mode 100644 index 90d66290d2..0000000000 --- a/content/security/subprocessors.mdx +++ /dev/null @@ -1,68 +0,0 @@ ---- -title: Subprocessors ---- - -# Subprocessors - -Langfuse (Langfuse GmbH) uses the following subprocessors to provide our services. See [data regions](/security/data-regions) for more information on our availability zones (EU, Japan, US, and HIPAA US). - -## Affiliates - -| Company | Purpose | Type of Data | Categories of Data Subjects | Location of Data Processing | -| ------------------------------------------------- | ------------------- | ------------ | ---------------------------------- | --------------------------- | -| Clickhouse Inc. (parent company of Langfuse GmbH) | Servicing & Support | Client Data | Affected individuals of the client | US | - -## Langfuse Cloud: EU - -`cloud.langfuse.com` - -| Company | Purpose | Type of Data | Categories of Data Subjects | Location of Data Processing | -| -------------------------------------- | --------------------------------------------------------- | ------------ | ---------------------------------- | --------------------------- | -| Amazon Web Services, Inc. | Application Hosting | Client Data | Affected individuals of the client | EU | -| Clickhouse Inc. | Application Hosting | Client Data | Affected individuals of the client | EU | -| Google LLC | Product Metrics | Client Data | Affected individuals of the client | EU | -| Posthog, Inc. | Product metrics | Client Data | Affected individuals of the client | EU | -| Datadog, Inc. | Application logs | Client Data | Affected individuals of the client | EU | -| Cloudflare, Inc. | Web Application Security (e.g. Firewall, DDOS protection) | Client Data | Affected individuals of the client | Global Edge | -| Functional Software, Inc. d/b/a Sentry | Application logs | Client Data | Affected individuals of the client | EU | - -## Langfuse Cloud: US - -`us.cloud.langfuse.com` - -| Company | Purpose | Type of Data | Categories of Data Subjects | Location of Data Processing | -| -------------------------------------- | --------------------------------------------------------- | ------------ | ---------------------------------- | --------------------------- | -| Amazon Web Services, Inc. | Application Hosting | Client Data | Affected individuals of the client | US | -| Clickhouse Inc. | Application Hosting | Client Data | Affected individuals of the client | US | -| Google LLC | Product Metrics | Client Data | Affected individuals of the client | EU | -| Posthog, Inc. | Product metrics | Client Data | Affected individuals of the client | EU | -| Datadog, Inc. | Application logs | Client Data | Affected individuals of the client | US | -| Cloudflare, Inc. | Web Application Security (e.g. Firewall, DDOS protection) | Client Data | Affected individuals of the client | Global Edge | -| Functional Software, Inc. d/b/a Sentry | Application logs | Client Data | Affected individuals of the client | US | - -## Langfuse Cloud: Japan - -`jp.cloud.langfuse.com` - -The Japan region uses the same subprocessors as the EU region. Amazon Web Services and Clickhouse host application data in Japan; all other subprocessors match the EU region. - -| Company | Purpose | Type of Data | Categories of Data Subjects | Location of Data Processing | -| -------------------------------------- | --------------------------------------------------------- | ------------ | ---------------------------------- | --------------------------- | -| Amazon Web Services, Inc. | Application Hosting | Client Data | Affected individuals of the client | Japan | -| Clickhouse Inc. | Application Hosting | Client Data | Affected individuals of the client | Japan | -| Google LLC | Product Metrics | Client Data | Affected individuals of the client | EU | -| Posthog, Inc. | Product metrics | Client Data | Affected individuals of the client | EU | -| Datadog, Inc. | Application logs | Client Data | Affected individuals of the client | EU | -| Cloudflare, Inc. | Web Application Security (e.g. Firewall, DDOS protection) | Client Data | Affected individuals of the client | Global Edge | -| Functional Software, Inc. d/b/a Sentry | Application logs | Client Data | Affected individuals of the client | EU | - -## Langfuse HIPAA: US - -`hipaa.cloud.langfuse.com` - -The HIPAA-compliant US region is hosted in the US and is subject to the same subprocessors as the US region. PHI data is only stored and processed by the following subset of subprocessors: - -| Company | Purpose | Type of Data | Categories of Data Subjects | Location of Data Processing | -| ------------------------- | ------------------- | ------------ | ---------------------------------- | --------------------------- | -| Amazon Web Services, Inc. | Application Hosting | PHI | Affected individuals of the client | US | -| Clickhouse Inc. | Application Hosting | PHI | Affected individuals of the client | US | diff --git a/content/security/toms.mdx b/content/security/toms.mdx deleted file mode 100644 index f2ae6d2858..0000000000 --- a/content/security/toms.mdx +++ /dev/null @@ -1,177 +0,0 @@ ---- -title: Technical and Organisational Measures (TOMs) ---- - -# Langfuse Technical and Organisational Measures (TOMs) - -Langfuse implements the following technical and organisational measures (TOMs) to protect the confidentiality, integrity, and availability of data. - -**Latest revision:** October 17th, 2025 | **download as PDF** - -## 1. Confidentiality - -### 1.1 Physical Access Control - -> Preventing unauthorised persons from gaining access to data‑processing systems. - -_Technical Measures_ - -- Locking systems -- Lockable storage containers - -_Organisational Measures_ - -- Physical Security Policy -- Visitors accompanied by employees -- Information Security Policy - -### 1.2 Logical Access Control - -> Preventing data‑processing systems from being used by unauthorised persons. - -_Technical Measures_ - -- Login with username and strong password or SSO where available -- Encryption of devices -- Enforced MFA where applicable -- Automatic desktop lock - -_Organisational Measures_ - -- User‑permission management -- Creating user profiles -- Information Security Policy - -### 1.3 Authorisation Control - -> Ensuring employees can only access data subject to their authorisation and cannot read, copy, modify or remove Personal Data without permission. - -_Technical Measures_ - -- Logging of access to applications or databases (entering, changing, deleting data) -- SSH‑encrypted access -- TLS encryption in transit - -_Organisational Measures_ - -- Minimum number of administrators -- Management of user rights by administrators -- No shared accounts where technically feasible -- Information Security Policy - -### 1.4 Separation Control - -> Ensuring data collected for different purposes is processed separately. - -_Technical Measures_ - -- Separation of production and test environments -- Multi‑tenancy of relevant applications - -_Organisational Measures_ - -- Control via authorisation concept -- Determination of database rights -- Information Security & Data‑Protection Policies - -## 2. Integrity - -### 2.1 Transfer Control - -> Ensuring Personal Data cannot be read, copied, altered or removed by unauthorised persons during electronic transmission or transport/storage on media. - -_Technical Measures_ - -- Provision via encrypted connections (SFTP, HTTPS, secure cloud stores) - -_Organisational Measures_ - -- Information Security & Data‑Protection Policies - -### 2.2 Input Control - -> Ability to verify whether and by which user Personal Data has been entered, modified or removed. - -_Technical Measures_ - -- Manual or automated logging of database access -- Traceability through individual user names (not groups) - -_Organisational Measures_ - -- Assignment of rights based on an authorisation concept -- Information Security Policy - -## 3. Availability and Resilience - -### 3.1 Availability Control - -> Protecting Personal Data against accidental destruction or loss. - -_Technical Measures_ - -- Hosting in certified data centres by reputable cloud providers (e.g. AWS) -- Using multiple availability zones within a cloud region -- Backup concept -- Use of as many fully managed services as feasible to reduce downtimes -- Monitoring and alerting for capacity and functioning of core processes -- Using highly available and horizontally scalable architectures where possible - -_Organisational Measures_ - -- Business continuity and disaster‑recovery plan -- Information Security Policy - -### 3.2 Recoverability Control - -> Rapid restoration of availability and access after an incident. - -_Technical Measures_ - -- Backup monitoring and reporting -- Automated restoration tools -- Regular recovery tests with logged results - -_Organisational Measures_ - -- Recovery concept aligned to data criticality and Client specs -- Information Security Policy - -## 4. Regular Review, Assessment and Evaluation - -### 4.1 Data‑Protection Management - -- Central documentation of data‑protection regulations accessible to employees -- Privacy Officer appointed -- Annual review of TOMs and updates -- Staff trained and bound to confidentiality -- Regular awareness trainings -- Processes for information obligations (Art 13/14 GDPR) -- Formal DSAR process -- Data protection in corporate risk management - -### 4.2 Incident Response Management - -- Email security gateway, anti‑malware, and filtering controls with regular updates -- Documented incident‑response process covering authority notifications -- Formalised procedure for handling incidents -- Involvement of Privacy Officer and CTO -- Ticket‑based documentation and follow‑up of incidents - -### 4.3 Data Protection by Design and Default - -- No more Personal Data collected than necessary -- Privacy‑friendly default settings in software - -### 4.4 Order Control (Sub‑Processors) - -- Vendor due‑diligence and DPAs/SCCs in place -- Monitoring of subcontractors -- Audit rights over contractors -- Secure deletion of data after contract end - -## 5. Organisation and Staff - -- Information‑security as a core corporate objective -- Employees bound to confidentiality and data secrecy -- External parties subject to NDA before work commences diff --git a/lib/redirects.js b/lib/redirects.js index 91496d2564..085cdd6121 100644 --- a/lib/redirects.js +++ b/lib/redirects.js @@ -14,6 +14,28 @@ const nonPermanentRedirects = [ "/loom-gpt4-PR", "https://www.loom.com/share/5c044ca77be44ff7821967834dd70cba", ], + [ + "/terms", + "https://clickhouse.com/legal/clickhouse-general-terms-and-conditions", + ], + [ + "/security/dpa", + "https://clickhouse.com/legal/agreements/data-processing-addendum", + ], + ["/dpa", "https://clickhouse.com/legal/agreements/data-processing-addendum"], + [ + "/security/subprocessors", + "https://clickhouse.com/legal/agreements/langfuse-subprocessors", + ], + [ + "/subprocessors", + "https://clickhouse.com/legal/agreements/langfuse-subprocessors", + ], + [ + "/security/toms", + "https://clickhouse.com/legal/agreements/security-addendum", + ], + ["/toms", "https://clickhouse.com/legal/agreements/security-addendum"], // short links ["/discord", "https://discord.gg/7NXusRtqYU"], From 9bf47388c25d939ecd0b8aa2af3b5136182387e4 Mon Sep 17 00:00:00 2001 From: Marc Klingen Date: Fri, 26 Jun 2026 11:19:16 +0200 Subject: [PATCH 3/5] update NDA page --- content/security/nda.mdx | 113 ++------------------------------------- 1 file changed, 5 insertions(+), 108 deletions(-) diff --git a/content/security/nda.mdx b/content/security/nda.mdx index 681ed25fe5..7bd9ce9a18 100644 --- a/content/security/nda.mdx +++ b/content/security/nda.mdx @@ -1,113 +1,10 @@ --- -title: NDA (Non Disclosure Agreement) -description: Request a NDA (Non Disclosure Agreement) with Langfuse +title: NDA (Non-disclosure agreement) +description: Langfuse can enter into NDAs with customers. Contact us to start the process. --- -# NDA (Non Disclosure Agreement) +# NDA (Non-disclosure agreement) -## Request an NDA with Langfuse +Langfuse can enter into non-disclosure agreements with customers during procurement, security reviews, or onboarding. -During procurement and onboarding, users sometimes request an NDA (Non Disclosure Agreement) with Langfuse. We have a standard NDA template that you can find below. You can request signature of this NDA by sending an email to legal@clickhouse.com. Please include a few sentences about the purpose of the NDA. - -**Latest revision:** October 17th, 2025 | **download as PDF** - -## Langfuse NDA Template - -### Mutual Non-Disclosure Agreement (MNDA) - -This Mutual Non-Disclosure Agreement (the "Agreement") is entered into by and between the parties below and shall be effective as of the date of the last signature affixed hereto (the "Effective Date"): - -**Party 1:**\ -Langfuse GmbH\ -Oranienburgerstraße 91, 10178 Berlin, Germany\ -Notices to: legal@clickhouse.com - -**Party 2:**\ -[Counterparty Name] \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ - -[Counterparty Address] \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ - ---- - -### 1. Purpose - -The parties wish to explore a potential business relationship. In connection with this, each party may disclose certain confidential and proprietary information to the other. - -### 2. Definition of Confidential Information - -"Confidential Information" means any non-public information disclosed by one party ("Disclosing Party") to the other ("Receiving Party"), whether oral, written, electronic, or otherwise, that is designated as confidential or that reasonably should be understood to be confidential under the circumstances. - -Confidential Information includes, without limitation, business, technical, financial, product, roadmap, pricing, or other proprietary information. - -Confidential Information does not include information that: - -- (a) is or becomes publicly known without breach of this Agreement; -- (b) was rightfully known by the Receiving Party before disclosure; -- (c) is rightfully received from a third party without restriction; or -- (d) is independently developed without use of the Disclosing Party's Confidential Information. - -### 3. Obligations of the Receiving Party - -The Receiving Party agrees to: - -- (a) use Confidential Information solely for the Purpose; -- (b) not disclose Confidential Information to any third party except to employees, contractors, or advisors with a need to know who are bound by confidentiality obligations at least as restrictive as those herein; and -- (c) protect Confidential Information with the same degree of care it uses to protect its own confidential information, but at least a reasonable standard of care. - -### 4. Disclosures Required by Law - -The Receiving Party may disclose Confidential Information if required by law, regulation, or court order, provided it gives reasonable notice to the Disclosing Party (where legally permissible) to allow the Disclosing Party to seek protective measures. - -### 5. Term and Termination - -This Agreement will remain in effect for three (3) years from the Effective Date. Either party may terminate this Agreement upon written notice. The Receiving Party's duty to protect Confidential Information survives for two (2) years from the date of last disclosure, except for trade secrets, which remain protected until they cease to qualify as trade secrets under applicable law. - -### 6. Return or Destruction of Information - -Upon termination or upon written request, the Receiving Party shall return or destroy all Confidential Information, except that copies retained in standard backup or archival systems may be kept provided they remain subject to this Agreement. - -### 7. Proprietary Rights - -All Confidential Information remains the property of the Disclosing Party. No license or other rights are granted except as expressly set forth herein. - -### 8. Disclaimer - -ALL CONFIDENTIAL INFORMATION IS PROVIDED "AS IS" WITHOUT WARRANTIES OF ANY KIND, WHETHER EXPRESS OR IMPLIED. - -### 9. Equitable Relief - -The Receiving Party acknowledges that unauthorized disclosure or use of Confidential Information may cause irreparable harm for which monetary damages may be inadequate, and the Disclosing Party is entitled to seek injunctive or equitable relief. - -### 10. Governing Law and Jurisdiction - -This Agreement shall be governed by and construed in accordance with the laws of England and Wales. The parties submit to the exclusive jurisdiction of the courts of London, England, United Kingdom. - -### 11. General - -This Agreement constitutes the entire agreement between the parties with respect to the subject matter hereof and supersedes all prior agreements or understandings. Any amendments must be in writing and signed by both parties. If any provision is found invalid or unenforceable, the remaining provisions will remain in full force and effect. - ---- - -## Signatures - -**Langfuse GmbH** - -By: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ - -Name: Marc Klingen - -Title: Managing Director - -Date: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ - -**Counterparty** - -By: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ - -Name: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ - -Title: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ - -Date: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ - -Email: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ +To start the process, please [talk to us](/talk-to-us) and include a brief note about the purpose of the NDA. From 79ac874f046785e8de026ddea142b02b586ded59 Mon Sep 17 00:00:00 2001 From: Marc Klingen Date: Fri, 26 Jun 2026 11:49:05 +0200 Subject: [PATCH 4/5] ensure consistency --- content/faq/all/fifteen-questions-langfuse-answered.mdx | 4 ++-- .../playbooks/vulnerability-handling.mdx | 2 +- .../handbook/support/how-to-answer-support-questions.mdx | 2 +- content/marketing/privacy.mdx | 8 ++++---- content/security/data-regions.mdx | 2 +- content/security/dependencies.mdx | 2 +- content/security/encryption.mdx | 2 +- content/security/iso27001.mdx | 2 +- content/security/networking.mdx | 2 +- content/security/penetration-testing.mdx | 2 +- content/security/responsible-disclosure.mdx | 4 ++-- content/security/security-faq.mdx | 2 +- content/security/soc2.mdx | 2 +- 13 files changed, 18 insertions(+), 18 deletions(-) diff --git a/content/faq/all/fifteen-questions-langfuse-answered.mdx b/content/faq/all/fifteen-questions-langfuse-answered.mdx index 087abc26de..ead8b661db 100644 --- a/content/faq/all/fifteen-questions-langfuse-answered.mdx +++ b/content/faq/all/fifteen-questions-langfuse-answered.mdx @@ -65,7 +65,7 @@ As a fallback, you can always use [our API](/docs/api) to ingest data into Langf ## 7. Can Langfuse provide a DPA to its customers? -**Yes, Langfuse can provide customers with a DPA.** We are happy to enter into Data Protection Agreements with customers on our paid plans. Please navigate to our [Security Center](/security/gdpr) to review our DPA template. +**Yes, Langfuse can provide customers with a DPA.** You can review the current [DPA](/dpa) from our [Security Center](/security/gdpr). ## 8. Is Langfuse SOC2 Type2 certified? @@ -77,7 +77,7 @@ As a fallback, you can always use [our API](/docs/api) to ingest data into Langf ## 10. Is Langfuse GDPR compliant? -**Yes, Langfuse is GDPR compliant.** Langfuse is a German company, based in Berlin, Germany and we take privacy a data security very seriously. You can use Langfuse in compliance with GDPR. You will need to a) use our EU Cloud Data Region and enter into a DPA with us or b) self-host Langfuse. +**Yes, Langfuse is GDPR compliant.** You can use Langfuse in compliance with GDPR by using our EU Cloud Data Region and entering into a [DPA](/dpa), or by self-hosting Langfuse in your chosen environment. You can find more information in our [Security Center](/security/gdpr). diff --git a/content/handbook/product-engineering/playbooks/vulnerability-handling.mdx b/content/handbook/product-engineering/playbooks/vulnerability-handling.mdx index 96d70f3fe0..fb6aa1a0c9 100644 --- a/content/handbook/product-engineering/playbooks/vulnerability-handling.mdx +++ b/content/handbook/product-engineering/playbooks/vulnerability-handling.mdx @@ -9,7 +9,7 @@ We have two different processes for handling security reports. These security re ## Process 1: Manual Security Reports -Security reports sent to `security@langfuse.com` are forwarded to Pylon (our support tool), where an engineer is auto-assigned to triage and create a Linear ticket. +Security reports sent to `security@clickhouse.com` are forwarded to Pylon (our support tool), where an engineer is auto-assigned to triage and create a Linear ticket. ```mermaid flowchart LR diff --git a/content/handbook/support/how-to-answer-support-questions.mdx b/content/handbook/support/how-to-answer-support-questions.mdx index 816064428e..57087b8f46 100644 --- a/content/handbook/support/how-to-answer-support-questions.mdx +++ b/content/handbook/support/how-to-answer-support-questions.mdx @@ -576,7 +576,7 @@ Container scanners (Wiz, Snyk, Trivy, Black Duck) regularly produce long lists o **Triage steps:** 1. Check the version the customer scanned. If it's not the latest, ask them to scan the current image first, many CVEs are already patched in the next release. -2. For genuine concerns, route to `security@langfuse.com` for triage. +2. For genuine concerns, route to `security@clickhouse.com` for triage. 3. Do not promise fix timelines. We patch on rolling cadence with each release. **Reply template:** diff --git a/content/marketing/privacy.mdx b/content/marketing/privacy.mdx index d48d188521..ce317ea7a1 100644 --- a/content/marketing/privacy.mdx +++ b/content/marketing/privacy.mdx @@ -388,10 +388,10 @@ to be informed of how we are protecting your information. If you have questions or comments about this notice, you may email us at **[legal@clickhouse.com](mailto:legal@clickhouse.com)** or contact us by post at: -ClickHouse, Inc. -c/o Goodwin Proctor LLP -601 Marshall St -Redwood City, CA 94063 +ClickHouse, Inc.
+c/o Goodwin Proctor LLP
+601 Marshall St
+Redwood City, CA 94063
Attn: Privacy Practice Group If you are a resident in the European Economic Area, we are the "data controller" of your personal information. diff --git a/content/security/data-regions.mdx b/content/security/data-regions.mdx index d276bf1ebd..145e79c05f 100644 --- a/content/security/data-regions.mdx +++ b/content/security/data-regions.mdx @@ -101,4 +101,4 @@ Alternatively, you can self-host Langfuse for full control over your data and in ## Contact -For questions about data regions or availability, contact security@langfuse.com. +For questions about data regions or availability, please [talk to us](/talk-to-us). diff --git a/content/security/dependencies.mdx b/content/security/dependencies.mdx index 5668219aa5..863e62209d 100644 --- a/content/security/dependencies.mdx +++ b/content/security/dependencies.mdx @@ -1,6 +1,6 @@ --- title: Software Dependencies -description: Information on Langfuse's software dependencies, licensing, and data subprocessors. +description: Information on Langfuse's software dependencies and licensing. --- # Software Dependencies & Licensing diff --git a/content/security/encryption.mdx b/content/security/encryption.mdx index fb998bbcd8..f4c48d05ec 100644 --- a/content/security/encryption.mdx +++ b/content/security/encryption.mdx @@ -28,4 +28,4 @@ This applies to data stored in: ## Contact -For questions regarding encryption practices, please contact security@langfuse.com. +For questions regarding encryption practices, please [talk to us](/talk-to-us). diff --git a/content/security/iso27001.mdx b/content/security/iso27001.mdx index efa7e2ca24..072baf044f 100644 --- a/content/security/iso27001.mdx +++ b/content/security/iso27001.mdx @@ -13,4 +13,4 @@ Langfuse Cloud is **ISO 27001 certified**. This international standard specifies ## Contact -For questions regarding ISO 27001 compliance, please contact compliance@langfuse.com. +For questions regarding ISO 27001 compliance, please [talk to us](/talk-to-us). diff --git a/content/security/networking.mdx b/content/security/networking.mdx index 0ff2046e4b..b9f25e24a8 100644 --- a/content/security/networking.mdx +++ b/content/security/networking.mdx @@ -19,4 +19,4 @@ Langfuse Cloud makes outbound API calls from our infrastructure on behalf of use ## Contact -For questions regarding networking, please contact security@langfuse.com. +For questions regarding networking, please [talk to us](/talk-to-us). diff --git a/content/security/penetration-testing.mdx b/content/security/penetration-testing.mdx index 2a77e2eaf5..189243f402 100644 --- a/content/security/penetration-testing.mdx +++ b/content/security/penetration-testing.mdx @@ -27,4 +27,4 @@ The findings from these penetration tests help us continuously improve our secur ## Contact -For questions regarding our penetration testing program, please contact security@langfuse.com. +For questions regarding our penetration testing program, please [talk to us](/talk-to-us). diff --git a/content/security/responsible-disclosure.mdx b/content/security/responsible-disclosure.mdx index 24acbd7448..2e0db20041 100644 --- a/content/security/responsible-disclosure.mdx +++ b/content/security/responsible-disclosure.mdx @@ -9,7 +9,7 @@ We value the security community and prioritize the security of our systems. We e ## Reporting a Vulnerability -If you believe you have found a security vulnerability in Langfuse, please send an actionable vulnerability report to **security@langfuse.com**. +If you believe you have found a security vulnerability in Langfuse, please send an actionable vulnerability report to **security@clickhouse.com**. Please include the following details in your report: @@ -74,4 +74,4 @@ We appreciate the efforts of security researchers who help keep Langfuse secure. ## Contact -For all security-related inquiries, including vulnerability disclosures, please contact security@langfuse.com. +For all security-related inquiries, including vulnerability disclosures, please contact security@clickhouse.com. diff --git a/content/security/security-faq.mdx b/content/security/security-faq.mdx index 5500b4a398..bf19c057f3 100644 --- a/content/security/security-faq.mdx +++ b/content/security/security-faq.mdx @@ -7,7 +7,7 @@ description: Answers to common questions about Langfuse's security practices. This page addresses frequently asked questions and common security topics for Langfuse. Please refer to [compliance FAQs](/security/compliance-faq) for details on compliance topics. -If you don't find a solution to your issue here, try using [Ask AI](/docs/ask-ai) for instant answers or reach out to security@langfuse.com +If you don't find a solution to your issue here, try using [Ask AI](/docs/ask-ai) for instant answers or reach out to security@clickhouse.com ## Application Security diff --git a/content/security/soc2.mdx b/content/security/soc2.mdx index e3e2adf000..98dcda5afa 100644 --- a/content/security/soc2.mdx +++ b/content/security/soc2.mdx @@ -13,4 +13,4 @@ Langfuse Cloud has successfully completed the **SOC 2 Type II audit**. ## Contact -For questions regarding SOC 2 compliance, please contact compliance@langfuse.com. +For questions regarding SOC 2 compliance, please [talk to us](/talk-to-us). From f09c78bb491ee06e1871af81e906ef3978b64060 Mon Sep 17 00:00:00 2001 From: Marc Klingen Date: Fri, 26 Jun 2026 11:52:01 +0200 Subject: [PATCH 5/5] Update cookie policy --- content/marketing/cookie-policy.mdx | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/content/marketing/cookie-policy.mdx b/content/marketing/cookie-policy.mdx index 33df31d513..3261b4209e 100644 --- a/content/marketing/cookie-policy.mdx +++ b/content/marketing/cookie-policy.mdx @@ -4,9 +4,9 @@ title: Cookie Policy # Cookie Policy -**Last updated: June 19, 2026 | download as PDF** +**Last updated: July 26, 2026 | download as PDF** -This Cookie Policy explains how **Langfuse GmbH** ("Company," "we," "us," and "our") uses cookies and similar technologies to recognize you when you visit our website at https://www.langfuse.com ("Website"). It explains what these technologies are and why we use them, as well as your rights to control our use of them. +This Cookie Policy explains how **ClickHouse, Inc.** and its affiliates and subsidiaries ("we," "us," and "our") uses cookies and similar technologies to recognize you when you visit our website at [https://www.langfuse.com](https://www.langfuse.com) ("Website") and any other website that we own or control and which posts or links to this Cookie Policy (collectively, the “Online Properties”). It explains what these technologies are and why we use them, as well as your rights to control our use of them. Note that we maintain a separate cookie policy for ClickHouse-branded websites and online services, which is different from this Cookie Policy. For more information about that policy, visit: https://clickhouse.com/legal/cookie-policy. In some cases we may use cookies to collect personal information, or that becomes personal information if we combine it with other information. @@ -14,7 +14,7 @@ In some cases we may use cookies to collect personal information, or that become Cookies are small data files that are placed on your computer or mobile device when you visit a website. Cookies are widely used by website owners in order to make their websites work, or to work more efficiently, as well as to provide reporting information. -Cookies set by the website owner (in this case, Langfuse GmbH) are called "first-party cookies." Cookies set by parties other than the website owner are called "third-party cookies." Third-party cookies enable third-party features or functionality to be provided on or through the website (e.g., advertising, interactive content, and analytics). The parties that set these third-party cookies can recognize your computer both when it visits the website in question and also when it visits certain other websites. +Cookies set by the website owner (in this case, us) are called "first-party cookies." Cookies set by parties other than the website owner are called "third-party cookies." Third-party cookies enable third-party features or functionality to be provided on or through the website (e.g., advertising, interactive content, and analytics). The parties that set these third-party cookies can recognize your computer both when it visits the website in question and also when it visits certain other websites. ## Why do we use cookies? @@ -72,10 +72,10 @@ The date at the top of this Cookie Policy indicates when it was last updated. ## Where can I get further information? -If you have any questions about our use of cookies or other technologies, please email us at legal@clickhouse.com or by post to: +If you have any questions about our use of cookies or other technologies, please email us at privacy@clickhouse.com or by post to: -Langfuse GmbH
-Oranienburgerstraße 91
-10178 Berlin
-Germany
-Phone: (+49)015208459573 +ClickHouse, Inc.
+c/o Goodwin Proctor LLP
+601 Marshall St
+Redwood City, CA 94063
+Attn: Privacy Practice Group