Last updated 5 November 2026
There are two Mero Paisa products and they handle your information in completely different ways. The Android app keeps your records on your phone and sends them only when you ask Ask Me a question. The web app uses an account and stores your records on a server. This page covers both, separately. Nothing below applies to the other product unless it says so.
In short
Everything you record, and everything the app reads — including SMS and notifications, if you switch those on — stays on your device, with one exception: Ask Me. Asking it a question sends your ledger to our server to be answered, and is described in full under Ask Me below.
Ask Me needs a Mero Paisa account; nothing else in the app does. If you create one, our server holds the email address, first and last name you give, your password (only as a hash, never in a form we could read back), and the Ask Me usage records described below. It is the same account the web app signs in with. We email that address a link to verify it is yours, and again only if you ask for a new link; the account cannot sign in until it is verified.
The app contains no automatic crash reporting, no advertising and no third-party tracking code. Separately from Ask Me, it sends anonymous counts of which features are used, which contain no financial data; see Usage counts. If something fails on our side, you can choose to send an error report. Settings › How to use Mero Paisa opens our guide at meropaisa.app in your own browser; the app sends nothing for it.
These six, and nothing else. Several permissions that the app's libraries would otherwise add — access to your photos, videos, audio and external storage — are explicitly removed from the released app, because it has no use for them.
| Permission | What it is for |
|---|---|
| USE_BIOMETRIC | The optional app lock. |
| USE_FINGERPRINT | The same lock on Android 9 and older. Capped at API 28 so newer devices are never asked for it. |
| READ_SMS | Reading bank transaction alerts, from the senders you link to an account yourself. Not RECEIVE_SMS — nothing wakes the app when a message arrives. |
| POST_NOTIFICATIONS | Delivering the two reminders, if you switch them on, and telling you an Ask Me answer has arrived while you were elsewhere. |
| RECEIVE_BOOT_COMPLETED | Restoring those two reminder alarms after a restart or an app update, which Android otherwise drops. |
| INTERNET | Asking a question with Ask Me, signing in, checking whether your account is on Pro, and sending the usage counts and error reports described below — nothing else. Versions before Ask Me did not declare it at all. |
The app can read your bank's transaction alerts so you do not have to type them in. This is off until you set it up, and setting it up means picking the sender for each account yourself from the list of senders on your phone — only their names are listed, and no message is read to build that list.
eSewa, Khalti, IME Pay and most mobile-banking apps confirm a payment with a push notification and nothing else — there is no SMS to re-read later. So the app can also read notifications, from the apps you link to an account.
The app can post two local reminders: one in the evening, and one on Sunday morning at the start of the budget week. Both are optional and are scheduled by your phone, on your phone. No reminder contains or transmits any of your figures, and nothing about them leaves the device.
Everything you enter — transactions, money sources, savings goals, spending limits, debts and family member tags — is stored in a single database file in the app's private storage on your device. It is never uploaded for storage and we hold no copy of it. The one time it is transmitted at all is when you ask Ask Me a question.
To be precise about what protects it: that file is not separately encrypted by the app. It is protected by Android's app sandbox, which keeps other apps out, and by your device's own encryption. If you want a lock on top of that, switch on the app lock described below.
Any backup or export you create — a .bak backup file or an .xlsx workbook — is written to a location you choose, or handed to the app you choose through your phone's share sheet. Those files are entirely under your control. We never receive them, see them, or know they exist.
Ask Me answers questions about your own finances — how you are tracking against a savings target, where your spending is going. Answering one needs a server, so this is the only part of the app that sends your financial data anywhere.
How many messages, and what we keep. A free account can send Ask Me 3 messages a month and a Pro account 20. Every message counts, a greeting included. For each message our server keeps a usage record against your account: when it was sent, which AI model answered it, how much text went in and out (counted in tokens), and what that is estimated to have cost. We use these records to run the allowance and to see what Ask Me costs to provide, and we can see them, with the account's email address, on an admin page. They are all our server keeps about your messages — not the messages, the answers or your ledger.
What you can do. Not using Ask Me means none of this happens; the rest of the app works with no connection at all. If you would rather not send your notes, clear or edit them before asking — the app sends whatever an entry holds at the time you ask.
To learn which features people use and what to improve, the app counts a short, fixed list of actions: opening the app, finishing setup, adding, editing or deleting an entry (and whether it came from Quick Add, the full form, an SMS or a notification), setting a budget, adding a goal or a money source, switching on automatic entries, making a backup or an Excel export, asking Ask Me a question, and changing the language, the account mode, the Dashboard order or the app lock. It also counts which screens you open.
What is sent. The name of each action or screen and when it happened, a random identifier created when the app was installed, the app's version and its language. If you are signed in, the counts are linked to your account. No amounts, notes, names, money-source names, categories you type or message text are ever sent.
When it is sent. The counts are kept on your phone and sent to the MeroPaisa API at most once a day, when you open the app. They are not shared with anyone else.
Always on. Counting is part of the app and has no setting to turn it off. It never includes your financial data, as described above.
When it is sent. Only when you tap Send report, which the app offers after something fails on our side. Nothing is sent automatically; if you do not tap it, nothing is sent.
What is sent. The app's version, which feature failed, and a reference to the technical error our server recorded — or, if our server never answered, the type of error and its message. No amounts, notes, names or message text are ever sent.
What we do with it. We use it only to find and fix the problem.
If you turn on the app lock, authentication is handled entirely by your device's operating system. The app never sees, stores or transmits your fingerprint, face or PIN — it is only told whether the check passed.
The one place a Google service is involved. The app can ask whether a newer version is available and hand you over to the Play Store to install it. That check runs inside the Play Store app's own process, not ours — Mero Paisa opens no connection of its own for it. Nothing about you or your finances is part of it. If you installed the app some other way, you will never be offered an update this way at all.
The app does not knowingly collect data from children. Nothing in it needs an account except Ask Me. Without one, the most that reaches us is the anonymous usage counts.
The web app is a different product from the Android app and gives you different guarantees. It has accounts, so it necessarily has a server, and what you enter is stored there rather than on your device. It is still being built: signing up and signing in work, but the ledger behind them is not finished.
We do not collect anything else. There is no analytics code, no advertising, no third-party tracker and no third-party cookie on this site.
Exactly two, both strictly necessary to keep you signed in, and both set when you log in:
Both use SameSite=Lax and are deleted when you log out. They last as long as the sign-in the API grants, and at most seven days, after which you are signed out and have to log in again. Your access token is never exposed to the browser: pages call this site, and this site calls the MeroPaisa API on your behalf.
On the MeroPaisa API, which runs on Microsoft Azure App Service with a managed SQL Server database. Microsoft acts as our hosting provider and processes the data on our instructions.
Signing in here does not give you your phone's records, and entering something here does not put it on your phone, even though the same Mero Paisa account signs in to both. The only thing the Android app sends that contains your records is Ask Me, which sends your ledger to be answered and does not store or sync it. The two keep entirely separate records. To move data yourself, use the app's backup and export files.
Delete your account from the Android app (Settings › Delete account, while signed in) or on the web at meropaisa.app/delete-account. We erase your email address, name and password, and nothing that identifies you stays on our server. You are signed out and the account can never be used again. You can sign up again with the same email address whenever you like. Your entries in the app were never sent to us; they stay on your phone until you remove them. If you cannot sign in, email us at nepcoder.me@gmail.com from the address you registered with and we will delete it for you.
If this policy changes, the updated version is posted on this page with a new “last updated” date.
Questions about any of this go to nepcoder.me@gmail.com.