# JoeSSH Trademark Policy

Last updated: 2026-07-30

The MIT License grants broad rights in the source code but does not grant rights
to imply endorsement or to pass off modified software as an official JoeSSH
release. This policy keeps those source-code freedoms intact while helping users
identify official builds.

`JoeSSH`, `JoeSSH Community`, the JoeSSH logo, and the distinctive JoeSSH
application icon are project marks. No claim is made here that a mark is
registered. The legal owner for future permissions and enforcement must be
published before a commercial launch:
`{{TRADEMARK_OWNER_LEGAL_NAME_AND_CONTACT}}`.

## Uses That Do Not Need Separate Permission

You may:

- truthfully refer to JoeSSH in discussion, reviews, tutorials, issue reports,
  and compatibility statements;
- link to the canonical repository or an official release;
- use an unmodified project screenshot to describe the project, with
  attribution and without implying sponsorship;
- state that a fork is “based on JoeSSH” or “compatible with JoeSSH” when the
  statement is accurate and visually secondary to the fork's own name;
- retain notices required by the MIT License or a third-party license.

## Uses That Need Permission

Separate written permission is required to:

- distribute a modified binary, hosted service, extension, or bundle under the
  JoeSSH or JoeSSH Community name;
- use a JoeSSH mark as the primary name, logo, domain, social account, package,
  app-store listing, or marketplace identity of another product;
- use a mark on paid merchandise, advertising, or commercial sponsorship;
- claim that a fork, service, training course, or integration is certified,
  approved, supported, or operated by the JoeSSH project.

Until `{{TRADEMARK_OWNER_LEGAL_NAME_AND_CONTACT}}` is replaced by a verified
permission route, no discretionary trademark permission can be granted.

## Forks And Redistributors

The MIT License permits modification, redistribution, hosting, and sale of the
code when its notice is preserved. A materially modified distribution should:

1. choose a distinct product name and icon;
2. remove claims that it is an official JoeSSH build;
3. identify the modification and its maintainer;
4. retain applicable copyright and license notices;
5. use any JoeSSH reference only to explain origin or compatibility.

An unmodified mirror may identify the original project, but must not imply that
the mirror is the canonical download source. Security-sensitive users should be
directed to the canonical repository and its published checksums.

## Community Events And Contributions

Contributors may identify themselves as JoeSSH contributors, but not as
employees, agents, or authorized spokespeople unless that relationship exists.
Community groups may use a factual phrase such as “JoeSSH user group” if they
clearly state that they are independent and do not use the official logo as
their own identity.

## Reporting Confusing Use

Use `{{TRADEMARK_OWNER_LEGAL_NAME_AND_CONTACT}}` to request permission or report
confusing use after that route is verified. Security issues belong in the
private channel documented in [SECURITY.md](SECURITY.md).