For clients who will not install apps or create accounts

SecureMint for Legal Professionals

How lawyers and legal professionals use SecureMint to share confidential documents via self-decrypting HTML files that clients can open with zero setup.

Use self-decrypting HTML when you need the lowest-friction way to deliver privileged or confidential documents to non-technical clients.

Create a self-decrypting HTML file Open SecureChannel for ongoing matters

Best fit when

Clients cannot or will not install a dedicated app.
You send contracts, evidence bundles, or legal advice to many one-off recipients.
You need something easier to explain than an encrypted portal login.

What this page gives you

A no-install delivery pattern for non-technical clients.
A separate-channel password handoff model that is easy to explain.
A path from one-off deliveries to ongoing encrypted communication.

Who this is for

Lawyers, paralegals, judicial scriveners (司法書士), and administrative scriveners (行政書士) handling privileged communications, contracts, and evidence.

The typical pain

Clients are not technical. They cannot install apps, create accounts, or remember passwords. Email is insecure and often blocked by strict corporate policies. Legal professionals need something that works for the most non-technical client without compromising on privilege protection.

How SecureMint solves it

Use SecureMint's Self-Decrypting HTML feature. It produces a single .html file that the client can open in any browser, enter a password, and read. No SecureMint account, no plugin, no app. For long-running matters, upgrade to SecureChannel (Pro) for ongoing E2E-encrypted messaging that does not touch your email server.

SecureMint uses zero-knowledge design. The server cannot read your data.

Workflow

1. Prepare the confidential document

Have the PDF or Word document ready. Optionally strip metadata via /metadata first.

2. Generate a self-decrypting HTML

Go to /self-decrypt, upload the file, set a password, and download the resulting .html file. It contains the encrypted payload and decryption logic bundled together.

3. Deliver the HTML and password separately

Email or courier the .html file. Send the password by phone, SMS, or hand-delivery. The client opens the .html in any browser (Chrome, Safari, Edge, Firefox), enters the password, and reads.

4. For ongoing matters, move to SecureChannel

SecureChannel (Pro) provides a persistent E2E-encrypted messaging thread. Once both parties are set up, all ongoing communication happens inside SecureMint with zero email involvement.

Ready-to-use templates

Use these snippets as a starting point when you need to explain the workflow without drafting from scratch.

Self-decrypt HTML delivery email

Use this when sending a confidential document as a standalone HTML file to a non-technical client.

Subject: Confidential document enclosed

Hello,

I am sending the enclosed self-decrypting HTML file for secure review. Please save the file locally, open it in your browser, and enter the password I will provide separately.

No account or app is required. If the file does not open, reply to this email and we will provide an alternative route.

Best regards,

Separate-channel password note

Use this short note for SMS or chat when you send the password outside email.

Password for the document sent separately: [password]
Please use this only with the HTML file delivered earlier. If the file does not match, contact us before opening it.

Tools used

Self-Decrypting HTML→SecureChannel (Pro)→Secure File Send→Self-Decrypt Guide→

When Pro becomes the right next step

Start free if you want. These are the moments where Pro starts paying for itself operationally.

When one-off deliveries turn into an ongoing matter

Move from self-decrypting HTML to SecureChannel once both parties need an ongoing encrypted thread instead of repeated file-by-file delivery.

Open SecureChannel

When matters require auditability and revocation

Pro becomes useful when you need to prove delivery timing, manage histories, or disable a shared item after a matter closes.

Review Pro controls

FAQ

Is self-decrypting HTML safe?

Yes. The encryption is AES-256-GCM with PBKDF2-SHA256 (600,000 iterations). The decryption logic runs entirely in the client's browser with no network calls. An attacker who intercepts the HTML still needs the password, which you deliver over a separate channel.

Does this preserve attorney-client privilege?

SecureMint's zero-knowledge architecture means we cannot read your communications under any circumstance — we have no technical means to do so. This materially reinforces the factual basis for privilege compared to standard cloud services. That said, privilege is a legal question determined by jurisdiction and facts — consult local counsel for formal opinions.

Try it free

No signup. Open your browser and start using it immediately.

Create a self-decrypting HTML file