License notice in source
D3pth engine commercial licenses are issued together with a license notice that forms part of the licensed materials. The notice defines the permitted use of the delivered D3pth engine code and must remain attached to it.
Part of the licensed materials
The license notice is not separate marketing text or optional documentation. It is part of the licensed D3pth engine package and identifies the scope under which the code may be used.
Must remain attached
The license notice must remain complete, unchanged, and attached to the licensed D3pth engine code. This applies to source, deployed, bundled, minified, embedded, or published forms of the licensed materials.
No removal or separation
The license notice may not be removed, modified, redacted, replaced, obscured, or separated from the licensed code. Keeping the notice attached is a basic condition of permitted use.
Clear license scope
The notice may identify the licensee, licensed domain, permitted hosts, permitted IP addresses, product name, license version, and other practical limits of the license. The exact wording depends on the issued license.
Public website deployment
If the licensed D3pth engine code is deployed on a public website, the license notice remains part of the deployed materials. Publication of the website does not remove or weaken the obligation to keep the notice attached.
Why the notice matters
The license notice makes the commercial use verifiable without a subscription account, external tracking, or a hidden activation system. It keeps the licensing model transparent and practical for regular web deployment.
Questions about implementation
If your build process, bundler, deployment pipeline, or hosting setup affects source comments or license headers, contact us before publishing the licensed materials.
Email: ceo@d3pth.store