PopaDex Encryption: Scope, Limits and Recovery
Understand PopaDex’s optional client-side vault, the difference from ordinary online storage, and what to check before enabling encryption or sharing data.
The important distinction
PopaDex includes an optional client-side encrypted vault. Do not assume that every PopaDex account, field or bank integration is end-to-end encrypted. An account without an initialized vault can use server-processed financial data.
HTTPS protects data in transit. That is different from client-side encryption, and neither makes a complete guarantee about every possible security incident.
What the implementation establishes
The application has separate handling for accounts with an active vault. For example, the account model distinguishes numeric balances from encrypted balance values. The sharing model also includes wrapped-key and encrypted-field handling.
That source-code evidence is narrower than a claim that all financial information is inaccessible to PopaDex. Account metadata, bank-provider processing, operational services and unencrypted workflows have different data requirements. A feature’s presence in code is not an independent audit of every route or of a customer’s current configuration.
This page therefore does not promise:
- Zero-knowledge processing across every account and integration.
- That all account names, transactions, goals, notes or projections are encrypted client-side.
- That a server breach could reveal only harmless information.
- Identical encryption behavior across every browser, native storefront and connection provider.
- A particular certification or an independent cryptographic audit.
Before enabling a vault
Check the security settings and instructions shown in your account. Confirm which data the current workflow covers, how recovery works, and how bank connections and sharing interact with the vault.
Keep a secure, readable backup of the recovery material the app provides. Test that you can locate it before relying on it. Do not email a recovery key, password or full financial export to support.
If both the credentials and the recovery material needed to decrypt covered data are lost, access may be unrecoverable. A password reset and recovery of encrypted financial data are different operations. Do not disable encryption, reset keys or delete data to troubleshoot without understanding the consequences.
Manual tracking and bank connections
You can use the free manual tracker without connecting a bank. This reduces the number of integrations you use, but the tracker remains an online service. Use an offline Excel file if keeping a local-only financial record is the requirement.
Before authorizing a bank connection, review the provider, requested permissions and available revocation controls. Supported connections are intended for reading financial information, not moving money; verify the actual consent screen for your institution.
Sharing with a partner
Use separate logins and share only the accounts you intend to disclose. The implementation distinguishes view-only and full-access permissions. Confirm the recipient’s experience with a test record before sharing a complete portfolio.
A shared account does not automatically resolve duplicate real-world assets, partial ownership or all encrypted recovery scenarios. See the household checking workflow.
Questions about your account
Contact [email protected] with the feature you are using and the issue you see, without including passwords, recovery keys or sensitive balances. Read the privacy policy for the service’s data-processing terms.
Scope reviewed on 8 September 2026 against the application’s account and shared-account models and public product behavior. This is a product documentation review, not an independent security certification.