Direct answer
PDFX processes files entirely in your browser. Your PDFs are never uploaded to PDFX servers for merge, split, conversion or compression.
Client-side architecture
When you open a PDFX tool, the site loads open JavaScript libraries (pdf.js, pdf-lib) on your device. The file you select stays in local browser memory. All reading, transformation and output generation runs on your CPU, not in a data center.
This differs from iLovePDF, Smallpdf and PDF24, which require upload for remote processing — even when they promise deletion after an hour.
Threat model
| Threat | PDFX mitigation |
|---|---|
| Transit leak | No upload = no TLS exposure of file content |
| Server retention | Impossible: no processing server |
| Employee access | Not applicable to file content |
| GDPR / personal data | No international transfer of PDF content |
What PDFX does not do
- Store PDFs in the cloud
- Index your document content
- Sell file data (there is no file data)
- Require accounts for free tools
Verification
Open browser developer tools (Network tab) and confirm: no request sends the PDF binary to pdfx.com.br during processing.
Honest limitations
Local processing depends on device memory. High-quality OCR on scans and qualified digital signatures need infrastructure browsers alone cannot provide — server tools may be required, with corresponding privacy trade-offs.
Security contact
Questions: hello@pdfx.com.br