Open Source & Third-Party Notices

License policy and per-release notice template

1. License Policy

Gylt.me LLC may use third-party and open-source components when their license terms are compatible with the intended distribution model and all required notices, attribution, source, modification, patent, and other obligations are satisfied.

2. Approval Tiers

Generally acceptable with compliance review: MIT, BSD-2-Clause, BSD-3-Clause, ISC, Apache-2.0, and similarly permissive licenses.

Requires written review before use or distribution: MPL, LGPL, EPL, CDDL, or other weak/limited copyleft licenses.

Requires explicit written approval from Gylt.me LLC before inclusion: GPL, AGPL, SSPL, strong copyleft, network-copyleft, source-available licenses, licenses with unusual field-of-use restrictions, or licenses that could require disclosure or reciprocal licensing of proprietary Gylt.me code.

Unknown, missing, custom, or ambiguous licenses must be treated as not approved until reviewed.

Third-party fonts, icons, images, datasets, SDKs, models, and other non-code assets are subject to the same review principle.

3. Proprietary Code and Plagiarism Protection

Use of open-source software does not place Gylt.me proprietary source code, original designs, documentation, or other protected Gylt.me expression into the public domain. Gylt.me proprietary code must remain separate from third-party licensing obligations except where an approved license expressly requires otherwise. No contributor may copy third-party proprietary code, designs, text, or assets into a Gylt.me product without documented authorization.

4. Release Record

Product: ______________________________

Version: ______________________________

Release Date: _________________________

Reviewed By: __________________________

5. Release Compliance Checklist

Inventory direct and transitive dependencies actually distributed to users.

Verify upstream LICENSE and NOTICE files; do not rely only on package-manager metadata.

Preserve all required copyright and license notices.

Review Apache NOTICE obligations where applicable.

Confirm that any copyleft or source-disclosure obligations were approved before release.

Include licenses/attribution for non-code assets where required.

Regenerate and review notices for each material release.

Do not apply Gylt.me proprietary restrictions to third-party components where their licenses grant broader rights.

6. User-Facing Intro

This product includes software and other materials provided by third parties. Those components are licensed under their respective terms. The following notices are provided as required by those licenses. Gylt.me LLC's proprietary license does not restrict rights granted under an applicable third-party license.

Per-release component names, versions, licenses, copyright notices, and attribution must be generated from the software actually distributed in that release.