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. No account is required for these browser tools.
Your PDF is processed locally in your browser and is not uploaded to Sign X PDF servers for tool processing.
What this tool does
This page explains the privacy model for Sign X PDF browser tools, how local processing differs from upload-based online PDF sites, and a practical checklist for evaluating any PDF editor you trust with confidential files.
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 browser keeps a local File reference).
- The file is read with browser APIs and processed on-device with client libraries and, where used, WebAssembly.
- You save the output file to your device; the workflow is not designed to keep a server-side copy of your PDF.
How local processing works
Local processing means the edit pipeline runs in your browser tab using client-side code (including pdf.js-style rendering, pdf-lib assembly, and QPDF WebAssembly for selected operations). 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. Document bytes for the tool workflow are intended to stay in the tab rather than being POSTed to Sign X PDF application servers.
Browser storage used by Sign X PDF
| Storage | Purpose |
|---|---|
| localStorage | Language preference and a short export-rate window used to limit repeated free exports. These are first-party site data, not advertising cookies. |
| IndexedDB | Saved signature library entries (including signature image blobs) that you choose to keep in this browser for reuse. |
| Cookies | Core PDF processing does not require first-party advertising cookies. Ordinary third-party ads or analytics, if present on a page, may set their own cookies under their policies. |
Clearing this site’s data in your browser removes locally saved preferences and signatures. Your PDF files are not kept as a server-side copy of the tool workflow.
FAQ
Q1 Does any data leave my device?
A1 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).
Q2 Do you store my PDF on a server?
A2 The browser tools described here are not designed to upload your PDF to Sign X PDF servers for storage or conversion.
Q3 What browser storage does Sign X PDF use?
A3 localStorage stores language preference and an export-rate window. IndexedDB stores saved signatures you keep for reuse. Core PDF processing does not require first-party advertising cookies. Clear site data to remove those local items.
Q4 Do I need an account?
A4 No account is required to use the browser sign and PDF tools described on this site.
Q5 How should I judge whether an online PDF editor is safe?
A5 Prefer a clear processing model (upload vs local), retention policy, account requirement, telemetry disclosure, whether signatures are visible marks or certificate-backed, open-source components you can inspect, and practical file limits. Verify claims with browser Network tools using a uniquely named test file.
Q6 Is Sign X PDF automatically the safest option?
A6 No tool is automatically safest for every threat model. Sign X PDF aims for local document processing and transparent limits. Compare criteria—not slogans—and re-check network behaviour for your own use case.
Q7 Can I inspect open-source components?
A7 Yes. Licence notices for QPDF, pdf-lib, and other libraries are listed on the open-source licences page.