# Trademark policy

The **code** in this repository is open source. The **name and the branding**
are not part of that grant. This is the same split Bitwarden and many other open
projects use, and it exists for one reason: so that when someone downloads
something called Relic, they know where it came from.

## What is licensed

Everything in this repository is licensed under [AGPL-3.0](./LICENSE), except
`crypto/`, which is Apache-2.0. You may run it, read it, modify it, redistribute
it, and offer it as a service, under those license terms. Nothing below takes
any of that away.

## What is not licensed

The following are not covered by the software license and no rights to them are
granted:

- the name **Relic** and the name **Relic Cloud**,
- the Relic logo, icon, and other visual branding assets in this repository,
- the domain **relic.space** and its subdomains,
- the package identifiers used for official distribution, including
  `Relic.Relic` on winget and `relic.space.app` on Google Play.

## If you fork or redistribute

You are very welcome to fork. When you do:

- **Use a different name.** Not "Relic", and not something so close that people
  would confuse the two. Do not publish under the official package identifiers.
- **Use different branding.** Replace the logo and icons with your own.
- **Do not imply endorsement.** Do not present your build as official, as
  affiliated with us, or as approved by us, and do not use the branding in a way
  that suggests any of that.
- **Do not point at our infrastructure as though it were yours.** Your fork
  should not present relic.space, Relic Cloud, or our support channels as its
  own.

## What is always fine

- Saying, accurately, what your project is built on: "based on Relic's
  open-source code", "a fork of Relic", "compatible with Relic". Referring to
  the project by name to describe it factually is normal and allowed.
- Writing about Relic: reviews, comparisons, tutorials, screenshots, talks,
  academic work, news coverage.
- Building an unofficial client, integration, or package and naming it in a way
  that makes the "unofficial" part clear, such as "Relic client for X" rather
  than just "Relic".
- Running an unmodified build of this code for yourself, your family, or your
  organization. Self-hosting is the point.

## Questions

If you are not sure whether a particular use is fine, ask before you ship. We
would rather say yes to a clear question than send a takedown later. Contact:
**support@relic.space**.