Our approach to your signatures.
Signatures are personal. We treat them that way. Here is how Signer is built, and how we think about the trust you place in us.
Your documents stay with you
Signer runs on your own computer. When you sign a PDF, the document is read locally, signed locally, and saved locally — there is no copy on our servers or on anyone else's. That is a deliberate part of the design, not something you need to configure.
Your certificate stays on the token
Indian Digital Signature Certificates live inside USB tokens designed so the private key cannot be extracted — all signing happens inside the token itself. Signer works through the token's own driver and never attempts to copy, store or cache either the certificate or the PIN.
A light, anonymous update signal
Signer checks in occasionally so we can tell which versions are out there and plan updates. The check carries no personal information and no details about the documents you sign — the app version, the operating system, and whether a token is currently connected is roughly it.
If you are curious about the specifics, we are happy to share the exact list with you — write to security@indhanpay.com.
Updates are small and signed
When a new version is available, Signer lets you know. The installers themselves come from a public release channel hosted on GitHub, served over HTTPS and verified by your operating system when they run.
Open release channel
You can browse every published release, check the version history and inspect the installer sizes at github.com/InDhan/indhan-signer-releases. Keeping the release channel in the open is our way of letting you verify what you installed.
Found something that doesn't match the behaviour above? Please let us know at security@indhanpay.com. Last reviewed: 12 October 2026.