Security Architecture.
Privacy isn't a feature we bolt on — it's the foundation. Here is exactly how Expense Lite protects your financial data.
Local SQLite Storage
Transactions are stored in a local SQLite database on your device.
App Sandbox Isolation
The database lives inside the Android app sandbox, isolated from other apps.
PIN & Biometric Lock
Add an optional PIN or biometric lock for an extra layer of protection.
Offline-First
No default cloud dependency. The app works fully offline.
Zero-Knowledge
Your records are never visible to Planck Studio or processed remotely.
You Control Backups
Backups are created and stored only when and where you choose.
Local SQLite Storage
Every transaction you enter is stored inside a local SQLite database on your device. There is no default cloud dependency and no central transaction server — which is why the app is fast offline and your records never leave your phone unless you choose to back them up.
App Sandbox Isolation
On Android, each app runs in its own sandbox. Expense Lite's database is isolated within the app's private storage, so other apps cannot read it. This is a core part of the platform's security model.
App Lock: PIN & Biometrics
For an extra layer of protection on shared or lost devices, you can enable a PIN or biometric (fingerprint/face) lock so the app can't be opened without authentication.
Offline-First by Design
Expense Lite is designed around local-first financial management. There is no mandatory account creation, no transaction scraping, and no financial profiling. Your spending history is never processed on company servers.
Zero-Knowledge Principles
Because there are no central servers handling your transactions, your financial records are never visible to Planck Studio. We don't analyze your spending, and we never sell your financial information.