Escape hatch, not lock-in

Lock-in is a trust smell

Many apps make import easy and export vague. That is especially dangerous for a vault.

If you store bank details, identity documents, seed phrases, and credentials, the product becomes part of your life infrastructure. You should not have to keep paying or keep syncing just to hold a copy of your own encrypted records.

NT² treats an escape hatch as a core feature, not a compliance checkbox.

The backup belongs to the user

A .nt2backup file is an encrypted vault snapshot you can keep, move, and restore from. It is not the same thing as giving NT² your plaintext. It is not a cloud-only recovery promise. It is a file in your hands.

That matters for ordinary reasons:

• moving to a new device;
• keeping an offline disaster-recovery copy;
• choosing not to enable cloud sync;
• preserving access if a service changes direction.

The point is not that everyone should manage files forever. The point is that ownership should remain possible.

Cloud optional means export real

Local-first only has meaning if the user can carry data out of the local system. Zero-knowledge only has meaning if recovery does not secretly depend on the provider holding a master key.

NT²'s backup posture ties those ideas together. The vault can work on device. Optional sync can help across devices. Export gives you a path that does not require the cloud to be the source of truth.

That is what an escape hatch should feel like: not a panic button, but a normal part of responsible ownership.

Learn more in the guides at nt2.me/guides, or follow the RSS feed.