STEP 01
Send a protected document
Upload a contract, report, medical record, or board packet. The file is encrypted in the browser before it leaves the sender device.
Steek replaces risky email attachments and public file links with identity-verified access, local encryption, expiring shares, QR delivery, and a clear audit trail.
A normal recipient flow: receive the link, verify with the device they already trust, open the file, and leave an audit trail.
STEP 01
Upload a contract, report, medical record, or board packet. The file is encrypted in the browser before it leaves the sender device.
STEP 02
Recipients open with Face ID, Touch ID, Windows Hello, or another passkey flow. No passwords, no shared inbox risk, no long account setup.
STEP 03
Use one-time links, QR handoff, recipient verification, and signed audit events so sensitive documents stay controlled after sending.
Files are encrypted before upload, access can expire, and every open leaves a record. Your recipient gets a direct flow instead of a portal maze.
Passkeys prove who is opening the document. The key that unlocks the file is unsealed on the recipient's own device, so signing in never lets our servers read it.
Business outcome
Give legal, finance, HR, and client-facing teams a safer way to deliver sensitive files without slowing down the person receiving them.
See why companies buy itCompliance evidence
Controlled delivery gives compliance teams repeatable evidence for recipient verification, encryption, expiring access, QR handoff, revocation, and audit trails.
Pricing
Start with secure external sharing, then add team controls, QR access, longer audit retention, and enterprise policy when the workflow grows.
Free
Prove the secure delivery flow before moving sensitive work off attachments.
Pro
For individual professionals sending confidential files to external recipients.
Organizations
Configure a team workspace for governed confidential document delivery.
Custom
For higher-volume delivery programs, special retention needs, and negotiated terms.
Our vocabulary
A few names appear across the product. Here is what each one means and how they fit together.
Dutch and Scots “steek”: to latch, to close, to stitch shut.
The zero-knowledge confidential-document delivery product—the app you are using. Every document is encrypted to the recipient's own keys and can be opened only with their passkey, so it stays sealed to everyone else, including us.
Japanese 認め (mitome), a personal seal or hanko: acknowledgement, to recognize.
The shared identity and attestation authority behind Steek—passkeys, verification, and notary. One trusted identity and attestation layer that Steek and future products federate through, so recognition and proof are consistent everywhere.
From “muniment,” a document kept as evidence of legal right or title, softened by dropping the M.
An upcoming secure dataroom and document-custody product. It will extend the same identity and attestation trust to whole collections of records, not just single deliveries.
Steek's encrypted file format and extension.
Not a normal file. Every delivered document is packaged and encrypted client-side into a .stk container—AES-256-GCM content with hybrid post-quantum wrapped keys—openable only by the intended recipient. It is the zero-knowledge artifact itself, not a file with a lock bolted on.
How they fit together
Steek delivers, and it trusts Mitome for identity and attestation. Uniment, when it arrives, will extend that same trust to datarooms. A .stk file is the encrypted artifact that flows between them—sealed by Steek, addressed to a Mitome-verified recipient.
Steek, Mitome, and Uniment are all part of the Morrive group.