Last updated: 19 September 2026
Applies to: ExpenseTracker for Android, version 1.0.5 and later
ExpenseTracker does not collect, transmit, or share any of your data. It has no user accounts, no servers, no analytics, and no advertising. Everything the app reads and everything it produces stays in the app's private storage on your phone, unless you deliberately export it yourself.
This is enforced by the way the app is built, not only by policy: the app does
not declare the Android INTERNET permission, so it is technically incapable of
making a network connection.
ExpenseTracker requests two sensitive permissions: READ_SMS, and RECORD_AUDIO
for the optional voice entry described below.
The app reads messages from your device's SMS inbox in order to recognise transaction alerts from banks and card issuers and turn them into a spending record. This is the app's only function; without this permission it has nothing to show.
Messages are examined on your device. A message is only considered if it looks like a financial transaction alert, and messages from senders you have muted on the Senders screen are skipped entirely. Ordinary personal messages are not turned into ledger entries.
The app also requests POST_NOTIFICATIONS, a normal (non-sensitive)
permission, and only when you set your first category budget. It is used to show
you an alert when your own spending crosses your own budget threshold. Nothing is
sent anywhere.
Because the app schedules a periodic background scan of the inbox, the Android
build system merges four additional normal permissions into the app —
RECEIVE_BOOT_COMPLETED, WAKE_LOCK, FOREGROUND_SERVICE and
ACCESS_NETWORK_STATE. These are used solely to let that scheduled on-device
scan run reliably; the last only lets the scheduler read whether the phone is
online, and gives no ability to connect. They grant no access to your data and
no ability to communicate off the device.
On Android 12 and later, on phones that have an on-device speech engine, you
can add a transaction by saying it — for example "paid 500 to Ramesh". The app
asks for the microphone (RECORD_AUDIO) the first time you tap the mic, and
uses it only while the listening sheet is open.
Your speech is recognised by your phone's own on-device speech engine. The app uses only Android's on-device recognizer, which works without a network and refuses rather than falling back to an online service; the app never uses the system voice popup or any other recognizer that may send audio to a server. On phones without an on-device engine the mic is simply not shown.
If your phone's speech engine supports a language but has not downloaded it yet, the app offers a Download button. That asks your phone's speech engine to fetch the language from Google; it is a download of Google's language data and sends none of your speech, text or transactions.
The audio is not recorded or stored by the app. The recognised words fill in the add form, and if you save the transaction they are kept with it as its original text, in the same way a pasted message is.
Transactions recognised from your messages are stored in a SQLite database in the app's private internal storage, which no other app on your device can read.
For each stored transaction the app keeps the verbatim text of the SMS it came
from, in a database column named raw_body. It is kept because the app needs
to be able to re-read the original message when its parsing rules improve, and to
recognise that a message it sees again is the same message it has already
recorded. This text is never transmitted anywhere.
A transaction you add by voice keeps the words you said in the same column; a transaction you paste keeps the pasted text. Neither is transmitted anywhere.