Privacy Policy
Last Updated: June 17, 2026
Local Processing
Your financial values, balances, transaction lists, and portfolio logs reside on-device in your SQLite database.
OS-Isolated Biometrics
Biometric checks are handled locally via Android OS secure APIs. Worth never accesses or stores your physical fingerprint.
1. Core Information Principles
Worth is designed as a standalone, offline-first personal financial operating system. Unlike traditional fintech applications, we do not require you to connect your bank accounts to third-party scrapers, nor do we run background analytics on your financial performance.
Your data belongs solely to you. We believe in complete transparency and maximum local data containment.
2. Collected Data & Permissions
- Financial Assets & Transactions: All asset balances, outstanding liabilities, investment values, receivable timelines, expected streams, and goals you enter are stored inside an encrypted local Drift (SQLite) database cache. This data is never transmitted to us or any third-party marketing companies.
- Biometric Authentications:The app requests permission to use your device's Biometric sensors (Fingerprint / Face Unlock). This authentication is managed directly by the Android operating system. Worth does not have access to, nor does it log, your actual biometric identifiers.
- Device State permissions: We query basic local storage directories to save local SQLite backups if you choose to trigger database exports.
3. Optional Firestore Synchronization
Worth provides an optional cloud sync module allowing you to backup database snapshots. If you choose to enable cloud backup, the app connects directly to your private Google Firestore container.
This sync pipeline uses secure, authenticated HTTPS channels. We do not host, store, or monitor these Firestore documents; they reside entirely within your own Firebase environment.
4. Security Measures
Worth uses cryptographic key wrapping to verify app access PIN codes and security states. We recommend keeping your Android device updated, enabling device-level encryption, and disabling developer debugging interfaces to maximize local SQLite file security.
5. Privacy Updates
We may modify this privacy protocol from time to time as features develop. Any updates will be pushed to the GitHub repository and reflected on this website. Continued use of the application constitutes acceptance of these local storage policies.