How does zero-knowledge encryption work? A bank vault analogy

Imagine a bank with a large vault containing thousands of safety deposit boxes. Each box holds a single piece of information. Every box is locked, and only someone with the right key can open it. The vault itself is locked, too.

When you first become a customer, you get a personal keyring with all the keys to your boxes, plus a special Recovery Key that only you know.

The bank also keeps a backup of your keyring, safely locked away. Only your password or your Recovery Key can unlock it. And since the bank doesn't know either of those secrets, it can't unlock your keyring.

This is what makes this bank different: even the bank itself cannot open your locked safety deposit boxes without your keys.

When you arrive, the front desk verifies who you are and lets you into the vault. Your password unlocks your personal keyring as you walk in. Inside, you can open boxes, provided you possess the correct keys. Other boxes stay locked.

When you return on another day, use your password or Recovery Key again to retrieve a new copy of your keyring.

Suppose you are asked for your name, address, tax ID, date, and signature. Five pieces of potentially sensitive information. Imagine each value being placed in its own locked box.

Everyone authorized to see these five values gets the keys they need added to their own personal keyring. You have yours, the sender has theirs, and any other authorized person has theirs.

Sign another agreement? The pattern repeats with new boxes and keys for that agreement's authorized participants. Access to one agreement does not automatically open another. Not every participant can open every box; access depends on which protected values have been shared with them.

And no matter how many agreements or people are involved, the bank still can't unlock anyone's keyring or open their boxes.

But you also need a private place to open your box.

Safety deposit boxes aren't supposed to be opened at the front desk. They contain confidential information. Nor would you want to open one in the vault, where other customers might be retrieving their boxes or security cameras could compromise your privacy. That's why many banks provide private viewing rooms. You enter with your keys, open the box privately, and lock it again before the bank takes it back.

Inklok works similarly for protected signing values. Your web browser is the viewing room. When you read protected signing information, your browser opens it on your device. When you enter a value, your browser locks it before Inklok stores it.

Inklok handles the locked boxes. Your browser handles what is inside.

Managing all those boxes, keyrings, permissions, and recovery paths by hand would be a nightmare. Inklok does the coordination for you: it manages agreement workflows, safeguards protected values, routes signing invitations, and helps authorized account holders regain their personal keyring on a new device.

Sending an agreement? Inklok coordinates access for the intended people without needing a copy of their unlocked private keys. Signing? Your browser takes care of locking and opening protected values in the background. Looking for an agreement from years ago? Your agreement vault helps you find it.

Zero-knowledge protection, with the familiar feel of a modern agreement platform.

Not all data at Inklok is zero-knowledge protected. Inklok needs access to agreement metadata and audit history to manage signing workflows, and source PDFs are processed separately from protected signing values. For the precise technical boundary, see our Security overview.

Want the bigger picture? Read Why your e-signature provider shouldn't have your keys.

Most software platforms ask you to trust them with your data. They store it, manage it, and often retain the technical ability to access it.

But agreements are different. They regularly contain some of your most sensitive personal and business information: Social Security numbers, financial details, signatures, addresses, and confidential terms.

We don't believe an e-signature provider should automatically have access to that information simply because you use its software.

That's why we built Inklok differently.

We believe your protected signing information should remain private, accessible to the people authorized to see it, without giving Inklok its own keys to unlock it.

And we believe that level of privacy should come standard for all users, without complicated setup or sacrificing the simplicity of modern software.

Because your agreements are yours.