Appendix H — Terms, licensing and acknowledgements
Summary
This page records only what can be verified from the repository: how the commercial SDK licences are linked from the apps, what the open-source migration note says, and which legal pages the site links to. It is not legal advice and it does not restate the Terms of Use or the Privacy Policy. Those live on the website and are the only authoritative text; this book has not read them and does not summarise them. If something here conflicts with the site's terms, the site wins.
Details
Terms of Use and Privacy Policy
- The site's footer links to a Privacy Policy (the link recorded in the interface resources points to
about.smallize.com/legal/privacy-policy/). - Several app pages carry the checkbox text "I agree to the Terms of Use and Privacy Policy" on their contact form (seen in the AI app resources).
- Read both on the live site before uploading confidential, personal or regulated material. For how the apps treat your files in practice, see Privacy and data lifecycle and, for sensitive work, self-host.
- The repository contains no
LICENSEfile at its root, and the rootREADME.mdis the unedited GitLab template (its "License" and "Roadmap" sections are template text). So no licence or terms for the web service itself can be quoted from the repo.
Commercial SDK licences linked from the apps
The file Documentize.UI/resources/licensing.yaml drives the "Licensing <App>" call-to-action on app pages and CLI plugin cards. It maps pages to the commercial SDKs sold at products.documentize.com:
| Product | What the file says it is for |
|---|---|
| Documentize SDK (suite) | The full product family for C#/.NET |
| PDF Manager | Merge, split, rotate, resize, optimize, compress |
| PDF Converter | PDF to DOC, XLSX, HTML, images and PDF/A, and back |
| PDF Extractor | Text, images, metadata, form data |
| PDF Security | Encrypt, decrypt, sign, sanitize |
| PDF Form | Flatten, export, remove and inspect form fields |
Facts from that file that matter to readers:
- Pages such as Merger, Splitter, Compressor, Resize, Add Table, Add TOC, Booklet and Optimize map to PDF Manager; Converter and PDF/A Validator to PDF Converter; Extract Text/Image/Metadata, Parser and Search to PDF Extractor; Extract Form Data and Flatten to PDF Form (and Extractor); Unlock, Protector and Signature to PDF Security. Self-Host, MCP and Desktop link to the suite.
- Some pages are intentionally unmapped because there is no matching commercial SDK: Illustrator, Resume, Checklist, SVG Maker, Abstracts, Assembly Chat, Collage, Deskew, Cheat Sheet, Advisor, Unwatermark, OCR and Searchable.
- CLI plugins need a licence file. Each plugin reads
documentize.licnext to its binary, and it must be a licence for the product the plugin belongs to (PDF Manager, Converter, Extractor, Form or Security). Without it the plugin runs in evaluation mode. Plugins with no Documentize package (for example ArchiveCreate, ArchiveExtract, ImageConvert, MsOffCryptoUnlock, OcrImage, PdfToHtml, SofficeConvert, TesseractOcr) need none. - Self-host runs in trial mode without a licence (evaluation watermarks, per the Self-host chapter). Tiers and limits: limits table.
- Prices are not in the repository material.
Open-source engine (FOSS migration)
The repository's FOSS.md is a working status note, not a licence. It states, as of that note:
- The back end, agent and tests build only on Aspose.PDF.FOSS (an open-source library on NuGet), with the commercial drawing package removed from them; plugins cover merge, split, compress, rotate, encrypt, decrypt, sign, flatten, optimize, resize, extraction and Word, Excel, HTML, image and PDF/A conversions.
- Not done: Self-Host still uses a commercial package and its licence; nothing had been verified on Linux or deployed; other commercial Aspose packages (Cells, Words, Slides) were not touched.
- Known differences: editable-text PPTX output no longer exists; the MOBI and PCL routes are gone; Arabic/right-to-left is unchecked; a workaround exists for rotated 180/270 degree text positions. Whether the live site already runs that build is not stated. If a MOBI/PCL/PPTX behaviour matters, test it (verify on the live app). The how-to chapter links the open-source library for developers: see Plugins and How-to guides.
Your responsibilities (from the chapters)
- Unlock only files you are entitled to unlock (Unlock).
- A digital signature is only as trusted as its certificate (Sign); the book does not promise that a signature or PDF/A result is accepted by any authority (PDF/A Validator).
- AI outputs are drafts and not professional advice (Trust). Documents of other people (for example CVs) go to an AI service: check you may upload them (Resume Analyzer).
- For private repositories, inviting the
arise-projectGitHub account gives it access (Code Graph).
Acknowledgements
Third-party services named in the chapters include Tesseract (the OCR language codes used by CLI plugins), Google's search box on Global Search, nuget.org, GitHub and GitLab. Their terms apply to your use of them. The book does not list every dependency; the repository has no consolidated third-party notices file that was reviewed for this appendix.
Related
- Privacy · Self-host · What's new · FAQ