App / Mobile
vk8888 publishes this page so you can read the account rules and transaction terms before you fund a wallet or open the lobby. Everything here covers how you access the site, and access itself depends on your local law and eligible regions.
Legal wording on this page is written for a Bangladesh audience, but it does not override the law where you actually live. We treat the policy as the working agreement between you and vk8888: it covers how you open an account, how you fund it, what we record, and how we handle a disagreement if something goes wrong. Where local rules differ from what is written here, the stricter position wins, and some features may simply not be offered to you. That is why we ask you to confirm two things before you go further. First, that your own law allows you to use a site of this kind. Second, that you are inside a region we can serve. Nothing on this page is a promise that a specific payment route, game or lobby section is open to you today — availability is decided per account and per region. When you fund an account through Nagad, Rocket or Upay, the wallet operator's own terms sit alongside ours. We do not control those terms, and a wallet provider can change a fee or a step without telling us first. Our part is the account side: what balance we show you, what we log, and how you raise a question about a recorded transaction. We may revise this page as the service changes. The version you see when you sign in is the version that applies to you at that moment, so read it again after any update appears in your account.
Scope is the question we get asked most, so we keep the answer blunt. This policy governs the account you hold with us, the transactions we record against it, and the pages we publish. It does not govern the wallet app on your phone, the browser you use, or any site you reach by leaving ours. Think of it as four layers. Your account access is ours to define — the sign-in path, the password you set, the sessions we keep open. Your money movement is shared: we record the Nagad, Rocket or Upay transfer we can see, while the wallet provider owns the step before it. Site content is ours, including the lobby, the game titles we carry and the rules shown on each one. Third-party services sit outside the line completely, and that takes in your mobile network, your bank, and any studio whose games are displayed. Where the layers overlap, the narrower rule applies. A wallet provider refusing a transfer is a wallet decision, not a term we can waive on your behalf.
Your sign-in, your password and the sessions we keep open all sit inside this policy. We define the steps you meet at the login screen, and we ask you to keep that password to yourself instead of sharing one device login around a household.
Every Nagad, Rocket or Upay top-up we can see against your account is logged with its reference and date. That line is what we check when you raise a question, so keep the wallet confirmation in your own app until the balance updates on our side.
The lobby, the titles we display and the rules printed on each one are ours to publish. Game rules come from the studio that supplied the title, and they are worth reading before you stake anything — a rule you skip is not one we can undo later.
Wallet apps, mobile networks and bank rails are third-party services. We cannot change their fees, their downtime or the extra steps they occasionally ask for, and this policy does not reach into them at any point — your relationship with those providers runs on their own terms.
Rights only matter if you can use them without hunting, so we keep the paths short. You can read your own transaction history from the signed-in account area at any time, and you can compare what we show against the confirmation in your Nagad, Rocket or Upay app. If the two do not match, that is exactly the case to raise with us. You can also correct the details we hold — a phone number that changed, a name spelled differently from your wallet account, an email you no longer open. Open the account area and follow the fields shown there; if a field is locked, ask support to change it rather than opening a second account. Questions about wording go through the same route as any other account question. Say which section you are reading and what you think it means, and we will point you to the clause that decides it. You do not need to wait for a disagreement to ask — a plain question about a sentence is enough.
Your account area lists the transactions we have logged, each with a date and a reference. Open it after a top-up and match the entry against the confirmation sitting in your wallet app, and take a screenshot of any gap before you message us.
Phone number and email can be changed from the account fields, and you should keep both current so a verification step reaches you. Where a field is fixed — a name that mismatches your wallet — ask us to correct it rather than opening a second account.
If a clause reads unclearly, quote the heading in your message and say which part you want explained. We would rather answer the question early than handle a disagreement over a transfer later, and a plain question costs you nothing.
You can ask for a copy of the account details we hold and for anything inaccurate to be corrected. Tell us which records you mean — transactions from a set of dates, or a field on the account — and we will work through it with you directly.
Policy questions land in the same queue as account questions, which is deliberate: one place to ask, one place to look for the answer. The support entry sits inside your signed-in account area, so open it while you are logged in and your account reference travels with the message. From the public side, the contact route listed on the site reaches the same team. Come with the specifics. Tell us the section heading you are reading, the page it sits on, and what your account shows at that moment. If the question is about a transfer, add the wallet name, the reference and the date — Nagad, Rocket and Upay each print one — because that shortens the check on our side. We answer in the order questions arrive. We cannot promise a response time here, and we will not invent one on this page. What we can say is that a message with a reference attached is easier to act on than one without.
The support entry in your signed-in account area carries your account reference with the message automatically. Open it while you are logged in, describe the policy point in your own words, and the team gets the context it needs without a back-and-forth.
The contact route we publish on the site reaches the same team from outside your account. Use it when you cannot sign in at all, and include the email or phone number registered to the account so it can be located quickly.
Read the clause before you write. Most questions about scope, transaction records and retention are settled by the wording on this page, and quoting the heading you are stuck on makes any follow-up shorter for both sides.
Handling is where a policy either holds up or does not, so here is what we do. We keep the account details you give us — name, contact, wallet reference — and the transaction lines we log against them. That record runs your account and answers your questions. We do not pass it to anyone outside that purpose. Cookies do a narrow job here: they keep you signed in, remember display choices and show us which pages get read. Clear or block them in your browser settings and the site still loads, though the session cookie going means signing in again. Account security rests on the password you set and the device you use. Sign out on a shared phone, keep your email address current so a reset reaches you, and tell us at once if you think someone else has your login. Retention follows the same logic: we hold transaction records while the account is open and for the period local law requires afterwards. To have something corrected, use the support entry inside your account.
Your account holds the name, contact details and wallet reference you supplied, plus the transaction lines we have logged against them. That record is what answers a question when you ask, and it stays attached to the account rather than to a device.
Cookies keep your session open, remember how you like the lobby displayed, and show us which pages get read. Clear or block them in browser settings whenever you like, but expect to sign back in once the session cookie is gone.
Your password is yours to keep, and the device you sign in from matters as much as the password itself. Sign out on a shared phone, refresh your email address so a reset message lands, and tell us if a login looks wrong.
Account and transaction records stay with us while the account is open and for the period local law requires afterwards. To ask what is held, or to have an entry corrected, send the request through the support entry inside your account.
These are the questions that reach our support queue most often, so they are worth a minute before you write to us. Each answer points back to the wording on this page rather than restating it in full — that way the two do not drift apart as the policy changes. Start with the question that matches what you are actually trying to do. Signing in, reading a transaction line, correcting a name and asking what we hold are four different paths, and the answer changes with each one. Some cases are not covered here at all, and that is fine: open the support entry inside your account, describe the situation, and attach the reference if there is one. We revise these answers whenever the wording beneath them moves, so a re-read after an update is worth the two minutes. Nothing here replaces the policy text itself.
It applies to the account wherever you open it, but whether you may use the site at all depends on your local law and on whether your region is one we can serve. Confirm both before you fund a wallet, and check the wording again if you move country.
Yes. Your signed-in account area lists the top-ups and withdrawals we have logged, each with a date and a reference. Match that line against the confirmation in your Nagad, Rocket or Upay app, and send both references to support if the two differ.
Tell us the wallet name, the reference and the date. We can only act on transfers we can see on our side, so the reference from your wallet app is what lets us trace one. The wallet provider handles anything that failed before it reached us.
Phone number and email you can usually update yourself from the account fields. A name that does not match your wallet account is different — ask support to correct it rather than opening a second account, because two accounts under one person cause more problems than they solve.
Transaction records stay with us for the period local law requires after an account closes, and are removed once that period ends. Details you can ask about at any time while the account is open, through the support entry inside it.
Send the request through the support entry in your account and say which records you want. We work through it with you directly and correct anything that turns out to be wrong; that is also the route if you simply want a clause explained.