Privacy Policy

HisabX (HisabX, we, us) publishes the HisabX mobile app and the website at hisabx.app. This policy covers both of them, and the servers behind them.

It does not cover what somebody else does with information you give them directly. If you follow a link out of HisabX — to an app store, to a bank, to anywhere — that destination's own policy governs from the moment you arrive.

For readers in a jurisdiction that uses the term: for the personal data described here, HisabX is the data controller. Questions go to hisabx.app@gmail.com, and there is a person on the other end of that address.

A debt record names a person and sometimes carries their phone number. That person is not a HisabX user by virtue of being in your ledger. They have not agreed to this policy, and they cannot see or correct what you have written about them.

So enter the least that makes the record useful to you, and treat it the way you would want a record of yourself treated. Where the law where you live places obligations on you for holding somebody else's details, those obligations are yours rather than ours.

We use a name or a number only to draw your own screens and, where you have asked for a reminder about a due date, to write that reminder for you. We do not contact the people in your ledger, and we build no profile of them.

One thing the website does on the first visit deserves naming: our delivery network attaches a country hint to the request, and we read it once to decide whether to show you English or Bangla. It is used for that decision and is not stored, logged against you, or used for anything else.

Diagnostics in a finance app are a genuine hazard, and it is worth being specific about why. The ordinary way to report a crash is to send the error text; the error text from a failed save contains the values the database was given, which for a transaction means the amount and the note. HisabX redacts before reporting, and the rule is tested against a real database error rather than asserted in a document.

Beyond that: HisabX never asks for your location, and nothing in the app or the backend records what country you are in. We ask for no access to your camera, microphone, photos, messages or call history, and we do not read your address book. We are not a bank: we hold no card numbers, no bank credentials and no account numbers beyond the names you choose to give the accounts you track.

We do not sell personal data, and we do not share your financial records with anyone for their own marketing. Nothing you enter is used to choose an advertisement — the ad network never receives it.

Some of what HisabX does happens on our servers rather than on your phone, and it reads your records to do it. About once an hour a scheduled job looks at recent activity in your account to decide whether anything is worth telling you about: a budget heading over, a category unusually far above its own average, a recurring entry falling due, a run of days with nothing logged. Separately, recurring entries you have set up are posted on their due date whether the app is open or not.

None of this makes a decision with a legal or similarly significant effect for you. It produces messages, and only messages.

You can switch off any category of notification in Settings, or all of them at your device level. Switching them off stops the messages. The recurring entries you asked for still post, because posting them is the feature rather than the notification.

HisabX is free, and free accounts see advertising: a card inside some lists, and an occasional short video you may choose to watch. Ads are served by Google AdMob.

Before any ad is requested the app runs a consent flow — Google's consent form where a data-protection law requires one, and on iOS Apple's App Tracking Transparency prompt as well. If you decline, ads still appear but are non-personalised: chosen without an advertising identifier and without a profile.

You can change your answer later. On iOS, in system Settings under Privacy and Security, then Tracking. On Android, by resetting or deleting your advertising id in Google settings. Where a consent form applies, HisabX offers a way to reopen it.

No ad network receives your transactions, balances, budgets, notes, categories or the names of people in your ledger. What Google collects in order to serve an ad is governed by Google's own policies, and we have no access to it.

Every paid plan removes advertising entirely.

Paid plans are sold through the app store you installed from, and managed through RevenueCat, the service that tells the app what your account is entitled to.

We never see your card number, and no payment instrument reaches our servers. What we receive is the outcome: which plan is active, when it renews or expires, and whether a trial has been used. RevenueCat is given an identifier for your HisabX account, so that a purchase follows you to a new phone.

Where a plan is arranged directly with us — a bKash, cash or bank transfer that no app store can see — we record it against your account ourselves, with the same two facts: what it is, and when it ends.

Billing history, cancellation and refunds are handled by whoever took the payment, under their own policy.

Beyond that we disclose personal data only where we must: to comply with a law, a court order or a lawful request from an authority; to enforce our Terms of Service; or to protect the rights, safety or property of a user, a third party or ourselves.

If HisabX is ever sold, merged or acquired, your data may transfer as part of it. You will be told before that happens, and this policy continues to apply until you are told otherwise.

It would read better to claim that nobody at HisabX can reach your data. It would also be untrue. We run an internal console with privileged access to the database, and it exists because somebody has to be able to answer questions like why a subscription did not unlock, or why an account is stuck.

The rules we hold ourselves to: access is limited to named operators, operator actions are recorded, and the console is used for support, billing and operations rather than for browsing. The figures we look at routinely — how many accounts there are, how many are active — are aggregates that never require opening an individual ledger.

If you would rather nobody could ever open yours, the app exports your records in full, and deleting your account removes them from our side entirely.

HisabX is operated from Bangladesh, and the services listed above run in data centres outside it. Using HisabX means your information is transferred to and processed in countries whose data-protection laws may differ from those where you live.

Where the law requires a safeguard for that transfer — in the EEA and the UK in particular — we rely on the standard contractual clauses and transfer arrangements our providers publish.

Export before you delete. Once the account is gone, so is the only copy we hold.

No system is perfectly secure, and a policy that claims otherwise is selling something. If you find a weakness, write to hisabx.app@gmail.com — we would rather hear it from you.

Depending on where you live you may also have rights to a copy of your personal data, to have it corrected or erased, to restrict or object to certain processing, to receive it in a portable form, and to withdraw a consent you have given. Write to hisabx.app@gmail.com and we will act within the time your law allows. We may need to confirm who you are first, and confirming will never ask for more than is necessary to be sure.

If you believe we have handled your data wrongly, we would rather hear it directly. You are also entitled to complain to the data-protection authority where you live.

HisabX is not directed at children. You must be at least 13 to hold an account, and if you are under the age of majority where you live you may use it only with the involvement of a parent or guardian, who must agree to the Terms of Service and authorise any purchase.

We do not knowingly collect personal data from a child under 13. If you believe a child has created an account, write to hisabx.app@gmail.com and we will remove it.

We will update this policy as the product changes. The date at the top says when it last changed, and the version you are reading is the version in force.

Where a change materially affects you — a new recipient of your data, a new purpose, a narrower right — we will say so in the app before it takes effect, rather than only here.