Terms Of Use
Conduct rules for your account, along with how we pause or close it, written to sit beside the data clauses on this page without contradicting them.
Open an account with habesha bet and you share a small set of details with us — your name, your contact number, your date of birth and the...
This Privacy Policy covers accounts opened from Pakistan and other supported regions, and it applies where local law permits us to serve you. We hold your account data; the payment services you already use — JazzCash, Easypaisa, SadaPay, NayaPay and Raast — move your money under their own terms. Device signals, transaction trails and identity records stay with us as long as
tax, audit and dispute work requires. You can browse parts of our lobby before you register, but the moment you open an account we begin keeping the records needed to run it. Where a provincial rule is stricter than ours, the stricter reading applies to your account.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
If a question about your own data comes up, you should not have to hunt for a form. Write to our policy desk from the email tied to your account and a person replies, usually inside one working day. Chat and in-account help run alongside it, and both stay open through the week.
Email the address on your account and we log the request the same day, then send back a reference number you can quote in any later message to us.
Open the help tab inside your account to raise a data question, ask which records we hold on your profile, or request a change of contact details.
Copies, corrections and account closures go to our data team, and we confirm each step in writing, normally with a reply inside seven working days.
We write these pages the way we would want them written for us. Every clause names the thing it talks about, a version stamp sits at the head of the page, and...
Sentences stay short and legal padding is left out, so you can read a clause once and understand what it means for the account you hold with us.
Each update carries a date at the head of the page, letting you compare the wording you agreed to with the wording in force on the day you read it.
A small data team owns this text, and our contact address is published on the page rather than buried in a general corporate mailbox that nobody checks.
Anything about sharing, retention or account closure appears here in full, instead of pointing you across to a separate contract written for a different audience.
Examples use the rails you pay with in Pakistan, so a line about JazzCash or Easypaisa means something concrete rather than an abstract reference.
We refresh the text whenever our systems change and mark which paragraphs moved, so readers who come back regularly can spot the difference quickly.
This Privacy Policy is one of a small family of pages, and they should never contradict one another. The terms page covers account conduct, the cookie notice explains browser storage, the payments...
Conduct rules for your account, along with how we pause or close it, written to sit beside the data clauses on this page without contradicting them.
Browser storage explained in the same plain voice, covering session cookies, saved preferences and the switches you can turn off whenever you like from your account.
Covers JazzCash, Easypaisa, SadaPay, NayaPay and Raast flows in detail, while this policy stays with the records those flows create on our side.
Sign-in protection, device checks and password resets, with the data we log for each event described in the same terms used on this page.
Where you raise a complaint and how long a reply takes, kept consistent with the response times printed here for policy contact requests.
English serves Pakistan by default, and any translated copy is aligned line by line with the version published here on our own site.
Older versions of this text are kept on file, so you can ask for the wording that applied when you first opened your account with us.
The layout of this page is deliberate. Headings deal with one subject each, related promises sit in grouped cards, and our payment names appear where they belong instead...