Authenticated encryption.
Sensitive finance fields are encrypted with AES-256-GCM before ordinary database storage.
Security and privacy
worthi is manual-first and protects sensitive finance fields with application-level envelope encryption, per-user data keys, and authenticated encryption metadata.
Sensitive finance fields are encrypted with AES-256-GCM before ordinary database storage.
Each user gets a separate data encryption key, and the database stores only a wrapped version of that key.
Account names, asset details, holdings, transaction notes, recurring rules, and history labels are protected fields.
What it helps with
Encryption
worthi uses application-level encryption for fields that can reveal personal financial details. That includes names, notes, labels, asset descriptions, and other sensitive finance records.
Isolation
Server-side access patterns keep user-owned accounts, assets, transactions, holdings, recurring rules, and history tied to the authenticated account.
Manual-first
Because worthi does not require bank-linking credentials, there is less credential exposure from the start. Market and FX lookups use reference symbols and currencies, not bank passwords.
Questions
worthi uses application-level envelope encryption for sensitive finance fields before ordinary database storage. The current implementation uses AES-256-GCM and per-user data keys.
No. worthi is manual-first, so it does not need bank, brokerage, or card login credentials to build a net worth dashboard.
Payments are processed through Stripe Checkout. worthi does not store card details directly.
Encrypted values include authenticated metadata tied to the user, record type, field, and encryption version, which helps detect copied or altered ciphertext.
Start simple