Skip to content
KBVE Holdings LLC · legal

Your rights, and what we owe you.

Every policy that governs your use of KBVE services, plus the full text of each open-source license our software and assets are distributed under. Components declare their license in their own manifest; these pages are what those declarations point at.

4Policies
11Licenses
KBVE Holdings LLCGoverning entity
Dec 2022Policies updated

Open source

Licenses we distribute under

How to read these

The KBVE monorepo and its distributed applications bundle open-source components. Each one names its license in its own Cargo.toml, package.json, or LICENSE file — the pages below are the full texts those files point at.

Proprietary vs open source

KBVE applications themselves ship under the EULA. That agreement governs the application; the licenses here govern the third-party components inside it.

Attribution

Every license listed requires attribution except the public-domain dedications. Where a component requires a NOTICE file, it ships alongside the distributed build.

Common questions

FAQ

What is the purpose of the Privacy Policy?

It explains how we handle your personal data, including collection, usage, and the measures we take to protect it.

How can I manage cookies on your site?

The cookie section of the Privacy Policy covers cookie management, including how to control or delete them.

What does the EULA cover?

The End-User License Agreement sets out the terms under which you may install and use our software applications.

Which license applies to a given component?

Each component declares its license in its own Cargo.toml, package.json, or LICENSE file. The pages here are the full texts those declarations point at.