SelinaSEND
Up to 500 MB on a free account. Expiring links, download limits, and nothing for your recipient to install. We store ciphertext, never the passphrase. The person you send it to needs a link and a passphrase — not an account, not an app.
Not “we promise not to look.” We are not able to.
Start sending free7-day trial, no card required.
Your browser derives a key from the passphrase and encrypts the file before a single byte leaves your device.
We store ciphertext and nothing else. Share the link or a QR code however you like — and the passphrase by a different route, so the two never travel together.
No account, no install, no sign-up. The file decrypts locally on their machine and never in plaintext on ours.
A link you cannot take back is a liability. Every send carries its own expiry, its own download budget, and a kill switch.
The key is derived from a passphrase in your browser. It is never sent to us, so it is never ours to hand over.
Ask for a window and the link dies at the end of it — up to 24 hours free, 72 on a paid plan. After that the ciphertext is unreachable whether or not anyone opened it.
Three downloads free, ten on a paid plan. When the count is spent the link stops working.
Sent to the wrong person? Kill the link from your dashboard and it dies immediately.
The difference that matters is whether the company holding your file can open it.
| Capability | SelinaSEND | WeTransfer | Dropbox | Drive |
|---|---|---|---|---|
| Encrypted before it leaves your device | ||||
| Provider cannot read the file | ||||
| Recipient needs no account | ||||
| Passphrase protection | ||||
| Expiring links | ||||
| Download-count limit | ||||
| Revoke a sent link | ||||
| Included with an AI assistant |
Compared against each product’s published documentation. Capabilities change — check the current terms of any service before relying on it for sensitive material.
Selina is built around long-term memory — and a send is deliberately kept out of it. What you transfer is never stored in what she remembers, never learned from, and never folded into your history. It is a separate, ephemeral channel that exists alongside the assistant rather than inside it. That separation is the design, not a setting.
Most products use one word for four different things. We won’t, so here is exactly what each path gives you.
Zero-knowledge. Encrypted in your browser; we hold ciphertext and never the passphrase. Paid plans.
Zero-knowledge. Same path, same guarantee. Paid plans.
Encrypted in transit and at rest — but a model processed that content when you wrote it, so it was never zero-knowledge. We will not pretend otherwise.
Encrypted at rest under a key you control, and cryptographically erasable — destroy the key and the data is gone, backups included.
On a paid plan, yes. Compose a send directly and your browser derives a key from your passphrase with PBKDF2-SHA256 at 200,000 iterations, encrypting with AES-256-GCM before upload — we receive ciphertext and never the passphrase, so we cannot decrypt it for you or for anyone who asks us to. Sending a file from your Selina vault works on any account and is encrypted for the recipient the same way, with the key held on your side of the link.
No. They open the link in any modern browser, enter the passphrase you gave them, and the file decrypts on their own machine. No sign-up, no install, no app.
Up to 500 MB and three sends a day on a free account or the seven-day trial, with links lasting 24 hours and three downloads. Paid plans raise that to 5 GB, 50 sends a day, 72-hour links and ten downloads, and unlock composing a send directly in your browser.
The file is unrecoverable. That is the honest trade of real zero-knowledge encryption — there is no reset link, because there is no copy of your key on our side.
No. A send sits deliberately outside the memory system: it is never stored in what Selina remembers, never learned from, and never mixed into your history. The separation is the point.
Files encrypted in your browser reach us as ciphertext we cannot read, which is the property most data-handling reviews are looking for. Whether that satisfies a specific obligation depends on your policies and your own assessment — talk to whoever signs off on it.
A send composed in your browser is zero-knowledge: the key is derived on your device and we never see it. A file sent from your Selina vault is encrypted at rest under a key you control and encrypted again for the recipient, though it passed through Selina to get there. A message or conversation from inside the assistant is encrypted in transit and at rest, but a model processed that content when you wrote it. We keep those distinctions rather than flattening them into one word. Browser-composed sends, notes and conversations are paid-plan features; vault file sending is on every account.
Encrypted file sending works on any account, including the seven-day trial, no card required. Paid plans lift the size, expiry and download limits, and add browser-held keys, secure notes and conversation sending.
Every account sends encrypted files, alongside an AI with long-term memory across your conversations, files and projects. Paid plans raise the limits and add secure notes and conversation sending.
Create a free account7-day trial, no card required.