Vaultine for Lawyers — Keeping Client Files Separate and Encrypted

Situations this covers

—A client's documents or photos shouldn't share a camera roll or a folder with your own personal files.

—Multiple active cases mean multiple sets of material that shouldn't mix with each other.

—A laptop used in the office and a phone used between meetings should hold the same protected files, not two different copies.

—An existing case folder needs to come in as a folder, not one file dragged in at a time.

—A phone that's lost, seized, or simply reviewed by someone else shouldn't mean client material becomes readable.

What does the work

Multiple separate vaults

Keep each client or case in its own vault, apart from your personal files and from each other.

Folder import

Bring in an entire directory of existing case files at once, preserving the structure it was already in.

Zero-knowledge design

Encryption keys are derived on the device from your code and never leave it — there's no account and no server holding a copy of your files or your key.

Works on Windows, macOS, iOS and Android

The same vaults on the laptop you use in the office and the phone you carry between meetings.

Duress Vault

A third code opens an empty vault and wipes the real ones as it does, for a device that's forced open under circumstances you don't control. Afterwards that vault simply becomes your main one, with no empty shell left behind.

No account or email to sign up

Nothing links a vault to your identity beyond the code you set for it.

Separate vaults, not one folder with everything in it

The practical problem with keeping client material next to everything else on a device isn't abstract — it's the moment someone else looks at the phone, whether that's IT, a courtroom exhibit, or a lost device. Vaultine supports as many separate vaults as you need, so a case can live entirely apart from your own files and from every other case.

Folder import matters for the same reason: an existing case file directory comes in as a folder, with its structure intact, instead of being rebuilt one file at a time.

No copy anywhere but the device

Vaultine's encryption key is derived from your code on the device itself and never leaves it. There's no account tying a vault to your name, and no server holding a copy of the files or the key. That's a factual description of the architecture, not a claim about satisfying any specific ethical wall or regulatory rule — those judgments are yours to make. What it does mean is that there is no vendor-side copy for anyone else to request or lose on your behalf.

One set of vaults, every device you actually use

A vault set up on the office laptop is the same vault on the phone used between meetings — Vaultine runs on Windows, macOS, iOS and Android as native apps, not a mobile-only tool bolted onto a desktop later.

The bottom line

This is a description of what the software does, not a claim about meeting any particular ethical or regulatory obligation — those are calls only you and your bar can make. What Vaultine offers is a factual one: client material kept in its own encrypted vault, separate from your own files and from other clients', with no account and no server on our end holding a copy of any of it.

Frequently asked questions

Can I keep separate vaults for separate clients or cases?

Yes. Vaultine supports as many separate vaults as you need, so each client or case can be kept apart from the others and from your personal files.

Does Vaultine or anyone at Vaultine have access to what's inside my vault?

No. The encryption key is derived from your code on your device and never leaves it. There's no account and no server holding your files or your key, so there's nothing on our end to access.

Can I import an entire folder of case files at once?

Yes — folder import brings in a full directory structure rather than requiring files one at a time.

Is the same vault available on my laptop and my phone?

Yes. Vaultine runs on Windows, macOS, iOS and Android, so the vaults you set up are the same ones on every device, not separate copies you have to keep in sync.

Some client files shouldn't sit next to your own photos.