Privacy
Private electronic signatures with a clear boundary.
Privacy is not a promise that a service never processes anything. It is a precise question about which information it can independently read. Inklok protects signing values separately while still operating the agreement workflow.
What Inklok protects
Protected values entered during signing, including signatures, initials, names, dates, text, and sensitive form values, are encrypted in the browser before upload. Inklok stores them in encrypted form and does not keep an independent private key for decrypting them.
- Protection starts in the participant browser
- Authorized participants receive the required cryptographic path
- Inklok cannot independently reconstruct protected completed values
What Inklok still processes
Inklok processes the original PDF, templates, workflow configuration, participant and routing information, permissions, status, and audit events. Those systems are necessary for sending, signing, status tracking, and support of the agreement workflow. They are not inside the protected signing-value boundary.
- Original PDF
- Operational metadata
- Workflow status and audit history
- Participant routing and permissions
Privacy includes a recovery responsibility
Account access and cryptographic access are related but not identical. Inklok is designed for normal sign-in and cross-device use, but users should safeguard their Recovery Key because it can be needed in applicable account-recovery situations.
- Familiar account access
- Recovery Key for applicable recovery flows
- No silent provider recovery key
Example: collecting a sensitive field during signing
Suppose a form asks a participant to enter an address or payment-related detail during signing. Inklok can protect that entered value in the browser while still handling the original form PDF and routing details. That distinction matters: information already printed in the uploaded PDF is not made invisible to Inklok merely because another field is protected.
Questions to ask any signing provider
Ask whether the provider can decrypt stored values independently, who receives decryption access, what support staff can see, and what happens if the participant loses a device. Ask the same questions about uploaded PDFs and metadata separately. A claim of encryption at rest does not answer all of them.
Questions
Questions about privacy
Is every part of every agreement zero knowledge protected?
No. Source PDFs and operational metadata remain outside the current protected signing-value boundary.
Who can read protected signing values?
Authorized participants with the applicable cryptographic access can read protected values. Inklok does not maintain an independent private key that can be used instead.
Is privacy the same as encryption at rest?
No. Encryption at rest is important, but it does not by itself answer who can decrypt stored content. The key and access model matter.
Keep exploring