> ## Documentation Index > Fetch the complete documentation index at: https://docs.tomorrowos.org/llms.txt > Use this file to discover all available pages before exploring further. # Trademark # Trademark and Brand Usage TomorrowOS is an open source unified API layer for digital signage operating systems. This document explains how the TomorrowOS name, logo and brand may be used. The goal is to allow healthy open source use while protecting the official identity of the project. ## Purpose TomorrowOS may be forked, modified, extended or used as a foundation for other projects, subject to the project license. However, the project license does not automatically grant permission to use the TomorrowOS name, logo, branding or official project identity in a way that may confuse users. This policy is intended to protect: * The TomorrowOS name * The TomorrowOS logo * The official project identity * The reputation of the project * Users who need to know whether something is official or unofficial ## Open source code vs brand identity The TomorrowOS code may be used under the project license. The TomorrowOS brand is separate from the code. This means you may be allowed to use, fork or modify the code, but that does not automatically mean you can present your fork, product, service or commercial offering as the official TomorrowOS project. ## Acceptable use You may use the TomorrowOS name when making truthful, non-misleading references to the project. Examples of acceptable use: * “Built using TomorrowOS” * “Compatible with TomorrowOS” * “Powered by TomorrowOS” * “Uses the TomorrowOS SDK” * “Forked from TomorrowOS” * “Based on the TomorrowOS open source project” * “Contributes to the TomorrowOS project” These uses should make it clear whether your project is official or independent. ## Unacceptable use You may not use the TomorrowOS name, logo or brand in a way that suggests your project, company, product, service or fork is officially operated, approved, endorsed or maintained by the TomorrowOS maintainers unless you have written permission. Examples of unacceptable use: * Presenting a fork as the official TomorrowOS project * Using the TomorrowOS name as the main name of a competing commercial product * Using the TomorrowOS logo in a way that suggests official endorsement * Registering domains, social handles or company names that imply official control of TomorrowOS * Claiming official partnership, certification or approval without permission * Using TomorrowOS branding in a misleading way * Removing attribution while still implying official association ## Forks You may fork TomorrowOS under the project license. If you publish a fork, please make it clear that it is a fork and not the official TomorrowOS project. A fork should not use a name, logo or branding that could confuse users into thinking it is the official TomorrowOS repository or release. Good examples: ```txt theme={null} MySignageRuntime, based on TomorrowOS ExampleOS, a fork of TomorrowOS Custom signage connector built on TomorrowOS ``` Avoid examples like: ```txt theme={null} TomorrowOS Pro TomorrowOS Enterprise Official TomorrowOS Cloud TomorrowOS Certified Runtime ``` unless you have written permission. ## Commercial use You may use TomorrowOS in commercial products, subject to the project license and disclaimer. Commercial products built on top of TomorrowOS should not imply that they are official TomorrowOS products unless that relationship has been agreed in writing. If you offer a commercial product, service, support plan or hosted platform built on TomorrowOS, you are responsible for: * Your own customers * Your own support * Your own security * Your own uptime * Your own warranties * Your own documentation * Your own claims * Your own compliance * Your own fork or implementation See: ```txt theme={null} DISCLAIMER.md SUPPORT.md LICENSE.md ``` ## “Powered by TomorrowOS” You may use “Powered by TomorrowOS” if your project genuinely uses TomorrowOS and the statement is accurate. The statement should not suggest that the TomorrowOS maintainers are responsible for your product, deployment, support or customer outcomes. Recommended wording: ```txt theme={null} Powered by TomorrowOS open source technology. ``` or: ```txt theme={null} Built using the TomorrowOS open source project. ``` ## Certification claims Do not claim that a device, connector, CMS, player, app, runtime or product is “TomorrowOS Certified” unless an official certification process exists and the product has completed that process. Until an official certification process is published, certification language should be avoided. Avoid claims such as: ```txt theme={null} TomorrowOS Certified Official TomorrowOS Partner Official TomorrowOS Device Official TomorrowOS Connector Approved by TomorrowOS ``` unless written permission has been granted. ## Compatibility claims You may make truthful compatibility claims if they are accurate and tested. Examples: ```txt theme={null} Tested with TomorrowOS capability checks. Compatible with the TomorrowOS SDK. Uses TomorrowOS-style capability mapping. ``` Compatibility claims should include tested versions, devices or environments where possible. Do not imply universal compatibility unless it has been properly tested. ## Logo usage If a TomorrowOS logo or visual identity is published, it should only be used in a way that is truthful and not misleading. Do not modify the logo in a way that suggests official endorsement of a separate product, fork or service. Do not use the logo as the main brand identity for an independent commercial product without permission. ## Domains and social handles Do not register domains, social media accounts or project names that imply official ownership or control of TomorrowOS unless you are authorised to do so. Examples to avoid: ```txt theme={null} tomorrowos-cloud.com tomorrowos-enterprise.com official-tomorrowos.com TomorrowOSCloud TomorrowOSEnterprise ``` ## No endorsement Use of TomorrowOS does not mean the project maintainers endorse your product, service, company, connector, deployment, fork or customer implementation. You are responsible for your own claims and customer commitments. ## Reporting misuse If you believe the TomorrowOS name, logo or brand is being used in a confusing or misleading way, please contact the project maintainers. For security issues, follow the process in: ```txt theme={null} SECURITY.md ``` ## Future updates This trademark and brand usage policy may be updated as TomorrowOS grows. Future updates may include: * Logo usage rules * Partner badge rules * Certification badge rules * Commercial support badge rules * Approved wording examples * Brand asset guidelines ## Summary TomorrowOS is open source, but the official project identity should remain clear. Use the code according to the license. Use the name and brand honestly. Do not mislead users into thinking an unofficial fork, service or product is the official TomorrowOS project.