CS Broker
Send privileged files with proof, through a broker that can’t read them.
Encrypt on your own machine for one person or a whole team. Each recipient is verified and collects separately, and both sides get a tamper-evident record. The broker holds only ciphertext it has no key to open.
Built on the CryptSecure client-side encryption engine. No account for us to breach, no keys for us to lose.
Most “secure” portals still hold your keys and ask for your trust. This one holds no keys and sees no plaintext, yet still proves the whole chain of custody.
The exposures a GC or a bank’s security lead already worries about.
Sensitive files still move through channels never built to protect or prove what passed through them. Each card is a real exposure, and how the broker closes it.
Email and drives leak, and the provider can read them.
Senders encrypt on their own machine; the broker stores only ciphertext it has no key to open. Breach it and nothing readable spills.
A subpoena to your vendor can pierce privilege.
No key, no plaintext, nothing to compel. Privilege is protected by cryptography, not just contract.
You can’t prove chain of custody when it counts.
Every step is hash-chained into a ledger both sides verify, with a one-click FRE 902 certificate for court.
“Secure” channels still accept plaintext.
Every deposit is validated as genuine ciphertext. Plaintext, Office docs, PDFs and images are refused at the door.
Regulators want immutable records and key control.
Self-hosted, customer-held keys, tamper-evident retention, legal hold, and erasure that keeps proof the file existed.
Today’s secrets are harvested for tomorrow’s quantum computers.
Post-quantum-ready from the client up, so long-lived privileged data stays protected past “Q-Day.”
The questions that actually decide it.
Seven questions a security or compliance reviewer asks of any channel. This is how the broker answers them next to the tools firms use today.
| CryptSecure Broker |
Email + attachment |
Cloud drive / link Dropbox, Box, Drive |
Typical “secure portal” provider holds keys |
|
|---|---|---|---|---|
| Can the provider read your files? | Nokey-blind by design | Yes | Yesunless you DIY-encrypt | Usually |
| Blocks plaintext / non-encrypted uploads? | Yesenforced at deposit | No | No | No |
| Tamper-evident custody record both sides can verify themselves? | Yeshash-chained + FRE 902 | No | Provider logs only | Provider-controlled |
| One encrypted envelope for many people, each verified and receipted separately? | Yesper-recipient pickup & record | Nosame readable copy to all | Shared linkanyone holding it | Provider-held keys |
| Runs on your own infrastructure, so data never leaves? | Yesself-hosted | No | No | Rarely |
| Post-quantum ready from the client up? | YesML-KEM / ML-DSA | No | No | No |
| Can anyone verify a document you issued, offline, with no account? | Yesserial + signed code | No | No | Provider-attested |
“Typical secure portal” = the provider generates or can access your keys. Products vary.
“Can’t I just encrypt a file and drop it in Dropbox?”
You can. But storage isn’t a broker.
Where it fits next to the tools you already use
These tools are leaders at a different job. The broker does the one none of them is built for: a handoff the operator can’t read, with a receipt both sides can check.
DocuSign, Dotloop, Qualia
How they compare
They execute and sign documents and issue a certificate of completion, which proves a person agreed. The platform can still read the document, the keys are the provider’s, and it is not built to deliver files only the recipient can open.
CertifID, ClosingLock
How they compare
Purpose-built for real-estate closings: identity and account verification, payments, and encrypted wire delivery with proof of receipt. Strong at that, and SaaS, so the platform can access content and the record is theirs.
MOVEit, GoAnywhere, Kiteworks
How they compare
Built to move files at scale with AES-256 and audit trails, often as a central server or appliance that holds the keys and can read content.
Virtru, Zix, Proton, Paubox
How they compare
They add encryption to the email you already send. Key custody and operator access vary by product and configuration, and the audit trail belongs to the provider.
Signal, WhatsApp
How they compare
Excellent for private real-time chat, and Signal even uses post-quantum key agreement. They are built for conversations between people, not for brokered file handoff.
Intralinks, Datasite, SecureDrop
How they compare
Data rooms host a deal’s library with strong logs the provider controls. SecureDrop is genuinely key-blind and self-hosted, but one-way anonymous intake needing Tor and server administration.
When the server is breached, what spills?
What happened in the MOVEit and GoAnywhere breaches.
It never holds a key, so there is nothing readable to take.
Capabilities vary by product and plan; check each vendor’s documentation. Names are their owners’ trademarks.
Six reasons it wins the security review.
Other tools give you one or two of these. The broker is the only place they come together, which is the whole point of a broker of record.
It can’t read your data, even under subpoena
Key-blind by construction: no private keys, no plaintext. Nothing for an operator, a breach, or a court order to pull.
It proves the handoff
A tamper-evident ledger both sides verify, with a one-click certificate that stands up as self-authenticating evidence.
It refuses fake encryption
Every deposit must be genuine ciphertext, so plaintext and documents never slip into a channel assumed secure.
It is yours
Self-hosted on your own WordPress and infrastructure, under your own keys and data residency. Nothing rented from a cloud.
It is ready for what’s next
Crypto-agile and post-quantum-ready from the client up, so long-shelf-life data stays protected as algorithms change.
One envelope for the whole room
Seal once for a deal team, board or panel. Each person opens it with their own key and gets their own verified pickup, in the same provable channel for legal, finance, escrow, defense and research.
Your keys and files never leave your side.
Stays with you
- All private keys
- The plaintext message
- Encryption & decryption
- Algorithm & residency choice
Held by the broker
- Ciphertext (cannot be opened)
- Public keys & certificates
- Routing & workflow state
- Tamper-evident audit ledger
It proves what happened, without ever reading what was said.
Register, encrypt, deposit, prove.
Register once and publish your public key. Every message then follows the same audited path, and all encryption happens on your own machine.
Proof you sent it, and of exactly who collected it.
A timestamped, tamper-evident receipt you can export, without ever handing your keys or your plaintext to a middleman.
A file only you can open, and a receipt you both share.
Released only after your identity is verified, decrypted on your own machine, backed by the same record the sender holds.
Only real encryption gets through.
A secure channel is worthless if people can drop plaintext into it. Every deposit is validated as a genuine encryption envelope (recognized format, parsed structure, and a payload-entropy check), so ciphertext passes and anything else is refused at the door. Validated against real CryptSecure, age and OpenPGP/GPG output, including files that wear a faked crypto header over ordinary content.
Accepted
Rejected
Hand a court the document. Let them prove it themselves.
A judge, opposing counsel or an auditor confirms a custody document is genuine and unaltered in seconds, with no account and no access to your broker.
Issued here, not one byte changed. Download the Certificate of Authenticity.
Fingerprint or signature fails. A doctored exhibit is caught, real-looking serial or not.
Unknown code. Treat the document as fabricated.
Built for FRE 902(13)/(14). The court decides admissibility; this is not a legal certification.
Everything a regulated exchange needs, and nothing that reads your files.
- Public-key directory: look up and send to any registered party.
- Private address book: named keys per contact, verified by fingerprint.
- Key rotation: retire and replace keys cleanly.
- Invite-to-send: onboard a recipient without ever holding plaintext.
- Tamper-evident ledger: every step hashed to the last.
- Signed checkpoints: the record can’t be quietly rewritten.
- FRE 902 certificate: self-authenticating record for court.
- Both-sides log: sender and recipient see the full lifecycle.
- Per-recipient custody: one envelope, a separate verified pickup for each person.
- Permanent serial: assigned once, never changed or reused.
- Unguessable code: a 120-bit public key to look up one document.
- Offline signature check: Ed25519 with a published public key.
- Public verify page: a court or auditor checks it with no account.
- Dual-control approval: four-eyes release of record.
- Retrieval limit: one-time or capped downloads.
- Acknowledgment gate: no release until the recipient accepts terms.
- Delayed, embargoed & TTL: available-from, not-before, expire-after-open.
- Scheduled revoke & recall: pull access on a clock or on demand.
- Classification & CUI marking: banners and distribution statements.
- Information barriers: ethical walls enforced at deposit and pickup.
- OFAC screening & Bates export: sanctions holds, e-discovery load files.
- Legal hold: scope by matter, notices and acknowledgments, reminders, silent holds, coverage, defensible handoff. WORM and retention block disposal until released.
- RFC 3161 timestamping: trusted time on the ledger and documents.
- REST API: the client talks to the broker directly.
- SMTP relay: transactional email via your own provider.
- SIEM & signed webhooks: feed your security tooling.
- SSO / PIV & IAL-2 gates: hook your IdP and proofing vendor.
- Self-hosted: on your own WordPress and infrastructure.
Built for anyone who has to prove what they sent.
Wherever a message carries legal weight, money, or a regulator’s interest, the same two needs appear: the content must stay private, and the send and the receipt must be provable later. That is this broker’s entire job.
Share CUI without a “deemed export”
Controlled technical data stays end-to-end encrypted to authorized recipients, so the broker carrying it never becomes the exposure.
Regulatory detail
ITAR treats letting an unauthorized person see controlled technical data as an export, and email or consumer file-sharing can trigger it, with civil penalties above $1.2M per violation.
- ITAR 22 CFR 120.54 end-to-end-encryption treatment
- DFARS 252.204-7012 CUI flowdown to subcontractors
- Auditable CUI custody as CMMC / DIBCAC evidence
Privileged delivery, with the receipts
A defensible chain of custody and a court-ready certificate, with no plaintext for opposing counsel to subpoena from the vendor.
Regulatory detail
Exchange discovery and client files while privilege is protected by cryptography, not just contract.
- ABA Model Rule 1.6 · Formal Ops. 477R / 483
- Ethical-wall-friendly routing & approval-of-record
- FRE 902(13)/(14) self-authenticating record
Client data regulators can examine
US and EU: statements, deal files and MNPI where neither operator nor breach sees readable data, with customer-held keys and embargoed release.
Regulatory detail
A single tamper-evident trail for exams, time-governed not-before release for material non-public information, and a key-blind, self-hosted channel that helps evidence EU operational-resilience and ICT third-party controls.
- SEC Rule 17a-4 (audit-trail alternative) · FINRA · GLBA
- NY DFS 23 NYCRR 500 · EU DORA ICT third-party risk
- Not-before release of embargoed MNPI
Closings criminals can’t reroute
Wire instructions out of open inboxes, where ~80% of firms faced a fraud attempt last year, with a verifiable record of what was sent.
Regulatory detail
Your eSign platform closes the signature; the broker secures the encrypted, out-of-band delivery around it.
- ALTA Best Practices-aligned handling
- Auditable proof your verification steps were followed
- Encrypted, out-of-band wire-instruction delivery
Protect controlled research, keep collaborating
Pre-publication, export-controlled and sponsored data readable only by named recipients, with a log you can show an agency.
Regulatory detail
Research-security programs must put federally funded research data under real access controls with incident reporting and evidence.
- NSPM-33 research security program (cybersecurity element)
- ITAR/EAR screening for controlled tech & foreign collaborators
- Tamper-evident logs as program evidence
Records and trial data, minimal exposure
PHI, clinical and GxP data where neither operator nor breach sees content, with tamper-evident, time-stamped custody.
Regulatory detail
Custody fit for audits and inspections across regulated life-sciences and clinical exchange.
- HIPAA-aligned confidentiality
- 21 CFR Part 11 · GxP chain of custody
- GDPR Art. 17 right-to-erasure
On your own infrastructure, with the evidence
Self-hosted or air-gapped, with identity assurance, MFA and network-bound pickup, and an exportable audit trail for oversight.
Regulatory detail
Controlled data never leaves your network; the trail supports records requests and incident reporting.
- NIST SP 800-63 identity · SP 800-207 zero-trust
- CJIS-conscious handling of sensitive records
- Supports CIRCIA-style incident documentation
Client data you can show an examiner
Returns, financials and PII under encryption your firm controls, with a record you can produce on demand.
Regulatory detail
The working core of a written information security plan.
- FTC Safeguards Rule
- IRS Pub. 4557 / 5708 WISP
- GLBA safeguarding of customer information
Policyholder data under a security program
Applications, claims, PHI and NPI exchanged under encryption you control, with the audit trail a cybersecurity program requires.
Regulatory detail
The NAIC Insurance Data Security Model Law now adopted across most states requires an information security program, third-party controls and incident evidence; health insurers also carry HIPAA.
- NAIC Insurance Data Security Model Law (#668)
- NY DFS 23 NYCRR 500 · GLBA safeguarding
- HIPAA for health lines · tamper-evident claims custody
Deal data without a readable data room
Diligence, MNPI and deal files exchanged where neither operator nor breach sees content, with embargoed release until announcement.
Regulatory detail
Private equity, banking and corporate development move the most price-sensitive material there is. Time-governed, not-before release supports MNPI handling.
- SEC / MNPI & selective-disclosure discipline
- Key-blind alternative to a provider-controlled data room
- Tamper-evident record both counterparties verify
Incident and OT data, documented
Exchange incident, vulnerability and operational-technology data on your own infrastructure, with an exportable trail for reporting.
Regulatory detail
Operators face mandatory incident reporting and sensitive OT data handling; a self-hosted, key-blind channel keeps controlled data on your network.
- Supports CIRCIA-style incident documentation
- NIST CSF-aligned confidentiality & access control
- Air-gap-friendly, self-hosted deployment
Protect trade-secret and controlled data
Exchange confidential formulations, process data and safety records under encryption you hold, with an auditable trail for inspections.
Regulatory detail
Trade-secret chemical data (TSCA CBI) and export-controlled process technology (EAR) stay end-to-end encrypted to authorized recipients, and RMP/PSM records keep a tamper-evident custody trail.
- TSCA Confidential Business Information handling
- EAR export control for controlled process technology
- EPA RMP / OSHA PSM recordkeeping custody
…and any team that has to prove what it sent: HR and background screening, notaries and apostille services, journalists and their sources, and NGOs operating in hostile environments.
Architected for where secure exchange is heading.
The terms your reviewers, examiners and counsel use, mapped to one capability set: client-side encryption, key-blind custody, a tamper-evident ledger and controlled release.
Evidence & admissibility
Court-ready records a third party can verify without trusting the operator.
Banking & broker-dealers
Books-and-records recordkeeping that satisfies examiners, with decryption authority kept at the firm.
Investment advisers & private markets
Keep material nonpublic information walled off and diligence rooms recipient-bound and revocable.
Insurance
Protect Nonpublic Information across claims and underwriting, with third-party oversight you can evidence.
Legal & litigation (legal hold, e-discovery)
Preserve first, then find the facts, without ever handing over the keys. Content review stays with the key-holder.
Real estate, title & escrow
Deliver closing documents and disbursement details so they cannot be spoofed or intercepted.
Government, defense & export control
Mark, compartment and release controlled information on a need-to-know basis, self-hosted.
Healthcare & life sciences
Exchange PHI and clinical records on a minimum-necessary basis, with erasure that keeps proof.
Cryptographic posture & data residency
The operator cannot read your data because it never holds the keys, on infrastructure you control.
Validation & operational assurance
Prove the system itself is reliable, and that the evidence of custody outlives the payload.
- Post-quantum by default in the client: ML-KEM-1024 + ML-DSA-87
- Key-blind: the broker stores only ciphertext
- Every control named above is supported
- Hybrid ML-DSA custody signatures (Ed25519 today)
- Transparency-log anchoring (external log)
- System Validation Record (you generate it)
- FIPS 140-3 validation or NIST / NSA certification
- Legal advice or QERDS status
- SOC 2 Type II / ISO 27001 (on the roadmap)
Legal-hold assessment uses metadata only; the broker never reads content.
Stop trusting the server with your secrets.
Key-blind. Encryption-enforced. Independently verifiable. Live now, self-hosted on your own WordPress.
Open the Broker →Questions? Contact Opey IT