Privacy Policy
Last Updated: June 26, 2026
WhereCash is designed from the ground up to protect your personal capital records. We believe your financial data should belong to you—and only you. Because WhereCash operates on a 100% offline-first model, we do not collect, transmit, share, or store any of your personal information or transaction data.
Local-Only Security Loop Visualization
Your Inputs
Expenses, budgets, loans, and CSV ledger file imports.
Local Device
Saved securely on your device using a local SQL/IndexedDB sandbox.
Secure Local Storage
Your ledger database is 100% client-side. Zero external data synchronization.
0% Server Egress
No external API connections, trackers, web hooks, or third-party loggers.
1. Information We Do Not Collect
Because WhereCash is designed with local-first parameters, we never ask for, collect, scrape, or transmit personal data. This includes but is not limited to:
- Identity details: Names, email addresses, phone numbers, or account logins.
- Financial coordinates: Bank account numbers, routing links, credentials, or credit/debit card numbers.
- Transactional records: Expense logs, category allocations, ledger balances, or personal loan contracts.
2. Device-Native Storage Mechanics
Any transactional input, custom budget, spreadsheet import, or amortization profile is processed and stored locally on your device (within local sandboxed data partitions, such as IndexedDB, localStorage, or WebSQL).
No remote cloud configurations or sync engines exist in our software architecture. If you delete WhereCash or clear its application storage cache through your device settings, your financial history will be permanently deleted and cannot be recovered by us. You are solely responsible for executing manual data exports (CSV backups) to safeguard your data.
3. Zero Third-Party Telemetry & Analytics
We refuse to monetize your attention or track your habits. We do not integrate third-party advertising networks, telemetry engines, or behavior analytics trackers. Your usage metrics, scroll telemetry, and feature engagement profiles remain fully private and system-native on your physical device.
4. Local Device Permissions
WhereCash may request system permission for alerts (such as EMI payment reminders). These alerts are scheduled and triggered entirely within your local device operating system background engine. No external push messaging servers are contacted to coordinate alerts.
5. Policy Modifications
We may update this Privacy Policy to reflect security standards. Because we do not compile accounts or collect contact info, we cannot notify users of amendments individually. We encourage you to review this page periodically to verify security structures.
6. Contacting Us
If you have questions about the local-first application environment or the design system of WhereCash, please contact our support team at support@honlor.com.