Sign X PDF · Guides
How to choose a private PDF tool
Compare a PDF tool by asking what happens to document bytes, whether an account is required, how long files are retained, what telemetry is collected, what kind of signature it creates, and which limits are disclosed. A “private” label is only useful when the processing model and evidence are clear.
This checklist is general product guidance, not legal, regulatory, or information-security advice for a particular organisation.
Verification scope: the owner-managed repository source and open-source components were reviewed on 2026-08-08. The linked GitHub repository currently requires access for anonymous visitors; it is a source reference, not a public-audit guarantee. The test files used for browser checks stayed on the test device and were not uploaded to Sign X PDF application servers. This is scoped evidence, not a guarantee about a compromised device, browser extensions, OS services, or future code changes.
Start with the processing model
First ask whether the PDF is uploaded to an application server, processed locally in the browser, or handled by a hybrid workflow. “The page uses HTTPS” does not answer that question: encrypted transport can still carry a document to a server.
If a product claims browser-local processing, test it with a unique fixture in the Network panel. Read the scope and limitations rather than treating “local” as “no network at all”.
Use this comparison checklist
The questions below are intentionally product-neutral. They help you compare a free browser tool, a hosted document service, and a self-hosted application without rewarding vague privacy slogans.
- Does the PDF upload? This determines whether document bytes leave the browser for server processing.
- Is an account required? An account can link document activity to an identity even when the file is deleted quickly.
- How long are files retained? Look for deletion timing, backups, logs, and support access—not only the word “temporary”.
- Does processing run locally? Confirm the claim with a repeatable Network trace and inspect the source when available.
- What telemetry exists? Distinguish document metadata, filenames, usage events, error reports, ads, and ordinary asset requests.
- Is the signature visible or certificate-backed? A drawn or typed mark is not the same as a cryptographic digital signature.
- Are limits disclosed? File size, page count, browser memory, password protection, and export failures matter for real work.
Match the tool to your threat model
For a low-risk form, a local browser tool may be convenient. For regulated records, consider whether you need identity verification, audit trails, certificate-backed signatures, retention controls, administrator policies, or a reviewable self-hosted deployment. Privacy is not one score that applies to every workflow.
Sign X PDF is deliberately narrower: it provides visible signature placement and common PDF operations in the browser, without claiming certificate-backed signing, universal legal validity, or protection from a compromised device.
Prefer evidence over claims
A useful provider explains how its claim was checked, publishes source code or a method, dates its verification, and names what the test does not prove. That evidence is more valuable than a long list of privacy adjectives.
Sign X PDF publishes a verification hub and links its privacy test code. The test is evidence about the configured workflows—not a blanket guarantee for every browser, extension, operating system, or future feature.
How we verified this
First-party privacy test scope
Result: Sign X PDF documents the five operations covered by its automated no-upload test instead of generalising from one tool.
Scope: Sign, merge, compress, reorder, and delete workflows
Limits: The test does not cover every future feature or every environment outside the test harness.
Source: /en/verification/
Signature terminology source
Result: The product distinguishes visible signature placement from certificate-backed digital signing.
Scope: Current sign tool capability and public terminology guide
Limits: Legal effect depends on jurisdiction and transaction context.
Source: docs/signature-terminology.md
FAQ
Is a browser-local PDF tool always the most private option?
Not automatically. Device security, browser extensions, caching, telemetry, product limits, and your required compliance controls still matter. Verify the actual workflow and threat model.
What is the first question to ask a PDF provider?
Ask whether the selected PDF bytes are uploaded to an application server for processing or storage, then ask how the provider proves the answer.
Does Sign X PDF claim to be the safest PDF tool?
No. It describes a browser-local processing design, publishes scoped tests, and discloses limitations so users can compare it with alternatives.