feat: update LICENSE.md to clarify usage rights and restrictions

LICENSE.md

@@ -8,27 +8,43 @@ This license applies to both the public and private versions of the repository.
 
 ## 2. Usage Rights and Restrictions
 
-### 2.1 Personal and Internal Use
-Use of NDS for personal projects and internal projects is permitted.
-You may study the project and draw inspiration from it, but direct copying of the core logic, styles, or components is prohibited unless explicitly authorized.
+### 2.1 General Use
+NDS may be used freely and without limitation in personal, internal, and commercial projects — including projects developed for paying clients, such as the design or development of a website, application, or service.
 
-### 2.2 Commercial Products and Services
-Any use of NDS in a commercial product or service requires explicit written authorization from the original creator.
-Only the original creator may grant that authorization.
-Contributors do not have the authority to grant usage rights to third parties.
+You may study the project and draw inspiration from it, but direct copying of the core logic, styles, or components outside of using the library as intended is prohibited unless explicitly authorized.
 
-Selling a website, application, service, or product that uses NDS is prohibited unless a specific commercial agreement has been granted by the creator.
+### 2.2 Billing and Resale Restriction
+You may not charge or invoice anyone specifically **for the use of NDS itself**. This includes, but is not limited to:
+- selling NDS as a standalone product or component library,
+- sublicensing or redistributing NDS to third parties,
+- adding a distinct line item, fee, or surcharge tied to "using NDS" on a client invoice,
+- building a product or service (e.g. a SaaS) whose core purpose or monetized value is to give paying users access to NDS's components or their usage.
+
+This restriction does **not** prevent you from billing normally for a broader deliverable (e.g. a website, application, or platform) simply because NDS was used as part of the underlying toolkit. In that case, NDS is a tool used to produce the deliverable, not the product being sold.
+
+**Example — SaaS:** if you build a SaaS and NDS is merely used internally to build its interface (the same way any UI library would be), this is authorized. If, however, the SaaS's purpose or value proposition is to give users access to NDS's components or their usage (e.g. a website-builder that resells NDS components to its own customers), this is prohibited.
+
+**Exception:** if a client explicitly requests that NDS specifically be used in their project, you may bill for that work as part of the agreed engagement, since the choice to use NDS was made knowingly by the client.
+
+Only the original creator may authorize the sale, sublicensing, or commercial redistribution of NDS as a standalone product. Contributors do not have the authority to grant such rights to third parties.
 
 ## 3. Modifications and Contributions
-All modifications to the library must go through the official GitHub workflow, including Issues and Pull Requests.
+All modifications to the library must go through the official Gitea workflow on the project's self-hosted instance, including Issues and Pull Requests.
 
 Any authorized modification or derivative work of NDS must remain under this same license.
 Re-licensing modified versions under a different license is prohibited.
 
 ## 4. Assets and Iconography
-Icons and visual assets introduced into NDS remain part of the project.
-Unless explicitly authorized, these assets may only be used through the NDS library itself.
-External reuse, extraction, redistribution, or standalone use of these assets is prohibited.
+
+### 4.1 Third-Party Icons
+Some icons used within NDS are not proprietary to NDS and originate from public or third-party sources (e.g. Iconify). These icons remain governed by their own original license and attribution requirements, independently of this license.
+
+A full list of these third-party icons, including their name, source (e.g. Iconify), and a link to their origin, is maintained in the `ATTRIBUTION.md` file at the root of the repository. Any icon not listed in `ATTRIBUTION.md` is presumed to fall under section 4.2.
+
+### 4.2 Icons Created for NDS
+Icons specifically created for NDS may be used outside of the NDS project, subject to the following conditions:
+- they may not be sold or resold, whether individually, in a set, or as part of another icon library or product,
+- their origin must be explicitly credited wherever they are used (e.g. "Icon from Nova Design System (NDS)" with a link to the project), in a clear and visible manner.
 
 ## 5. Disclaimer of Warranty and Liability
 This library is provided on an **"as is"** basis, without warranty of any kind.