Your data, your jurisdiction

Location is part of privacy

Privacy conversations often focus on encryption, and they should. But location matters too.

If every scan, account number, and recovery note is uploaded by default, your personal life becomes part of a server estate: storage regions, processors, logs, backups, vendors, policies, and legal requests.

That can be acceptable for many apps. It is a heavier ask for the information NT² is meant to hold.

Local-first reduces the question

NT² starts by keeping the vault on your device. Sensitive payloads are encrypted locally. Optional cloud sync, when used, is designed around ciphertext rather than readable content.

For users in places with strong data-protection expectations, such as the EU and Japan, that posture is practical. It does not magically solve every legal question. It does reduce the amount of private life that needs to be processed by someone else's infrastructure.

The best privacy story is often subtraction:

• fewer plaintext copies;
• fewer processors;
• fewer default uploads;
• fewer reasons a server needs to know.

Not fear, just boundaries

This is not a story about one country being safe and another being unsafe. It is not a promise that local storage removes every risk.

It is a product boundary. NT² should not need to know your bank details to help you store them. It should not need to read a passport scan to help you organize it. It should not turn optional sync into a content platform.

Your jurisdiction starts with your device, your password, and your choices. NT² is designed to keep that center of gravity close to you.

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