Compliance overview
GDPR
Crash reports are opt-in
PDFluent collects no usage data or analytics. The editor sends crash reports only if you turn them on. There are no tracking libraries in the SDK.
Data stays on your machine
PDFs are processed entirely within your own process. Document content is never sent to an external server.
No licence validation at all
Nothing in the SDK reads a licence or contacts a validation endpoint, so no key, hash, document metadata, file path or user data leaves the machine.
No sub-processors for document data
PDFluent has no sub-processors that receive document content. Your data processing agreements cover only your own infrastructure.
PDF standard compliance
| Standard | Description | Status |
|---|---|---|
| PDF/A-1b | ISO 19005-1 Level B conformance. Long-term archiving baseline. | Supported |
| PDF/A-2b | ISO 19005-2 Level B. Adds JPEG 2000, transparency, and attachments. | Supported |
| PDF/A-3b | ISO 19005-3 Level B. Allows arbitrary embedded files. | Supported |
| PDF/UA-1 | ISO 14289-1. Universal accessibility — tagged PDF, reading order, alt text. | Supported |
| PDF/X-3 | ISO 15930-3. Graphic exchange for print production. | Roadmap |
| PDF/A-4 | ISO 19005-4. Latest archiving standard. | Roadmap |
Licensing
Commercial license
The SDK is free and complete under the AGPL. What a commercial licence buys is the right not to publish your own source: €999 a year per organisation, unlimited developers, or a yearly OEM licence per product when you ship PDF functionality to your own customers. No seats, no per-document or per-API-call fees.
Full license termsNo GPL dependencies
PDFluent has no GPL or LGPL dependencies. All dependencies are MIT or Apache-2.0 licensed.
SOC 2
A SOC 2 Type II audit is on the PDFluent roadmap. Given that PDFluent processes documents locally with no cloud data pipeline, the audit scope is limited. Enterprise customers with specific compliance requirements can find more information on the pricing page or reach out via email.