2 min read By NT²
Three Stripe keys, three environments
The note says API stuff. Inside are three Stripe keys, two webhook secrets, an old test token, and no one remembers which one is safe to paste.
Product narratives about structured privacy, local-first vaulting, and encrypted handoffs.
2 min read By NT²
The note says API stuff. Inside are three Stripe keys, two webhook secrets, an old test token, and no one remembers which one is safe to paste.
2 min read By NT²
You are outside the consulate, the appointment is in twelve minutes, and the confirmation email will not load.
2 min read By NT²
Website logins already have good tools. The harder question is where to keep the secrets that are not just username, password, and URL.
2 min read By NT²
The notebook sits in the kitchen drawer. Everyone knows it matters. Nobody is sure whether the bank password on page seven is still current.
2 min read By NT²
The file started as a budget. Then someone added insurance details, bank accounts, passport numbers, and a few passwords. Now the most sensitive document in the house is called Family.xlsx.
7 min read By NT²
Self-sovereign identity sounds abstract. In NT², the practical version is simpler: your vault can prove itself, recover without a help desk, and share under your control while NT² stays blind.
2 min read By NT²
A short changelog for early followers. NT² Vault is still pre-launch—this note covers what we shipped recently, not the full product map.
3 min read By NT²
The contractor needed the Stripe key before deploy. You pasted it in #engineering. The key is rotated now—and the thread is still searchable forever.
3 min read By NT²
Front and back of your ID in WhatsApp or LINE is fast for the landlord—and a permanent copy in a chat log you do not control.
3 min read By NT²
The broker wanted employer name and the last four digits of your account. You emailed a twelve-page PDF. That is oversharing dressed as diligence.