Using the TOVIO name and logo

The marks are TOVIO, TOVIO Cloud, and the TOVIO logo — the faceted-gem mark and the wordmark. The software licence covers the code and not the name: Apache-2.0 section 6 grants no trademark rights, and the commercial licence grants none either.

The policy exists to keep the ecosystem legible, so that anyone who sees the name TOVIO can trust it refers to the official project. It is deliberately not a restriction on your use of the open-source code.

Permitted without asking

Provided the statement is truthful, you may:

• Say your product or service works with TOVIO, is compatible with TOVIO, or is built on TOVIO.
• Redistribute unmodified copies of the Apache-2.0 components under their own names, keeping all notices intact.
• Name a plugin, extension, or integration descriptively — patterns like yourname-for-tovio, tovio-pluginname in a plugin registry, or "Acme's TOVIO integration" — where the naming makes clear the thing is yours and for TOVIO, not from TOVIO.
• Use the name in truthful, nominative ways: articles, reviews, comparisons, tutorials, academic work, conference talks.

Not permitted without written permission

• Naming a fork, competing distribution, derived product, or hosted service "TOVIO" or anything confusingly similar — including misspellings, prefixes and suffixes such as "TOVIO Pro" or "OpenTOVIO", and translations.
• Using the marks in a company name, domain name, social-media handle, or app-store listing in a way that implies you are, or are endorsed by, the official project.
• Shipping a modified version that still carries the marks in a way suggesting it is the official build. Patched packages must make the modification apparent — distribution-style naming such as "tovio, Acme patchset" is fine.
• Using the logo as, or as part of, your own product's logo or branding.

Only the project operates the official TOVIO Cloud.

Forking is fine; misrepresenting a build is not

Apache-2.0 permits forks, and the policy does not touch that right. What it constrains is the name on the result. For a tool whose job is enforcing permissions cryptographically, a build carrying the official name while behaving differently is a security problem as much as a branding one, which is why this rule is stated rather than assumed.

Calling something "TOVIO-conformant"

An independent implementation may describe itself as TOVIO-conformant only if it passes 100 percent of the conformance corpus for the format version it claims. Partial conformance must be reported per vector family, never as a single aggregate pass rate.

This is the one naming rule that carries a technical test rather than a judgement call, and it exists for a reason: the specification and the corpus are Apache-2.0 precisely so independent implementations can be first-class, and the phrase only stays meaningful if the bar is fixed.

Asking

For any use outside the permitted list, ask first — open an issue titled "Trademark request" in the project repository, or contact the maintainers through the route named in the governance document. Requests that keep the ecosystem legible are routinely granted, and asking takes less time than guessing.

Stewardship, and the full text

The marks are held by the project's copyright holder. As governance broadens, formal trademark stewardship moves to whatever neutral body assumes governance. Material changes to the policy are made by decision record and announced in the release notes.

The authoritative document is TRADEMARK.md at the repository root. This article summarises it and does not add to it — if the two ever differ, the file governs.