Understanding your money shouldn't mean handing it over
BachatPe is built on a single constraint that shaped every other decision in the app: your financial data never leaves your phone.
One constraint, everything else follows
Almost every expense app solves the tracking problem the same way: send your transactions to a server, process them there, and send the results back. It works โ but it means the most sensitive record you own, a complete history of what you buy and when, lives somewhere you don't control.
BachatPe starts from the opposite end. The app requests no internet permission at all. That one decision rules out cloud sync, ad networks, analytics pipelines and data brokers in a single stroke โ not as a policy you're asked to trust, but as something the app is structurally incapable of doing.
Everything else in BachatPe is designed to work within that constraint: parsing happens on-device, budgets are computed on-device, and even household sharing runs phone-to-phone rather than through a server.
Four principles we design against
When a feature request conflicts with one of these, the feature changes โ not the principle.
Privacy is architecture, not a setting
No internet permission, no account, no login, no analytics. There is no server to leak, because there is no server.
The app should do the work
If your bank already sent you an SMS about a spend, you shouldn't have to type it in again. Manual entry exists โ it just shouldn't be the default.
Clarity over dashboards
Most people want one answer: am I okay this month? On Track, Watch or Over โ plus what's safe to spend โ beats a wall of charts.
Built for India, not localised for it
INR, UPI, Indian bank SMS formats, Indian merchants, and the Indian money calendar of insurance, EMIs, school fees and tax.
What the app reads โ and what it ignores
When you grant SMS permission, BachatPe scans the messages already on your phone for completed transaction alerts: debits, credits and UPI notifications. It identifies the amount, the merchant and the category, and files the expense โ all locally.
Everything else is deliberately skipped. OTPs, personal messages, promotional SMS and failed-payment notices are never used. The permission exists for exactly one job, and the app cannot transmit what it reads even if it wanted to.
Prefer not to grant it at all? BachatPe is fully usable with manual entry, and nothing about budgets, planning, family sharing or insights depends on SMS access.
- Reads completed transaction SMS only โ never OTPs
- Parsing, categorising and budgeting all happen on-device
- Does not send SMS, transfer money, or access your bank account
- Fully functional with SMS permission denied
Made for ordinary Indian households
Not just the financially savvy โ students, homemakers, gig workers, small-business owners and salaried families alike.
"Where did my salary go?"
If the month ends before the money does and you can't quite explain why, automatic tracking answers that in a week.
Households sharing expenses
Families who want a shared picture of spending without creating accounts or putting it all on somebody's server.
Anyone mixing work and personal
Freelancers and shop owners who need business spends kept separate from the household budget.
Things BachatPe will never do
- โ Upload your spending data to a server
- โ Require an account, email or phone number
- โ Sell, share or broker your data
- โ Read your OTPs or send SMS on your behalf
- โ Connect to your bank account or move money
- โ Show advertising
Bachat