# Trademark & brand policy

PipRail's **code** is open source under the [MIT License](LICENSE) — use it, fork it, build on it, commercially or otherwise. This page is about the **name and brand**, which the code license does *not* grant. (Plain-language policy, not legal advice.)

## What's covered

**PipRail™**, the PipRail logo, and the **`@piprail`** npm scope are trademarks of the PipRail project, asserted through use. The MIT license covers the source code; it does **not** grant any right to use these marks.

You don't need a company to hold a mark this way — the ™ and consistent public use establish the claim. If the marks are ever formally registered (e.g. with the EUIPO or USPTO), a legal owner will be named at that point.

## You can do this freely (no permission needed)

- Use, fork, modify, and redistribute the code under MIT.
- Say your project "works with PipRail", "is built on PipRail", or "is compatible with PipRail" — accurate, factual references are welcome.
- Write tutorials, posts, and talks that name PipRail.
- Keep PipRail's name in the copyright/attribution notice (the MIT license requires you to).

## Please ask first for this

- Naming a **fork, product, or service "PipRail"** (or a confusingly similar name).
- Using the PipRail **logo** as the logo for your own product or service.
- Publishing under the **`@piprail`** npm scope, or names that imply official PipRail releases.
- Anything that suggests your project is **endorsed by, affiliated with, or the official** PipRail.

The rule of thumb: **use the code freely; don't use the name in a way that confuses people about what's official.** If you fork it, give your fork its own name.

## Questions / permission

Open an issue, or reach out at [x.com/johnweeksdev](https://x.com/johnweeksdev).
