Skip to content

Privacy architecture

Agreement signing with a smaller trust boundary.

Inklok is built for the ordinary work of agreements, while reducing how much trust you must place in the service. Zero-knowledge agreement protection is the reason protected signing values can remain outside Inklok's independent decryption capability.

Start with the customer outcome

The people involved in an agreement may need to see sensitive values. The service running the workflow does not always need an independent way to read them. Inklok is designed around that distinction, rather than asking teams to replace their normal agreement process with a cryptography project.

How the protected-value boundary works

When a participant enters a protected value during signing, the browser encrypts it before it is sent to Inklok. Access is controlled through cryptographic grants for authorized people. Inklok can coordinate the workflow without retaining an independent private key that decrypts those protected completed values.

  • Browser-side protection
  • Participant and role-aware access
  • No silent server or KMS recovery path for protected values

What zero knowledge does not mean here

It does not mean every byte of the product is invisible to Inklok. The service processes source PDFs and operational metadata. It also does not remove the need for device security, account security, careful permissions, or recovery-key safekeeping. The security overview documents this boundary in more detail.

Follow the information, not the label

There are two different data paths to examine. The sender uploads a source PDF so Inklok can prepare and run the workflow. Later, a participant enters protected signing values that are encrypted in that participant's browser. An evaluation should trace both paths rather than assuming the phrase zero knowledge applies to all content.

What this architecture asks of users

A provider without a spare decryption key cannot always repair lost cryptographic access on a customer's behalf. The Recovery Key and participant authorization model are part of the privacy tradeoff. Before adopting the product, understand account recovery, device changes, and who needs future access to completed signing values.

Questions

Questions about privacy architecture

Is Inklok a password manager?

The product shares a client-side encryption idea for protected values, but it is an agreement platform with templates, workflow roles, signing, routing, audit history, and organization management.

Can I sign as a guest?

Yes. External signers can participate without creating an account.

Why does the original PDF remain accessible to Inklok?

The PDF is processed under the service boundary so Inklok can operate the agreement workflow. Protected values entered during signing are handled separately.

Keep exploring

Related Inklok resources

Zero-Knowledge Agreement Signing | Inklok