Privacy Policy
Your money data stays on your phone.
AutoHisaab reads bank transaction SMS on your device to build a spending history. It has no server of its own and never uploads your messages or transactions. This policy explains exactly what the app touches, and the few things that do go over the network.
The short version
Your SMS content and transaction history never leave your device. They are parsed and stored locally. The app uses the network only for optional sign-in (Firebase Authentication), ads (Google AdMob), the optional Remove Ads purchase (Google Play Billing) and app updates (Google Play). None of those carry your messages or your spending.
01 Who this policy covers
This policy applies to the AutoHisaab Android application (“the App”), published under the package name com.autohisaab.app and developed by Mustafa Sidhpuri (“we”, “us”). It also covers this website.
02 What the App reads on your device
The App's core function is turning the bank, card, UPI and wallet alerts your phone already receives into a categorised spending record. With your permission it reads SMS messages stored on the device.
- SMS inbox. The App reads message text to detect transaction alerts and extracts the amount, direction (spent or received), merchant, account tail, reference number, balance and date. Messages that are not transaction alerts — personal messages, OTPs, promotions — are not stored.
- Incoming SMS (optional live capture). If you turn on live capture, the App is notified as new messages arrive so transactions are recorded without a manual scan.
This reading and parsing happens entirely on your device. SMS content is never transmitted off the phone, never sent to us, and never shared with any third party, including our advertising partner.
03 What is stored on your device
- Transaction records (amount, category, merchant, date, account tail, reference, balance);
- The original SMS text kept with each transaction as “proof”;
- Manually entered transactions and notes;
- Your category corrections, merchant rules and refund links;
- A log of financial-looking messages the parser skipped;
- App settings, including whether app lock is on and whether ads have been removed.
This data lives only in the App's private storage on your phone. The App can lock itself behind your device's biometric or screen-lock check, but the underlying database is not separately encrypted by the App — your device lock and Android's storage encryption are its main protection.
04 Backups and exports you create
You can export a JSON backup (which includes the original SMS for every transaction) or a CSV file. The App creates the file and hands it to the destination you choose through Android's share sheet or file picker — for example a folder on your phone, a cloud drive, or a messaging app. We never receive a copy. Once exported, the file is governed by wherever you put it, so store it somewhere you trust.
05 Optional account (Firebase Authentication)
An account is optional. “Continue without an account” is a full path and every feature works on it. If you sign up, Google Firebase Authentication processes on our behalf:
- Your email address and password (stored by Firebase as a secure hash, never in plain text);
- A Firebase user ID and basic metadata such as account creation and last sign-in time.
An account provides identity only. Your transactions and SMS are not uploaded to Firebase or anywhere else. See Firebase's privacy information.
06 Advertising (Google AdMob)
The free version of the App shows banner and occasional full-screen ads served by Google AdMob. To serve and measure ads, the Google Mobile Ads SDK collects and sends to Google information such as:
- Your device's advertising ID (which you can reset or delete in Android settings);
- IP address, approximate location derived from it, device model, OS version and language;
- Ad interactions (impressions and taps) and diagnostic data about ad performance.
The ads SDK has no access to your SMS or the App's transaction database, and we never pass any of that data to it. Ads are not targeted using your spending.
Where the law requires consent (for example in the EEA, UK and Switzerland), the App asks through Google's consent form before any ad is requested. To change your choice, clear the App's data in Android settings and the form is shown again (or buy Remove Ads, which stops ad requests entirely). Google's use of this data is described in How Google uses information from apps that use its services.
Buying Remove Ads stops the App from loading ads at all.
07 Purchases (Google Play Billing)
The one-time Remove Ads purchase is processed entirely by Google Play. We never see your card, UPI or other payment details. The App receives a purchase confirmation from Google Play and stores locally that ads are off; Google may restore that purchase when you reinstall. Google's handling is covered by the Google Privacy Policy.
08 App lock and updates
- App lock. If enabled, Android's own biometric or screen-lock prompt is shown when you open the App. Android only tells the App whether the check passed; your fingerprint, face data or PIN never reach the App or us.
- Updates. The App asks Google Play whether a newer version is available so it can offer an in-app update. That check is handled by Google Play.
09 Permissions, and why each is requested
| Permission | Why the App needs it |
|---|---|
READ_SMSRECEIVE_SMS | The App's core purpose: reading transaction alerts, and recording new ones as they arrive if you enable live capture. Requested at runtime; you can decline and still use manual entry. |
USE_BIOMETRIC | Only for the optional app lock. |
INTERNETACCESS_NETWORK_STATE | Sign-in, ads, the Remove Ads purchase and update checks. No SMS or transaction data is sent. |
AD_ID | Added by the Google Mobile Ads SDK to read the advertising ID for ads. |
The App does not request location, contacts, camera, microphone or photo/media permissions.
10 What we do not do
- We do not collect, transmit, sell or share your SMS content or transaction data.
- We do not run a server that stores your financial information.
- We do not use your spending to target ads or build a profile of you.
- We do not include analytics or crash-reporting SDKs.
11 Retention and deletion
On-device data
Your transactions, SMS proofs and settings stay on your device until you delete them in the App, clear the App's data in Android settings, or uninstall the App. We hold no copy, so there is nothing for us to delete.
Account data
If you created an account, its email and authentication record are kept by Firebase until you ask us to delete it. See how to delete your account.
Advertising data
Data collected by AdMob is retained by Google under its own policies. You can reset or delete your advertising ID at any time in Android settings.
12 Children
AutoHisaab is a personal-finance tool for adults managing their own bank accounts. It is not directed to children under 13 (or the minimum age in your country), and we do not knowingly collect information from children.
13 This website
This site is hosted on Vercel, which processes standard server logs (such as IP address and browser type) to deliver and secure the site. The site sets no cookies and runs no analytics or advertising.
14 Changes to this policy
We may update this policy as the App changes. Material changes will be reflected in the “Last updated” date above.
15 Contact
Questions about this policy, or a request about your data: mustafasidhpuri13@gmail.com