Skip to content
Business
4 min read · May 5, 2026

Confidential file sharing for lawyers, accountants and consultants

Client documents under privilege or NDA need a transfer method you can describe to a client. What to look for, what to avoid, and what "we cannot read it" is worth in practice.

If you handle other people's confidential material for a living, file transfer is a professional obligation rather than a preference. It is also, in most small practices, the weakest link — because the tool that gets used is whichever one the client will tolerate.

The actual constraint

Every professional-services firm has the same problem: the security of a document transfer is determined by the least technical person in the chain.

You can buy an excellent client portal. If the client cannot work out how to log in, they will email the document instead, and you will accept it, because the alternative is losing the client. The portal has then achieved nothing except a line item.

So the practical requirement is not "most secure available". It is the most secure option a client will actually complete on the first attempt, which is a much harder specification.

What to evaluate

Can the vendor read the files? The single most consequential question. A vendor who can read client documents is a vendor whose breach is your disclosure event, and whose subpoena is your privilege problem. End-to-end encryption removes them as a party to the data — see what end-to-end encryption actually means for how to tell a real claim from a marketing one.

How many steps for the client? Count them honestly, including account creation, email verification, and password setup. Anything over three and expect drop-off.

Does it work on a phone? A meaningful share of clients will do this on a phone, badly, while doing something else.

What is the retention default? Documents that persist by default accumulate into a liability. Prefer delete-on-collection.

What does it log, and what could be produced? You should be able to answer this for your client. "The service can see that an encrypted transfer occurred, its size, and roughly when — not its contents" is an answer. "I assume they're fine" is not.

Where is it hosted? For some regulated work this determines whether the tool is usable at all.

What happens if the vendor disappears? Small SaaS vendors fold. A tool where the file lives only briefly is far less exposed to this than a portal that is also your document archive.

Where common approaches fall down

Email. Readable by two providers, copies persist indefinitely across at least six locations, and wrong-recipient errors are the leading cause of real-world disclosure incidents. Covered in more depth in is email secure for sensitive documents.

Password-protected ZIP or PDF. Better than nothing, but the password almost always travels in the same email or the following one, which defeats it. Older ZIP encryption is trivially broken. And clients on phones frequently cannot open them at all.

Consumer cloud drives. The provider can read the file. Share links default to broad permissions. Files persist. Perfectly reasonable for internal non-sensitive work; a poor fit for privileged material.

Full client portals. Genuinely the right answer for firms above a certain size, particularly where you need audit trails and matter-level organisation. Overkill for a sole practitioner sending three documents a week, and the adoption problem is real.

WhatsApp and Signal. Genuinely end-to-end encrypted, and often the pragmatic choice. Drawbacks: it puts client material on a personal phone, mixes professional and personal channels, requires exchanging phone numbers, and file size limits are restrictive.

A workable setup for a small practice

For a solo or small firm without a portal, a defensible and low-friction arrangement:

For receiving documents from clients: publish an alias — smithlaw_intake — on your website and in your engagement letter. A client goes to the site, clicks once to create a mailbox, types your alias, attaches the document, and sends. No account, no password, no verification email. Three steps, works on a phone.

For sending to clients: ask for their alias, or send them an invite link that opens a conversation directly. For an ongoing matter, the chat keeps a running encrypted thread rather than a series of disconnected transfers.

For your records: download and file documents into your normal document management system on receipt. The transfer tool is a pipe, not an archive — which is the correct division, since an archive that a vendor cannot read is also an archive you cannot search.

What to tell a client who asks: "It encrypts the file in your browser before it uploads. The service carrying it holds an encrypted blob and no key that opens it, and their copy is deleted as soon as I download it. Neither of us has to create an account."

That is a sentence you can say in a meeting, which is worth more than a feature list.

What this does not replace

Being clear about scope:

  • Not a document management system. No matter organisation, no retention schedule, no audit trail across a file's life.
  • Not a compliance product. If your regulator requires specific certifications, verify them directly. AliasCloak makes no certification claims, and any vendor that waves a compliance logo without a scope statement should be treated with suspicion.
  • Not a substitute for a signed data processing agreement where your obligations require one.
  • Not protection against your own device. If your laptop is compromised, encryption in transit is not your problem.

For firms with genuine regulatory obligations, a proper portal with the paperwork behind it remains the right answer. For the very large number of small practices currently emailing PDFs, an end-to-end encrypted transfer with no account requirement is a substantial improvement that clients will actually complete.

The security model sets out exactly what is and is not protected, in language you can quote to a client.


Private by design

Start private. Stay in control.

Create a free AliasCloak mailbox in seconds, then use the same private identity for encrypted mail, chat, and file delivery.