docs / secure / brand

Brand, Trademark & Copyright Policy

Last Updated: July 10, 2026

1. Overview

Arkyn's software source code is open source under the Apache License 2.0 (see License). Its name, logos, visual identity, and documentation content are a separate matter, protected independently of that license. This document — combining Arkyn's trademark policy, copyright notice, and brand usage guidelines into a single reference — explains what you can and cannot do with the Arkyn brand and its creative assets.

The core principle: the Apache License gives you rights to Arkyn's code. It gives you no rights to Arkyn's name, logos, or content. Those remain reserved to the Maintainer unless explicitly licensed, exactly as Section 6 of the Apache License itself states for trademarks.

2. Definitions

See Arkyn Legal Documentation for the shared glossary. Terms specific to this document:

"Marks" means the word "Arkyn," any Arkyn logo, wordmark, icon, or other source-identifying symbol used by the project, whether or not formally registered.
"Brand Assets" means Arkyn's logos, color palette, typography choices, design system components as visually presented (not as code), iconography, and similar visual identity elements.
"Content" means the text, structure, illustrations, screenshots, videos, and other creative material published in the Documentation, on the website, or in official marketing materials — as distinct from the Software's source code.

3. Copyright

3.1 What Is Protected

Independent of the Apache License covering Arkyn's source code, the Maintainer holds copyright in:

The Documentation's written content: guides, API references, conceptual explanations, and prose.
Illustrations, diagrams, screenshots, and videos published on the website or in the Documentation.
The Arkyn logo and other Brand Assets.
The website's visual design and layout (as distinct from any underlying open-source code that renders it).
Marketing and promotional materials.

3.2 Permitted Use of Documentation and Code Examples

To support developers learning and using Arkyn, the following limited permissions apply without requiring separate permission:

You may copy code examples and snippets from the Documentation into your own projects, for the purpose of using Arkyn's Software (the same permission implicit in any software documentation).
You may quote, link to, and reference the Documentation in your own articles, tutorials, or internal materials, with reasonable attribution (for example, "as shown in the Arkyn documentation" with a link).
You may take and share screenshots of your own application built with Arkyn's components, even though those components' visual output derives from Arkyn's design system.

The following are not permitted without prior written permission:

Republishing, mirroring, or rehosting substantial portions of the Documentation's prose, structure, or illustrations as your own content (for example, a competing "Arkyn docs mirror" or a translated copy hosted outside the official website without authorization).
Using Arkyn's screenshots, diagrams, or illustrations in your own commercial materials in a way that implies endorsement or affiliation.
Reusing the Documentation's website layout or visual design for an unrelated project.

3.3 Attribution

When quoting or referencing Arkyn's Documentation, a simple attribution such as "Source: Arkyn Documentation (docs.arkyn.dev)" with a link back is sufficient and appreciated. Attribution does not, by itself, grant any of the permissions described in Section 3.2 beyond what that section already allows.

4. Trademarks

4.1 The Arkyn Marks

"Arkyn" and its associated logos are the Maintainer's trademarks (registered or common-law, as applicable), used to identify the genuine Arkyn ecosystem and distinguish it from unrelated projects and services.

4.2 Independent From the Apache License

Trademark rights are entirely independent of the Apache License. Having the right to use, modify, and redistribute Arkyn's source code under Section 3 of LICENSE.md does not give you any right to use the Arkyn name or logo to describe your own fork, product, or service, beyond the limited "referential" uses described below. This mirrors how projects like Kubernetes, Node.js, and countless other Apache/MIT-licensed projects treat their names separately from their code license.

4.3 Permitted Referential Uses

You may use the word "Arkyn" in plain text, without prior permission, to truthfully describe your project's relationship to Arkyn, for example:

"Built with Arkyn"
"Compatible with Arkyn"
"Plugin for Arkyn"
"Extension for Arkyn"
"Powered by @arkyn/components" (referring to the actual npm package by its real name, in prose or dependency listings)

These uses are permitted as long as they are truthful, do not imply official endorsement or partnership that does not exist, and do not use the Arkyn logo as part of your own product's primary branding (see Section 5).

4.4 Uses Requiring Prior Written Permission

The following types of use require the Maintainer's prior written permission, because they risk creating confusion about who operates, endorses, or is responsible for the named thing:

Using "Arkyn" as part of the name of your own product, service, company, or community, for example: "Arkyn Studio," "Arkyn Framework," "Arkyn Cloud," "Arkyn Brasil," "Arkyn UI," or similar. (This is distinct from truthfully naming the real, official package @arkyn/components in your dependency list or prose, which is always permitted under Section 4.3.)
Registering domain names, social media handles, or app store listings that include "Arkyn" or a confusingly similar variation.
Using the Arkyn logo (in original or modified form) as the primary branding of an unrelated product, plugin marketplace, course, or community.
Any use that could reasonably be understood as an official Arkyn product, service, or communication channel when it is not.

To request permission for any of the above, contact the Maintainer as described in Section 9 with a description of the intended use.

5. Visual Identity and Design Assets

Arkyn's logos, color palette, and design system, as visually presented, are Brand Assets under Section 3.1 and are licensed separately from the code that implements the design system (which is Apache-2.0 licensed as software, per LICENSE.md). In practice:

You may use the @arkyn/components package's code, including its default visual styles, to build your own application — that is ordinary, permitted software use.
You may not extract Arkyn's logo, wordmark, or brand color palette to brand an unrelated product, service, or company as if it were an official Arkyn offering.
Press, media, and community members writing about Arkyn may use the official logo, unmodified, for identification purposes (for example, in a blog post about Arkyn), consistent with ordinary nominative fair use.

6. Domain Names

The arkyn.dev domain, and any official Arkyn subdomains (such as docs.arkyn.dev), are controlled exclusively by the Maintainer. Registering or using confusingly similar domain names (such as common misspellings, alternate TLDs used to impersonate the project, or "arkyn-" prefixed domains suggesting official status) to host unrelated or impersonating content is a violation of this policy and may additionally constitute trademark infringement or cybersquatting under applicable law.

7. Prohibited Conduct

Regardless of the specific category above, the following are always prohibited:

Creating confusingly similar names, logos, or domains intended to be mistaken for official Arkyn properties.
Impersonating the Maintainer, Arkyn contributors, or official Arkyn communication channels (including on social media, forums, or chat platforms).
Operating fake "official" Arkyn communities, Discord servers, or social media accounts that are not authorized by the Maintainer.
Using Arkyn's name, logo, or Content in a way that is misleading about the commercial relationship between your offering and the genuine Arkyn project.
Any deceptive branding practice designed to trade on Arkyn's reputation or user trust.

8. Enforcement

The Maintainer reserves the right to request removal or modification of infringing use of the Marks, Brand Assets, or Content, and to pursue any remedies available under applicable trademark, copyright, and unfair competition law. Good-faith questions about whether a specific planned use is permitted are welcome before you proceed — see Section 9.

9. Contact

Trademark, copyright, and brand permission requests: lucasgoncalves@arkyn.dev.

10. Related Documents

Arkyn Legal Documentation — index and shared definitions.
License — the Apache License 2.0 governing Arkyn's source code, and how it relates to this document.
Terms of Use — general rules for using the Arkyn website and Documentation.

On this page