The Privacy Myth: Can Your Email Provider, Your Bank, or Soult Read Your Data?

Most people think about privacy as a light switch. Either your data is protected or it isn't. Either a company can read your information or it can't. Either something is "encrypted" and therefore safe, or it isn't and therefore exposed.

Real privacy doesn't work like a switch. It works like architecture. The same word — encrypted — can describe two systems that behave in completely opposite ways at the moment it matters most: when you forget your password, when your phone breaks, or when a court comes knocking.

So before we talk about how Soult protects your data, let's talk about how privacy actually works, trade-offs included.

Start with a question you can picture

If a government agency served a major email provider with a valid court order for your inbox, what would happen?

Most people answer one of two ways. Some say they can read everything, of course they'd hand it over. Others say it's encrypted, so nobody can read it, not even the provider.

Both answers are wrong, and why they're wrong is the whole point of this article. The truth turns on a single question almost nobody asks: who holds the keys? Not whether the data is encrypted — nearly everything is encrypted today — but who is capable of decrypting it.

Three questions people ask as one

"Can they read my data?" is really three separate questions.

Can employees read it?

For any serious provider — the big platforms, established banks, Soult included — no.

Your data isn't sitting on an engineer's laptop waiting to be opened out of curiosity. Production access is constrained by identity and access management, so systems rather than people touch data by default; by least privilege, so even authorised staff get the narrowest access that does the job; by audit logs, so every access is recorded and attributable; by approval workflows, so sensitive actions need sign-off; and by continuous monitoring, so anomalies get flagged.

When you read a headline about an employee improperly accessing user data, it's news precisely because it's rare, against policy, and usually ends in dismissal or prosecution.

Can the company itself decrypt it?

Here the honest answer is: it depends.

Some services hold the keys to your data, and they hold them to give you conveniences you genuinely rely on — instant search across your email, a file preview, a password reset that actually works. If a company can do those things, it can by definition decrypt your data.

Other services are built so they never hold a usable key at all. Data is encrypted before it reaches their servers, with a key only you control. Those companies genuinely cannot read your content, no matter who asks.

This is the fork in the road, and it's where the confusion lives. The same marketing word sits on both sides of it while meaning opposite things.

Can a court compel readable data?

This follows directly from the previous question. A company can only hand over what it can unlock. Holding keys means lawful process can produce readable information. Not holding keys means the only thing available to hand over is ciphertext — you cannot produce a key you never had.

So "can the government read my data?" isn't really a question about governments. It's the key-ownership question wearing a different hat.

The four models

Almost every service you use sits in one of four models. Each buys something real and gives something up.

Server-managed encryption

Major email services, mainstream cloud storage, most banking systems.

Your data is encrypted, but the company manages the keys for you. That single choice is what makes forgetting a password survivable: you reset it and walk back in. Losing a device isn't catastrophic either, because your data lives on the server rather than trapped on the phone you dropped in a lake.

The trade-off: because the company can decrypt to provide those conveniences, it can also decrypt when legally compelled. Under a valid court order, readable data can be produced. That's the price of frictionless recovery — and for most everyday data, most people consider it fair.

End-to-end encryption

WhatsApp, Signal.

Content is encrypted on your device and decrypted on the recipient's. The keys live on the endpoints, not with the company in usable form. The company cannot read your conversations, and cannot hand over their content under legal process.

The trade-off: recovery gets harder. Lose your device without a working backup and that history can go with it. The same wall that keeps the company out can keep you out.

Zero knowledge

Password managers — Bitwarden, 1Password, Proton Pass.

The strictest model. Your data is encrypted and decrypted only by you, with a secret that never leaves your control. The provider stores an encrypted blob and has zero knowledge of what's inside. Not an employee, not the company, not a court, not an attacker who breaches their servers.

The trade-off is absolute: forget the master secret and it's gone. No reset link, no support line, no recovery. Nobody can restore what nobody but you could ever read. Guaranteed secrecy and guaranteed recovery are mutually exclusive — not as a policy choice, but as a mathematical one.

Hybrid — what Soult does

Soult's position is that different information deserves different protection, because the things worth keeping behave very differently.

An insurance policy should be recoverable, so your family can find it years from now. A family photo should be recoverable, so it survives to the next generation. A medical directive should be recoverable, so it's there when it's needed.

But a bank password should be private. A crypto recovery phrase should be private. A government login should be private.

Force all of that into one model and something breaks either way. Make everything recoverable and your most sensitive secrets are, in principle, reachable. Make everything zero-knowledge and one forgotten password erases your family's entire inheritance of documents and memories.

So Soult runs two models side by side. Your vault — documents, assets, loved ones, memories, wallet — is recoverable, because that's what makes it useful to the people you leave it for. And inside the Password Keeper, any entry you mark Advanced is encrypted on your phone with a vault password we never receive, so those specific entries are ones we cannot read at any price.

You choose which entries get which treatment, one at a time. Most of your Password Keeper doesn't need Advanced. The handful that do, genuinely do.

The part that usually surprises people

Turning on end-to-end encryption normally means typing a master password constantly — to read and to write. That's tiring, and tiring is how good security gets switched off.

With Soult, adding an Advanced entry needs no password at all. Only reading one does.

Think of a letterbox. Anyone can post a letter through the slot without a key; only the keyholder opens the box. Your phone holds a public slot that seals new entries, and a private key that opens them — and your vault password is what unlocks that private key.

So saving a new bank password is instant and promptless. The vault password appears only when you actually want to look at something, which is rare, and which is exactly when a prompt makes sense.

If you want the algorithms and parameters behind that, they're published in full in our security whitepaper, and explained step by step in A Vault Inside Your Vault.

Why not make everything zero-knowledge?

It's the fair question, and it deserves a direct answer.

Imagine years of building your vault — insurance policies, property papers, your will, family memories, medical wishes, your children's documents. Then you forget one password.

In a pure zero-knowledge system, that's the end of all of it. Not you, not your family, not Soult can recover any of it. The vault becomes a safe whose only key was destroyed, and everything you preserved for the people you love becomes permanently unreadable.

That's the precise opposite of what a life vault is for. The entire purpose is continuity. A model that can silently erase a lifetime of documents on one memory lapse fails that purpose completely, however private it looks on a feature list.

Zero knowledge is the right tool for a bank password. It is the wrong tool for your family's legacy. We use each where it belongs.

What we're actually balancing

A life vault has to hold four things at once: privacy, keeping the right things unreadable to everyone but you; security, protecting everything against loss, breach and misuse; recoverability, so what should survive can be retrieved; and continuity, so your digital life outlives forgotten passwords, lost devices and time itself.

You cannot maximise all four with one setting. You can honour all four by matching the model to the material.

Privacy isn't about making data impossible to access. It's about making sure the right people can access the right information, at the right time, for the right reason — and nobody else.

That's harder to build than a single locked door, because it takes a judgement about what each piece of information is actually for. But it's the only approach that respects both your need for secrecy and your family's need for continuity.