Local encryption
SQLite database encrypted with AES-256-GCM; the key is derived with PBKDF2-SHA256 (600,000 iterations) when you set a vault passphrase.
Security and trust
What has been verified, what has not, and what is up to you.
No telemetry
No analytics or tracking. The only connections are licence activation and, if you enable it, P2P sync.
Encrypted backups
Export a .privybackup file protected by your passphrase. Without a backup or the recovery code, data cannot be recovered.
Limits, plainly
- In the web version the encryption secret lives in browser storage; turn on the vault passphrase if the device is not only yours.
- PrivyFinance does not protect against malware that fully controls your device.
- The native secure store (Keychain, Keystore, keyring) is implemented but has not yet been validated on real devices.
- Security has had an internal audit; there is no independent audit yet.
Optional external services
- Licence activation (once).
- P2P sync through a signalling server (off by default).
- A cloud folder you choose for syncing encrypted files.
- Plugins: off by default, sandboxed in an iframe with explicit permissions.
Good practice
- Turn on your device lock.
- Keep the recovery code somewhere safe, off the device.
- Do not share unencrypted exports.
- Check the Trust centre inside the app.