Sign X PDF
Privacy and local PDF processing
Sign X PDF is built so your selected PDF is read and processed in your browser for signing and common PDF edits. The PDF is not uploaded to Sign X PDF servers for that processing. Normal website assets still download over the network.
Your PDF is processed locally in your browser and is not uploaded to Sign X PDF servers.
What this tool does
This page explains the privacy model for Sign X PDF browser tools in plain language.
How to use it
- Application HTML, JavaScript, fonts, and WASM assets download like any website.
- You choose a PDF with the browser file picker or drag-and-drop.
- The file is read with browser APIs and processed on-device.
- You download the output file to your device.
How local processing works
Local processing means the edit pipeline runs in your browser tab using client-side code. It does not mean “no network at all”: scripts and other assets still load, and third-party ads or analytics may still request ordinary web resources if present on a page.
Limitations
- Local processing does not protect a compromised device or malicious extensions.
- We do not claim military-grade privacy, complete anonymity, or zero risk.
- If a future feature ever required a network upload, it would need an explicit design change and updated wording.
FAQ
Does any data leave my device?
Website assets are downloaded normally. The selected PDF is intended to stay in the browser for processing. We do not claim that no bytes ever leave your device under any circumstance (for example, OS or extension behaviour outside the app).
Do you store my PDF on a server?
The browser tools described here are not designed to upload your PDF to Sign X PDF servers for storage or conversion.