Spaces:
Running on Zero
Running on Zero
| # Commercial Licensing | |
| The LEGX toolkit, including the Document Integrity Verifier, is | |
| distributed under the [PolyForm Noncommercial 1.0.0](LICENSE) licence. | |
| That licence permits any **noncommercial** use — research, education, | |
| personal use, internal evaluation, hobby projects, use by charitable | |
| and government organisations — at no cost. | |
| If you want to use the Software for a **commercial purpose**, you need | |
| a separate, paid commercial licence. This includes (but is not limited | |
| to): | |
| - Selling, sublicensing, or rebranding the Software or any derivative. | |
| - Operating a hosted service (SaaS, paid Hugging Face Space, paid API, | |
| managed deployment) that processes documents for paying customers. | |
| - Embedding the Software, the lexicon, the detector matrix, or the | |
| reasoning verdict path into a commercial product, plug-in, browser | |
| extension, mobile app, or enterprise pipeline. | |
| - Using the Software internally at a for-profit company in support of | |
| revenue-generating activities (e.g. as part of a contracts pipeline, | |
| legal-review workflow, KYC/AML stack, AI-safety product). | |
| If any of that describes your situation, please get in touch. | |
| ## What a commercial licence gets you | |
| - A clear, written licence to use the Software for the purposes you | |
| describe, on the terms we agree. | |
| - Carve-outs from the [Acceptable Use Policy](ACCEPTABLE_USE.md) where | |
| appropriate (e.g. authorised red-team engagements with a documented | |
| scope). | |
| - Optional: indemnification, SLA, prioritised support, custom detector | |
| development, multilingual lexicon expansion, model fine-tuning. | |
| - Optional: removal of the "Required Notice" obligation for your | |
| branded distribution, subject to agreement on attribution elsewhere. | |
| ## What a commercial licence does **not** get you | |
| - Permission to violate the [Acceptable Use Policy](ACCEPTABLE_USE.md) | |
| outside the carve-outs explicitly written into your commercial | |
| agreement. | |
| - Permission to misrepresent the Software's output as compliance | |
| certification or as an audit by the licensor. The | |
| [`DISCLAIMER.md`](DISCLAIMER.md) limits remain in force. | |
| - Permission to re-licence the Software to third parties as if it were | |
| your own work. | |
| - An indefinite, unconditional warranty. Commercial agreements will | |
| define warranty scope; outside that scope the no-warranty clause | |
| applies. | |
| ## Third-party dependency note | |
| The Document Integrity Verifier (the detector path that ships with the | |
| Hugging Face Space) uses **pypdfium2** (Apache 2.0 / BSD-3-Clause, | |
| wrapping Google's BSD-3 PDFium) and **pypdf** (BSD-3-Clause) for all | |
| PDF operations. There is **no AGPL / commercial-licence wall** between | |
| you and a commercial deployment of the detector. | |
| The authoring side of the LEGX toolkit (`legal_doc_redteam/fixtures.py` | |
| and friends) does still use PyMuPDF, but the authoring side is excluded | |
| from the Space export and from any commercial detector licence anyway. | |
| If you specifically need a commercial licence to use the authoring side, | |
| you would also need a commercial PyMuPDF licence from Artifex; mention | |
| that when you contact us so we can scope the agreement correctly. | |
| ## How to get in touch | |
| Email: **gregor.koch@gmail.com** | |
| Please include: | |
| 1. The legal name of the entity that would hold the licence. | |
| 2. A short description of the intended use (one paragraph is enough). | |
| 3. Estimated scale (documents / month, deployment surface). | |
| 4. Any specific carve-outs you need from the AUP. | |
| Initial response is typically within a few business days. Commercial | |
| licences are bespoke; there is no automatic pricing page. | |
| ## Good faith | |
| If you are genuinely unsure whether your use is commercial, ask. The | |
| licensor would rather have an early conversation than discover a | |
| deployment later and have to send a notice under the LICENSE's | |
| **Violations** section. | |
| If you are a small research group, an academic lab, an open-source | |
| project, a non-profit, a government agency, or an individual using the | |
| Software for personal or educational purposes, **you already have a | |
| licence under PolyForm Noncommercial**. You do not need to contact us | |
| unless you are about to commercialise. | |