# Nacre Trademark Policy

Nacre's code is released under Apache 2.0. **A license to the code is not a
license to the name or the mark.** This document explains what you may do
without asking us first.

## The marks

The word mark **Nacre** and the figurative mark — the six-strata N monogram
in the Abalone palette.

## You may, without permission

- State that your product uses, runs on, or is compatible with Nacre:
  "built on Nacre," "Nacre integration," "Nacre-compatible."
- Use the name in articles, talks, tutorials, and comparisons.
- Redistribute unmodified builds under the name Nacre.
- Use the mark unaltered to refer to the project, respecting its clear space
  and without distorting proportions or colors.

## You may not, without written permission

- Name a **fork or modified build** Nacre, or anything confusingly similar.
  Rename it. This one is not negotiable.
- Use the name or mark in your company name, product name, domain name,
  GitHub organization, social media handle, or package registry namespace.
- Offer paid hosting or support under the Nacre name in a way that could be
  read as an official offering.
- Alter the mark: recolor it, reorder the strata, skew it, add elements, or
  embed it in another mark.
- Use the mark in any way that implies partnership or endorsement where no
  such agreement exists.

## Modified builds

Fork and modify freely — that is what Apache 2.0 is for. Just ship the result
under your own name, describing it as "a fork of Nacre" or "based on Nacre."
This isn't a restriction on the code; it protects users. Someone who installs
something called Nacre is entitled to assume it behaves the way our docs say
it does — especially where access control is concerned.

## Questions and permissions

trademark@nacre.work

This policy follows Linux Foundation practice and may be updated.