CriticalPDF

Privacy

Privacy Policy

Last updated: 2026-04-15

What CriticalPDF runs on

CriticalPDF is software you install and operate on your own Windows machines. The product itself does not send the contents of your PDFs anywhere — the desktop app communicates with the local service over a loopback-only TCP endpoint on 127.0.0.1. PDFs are routed only to the destinations you configure in your templates: local folders, network shares, or your own email account.

Telemetry

The MSI installer reports back the suite version, Windows version, and a randomly-generated install ID at install time. This is used to size our release support matrix and identify clusters of install failures.

The installed service does not phone home. Update checks are pull-only — your machine asks our update endpoint whether a newer version exists, and that request includes only the suite version and install ID.

Account data

For Business and Enterprise licenses, we store: the licensed organization name, the billing contact, the license key, and the count of activated machines. We do not store the machine names or IP addresses of activated machines.

Support requests

When you email support and include a log file, we use that log only to diagnose your issue. We delete support-attached logs 90 days after the ticket is closed.

Contact

Questions about this policy: privacy@criticalpdf.com.