Product narratives about structured privacy, local-first vaulting, and encrypted handoffs.
4 min read By NT²
Tech
A proximity session has a budget. Contact invites and share manifests fit. PDF scans usually do not—so attachments leave on a bulk plane after SDP exchange, not stuffed into every control frame.
4 min read By NT²
Tech
If a proximity bootstrap can live in an ordinary https link, the authenticator has already toured browser history, referrers, and OS camera → URL launch paths.
5 min read By NT²
Tech
Connecting beside someone is a short-lived session. Recognizing them as a vault contact—and accepting a share into your vault—are still separate acts.
5 min read By NT²
Tech
Ciphertext and the secret that opens it should not travel as one convenient email. NT² splits carriers—file or link—from OOB passphrase delivery, and treats Strong as machine-handoff.
5 min read By NT²
Tech
Estate and emergency access tempt products to hold a second key “just in case.” NT² refuses that oracle. Legacy is a sealed package on a delay—not a support console unlock.
5 min read By NT²
Tech
After a share leaves your vault, “did they open it?” and “can I kill it?” are sender questions. The answers live in a local outbox—not a cloud mailbox of readable mail.
6 min read By NT²
Tech
Sharing to “someone in Contacts” only works if the row holds encryption material for that vault—not a phone number you hope matches the right person.
5 min read By NT²
Tech
If “form fields,” “share fields,” and “expiry fields” are three schemas, they will drift—and someone will see more than you meant. One active field set keeps every surface honest.
3 min read By NT²
Stories
The help page names four people. Each one stands for a habit NT² is built to replace—not a marketing mascot.
4 min read By NT²
Tech
A vault that cannot find a title is unusable. A vault that full-text indexes every password on a server is not a vault. The boundary is projected metadata versus sealed field values.
