End-to-end encrypted in your browser. Set who can preview, stream, or download.
Add view limits, time fuses, and passwords. The server never sees a byte.
The Problem
Every platform you rely on today reads your files, logs your shares, and keeps your content forever.
Once you hit send, that file lives on Gmail's servers, your recipient's inbox, and both Sent folders. Indefinitely. No expiry, no access control, no way to unsend once forwarded.
A Google Drive or Dropbox 'private' link is just a long URL. Anyone who gets it — via screenshot, forwarded message, or a data breach — has full access.
Instagram, Twitter, Slack, and Discord all store the files you share in messages on their servers. They can hand them over to third parties. Your confidential files deserve better.
How It Works
Drag in any file — documents, media, archives. AES-256-GCM encryption fires instantly in your browser. Not a single byte reaches the server in plaintext.
You get a link. The decryption key is baked into the URL fragment — the part after the #. Servers, analytics, and logs never see it.
Set a view limit or a time fuse — or both. When your conditions are met, every encrypted chunk is purged from storage. Permanently. No recovery.
Features
Every feature designed around one principle: your files are yours alone.
AES-256-GCM encryption runs in your browser before upload. The key lives only in the URL fragment. We cannot see your files — not technically, not legally, not ever.
Set a view limit, a time fuse, or both. Once triggered, every encrypted chunk is purged from storage permanently. No soft-delete, no recovery.
Recipients never need an account. Just the link. The free tier works without a credit card — upload and share in under a minute.
Add a second layer. Recipients need the password before decryption begins.
Files split into 4 MB encrypted chunks. MP4/MOV/M4A streams via MSE for constant ~30 MB RAM. Images, PDFs, and DOCX files render directly in the browser with zoom, pan, and fullscreen.
Track your drops, monitor views, manage active links. Know who accessed what.
Zero-Knowledge Architecture
This is not a privacy policy promise. It's a structural guarantee enforced by cryptography.
Every file is split into chunks encrypted individually using AES-256-GCM. Each chunk gets a unique IV derived by XOR-ing your drop's base IV with the chunk index. Tampering with any single chunk invalidates the authentication tag.
Your key is generated by the Web Crypto API and embedded in the URL fragment — the part after the #. Fragments are never sent to servers in HTTP requests. We have no database column to subpoena, no server log to leak it.
We receive encrypted blobs, store encrypted blobs, serve encrypted blobs, and delete encrypted blobs. Your file's content is opaque to us at every stage. A court order cannot compel us to produce plaintext we do not have.
Who It's For
From unreleased demos to legal contracts — if it's confidential and temporary, it belongs here.
Share contracts, NDAs, tax documents, or board decks with clients and counsel — knowing the link expires on your schedule. No permanent cloud URL to leak, no forwarding chain to lose track of.
Send unreleased tracks, rough cuts, design files, or photo galleries for review. Set a view limit and a time fuse — after they've seen it, it's gone. No piracy surface, no lingering copies.
Share medical records, ID documents, financial statements, or credentials with the people who need them — and no one else. Password protection adds a second layer. The link self-destructs when you say so.
Share sensitive materials with sources, editors, or legal teams — knowing the link won't outlive the story. No plaintext on the server means nothing to subpoena, nothing to leak.
Pricing
Start free. Upgrade when you need more.
FAQ