Applies to: All editions
PDF content stays local during normal processing
PDFSanitize performs document inspection, rendering, sanitization, verification, and report generation on the Windows computer. The PDF content does not need to be uploaded to an online PDF conversion or sanitization service.
Source and sanitized files remain in the local or network file locations chosen by the operator.
Network functions are separate from document processing
Network access can be used for:
- Pro or Enterprise activation;
- Periodic paid-license validation;
- Paid-license deactivation.
These functions use product, version, key, device, activation, and executable-integrity information rather than uploading the PDF being sanitized.
Offline paid-license cache
After successful validation, Pro and Enterprise can use protected local license information for temporary offline operation for up to 14 days. Connectivity is required again when that cached validity is no longer sufficient.
Local privacy responsibilities
Local processing does not remove the need for endpoint controls. Sensitive data can still exist in:
- The original source file;
- The sanitized output;
- Temporary operating-system caches;
- Backup and synchronization systems;
- User-accessible recent-file lists;
- Exported reports and certificates;
- Other copies created before sanitization.
Apply full-disk protection, access control, backup policy, and secure file-transfer rules appropriate to the document classification.
Network shares
PDFSanitize can operate on files where Windows file access is available, but the application writes the sanitized output beside the source. Confirm write permissions, file locking, synchronization behavior, and retention policy before processing PDFs on shared storage.