Offline by default is not offline-only

Two ideas often get blurred

People hear "offline" and assume isolation. They hear "cloud" and assume surrender.

NT² tries to keep those ideas separate. The vault is local-first: create, unlock, search, and store on your device. That is the default posture. You do not need a cloud account just to have a vault.

But a person may still want another device to have the same records. They may want a backup path, a laptop and phone, or a way to keep encrypted replicas updated.

The question is not "cloud or no cloud." The question is: what can the cloud see?

Blind sync keeps the center local

Optional NT² cloud sync is designed around ciphertext, not inspection. The vault encrypts sensitive data before it leaves the device. The server can help move and store encrypted replicas, but it should not read your master password or plaintext assets.

That keeps the product story consistent:

• local vault first;
• cloud sync optional;
• vault identity based on keys, not email;
• server sees encrypted data, not the contents of your life.

This is more limited than a cloud-first app, and that limit is intentional. Convenience should not quietly rewrite the trust model.

The useful middle

Offline by default is not nostalgia. It is a way to keep the user's device at the center.

Offline-only would be too rigid for many people. Cloud-first would be too much trust for the data NT² is meant to hold. The useful middle is a vault that works locally, then syncs only under rules that keep the server blind.

That is the value: the network can help without becoming the place where your secrets truly live.

Read more about NT²'s privacy posture at nt2.me/about, or follow the RSS feed.