Privacy policy
Last updated 12 October 2026
Hisaabo is a money diary made by Workaholic Developers (“we”). It is built so that your money stays with you: messages, statements and fund statements are read on your phone, and nothing leaves it unless you turn on encrypted sync or a family book. We follow India's Digital Personal Data Protection Act, 2023.
The short version
- No account, no email, no phone number, no name needed.
- No ads, no analytics, no trackers, no crash-reporting SDKs, no loan or credit offers. We never sell or share data.
- The text of an SMS is never stored and never sent. Hisaabo keeps only the payment details listed below.
- Sync and family books are optional and end-to-end encrypted: our server stores sealed bytes it cannot read.
What Hisaabo reads from a bank SMS
On Android, with your permission, Hisaabo reads SMS from banks, card issuers, UPI apps and wallets. On iPhone, a Shortcuts automation you set up passes each matching message to Hisaabo. Messages that are not about money (OTPs, offers, personal messages) are skipped. From a payment message Hisaabo keeps only these fields, on your phone:
| Field | What it is | Example (made up) |
|---|---|---|
| Amount | How much went out or came in. | ₹1,240.00 |
| Debit or credit | Whether money left or arrived. | debited |
| Account or card ending | Only the last four digits, stored as XX plus those digits. | XX1234 |
| Account type | Bank account, credit card, debit card or wallet. | credit card |
| Payee or payer name | Who was paid or who paid you, as the bank wrote it. | KESAR SWEETS |
| UPI ID | The UPI address in a UPI message. | shop@bank |
| Payment mode | UPI, card, net banking, ATM, NEFT/IMPS/RTGS, auto-debit or cheque. | UPI |
| Reference number | The bank’s reference, used only to spot the same payment twice. | 428109375011 |
| Available balance or limit | The balance or card limit after the payment. | Avl Bal ₹40,310 |
| Date and time | When it happened. | 11-10-26, 9:14 pm |
| Bank | Which bank’s message format matched (from the sender header). | the bank’s name |
| Card statement totals | Total due, minimum due and due date in card statement messages. | ₹18,240 by 5 Nov |
It also keeps the sender header (like AD-BANKNM) for 30 days to tell banks apart. When a bank's message can't be read yet, Hisaabo keeps its wording with every number, amount, name and code replaced by placeholders, so you can “teach” it once; this is deleted after 30 days. Never kept: the message text, OTPs, contacts, phone numbers or any other message.
Statements and fund statements
Bank and card statements (PDF, CSV, Excel) and the mutual-fund CAS are opened on your phone, password included, and only the rows are kept: date, description, amount, balance, and for funds the folio, scheme, ISIN, units and transactions. Your name, address, PAN, email and phone number in these files are not kept. The file itself is deleted after import.
What stays on your phone
Your diary (entries, accounts, budgets, categories and the rules you teach) lives in the app's private storage, protected by the phone's encryption (on iPhone it can't be read while the phone is locked). Hisaabo downloads the public daily NAV file from AMFI to value your funds; that request carries no information about you.
Encrypted sync (optional)
If you turn on sync, your phone creates a random key and shows you a recovery key. Changes are sealed on the phone with AES-256-GCM before they leave. Our server (hisaabo.wdlab.app, in our data centre) stores: a random device identifier and its public key; a lookup code and a hash of a proof derived from your recovery key; your vault key sealed with a key we never see; and the sealed change blobs with their size and time. We cannot read amounts, names, merchants or anything else in them. A new phone needs your recovery key; we cannot recover it for you.
Family books (optional)
A family book is shared with people you invite with a code. Each member chooses which accounts go in; their entries (date, amount, direction, category, merchant and the account's nickname) are sealed with the book's key, which only members' phones have. The server knows which devices are in a book and stores the sealed entries, sealed key copies and the sealed name of someone asking to join. Removing someone moves the book to a new key they never get.
Logs and how long we keep things
Our web server keeps no access logs. The sync service keeps error logs (never request contents) for at most 14 days. Invite codes expire after 7 days; unanswered join requests are deleted after 14 days. If a phone doesn't connect for 24 months, its sync account and anything only it could reach are deleted.
Your choices and rights
- Turn SMS reading off in Android settings at any time; import statements instead.
- Export everything as CSV, or as an encrypted
.hisaabobackup file, from Settings. - Delete everything on the phone from Settings → Delete everything.
- Delete your sync account (and, if you choose, the synced copy) from Settings → Sync and backup → Delete my sync account. This happens immediately on our server.
- For questions, corrections or a grievance under the DPDP Act, write to info@workaholicdevelopers.com. We reply within 7 days.
Children
Hisaabo is meant for adults managing their own money. We don't knowingly collect anything from children.
Changes
If this policy changes, we update this page and the date above, and the app shows a note on the next open.