Codebase & Fork Policy

• C1 CC0 Public Domain: The source code is completely free to fork, modify, commercialize, or close. No permission required. Verify →
• C2 Branding: You must rename your fork and change the logos. Do not use the "Leef" name or branding. Verify →
• C3 Services: Update the GitHub update-check repositories for your fork. Public gists (like GPC lists) are free to reuse. Verify →

No Copyright Constraints C1

Leef Browser's codebase is published under the Creative Commons CC0 1.0 Universal (Public Domain Dedication) license.

This means we have dedicated the work to the public domain by waiving all of our rights to the work worldwide under copyright law, including all related and neighboring rights, to the extent allowed by law.

You can:

• Copy, modify, and distribute the code without asking.
• Incorporate the code into proprietary/commercial projects.
• Compile your own versions and distribute them as binaries.
• No attribution or copyright notices are required in your source files or distributions.

Why we have branding rules C2

These rules exist solely to prevent user confusion, phishing, or malware distribution. If someone downloads a modified version of the browser, they must know exactly who built it so they don't mistake it for our official, telemetry-free releases.

Rebranding Requirements:

If you fork and distribute a modified version of the codebase, you must adhere to the following:

• Change the Name: Do not call your project "Leef", "Leef Browser", or any name confusingly similar (e.g., "Leefy", "Leef Pro", "Leef+").
• Change the Logos: You must replace all official Leef logos, app icons, and branding graphics with your own distinct brand assets.
• Clarify Origin: Your documentation, about screen, and distribution links must not state or imply that your browser is an official release of the QTech team or endorsed by us.

Configuring Updates & Public Resources C3

Leef does not run proprietary, closed update servers. Instead, it relies on public APIs and Gists. If you distribute a custom compilation or fork, please configure your queries as follows:

• Update Checking: You must change the update checker configuration to target your own GitHub repository. This prevents your users' browsers from querying official Leef release paths and downloading updates built for our version.
• Blocklists & Gists: You are fully permitted and welcome to continue pointing your fork to our public Gists (such as our Global Privacy Control allowlist and blocklist). These resources are free, open, and CC0-dedicated for the entire community.