No account, no email, no telemetry. Everything you write is sealed with a master key that never leaves your devices in a readable form. Here is exactly how that key is made, protected and recovered.
The database sits under iOS Data Protection — AES-encrypted by a class key tied to your passcode and the Secure Enclave. Unreadable while the phone is locked.
Nisshi has its own lock: Face ID, Touch ID or your password. Auto-lock re-seals it after it sits in the background — immediately, or after 1, 5 or 15 minutes.
With sync on, entries are encrypted end to end before upload. Your server stores ciphertext keyed by a random account id and never holds the key.
| They have | They can read | Why |
|---|---|---|
| Your locked iPhone | Nothing | Data Protection keeps the file sealed until the passcode is entered. |
| Your sync server | Nothing | It stores ciphertext and random ids. The key never reaches it. |
| An encrypted backup file | Nothing | Restoring it asks for the password that protected it. |
| Us, the makers of Nisshi | Nothing | There's no Nisshi server, no account and no analytics. Nothing reaches us. |
| Your 24 recovery words | Everything | The phrase re-derives your master key. Keep it offline and private. |
A few settings loosen a lock on purpose. Each one is off or explicit until you choose it.