Send a file only they can open

No. Email attachments are stored unencrypted on every mail server between sender and recipient, sit in inboxes indefinitely, and can be forwarded to anyone — with no way to verify who opens them or to make them expire. Armadoc encrypts files in your browser, verifies every recipient with a one-time code, and deletes them automatically when the link expires. There’s a point-by-point version of this answer on Armadoc vs. email attachments.

It helps, but the weak link is the password itself: you still have to get it to your recipient somehow — usually in the same email or a text, sitting right next to the file it unlocks. It’s also only as strong as the password you choose, and there’s still no way to verify who opens the file, no expiry, and no automatic deletion. Armadoc encrypts the file in your browser, delivers the key only to a recipient verified with a one-time code, and deletes it when the link expires.

They’re great at what they’re for: a shared library you and your collaborators come back to day after day. Armadoc is for the other situation, the one where you need to hand one file to one person and then have it gone. A cloud drive keeps a copy for as long as you both remember it exists, the provider can read it, and ‘sharing securely’ tends to drag your recipient into an account. Armadoc encrypts the file in your browser (so we genuinely can’t read it), opens it only for a recipient who verifies with a one-time code, and deletes it when the link expires, leaving nothing to revoke and nothing behind. If you’ll keep working in the file together, use a drive. If you’re handing it over once, use Armadoc.

Correct. They click the link, request a one-time code (sent to the email or phone you used to address them), enter the code, and the file decrypts in their browser. No app to install, no password to invent, no signup form to fill out.

Your file is encrypted in your browser before it’s uploaded. The decryption key is shared only via the secure link to the verified recipient. We store the encrypted blob — but we can’t open it. Nobody at Armadoc, including engineers and admins, can see the contents of what you send.

There’s nothing useful to take. Files are encrypted in your browser before they reach us, and we never hold the keys — so whether someone breaches our storage or serves us a legal demand, all that exists on our side is an encrypted blob we can’t open. We can’t hand over what we can’t read.

The file contents are end-to-end encrypted — we can’t read them. The file name isn’t, and the description isn’t either, because we include them in the recipient’s notification email so the delivery looks genuine and isn’t mistaken for spam or phishing. The description is completely optional — leave it blank if you prefer. The file name is always sent, so if the name itself is sensitive, rename the file before sending it.

Yes, with one catch. Each browser creates its own key and keeps it there, never on our servers, which is precisely why we can’t read your files. Adding a device enrolls another key alongside the ones you already have — nothing is replaced. Anything sent to you after that opens on either one. Anything sent before it won’t open on the new device, because the sender sealed it to the keys you had at the time; it stays readable on the device you were using then. The same applies to your recipients. Clearing site data or using a private/incognito window discards that browser’s key, which leaves you in the same position as a new device. Your dashboard lists every key on your account, so you can name them as you add them and revoke any you no longer use.

Your private key is stored only on your device and is never sent to us — so even we can’t recover it. If you sign in somewhere new, or your key is gone because you cleared site data, Armadoc lets you add a fresh key for that browser. You keep your account, and your other keys are untouched: files already sent to them stay readable wherever those keys still are. What the new key can’t do is open anything sent before it existed, so you’ll see a reminder to ask the sender to share those again. The key on the device you lost stays enrolled until you revoke it from your dashboard, and until you do, senders keep sealing new files to it. Revoking only affects future sends — anything already sealed to that key is untouched. (Opening files in a private/incognito window has the same effect — the key is discarded when you close it — so Armadoc warns you before you rely on it.)

On the Free plan, files are automatically deleted 10 days after they’re sent. On Pro, the sender picks the window — anywhere from 1 to 30 days. Once it’s up, the file is gone for good (more below).

The encrypted file is permanently deleted from our storage. There is no archive, no recoverable copy, no “trash” folder. If you need to send it again, you upload it again.

Because the Free plan is built for the person who needs to share something private a few times a year — not as a watered-down demo. If you’re sending more than that, you’re probably running a small business or freelance practice, and Pro is built for you.

PDF, XLS, DOC, JPG, PNG, and HEIC. These cover roughly 99% of the documents people actually need to share privately. More formats are on the roadmap.

Yes. On the Free plan each file can be up to 10 MB; on Pro the limit is 25 MB per file. If a file is larger than your plan allows, Armadoc tells you before the send goes through.

On the Pro plan, yes. You get a notification the moment the file is decrypted and viewed, including a timestamp. The Free plan doesn’t include read receipts.

Give it a minute, then check your spam or junk folder — that’s the first place to look. Armadoc sends from a brand-new domain, and some mail systems are extra cautious with senders they haven’t seen before. This settles down as the domain builds a track record.

On a personal inbox (Gmail, Outlook.com, iCloud, Yahoo): if you find it in spam, mark it “not spam” and future messages will land in the inbox.

On a work, company, or school account (the kind an IT team manages): the organization’s filter can hold the message before it reaches you, so it may not appear in junk either. Ask your IT team to allow mail from armadoc.link, or receive it at a personal email address instead.

Not yet — Armadoc isn’t formally certified for HIPAA or similar, and we don’t currently sign BAAs. That said, the architecture (end-to-end encryption, verified recipients, automatic deletion, no admin access) reflects the same principles those frameworks care about around data minimization and access control. If formal compliance is a hard requirement for your team, get in touch and tell us what you need.