1 min read By NT²
Timed reveal on a video call
Stories
The person on the call needs to confirm one field. Your screen is ready to show an entire document.
Product narratives about structured privacy, local-first vaulting, and encrypted handoffs.
1 min read By NT²
Stories
The person on the call needs to confirm one field. Your screen is ready to show an entire document.
9 min read By NT²
Tech
A vault does not need to enter a shared plaintext mailbox to sync. Its public cryptographic identity can name a dedicated edge coordinator that notifies replicas and points them to encrypted frames it cannot open.
1 min read By NT²
Stories
The vault app lives at se.nt2.me: sent to me. The phrase is playful, but the product idea is not.
9 min read By NT²
Tech
“Contact support to reset your password” sounds reassuring. For an encrypted vault, it also reveals who ultimately controls access. NT² chooses a harder promise: recovery material stays with you, not our help desk.
1 min read By NT²
Stories
Most sharing stories focus on the sender. The recipient has a quieter problem: should I trust this file, and where should it go if I do?
9 min read By NT²
Tech
Sync does not have to turn a local vault into a cloud database. The edge can identify an account, store opaque replica frames, and deliver updates without learning what those updates contain.
1 min read By NT²
Stories
If the file is too sensitive for a chat thread, sending it through one more inbox is not automatically better.
9 min read By NT²
Tech
SQLite wants a file. A privacy vault wants durable relational storage that stays fast as its item count, indexes, and encrypted attachments grow. Putting a SQLite virtual file system on IndexedDB can bridge those worlds, but it makes the bridge part of every database operation. For NT² Vault, the browser vault file belongs in the Origin Private File System.
2 min read By NT²
Stories
Your accountant needs the statement today. They do not need a permanent copy sitting in three inboxes and a downloads folder.
9 min read By NT²
Tech
One screen can make two security events look like a single login. We keep them separate because opening encrypted data and proving an identity to a server are different jobs with different risks.