← Legal

Trademark Policy

How to refer to Promethean accurately in your product, documentation, and press materials — and what the brand may not be used for.

Effective: 2026-05-15 · Last updated in repo: 2026-05-15

Draft · counsel review pending

These pages follow the standard B2B SaaS template (Stripe / Vercel / Linear pattern). Entity details marked [TBD] must be replaced and the document set must be reviewed by Dutch / EU B2B SaaS counsel before relying on them as a binding contract with any customer.

1. Marks claimed

Promethean B.V. [TBD] claims trademark rights, registered or at common law, in the following marks (collectively, the "Marks"):

  • Promethean — the product name, used in connection with the substrate, the runtime-AI SDK, the L12 chain, the workspace dashboard, and related goods and services.
  • Promethean Verified — the integration badge issued only to AI vendors that have completed the Promethean-Verified-tier integration audit.
  • The substrate's trust-anchor identifiers — including the Ed25519 public-key fingerprint y6F3rt10… and the canonical signature prefix S/n4yLMGhSsFt… — used to mark chains anchored under Promethean's operational identity.

Marks may be registered in the European Union, the United Kingdom, the United States, and other jurisdictions; pending applications, registration numbers, and class designations are available on request from legal@promethean.software.

2. Permitted nominative fair use

You do not need a licence to refer to Promethean accurately for descriptive purposes. Without limiting the doctrine of nominative fair use as recognised under EU and US trademark law, the following uses are permitted:

  • stating that your product, library, integration, or service is "compatible with Promethean", "integrates with Promethean", "anchored under Promethean", or "exports to a Promethean audit bundle" — provided the statement is truthful and not misleading;
  • press, journalistic, academic, regulatory, or analyst references to Promethean by name, including in titles and headlines;
  • accurate citation of Promethean's published verifier source code, public attestations, ADRs, and audit-bundle format;
  • use of the Marks in comparative reviews, security evaluations, and procurement materials, provided the comparison is substantiated and the source is identified.

These permissions do not grant any licence in any other intellectual-property right, do not create any sponsorship or endorsement relationship, and may be revoked for misuse.

3. Prohibited uses

The following uses are not permitted without a written licence:

  • modifying, recolouring, distorting, or recomposing the Promethean wordmark, the "Promethean Verified" badge, or any associated logo;
  • using the Marks in a manner that states or implies sponsorship, endorsement, certification, partnership, or official affiliation that has not been agreed in writing;
  • using "Promethean" as the leading element of a product, company, or service name (e.g., "Promethean Audit", "Promethean Compliance Cloud", "PrometheanAI") — descriptive suffixes attached to your own primary brand (e.g., "Acme for Promethean") may be acceptable under Section 4 below;
  • registering domain names, social-media handles, package names, npm/PyPI namespaces, or app-store identifiers that incorporate "Promethean" as a dominant element;
  • displaying the "Promethean Verified" badge or asserting that a chain is "Promethean-anchored" unless the corresponding integration audit or anchoring has actually occurred and remains in force;
  • using the Marks in connection with goods or services that violate the Acceptable Use Policy, applicable law, or the EU AI Act's prohibited-practice list under Art. 5;
  • re-publishing a forked, modified, or re-signed verifier or SDK under any of the Marks; forks must be rebranded.

4. Contributions to verify.mjs (DCO sign-off)

Promethean's open-source verifier (verify.mjs, Apache-2.0) and its companion canonical-form specification accept community contributions under the Developer Certificate of Origin v1.1 ("DCO") model. Each commit in a pull request must be signed off with a line of the form Signed-off-by: Name <email> (e.g., via git commit -s). By signing off, you certify that you have the right to submit the contribution under the Apache-2.0 licence and that the contribution is your original work or is otherwise properly licensed.

Contributions do not transfer any rights in the Marks. The DCO governs only copyright and patent rights in the contributed code, not trademark use.

5. Requesting a trademark licence

If your intended use falls outside the nominative fair-use permissions in Section 2 — for example, you want to apply the "Promethean Verified" badge to your integration, co-brand a joint offering, or use the wordmark in a product name — a written trademark licence is required. Send a written request describing the proposed use, including mock-ups where relevant, to legal@promethean.software. We respond within fifteen (15) business days.

6. Enforcement and changes

We may at any time, on reasonable notice, require you to modify or cease a use of the Marks that we determine, acting reasonably, falls outside this Policy. Failure to comply may result in revocation of any prior permission and the legal remedies available under applicable trademark, unfair competition, and consumer-protection law.

We may update this Policy from time to time. Material changes will be posted at this URL with a new "Effective" date.

7. Contact

Trademark enquiries, licence requests, and reports of misuse: legal@promethean.software. Postal: Promethean B.V. [TBD], [TBD street, postcode, city], Netherlands.