The Receive hub is not a downloads folder

Arrival is its own job

Most privacy products explain how to send secrets. Fewer explain what happens when you are the person receiving them.

A contractor emails a .nt2share file. A family member sends an encrypted link. Someone reads a one-time code aloud on a call. A landlord hands you a USB stick after a meeting. Your phone downloads a PDF you did not mean to keep forever.

The old habit is the same for all of them: save the file, hope you remember why, search for it later, or leave it in a folder called "Downloads."

That folder is not a vault. It has no structure, no accept-or-decline moment, and no clear path from "something arrived" to "this belongs in my records."

Receive before Inbox

NT² separates two ideas that often get blurred:

Receive is the front door for many kinds of arrival—not only messages from another NT² vault.

That can include:

• importing a Share file (.nt2share) from email, AirDrop, or USB;
• opening an encrypted link someone sent;
• capturing text quickly when someone reads a code or phrase aloud;
• bringing a file into the vault when the sender is not using NT² at all.

The goal is not to dump everything straight into storage. It is to give arrival a deliberate shape before the data becomes part of your vault.

From handoff to structured record

The value shows up in ordinary moments.

Your co-founder sends a production key as a share file. You import it through Receive, review what arrived, and accept it into a Credential item—not a mystery attachment in Downloads.

Your accountant sends an encrypted link for one statement. You open it through Receive, decrypt with a share passphrase that is not your master password, and keep the source record structured on your side.

Someone reads a recovery code over the phone. You capture it in Receive as a Secure Note instead of scribbling it on paper or pasting it into a chat.

Each path ends the same way: structured storage under your control, not another file lost in a generic folder.

Receive completes the product story

Store explains why secrets need fields and encryption on your device. Share explains how to send one item under rules you choose. Present explains how to show less in the moment.

Receive completes the loop on your side: when ciphertext is sent to you, you need a place that treats arrival as seriously as storage.

That is what the Receive hub is for—not a downloads folder with a nicer icon, but the start of turning a handoff into something you can find, protect, and use six months later.

For the recipient decision moment, read Something arrived in my Inbox. For offline file handoff, see Sometimes a USB stick beats email. Follow new posts through the RSS feed.