Null Trust² — what the name means
3 min read By NT²
NT² stands for Null Trust². The name is a promise about what we cannot do—even when that is inconvenient for support and onboarding.
The name on the tin
NT² reads as Null Trust²—a deliberate play on “zero trust” security, squared.
Zero trust in enterprise IT usually means: never assume a device or user is safe; verify every request. NT² applies a sharper version to your secrets:
- We do not trust ourselves with your master password.
- We do not trust the network to carry plaintext.
- We do not trust “encrypted in the cloud” as a substitute for you holding the keys.
That is what Null Trust² means in practice: the product is designed so NT²—the company and the servers—stays blind to vault contents.
What zero-knowledge actually feels like
Most people hear “zero-knowledge” and picture a padlock icon. The lived experience is simpler and harsher:
If you forget your master password, NT² cannot recover your vault.
There is no “Forgot password?” email. There is no support desk that can peek inside and confirm you typed the right thing. Your keys are derived in the browser from your password and a salt stored locally in your vault. NT² never receives the password in plaintext.
That trade-off is the whole point. A provider that can reset your password is a provider that could read your data—or be compelled to. We chose the other path.
One metaphor, not a whitepaper
Imagine a safe deposit box where you forge the only key, and the bank literally has no duplicate—not in a drawer, not on backup tape, not in a “break glass” envelope.
- You can still rent the box (use the app).
- You can still move cities (export a
.nt2backupfile to another device). - The bank can deliver a sealed envelope between branches (optional blind sync as ciphertext only).
But if you lose the key, the bank cannot open the box for you. That is not neglect—it is the design.
NT² Vault is built for people who would rather own that responsibility than outsource it to a logo they hope is trustworthy.
How this connects to Store · Share · Present
The three jobs we describe—store structured secrets locally, share them under your control, present only what a moment requires—all inherit the same rule:
| Job | Null Trust² implication |
|---|---|
| Store | Encryption keys stay in memory while unlocked; auto-lock clears them |
| Share | Share passphrases for links are separate from your master password |
| Present | Redacted views happen on your device; nothing uploads as plaintext for “convenience” |
We are building sharing modes—vault-to-vault, encrypted links, share files, safe presentation—so you can hand data to another person without falling back to chat screenshots. The server, when used, sees ciphertext only.
Still in development—and that is okay to say
NT² Vault is not publicly launched yet. This blog exists so you can understand why we are building it before you are asked to trust it with real mnemonics and bank details.
When we launch, the app will live at se.nt2.me—sent to me, where encrypted handoffs can arrive. Until then:
- Read how we think about privacy on nt2.me/about
- Browse scenario sketches at nt2.me/help/use-cases
- Follow new stories via RSS
Null Trust² is not a tagline we will walk back at launch. It is the constraint every feature has to pass.
Last updated 2026-06-28
Related stories
- Welcome to the NT² Blog
2 min read
- When your landlord asks for ID on WhatsApp
3 min read
- Your seed phrase shouldn't live in Apple Notes
3 min read