Skip to content

Visual privacy guide

Who can actually read your signed agreement?

A signed agreement is not one kind of data. Follow three different data paths to understand what encryption can protect and what the service may still need to process.

Updated November 8, 2026. This diagram explains Inklok's current scope, not an assessment of other vendors.

Three data paths, three different answers

The boxes below distinguish original documents, newly entered protected values, and operational metadata. They are not claims that a completed PDF as a whole is end-to-end encrypted.

01 / Before signing

The uploaded source PDF

The sender supplies a PDF that may already include names, addresses or contract terms. Inklok processes that source PDF so the signing workflow can work. Values already printed in it are outside Inklok's browser-encrypted signer-input boundary.

Provider processing occurs here

02 / While signing

New protected signing values

When a participant enters a protected value, the browser encrypts it before upload. Authorized participants use the intended cryptographic access path to read those values. Inklok cannot independently decrypt those protected completed values.

Protected in the participant's browser

03 / During the workflow

Routing and audit metadata

The service needs operational information to invite signers, show agreement status, apply permissions and maintain audit history. That metadata is not promised to be zero-knowledge encrypted.

Visible to service operations as required

Encryption terms do not answer the same question

Encryption in transit

Protects traffic between systems against interception in transit. It does not establish whether a provider can access the content after receipt.

Encryption at rest

Protects stored bytes. A service with access to the necessary keys may still decrypt them to operate.

Browser encryption

Moves encryption or decryption of specified data to the user's browser. Which values are covered, and who can unwrap the keys, still matters.

Key custody and recovery

Determines who can independently recover readable information. Access decisions, key grants, backup procedures and lost-device behavior deserve separate scrutiny.

A practical example

Imagine uploading a contract with a customer's company name already on page one, then asking the signer to enter a bank account number into a protected field. The existing company name is part of the source PDF the service processes. The newly entered protected account number follows the browser encryption path. The recipient email and completion status remain operational metadata. A claim that the entire agreement is invisible to the platform would blur these important differences.

For a simpler analogy, read the bank vault and keyring explanation. For the underlying protections, read Inklok's security overview. If evaluating multiple providers, use the privacy checklist.

Evaluate the actual workflow

Start with a test document that contains no real sensitive information. Check which parts are protected, who can access them after signing, and how recovery works.

Who Can Read Your Signed Agreement? A Data Flow Guide | Inklok