Live / Mobile
e222 hp publishes its legal terms in one place so you know the rules that apply to your account before you fund it. Everything below — eligibility, the transaction records your wallet keeps, the cookies this site sets and the support route you use when a clause needs explaining — belongs to this page.
Our terms are written for one market, Bangladesh, and they apply where the law in your area lets you hold an account with us. Nothing on this page overrides the rules that apply where you live: if local law or an eligible-region restriction means you cannot open an account, these terms do not bind you either. That is why we ask you to check your own position before you deposit anything. Practically, the notice below deals with four things. Access comes first — who may register, what you confirm when you do, and why a wallet check can be requested on a Nagad, Upay or Bank Transfer deposit. Records come second: what a transaction entry shows, how long we hold it, and how you read it from your account. Conduct is third: what belongs inside our lobby and what does not. Changes are fourth: how a revised version is published and where you find it. We have kept the wording plain rather than legal shorthand, so you can read the whole thing on a phone in one sitting. Payment names appear here only as the context they are — rails your money may travel on, not a promise about timing. Where a rule depends on your own jurisdiction, we say so instead of implying that one answer fits every country.
This policy reaches everything tied to the account you hold with us, and it stops where someone else's terms begin. So the boundary matters. We cover how you register and sign in, what your wallet shows after a Nagad, Upay or Bank Transfer movement, the titles we publish in the lobby — Cricket GoalBet, Aviator Sky Run and Teen Patti Puzzle among them — and the cricket-led sportsbook categories we carry. We do not cover your mobile operator's data charges, the browser or handset you reach us on, or the internal terms of a payment provider itself. Four boundaries are worth naming plainly. Account access is ours. Transactions are shared: we keep the record, the provider moves the money. Site content is ours, including how we describe a game. Third-party services sit outside this page entirely. If a question crosses one of those lines, tell us and we will point you at the right party.
Registration, sign-in, and the details you confirm when you open an account with us all sit inside this policy. So does the wallet verification we may ask for before a Nagad, Upay or Bank Transfer movement settles. If your access is blocked because of where you live, that decision is covered here too.
We keep the record; the provider moves the money. That split is the useful thing to understand. Your deposit or withdrawal appears on your account with the rail it travelled on, and we hold that entry for the retention period our terms state. Timing belongs to the provider's own system.
Everything we publish belongs to this policy: how a title is described, which studios supply games, and how categories are grouped in the lobby. Cricket GoalBet, Live Poker Pro and Aviator Sky Run are ours to present. The cricket-led sportsbook sits here as well, alongside slots and live tables.
These sit outside this page: your mobile operator's data charges, the browser you use to reach us, and the internal rules of Nagad, Upay or your bank. Those parties govern them, and this policy does not claim otherwise. Ask them directly when the question is theirs, and ask us when it is ours.
Your side of this policy is not passive. You can look at your own records at any time, correct a detail that no longer matches your wallet, and ask us a direct question when a clause reads oddly. Start from your account page: the transaction history sits there, with each deposit and withdrawal listed next to the rail it came through, whether that was Nagad, Upay or Bank Transfer. If your phone number changes or a name spelling is off, update it before your next movement so the record stays accurate. If something looks wrong — a record you do not recognise, a title that will not load on your handset — raise it with our support route rather than waiting. And if you want to know why a rule exists, ask. We would rather explain a paragraph than have you guess at it.
Open your account and read the transaction list without asking anyone. Each movement sits beside the rail it came through — Nagad, Upay or Bank Transfer — and the date it was recorded. Reading your own history is the quickest way to catch something that does not match your memory of it.
When your phone number changes or a name spelling is off, fix it before your next movement rather than after. A wrong detail on a wallet reference is harder to untangle once money has moved. Update the field, then check the next record to confirm it carried through.
A policy paragraph is rarely obvious on a first read, so ask. Send your question through the contact route published on this site and name the paragraph you mean. We can explain what a rule does and why it exists far quicker than you can guess at it.
Anything tied to your own account — a record you do not recognise, a title that will not load on your handset — goes through the support link inside your signed-in area. That route opens against your account, so the team can see the same entry you are looking at.
When a clause does not answer your question, ask us rather than guessing at it. We keep the routes short: the support link inside your signed-in account area is the one to use for anything tied to your own record, because it opens against your account rather than a blank form. For a general question about these terms — what a paragraph means, how a change was published — the contact route on this site reaches the same team. Come with the detail that lets us trace the issue: the date of the movement, the rail it came through, and the reference shown on your record if you have one. A vague message costs you a round trip. Nothing here promises a response window or an operating schedule, and we would rather tell you that plainly than publish a number we cannot hold to. If your question is about a payment provider's own process, we will point you to that provider while we check our side of the record.
Use this for anything about your own account: a movement you want traced, wallet verification you were asked to complete, or a game that fails on your device. The link sits inside the account area, so it opens against your record instead of a blank form.
General questions about these terms — what a paragraph means, when a revision was published, how a rule applies where you live — reach the same team through the contact route published on our site. Bring the clause you are asking about so we answer the right one.
Your message moves faster with the right detail: the date of the movement, the rail it came through, the reference on your record, and the device or browser you were using. We publish no response window here, because we would rather not promise a number we cannot keep.
This page is where we explain how account and policy data is handled, and the answer is deliberately narrow. We collect what an account needs — the details you give at registration, the wallet or bank reference attached to a movement, and the session data that keeps you signed in on your handset. Cookies do the small jobs: holding a session open, remembering a preference, and telling us which page you arrived from. We do not sell that data or hand it to anyone unrelated to running your account. Retention follows the record itself: transaction entries are held for the period our terms state, because a deposit you query later still needs to be traceable. Security sits with your side too — a password you do not reuse, a device you control, and no shared login. If you want to know what we hold, or you want a correction where the law in your area allows it, write to us through the contact route published on this site.
Registration details, the wallet or bank reference attached to a movement, and the session data that keeps you signed in. That is the working set. We do not pass it to anyone outside the running of your account, and we do not sell it on.
Cookies do small jobs here: holding a session open, remembering a setting, and showing us which page you arrived from. They are not there to build a profile you did not ask for. You can clear or block them in your browser, though parts of the site will then behave differently.
Transaction entries stay for the period our terms state, because a movement you query later still has to be traceable. Other account details are held while your account is open and handled after it closes as the notice describes. Ask us and we will say where that paragraph sits.
A password you do not reuse, a handset only you unlock, and a habit of signing out on shared devices do more for your account than any single setting we can switch on. If you think someone else has reached your login, tell us and change the password first.
These are the questions that reach our team most often about the terms on this page. Read the answer that fits yours, then open the clause itself if you want the wording behind it. Where an answer depends on where you live, we say so — eligibility follows your local law and the regions we can serve, and nobody at our desk can override that. For anything specific to your own record — a movement, a wallet check, a detail that needs correcting — use the support link inside your signed-in account area so we can look at the same entry you are reading. The contact route on this site handles everything else about the policy text itself. Ask once, plainly, and name the paragraph you mean; you will get a shorter and clearer answer than if you leave us to guess at it.
They apply where the law in your area lets you hold an account with us. That depends on your local rules and on eligible regions, so check your own position first. If a restriction where you live means you cannot register, the terms do not bind you either.
Open your account and work through the record there: registration details, transaction entries and the settings attached to your session. For anything not visible on screen, use the contact route on this site and say which detail you want explained. We will tell you what is held and why.
Yes, and it is worth doing before your next movement rather than after. Update the field in your account, then check the following transaction record to confirm the change carried through. If the detail sits on a wallet or bank side, that provider has to change it.
The rails we name are the ones you fund an account with: Nagad, Upay and Bank Transfer. They appear as payment context, not as a promise about how long a movement takes — timing belongs to the provider's system. Where a method is unavailable, your account page shows what else is offered.
A revised version is published on this page, and the date on the notice moves with it. We do not send a clause change as a promotional message. If a revision affects how your record is kept, read the paragraph named in the notice and write to us with anything unclear.
Transaction entries stay for the retention period our terms describe, because a past movement may still need to be traced. Other account details are handled as the notice sets out when an account closes. Write to us through the contact route and we will say what applies in your case.