Skip to content
TealbrickBring your next client (opens WhatsApp)

Legal

Brand Use and Contribution Policy

How you may use the Tealbrick name, logo and look and feel, and how contributions to our public repositories are licensed. Effective date: 15 October 2026.

Version 1.1 · Last updated 15 October 2026

Part 1 — Brand Use Policy

1.1 What the brand is

“Brand Assets” means: the names TEALBRICK, TEAL BRICK and POLYGONFACE; the Tealbrick logo and app icons; our product names when used with “Tealbrick” (for example “Tealbrick Knowledge”); and the look and feel of our websites, Portal and apps (layout, colour system, typography, icons, illustrations, screenshots). Polygonface s.r.o. owns them. Tealbrick™ is a trademark of Polygonface s.r.o.

1.2 Why we have rules

The Tealbrick mini apps are open source. The brand is not. People must be able to tell what comes from us. The Apache License 2.0 grants no right to our names or marks (its section 6), and neither does the Tealbrick Software Licence.

1.3 Allowed without asking

  1. Say truthfully, in plain text, that you use Tealbrick, that your mini app “works with Tealbrick” or is “built for Tealbrick”, or that your service “deploys Tealbrick mini apps”.
  2. Refer to our products by name in articles, reviews, tutorials, talks and comparisons, if the reference is accurate and does not suggest that we sponsor or endorse you.
  3. Keep our copyright, licence and NOTICE text in copies of our code, as the licences require.

Conditions: use the word mark in plain text only, do not change its spelling, do not use our logo, and do not make it the most prominent element.

1.4 Not allowed without our written permission

  1. Use a Brand Asset, or a confusingly similar name, logo, icon or look and feel, as or in the name of a fork, a product, a hosted service, a company, a reseller or consultancy offer, a domain name, an app store listing, a package name or scope, a container image name or a social media account.
  2. Distribute a modified version of a mini app under the Tealbrick name or logo. A fork must use a different name and remove our logo and product names from its user interface. It may say “based on Tealbrick Knowledge (Apache-2.0)” (with the name of the app it is based on) in its README and NOTICE.
  3. Use our logo, screenshots of Portal, or the current version of our design system in your product or marketing. Earlier versions of the design-system kit that were published under the MIT licence remain under that copyright licence, but it gives no trademark or trade-dress right.
  4. Suggest that you are a Tealbrick partner, reseller or certified provider without a signed partner agreement that allows it.
  5. Register a trademark, domain, company name, package scope or handle that contains “tealbrick” or a confusingly similar term.
  6. Name Tealbrick or Polygonface as the sender or sponsor of messages your agents send.
  7. Use the brand in a way that is false, misleading, disparaging or illegal.

1.5 Partners

Partners may use Brand Assets only as their partner agreement allows, only during the agreement, and must stop when it ends.

1.6 Requests and enforcement

Ask for permission at legal@tealbrick.com with the subject “Brand”. We may refuse or withdraw permission at any time. If you misuse the brand, we may ask you to stop, end your account or partner agreement, and enforce our rights, including under trademark and unfair-competition law.

Part 2 — Contribution Policy (public repositories)

2.1 Our model

Contributions to our public repositories are licensed inbound under the same licence as the repository outbound (the Apache License 2.0), with a Developer Certificate of Origin (DCO 1.1) sign-off on every commit. We do not use a Contributor Licence Agreement.

2.2 Rules for contributors

  1. By sending a contribution (pull request, patch or issue with code) to a public Tealbrick repository, you license it under the Apache License 2.0, as section 5 of that licence states.
  2. Every commit must carry the line Signed-off-by: Your Name <email>. With it you certify the Developer Certificate of Origin 1.1 (https://developercertificate.org).
  3. Use your real name. Do not contribute code you have no right to contribute, for example code owned by your employer without permission, or code under a licence that is incompatible with the Apache License 2.0.
  4. If your contribution contains code produced with an AI tool, you remain responsible for having the right to contribute it under the Apache License 2.0 and for it not copying third-party code. Say so in the pull request.
  5. Contributions give no right to the Tealbrick name or logo (Part 1).
  6. We may accept, change or refuse any contribution. We do not pay for contributions unless we agree in writing.
  7. Security issues: do not open a public issue. Follow the repository’s SECURITY.md and tealbrick.com/security.

2.3 Proprietary repositories

We do not accept outside contributions to private or proprietary repositories, except under a separate signed agreement.

Contact

Polygonface s.r.o., Sládkovičova 60, 974 05 Banská Bystrica, Slovakia. Brand requests and legal notices: legal@tealbrick.com. Tealbrick is a brand of Polygonface s.r.o.