# Project names and branding

Adminlume is developed by Dilorsoft. The names **Adminlume** and **Dilorsoft**, and any associated project logos, identify the project and its origin.

This policy describes how to avoid misleading users about project identity. It does not assert that any name or logo is a registered trademark, establish trademark registration, or expand rights beyond applicable law.

## Software freedom is unchanged

The code is licensed under `GPL-2.0-or-later`. You may use, modify, fork, redistribute, and sell it under that license. This policy is not an additional software license condition and does not restrict those freedoms. It addresses branding only to the extent protected by applicable trademark or unfair-competition law.

No separate trademark license is granted by the software license. Statutory rights, fair use, and truthful descriptive or nominative references are unaffected.

## Accurate references and redistribution

- You may refer to Adminlume by name to discuss the project, explain compatibility, or acknowledge its origin.
- You may identify an unmodified copy accurately as Adminlume and identify yourself as its distributor. Do not imply that your distribution channel, support, or services are operated or endorsed by Dilorsoft unless authorized.
- Preserve required copyright and license notices. Historical references to Adminlume in those notices are not a claim that a fork is an official release.

## Modified versions and independent services

For a fork or modified distribution, use a distinct public-facing name and visual identity where needed to avoid confusion. Clearly identify the changes and your role; for example: "Example Admin is an independent fork of Adminlume by Dilorsoft. It is not affiliated with or endorsed by Dilorsoft."

Do not present a modified version as an official Adminlume release or use names or logos in a way that falsely implies authorship, sponsorship, approval, or affiliation. The same applies to websites, domains, marketplace listings, and paid support services.

This does not require removing attribution or renaming internal namespaces, text domains, metadata keys, asset handles, or compatibility identifiers solely because they contain a project name.

## Permission and legal review

If you want to use project branding in a way that suggests an official partnership or endorsement, obtain written permission from Dilorsoft first. No dedicated trademark contact address is currently published in this repository; do not treat that absence as permission or send confidential material to public issues.

This document is not a substitute for legal review, a clearance search, or trademark registration. Protection and enforceability depend on applicable law and the actual rights held by the owner.
