# Trademark & brand

The code is GPL-3.0 — but a license on the code does **not** grant the right to
use the project's name or logo. A fork may copy the code; it should ship under
its own name.

## Do I need a registered trademark?

Not on day one. Two levels:

- **Unregistered (™).** You get common-law rights simply by using the mark, and
  you can put **™** next to the name today. Cheap, but limited.
- **Registered (®).** A national or EU registration gives stronger, easier-to-
  enforce rights. Relevant Nice classes: **9** (software) and **42** (SaaS and
  software services).

## When to file

When the project has users worth impersonating — some traction, or a paid tier.
Before that, a registration mostly costs money.

## Practical steps

1. Use **Linux Doctor™** in the README and on any site, with a short notice:
   "Linux Doctor is a trademark of <you>. The GPL-3.0 license covers the code,
   not the name."
2. Before filing, do a **clearance search** (EUIPO eSearch, USPTO TESS) — the
   name is common, so check for conflicts first.
3. File via **EUIPO** (EU) and/or **USPTO** (US) when it is worth it. A
   trademark attorney helps with the classes and the wording.
4. Keep the npm/AUR/COPR/AppImageHub package names registered to you — owning
   them blocks the cheapest form of impersonation.

Not legal advice.