PDFNova trust
How does PDFNova handle document privacy?
PDFNova processes supported transformations in the browser and does not send document contents to its application server. PDFNova does not send document contents, filenames, extracted text, metadata values, passwords, or generated files to analytics. These boundaries do not claim control of all browser, device, or network handling.
Separate document processing from analytics
Supported PDF transformations use browser code and do not send document contents to PDFNova’s application server. Product analytics permits a finite product-event type plus, where applicable, a tool ID, file count, or output count.
Payloads do not include URLs, filenames, free-form errors, document contents, extracted text, metadata values, passwords, or generated files. The finite allowlist distinguishes these exclusions from the approved interaction identifiers and counts.
Understand what the boundary does not cover
The PDFNova application and analytics boundaries do not make an absolute statement about the browser, operating system, extensions, network software, device management, backups, download storage, or other applications. Those parts of the environment require their own assessment.
Control the working files
Keep the tab open until processing finishes, download the generated result before resetting or leaving the workflow, and verify it while retaining an unchanged source. Store and dispose of both files according to the document’s sensitivity and your organisation’s rules.
Limitations
- The documented boundary is specific to PDFNova’s current supported transformations and analytics implementation; it is not a universal confidentiality or compliance guarantee.
- A downloaded output remains subject to the security, syncing, backup, sharing, and retention behaviour of the user’s environment.