Identity, assets, trust, and sharing — one story, not three features

Three verbs, one chain

When people first hear about NT² Vault, they often meet three words in a row: Receive, Store, Share.

That is accurate as navigation. It is incomplete as a story.

The product is built around four ideas that come first:

Receive, Store, and Share are how those ideas show up in the app. They are not three unrelated features glued together.

Identity: who is this vault?

Most apps identify you with email. That works for newsletters. It is a weak fit for a vault that holds seed phrases, tax documents, and production keys.

NT² gives each vault its own cryptographic identity. When your vault signs a package or answers a cloud challenge, the verification key is tied to that vault — not to a reset link in an inbox somewhere else.

Identity is the floor under person-to-person trust. Before you accept a bank detail from someone, you need to know which vault sent it. Before you share back, they need to know which vault is yours.

That is why identity belongs in the same story as sharing, not in a separate “advanced settings” corner. Read more in Threshold Vault and Key DID.

Assets: what you are protecting

An asset in NT² is not a blank note page. It is a Credential, Bank, Document, or other template with fields that match real life.

Structure matters for security psychology. A routing number belongs in a labeled field, not in paragraph three of a long memo you forgot to encrypt properly.

Store is the daily work of keeping those assets on your device, encrypted, searchable, and offline-capable. The vault holds the records. Sharing is always selective — one item, one set of fields, one moment.

Trust: the part software cannot skip for you

Trust is where many security products stop talking honestly.

NT² can verify signatures and vault identities. It cannot decide that your sister, co-founder, or accountant is the right human being for the moment. That judgment stays with you.

What software can do is give trust a shape:

• A share arrives as a request in Inbox, not as a mystery attachment.
• A secure contact is a per-vault trust relationship, not a phone address book entry.
• Trust states reflect events — invite accepted, reciprocal exchange completed, share accepted — not a “trust me” button.

Adding someone to Contacts is closer to “I am willing to recognize this vault as you” than to saving a phone number. That idea deserves its own post; start with Secure contacts are trust relationships.

Sharing: bounded handoffs

Share is not “export everything.” It is a family of modes with different trust models:

• Vault-to-vault through a secure contact — for people you share with repeatedly.
• Encrypted link with a separate share passphrase — for someone who may never install NT².
• Present or timed reveal — for in-person or video moments when you show less, not upload more.

Every mode still asks the same human question: do I trust this person with this slice of data for this period of time?

How Receive · Store · Share map to the core

Receive without trust is just downloads. Store without structure is just files. Share without identity is just chat paste with better marketing.

Together they implement one story: your vault has an identity, your assets live in it, your relationships with other people are trust relationships, and sharing is how selected assets cross those boundaries.

Two kinds of “trust” — do not mix them up

Null Trust² names a promise about NT²’s servers: we do not hold your master password, we do not read your vault contents, we cannot reset you into your data. That is trust in the product’s architecture.

Interpersonal trust is different: whether you believe the person behind a vault is your co-founder, your partner, or a scammer with a similar display name.

Both matter. They are not the same conversation. Confusing them makes good security feel paranoid and good product design feel naive.

For the architecture side, see Null Trust² — what the name means. For the recipient’s side of interpersonal trust, see Something arrived in my Inbox.

Where to go next

If this framing helps, the Trust series continues with secure contacts, mutual invites, verified trust states, three sharing modes, and when to end a relationship in the address book.

Browse scenarios at nt2.me/help/use-cases, read the product pillars at nt2.me/about, or follow new posts via RSS.