Confidencial Exchange

Send it. Request it. Sign it. Own it.

Confidently exchange sensitive data, internally and externally, without losing control. Share any file, any size, with built-in protection that travels with the data. Set granular access, track activity, collect signatures, and stay compliant, all from one powerful, intuitive platform.

No account required to viewRevocable after downloadPQC-ready
Data Exchange
See it work

One deal. Every workflow protected.

Step through a live M&A process: CIM distribution, financial disclosure intake, LOI countersignature, and revocation. All inside one platform with one audit trail.

Interactive Demo
What do you want to do?
Pick a workflow — see how Exchange handles it end to end.
Send
Send protected files to anyone. Policy travels with the file after it leaves.
Try it →
Request
Collect sensitive docs — encrypted before they leave the sender.
Try it →
Sign
E-sign agreements. Sensitive fields stay encrypted through signing.
Try it →
1
Add files
2
Recipients
3
Policy
4
Sent
5
Activity
Drop your files
Any file type · up to 1 TB · encrypts before upload.
Drop files here or click to add
PDF · DOCX · XLSX · any format · up to 1 TB
Add files
2
Recipients
3
Policy
4
Sent
5
Activity
2 files added — 9.6 GB
Files encrypt on device before upload. Now add recipients.
PDF
CIM_ProjectHeron_CONFIDENTIAL.pdf
8.2 GB
XLSX
FinancialModel_Heron_v4.xlsx
1.4 GB
Recipients
AF
A. Fletcher
a.fletcher@harborviewcap.com
External
MO
M. Osei
m.osei@pinnaclegrowth.com
External
DN
D. Nakamura
d.nakamura@strandadvisors.com
External
Add files
Recipients
3
Policy
4
Sent
5
Activity
Set access rules
These rules travel with the file — enforced wherever it goes.
👁View-only — no download
🚫Block forwarding
💧Watermark on view
Expires in 30 days
Add files
Recipients
Policy
4
Sent
5
Activity
Sent · 3 recipients notified
Recipients get a link. Nothing else.
No account needed. Click, verify, access — policy enforced on open.
From: noreply@confidencial.io · To: a.fletcher@harborviewcap.com
D. Whitmore has securely shared files with you
Hi A. Fletcher,

D. Whitmore has shared 2 protected files with you. No account required.
Confidencial protects all information before it is transferred.
1
Build form
2
Send link
3
Received
4
Activity
What do you need from them?
Build a form or use a template. Everything submitted arrives encrypted.
Request name
Buyer Financial Disclosure — Project Heron
Form fields
Text
Firm name
Required
Text
AUM / Fund size
Required
File
Proof of funds document
Required
Text
Financing structure
Optional
Build form
2
Send link
3
Received
4
Activity
They get a link. No account needed.
Fills out the form in their browser. Everything encrypts on their device before it leaves.
From: noreply@confidencial.io · To: a.fletcher@harborviewcap.com
D. Whitmore is asking you to securely submit information
Hi A. Fletcher,

D. Whitmore is requesting a secure submission for Buyer Financial Disclosure. No account required.
Confidencial protects all information before it is transferred.
Build form
Send link
3
Received
4
Activity
Received · encrypted on arrival
Submission arrived. Sensitive fields locked.
Encrypted before it left their device. Only your authorized team can read the sensitive fields.
Firm nameHarborview Capital Partners LLC
AUM / Fund size[ encrypted · authorized only ]
Proof of funds[ encrypted · authorized only ]
Financing structure[ encrypted · authorized only ]
SubmittedJun 19 · 11:42 · SHA-256 verified
1
Review
2
Sign
3
Sent
4
Activity
LOI_ProjectHeron_Harborview_v2.docx
Awaiting signature
Letter of Intent
Heron Data Systems Inc. · Harborview Capital Partners LLC · June 20, 2026
This Letter of Intent ("LOI") is entered into as of the date set forth above between Heron Data Systems Inc. ("Company") and Harborview Capital Partners LLC ("Buyer"). The Buyer hereby expresses its intention to acquire one hundred percent (100%) of the issued and outstanding equity interests of the Company for an aggregate purchase consideration as set forth in Schedule A hereto, subject to customary adjustments and satisfactory completion of due diligence.
This LOI shall not constitute a binding agreement except with respect to the exclusivity and confidentiality provisions set forth herein. The exclusivity period shall commence upon countersignature and continue for forty-five (45) calendar days thereafter.
Seller representative
D. Whitmore
Signed · Jun 20 · 08:41
Buyer — Harborview Capital Partners
Sign here
A. Fletcher
Review
Sign
3
Sent
4
Activity
Fully signed · audit certificate issued
Done. Cryptographic proof stays with you.
Both parties signed. The audit certificate lives in your environment — not a third-party vault.
From: noreply@confidencial.io · To: d.whitmore@heron.com
LOI_ProjectHeron — fully executed
Both parties have signed. Your audit certificate is ready.
Audit certificate
SHA-256 hasha3f2b9c1d4e7…08f1
Signature algoCRYSTALS-Dilithium (PQC hybrid)
Signers verified2 of 2 · identity-bound
Sensitive fieldsEncrypted throughout · principals only
Activity
Access origin map
Authorized
Denied
Blocked
Immutable trace log
0 events
The problem with file sharing

A shared link is not a handoff.

Email, SharePoint, and DocuSign hand over a copy and walk away. The moment it downloads, you lose access control, audit trail, and any way to take it back. The file is theirs now, not yours.

LINK ALONE

What sharing a link gives you

A copy leaves your environment and keeps going. Each hop is invisible, none of it is revocable, and a vendor breach quietly becomes yours.

Recipient downloads a copy. It's on their device, untracked.No control
They forward it. Second and third hops are invisible.Unaudited
The deal falls through. You can't pull the files back.Irrevocable
The vendor gets breached. Their breach now includes your documents.Third-party risk
WITH EXCHANGE

What Exchange changes

Protection and policy are embedded before the file moves. You stay in control after it leaves, and the audit trail never stops.

Encrypts on your device
Confidencial never sees plaintext
Policy travels with the file
VIEW-ONLYNO-FORWARDWATERMARKEXPIRES
Revoke any time, audit always
Every open & forward logged · identity-bound
How Exchange works

Client-side to destination. Protection never leaves.

Encrypt before upload, enforce policy at every hop, and log every interaction, regardless of where the file ends up or who has it.

1

Compose

Drag files, set recipients, choose a policy, and select options like view-only, no-forward, watermark, and expiration.

2

Encrypt client-side

Files encrypt on your device before upload. Your keys, your KMS. Servers never see plaintext.

3

Recipients open a portal

A branded notification links to a limited portal. No account for external users. Policy is enforced on open.

4

Audit & revoke

Every event logged with identity, time, and location. Revoke one file or an entire send instantly.

Compose & set policy
Encrypt on device
Your KMS & storage
Exchange
Send · Request · Sign
POLICYAUDITREVOKE
Recipient portal
No account · policy on open
Immutable audit log
Every hop, by identity
Revocable anywhere
Even after download
No agents. No recipient software. No plaintext in transit.
Three workflows, one protection layer

Send. Request. Sign.

Every motion shares the same encryption, policy engine, and audit trail. Choose the direction (outbound, inbound, or signature); the protection is identical across all three.

Document Send

Move large volumes. Retain full control.

Send files or folders up to 1 TB. Protection is applied before upload, recipients open a portal where policy governs what they can do. The moment they forward it, the next person gets ciphertext.

Up to 1 TB per send

Files or folders. Auto-resume on interruption. No per-GB caps.

Granular access

View-only, block download, block forwarding, watermark, expiration.

External, no friction

Recipients get a limited portal. No account. No install.

Forwarding kills access

Policy follows the file. Second-hop recipients get ciphertext.

Secure Document Send
Files
NDA_Blackstone_v3.docxEncrypted
Q3_Financial_Summary.xlsxEncrypted
Recipient
jane.doe@partnerfirm.com · External
Access policy
View-only
Disallow forwarding
Watermark on view
Expires in 30 days
Document Request

Stop receiving sensitive data over email.

Build reusable intake forms for PII, PHI, contracts, and financials. Documents submitted through a Request encrypt on the sender's device before they leave it, so it's encrypted on arrival with the policy applied at the field level.

Reusable templates

Specify required fields, file types, and data labels per request.

Field-level policy

Different access rules for different data types in one form.

Encrypted on arrival

Files encrypt client-side before upload. Nothing arrives as plaintext.

Approve, reject, trace

Full tracing on each submission. Verify file hash for integrity.

Regulatory Submission — IND Package
Submitter name
Dr. Sarah Chen
Document
IND_Phase2_Protocol_v4.pdf
Choose
PHIRegulatoryIP
Document encrypts on your device before submission. Confidencial protects all information before it transfers.
E-Signing

Legally binding. Cryptographically verifiable.

A full e-signature workflow on the same protection layer. Contracts never leave your storage. Document hashing and quantum-ready cryptography make signatures tamper-evident and auditable long after signing.

Data-blind architecture

Contracts stay in your cloud. No third party sees the content.

Hashing + PQC

Quantum-ready signatures. The hash proves the version is unchanged.

Audit certificate

Signer identity, timestamps, IP, device — defensible in litigation.

Reusable workflows

Build once for NDAs, engagement letters, employment agreements.

E-Signing — Services Agreement
Document prepared and hashed09:41
Signer 1 · Stewart Walchli10:02
2Signer 2 · Counterparty counselAwaiting
3Audit certificate generatedPending
Document integrity
SHA-256 · a3f2b9c1d4e7…
Algo · CRYSTALS-Dilithium (PQC)
Exchange in the wild

The moments where losing control has a price

Four situations where a shared link leaves you exposed, and where Exchange changes what the other party actually gets.

M&A diligence

The deal collapses. The bidder keeps your IP.

IP sent to ten bidders. One drops out. Their copy stays. The NDA means nothing.

With Exchange

Access revoked the moment they drop. One action, across every file.

IP_Package_BidderB.zipAccess revoked
Third-party intake

A vendor is collecting SSNs, PHI, and banking data over email.

No secure intake portal. Every submission lands as plaintext.

With Exchange

Submissions encrypt on the sender's device. The vendor never holds plaintext.

Direct_Deposit_Auth.docxEncrypted on arrival
Regulatory submission

Drafts go to outside counsel. Drafts carry the real IP risk.

Draft formulations and protocol notes leave by email weeks before filing. That's where the IP walks.

With Exchange

Client-side encryption, revocable any time. Their breach is not your breach.

IND_Draft_v7.pdfProtected · revocable
Legal matter

A signed engagement letter must hold up in court. DocuSign holds your contracts. You don't.

Your audit trail lives in DocuSign's vault. In a dispute, your evidence depends on their cooperation.

With Exchange

Document hash + PQC cryptography. Audit certificate stays in your environment, not a third-party vault.

Engagement_Letter_Signed.docxAudit cert ready
Why teams trust Confidencial

Built for the environments that matter

1 TB

Max per Send transfer,  files or folders

40+

File types supported, original format preserved

2026

Data Solution of the Year

HIPAA Compliant
PCI DSS Compliant
AFWERX STTR Phase II
Customer-controlled keys
Works with the environment you already have
AWS S3Azure BlobOneDriveSharePointBoxMicrosoft EntraOktaWord · Excel · Outlook
Questions about Exchange

What security teams ask us first

Does the recipient need a Confidencial account?

No. External recipients get a limited Confidencial portal to view and interact with documents — at no cost to them. Internal users see files in their org workspace. No software install on either side.

What happens if a recipient forwards the file?

The file carries its policy. If forwarding is disabled, the next recipient encounters ciphertext — not the document. Even if forwarding is permitted, every hop is logged with identity, device, and timestamp.

Can we really revoke access after a file is downloaded?

Yes. Because protection is cryptographic and key-bound — not dependent on the file's location — revoking access means revoking the key. The file becomes unreadable immediately, regardless of where it is or who has it.

Who controls the encryption keys?

You do. Confidencial never sees plaintext. Keys are managed in your environment — your KMS (AWS KMS or Azure Key Vault) or Exchange's built-in key server. Access is identity-bound through your IdP, so revoking one person is an IdP change, not a re-encryption job.

How is Exchange different from DocuSign or Kiteworks?

DocuSign executes signatures and stores audit trails in their environment. Kiteworks runs a managed transfer portal. Exchange embeds cryptographic protection into the file itself — policy travels with the data, not the platform. Protection persists after download, after a vendor compromise, and after the relationship ends.

Does Exchange work alongside our existing storage?

Yes. Exchange connects to your existing S3, Azure Blob, OneDrive, SharePoint, or Box infrastructure. Documents never have to leave your cloud. Confidencial adds the protection and workflow layer on top of storage you already own.

Stop sharing without sovereignty

Stop sharing without data sovereignty.

Just persistent protection on every document that moves outside your organization.