From cc8fac46c3b79db27f03bd6a48ecbec5b0b74a9d Mon Sep 17 00:00:00 2001 From: BOHEUS <56270748+BOHEUS@users.noreply.github.com> Date: Thu, 30 Jul 2026 18:36:22 +0200 Subject: [PATCH] Add licensing section to legal FAQ (#23560) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Review in cubic --------- Co-authored-by: Félix Malfait --- .../user-guide/legal/how-tos/legal-faq.mdx | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/packages/twenty-docs/user-guide/legal/how-tos/legal-faq.mdx b/packages/twenty-docs/user-guide/legal/how-tos/legal-faq.mdx index 68c3a5a282..069df6cc81 100644 --- a/packages/twenty-docs/user-guide/legal/how-tos/legal-faq.mdx +++ b/packages/twenty-docs/user-guide/legal/how-tos/legal-faq.mdx @@ -108,4 +108,18 @@ No, Twenty is in the process of becoming HIPAA compliant. +## Licensing + + + +No. Running a modified version for your own team is not distribution, so no publication obligation arises. The AGPL's network clause applies when people outside your organization interact with your modified instance over the network. + + +No. Your front end is your own, separate work, and talking to Twenty through its APIs does not change that. Since Twenty itself is unmodified, there is nothing to publish. + + +Yes, since you're modifying code to distribute it to others, you're required to publish those changes. If you don't want to publish your changes, you can obtain Organization license. + + + If you have more questions, please check our [Terms and Conditions](https://twenty.com/terms), [Privacy Policy](https://twenty.com/privacy-policy) and [Trust Center](https://trust.twenty.com/). If your questions are still unanswered, send them to [contact@twenty.com](mailto:contact@twenty.com) or via support chat.