Casino / Mobile
vt888a keeps this Privacy Policy short on purpose: it sets out what we hold when you sign in, what a bKash, Nagad or Rocket transfer leaves behind in your account, and how to ask us for a copy or a correction. Access to the account depends on your local law and eligible regions, so read the wording here alongside the rules where you live.
Bangladesh is the market we write for, so this is the version we publish for accounts opened and used from here. What we hold follows the account itself: the mobile number and email you sign in with, the wallet or bank details you attach when you move money, and the transaction lines that record each transfer you start with bKash, Nagad, Rocket or a bank transfer. Those lines exist because you can see them too — open your account and every payment sits there with its own reference and status. Privacy rules are not the same everywhere. They differ between countries and between payment channels, and local law may give you rights that a policy page can neither add to nor take away. Read the wording here as our baseline posture rather than a replacement for the rules that apply where you are. If you sign in from outside Bangladesh, or from a region where we do not offer accounts, access depends on your local law and eligible regions, and we may have to close an account that falls outside them. One thing does not move: we do not pass the contact details attached to your account to outside advertisers, and a payment line stays tied to the account that made it.
This policy follows the account rather than the pages around it. When you sign in with email and mobile number, the details tied to that sign-in are what we hold and what this page governs. Move money through bKash, Nagad, Rocket or a bank transfer and a record is created — that record, its reference and its status sit under the same policy. Lobby browsing is lighter again: which tiles you open and which rooms you return to, kept so that navigation keeps working on your phone. Then there is the part that is not ours. Wallet apps and banks run their own privacy terms, and when you leave our screen to finish a payment, the wallet provider handles that step and stores its own copy. Links out to a studio site, an app store listing or a payment app are outside this page too. A simple rule helps: anything you reach from inside your vt888a account is ours to explain, and anything that opens in another app belongs to that app's notice.
Your sign-in details, the email and mobile number attached to the profile, and the session that keeps you logged in on your phone. If you change a number or lose access to an email address, that change starts here, and we confirm it from inside the account rather than over a public channel.
Every transfer you start through bKash, Nagad, Rocket or a bank leaves a line in your account with an amount, a reference and a status. This policy covers how we keep those lines and who can open them; it does not replace the wallet's own record, which lives in the wallet app.
Pages you read while signed in, the lobby tiles you tap, and the rooms you return to are logged in a lighter way than payments. We use that to keep navigation working and to see which areas get opened. It is not the same data as your transfer history, and we treat it differently.
Wallet apps, banks, studio sites and any page you reach by leaving ours sit under their own privacy terms. We cannot answer for how bKash or your bank stores a record once the payment leaves our screen. Read their notice when you are redirected, because that step is theirs.
You are not stuck reading a policy and hoping. Almost everything you would want to change sits inside the account area, reachable from the same menu you use for payments. Open your profile to correct a name spelling, change a mobile number, or swap the wallet number you use for bKash, Nagad and Rocket. Open the transaction list to see the amount, reference and status attached to any transfer, including one that did not land the way you expected. Where the screens stop, we take over. Write through the contact route published on this site, name the account and the record you mean, and we will look at it from our side. Expect us to confirm the request from the signed-in account first — payment details are not changed on the strength of a message from an unknown number. Want a copy of what we hold? Ask the same way and we will answer on the same route.
Sign in and open the transaction list. Every line shows the rail, the amount, the reference and the status, so you can hold it next to the bKash or Nagad message on your phone before you ask us anything. Most questions end right there.
A misspelled name, a mobile number you have stopped using, a wallet number you no longer keep — those are edited from your profile while you are signed in. Change the detail, save it, then check the next payment lands against the new entry.
If you want to know why a record exists, or what we keep beyond the transaction list, send the question through the published contact route. Say which account and which period you mean, so the reply is about your case and not a general answer.
You can ask for a copy of the details attached to your account, or ask us to correct something the screens will not let you edit. We confirm those requests from the signed-in account first, then answer on the same route you used to raise it.
Privacy questions deserve a real reply, so we keep the routes on the page rather than behind a phone menu. Every page here carries the same contact path at the foot, and that path is the one to use when your question is about data, a record, or a request to change something on your account. Signed out? Use the site contact form and include the mobile number or email attached to the account so we can find it. Signed in? The help menu inside your account keeps the message tied to your profile, which saves a round of back-and-forth. Keep the message short and specific. Give the date, the rail and the amount when the question is about a transfer, because a bKash line, a Nagad line and a bank line each carry their own reference. Please do not send wallet PINs or passwords through any route; no one at our end needs them to look at a record.
Use the form linked in the footer of any page here. Write the account's mobile number or email in the message so the team can find the profile, and keep it to one subject. It reaches the same inbox as every other privacy request we answer.
Signed in, the help menu keeps your message tied to the profile, which means fewer questions about who you are. Use it for anything about a record, a closed account, or a detail you cannot edit yourself. Wallet PINs never belong in this message.
If we have already written to you about a record or a request, answer that message instead of starting again. The earlier exchange stays attached, so whoever picks it up can see what was asked and what we already confirmed. Quote the reference when a transfer is involved.
We collect what the account needs and not much more. A sign-in needs a mobile number, an email and a password you set; a payment needs the wallet or bank details the transfer runs through. Transaction lines stay attached to your profile so you can open them later. Cookies do simpler work: they keep you signed in across a page change, remember the last lobby tile you opened, and tell us when a page fails to load on a phone. You can clear them in your browser at any time, though some screens will ask you to sign in again. Retention is a practical question, not a decorative one. Payment lines are kept for as long as the account exists because they are your record as much as ours, and a closed account may still leave accounting lines behind. Nothing here is answered by a ticket number alone — if you want to know what we hold, ask on the published contact route and name the record you mean. We will tell you what we can, and tell you plainly when we cannot.
The email and mobile number you sign in with, the wallet or bank entry you attach for payments, and the transaction lines those payments create. We do not keep wallet PINs or one-time codes, and no one on our side will ask you to read one out.
Cookies keep a signed-in session alive between pages, remember the last tile you opened, and show us where a page breaks on a phone. Block them and the site still loads, but you will be asked to sign in far more often. Clearing them is done in your browser settings.
Your password is yours to set and yours to change from the profile screen. We will confirm account requests from the signed-in session before acting on them, and we will never ask for a wallet PIN. Treat any message that does as one to ignore.
If a line in your history looks wrong, or you want to know what we hold, use the contact path at the foot of the page and quote the reference. Retention questions get a straight answer: what we keep, why, and what happens to it when an account closes.
This is where the questions that land in our inbox most often get a straight answer, written the way we would say it across a counter. Read the short version first; if your case is different, the contact path at the foot of every page reaches the same team that handles account records. Include the mobile number or email attached to your account and the reference of the transfer you mean, and the reply usually needs less back-and-forth. Keep it to one clear question if you can — five in a single message usually means five half-answers. None of these answers is legal advice, and none of them overrides the law where you live. Where the two differ, local law and eligible regions decide what we can do for you.
It covers the account you open with us and everything tied to it: the email and mobile number you sign in with, the wallet or bank details you attach, and the transaction lines created when you move money through bKash, Nagad, Rocket or a bank transfer. Lobby pages you browse fall under it too.
We keep the wallet number and the record of the transfer, because you need to see the same line we see. We do not keep your wallet PIN, and we never ask for it. If a payment fails, the reference on that line is what lets both sides find it.
You can clear or block cookies in your browser settings. Blocking all of them will sign you out between pages and may stop parts of the lobby from loading. The ones we rely on most keep a signed-in session alive, so pages behave the way you expect on a phone.
Sign in and send the request through the contact path published on this site, naming the account and the period you want. We may confirm from inside the signed-in session before we release anything, because a copy of your records should not travel on a stranger's message.
Send the reference, the amount and the rail — bKash, Nagad, Rocket or bank — through the published contact route, and keep the wallet message on your phone. We will compare our line with yours. If the payment stalled inside the wallet app, that app's own support has to look at it first.
Yes, when the account flow or the rules around it change. This page always carries the current wording, so what you read here is what applies today. If a change affects what we hold or who can see it, we will say so on the site rather than quietly editing it.