Reference

Your Privacy Policy, Explained Without Legalese

This page tells you exactly what vamx records when you open an account, pay in through bKash, Nagad or Rocket, and move around the lobby.

Account data mapCookie choicesWallet checksDeletion requests
vamx Your Privacy Policy, Explained Without Legalese
DATA CONTROLS

Cookies, Logins and Retention Windows

Three things decide how long your data stays: whether your account is open, whether a cashier request is still inside a dispute window, and whether a law in your region requires us to hold a record. Cookies are the smaller story — a session cookie keeps you signed in, a security cookie remembers this device, and a preference cookie remembers your language. Clear them and you will be asked for the one-time code again on your next login. That is the trade, and it is yours to make.

What We Store

Account name, mobile number, the wallet number you pay from, cashier references, device and browser type, IP address, and the pages you open, from a slots room to the cricket sportsbook. Nothing about your contacts or your camera.

Cookies On Device

Session cookies keep you signed in. A security cookie marks a device we have already checked, so a fresh one triggers a one-time code. Preference cookies hold language and display settings, and your browser clears all three on command.

Login Security

Two steps guard a login: your password, then a one-time code sent to the mobile number on the account. Sign in from an unfamiliar device and the session waits until you confirm that code.

Retention Window

Records stay while your account is open. Once you close it, we keep cashier and login logs only as long as a dispute or a local legal duty requires, then delete them. Ask us which period covers your region.

ASK THE DESK

Who to Ask About Your Data

Data requests do not go into a general inbox where they sit unread. Log in, open the account menu, then the privacy request form — it lands with the team that handles wallet records and login logs. A correction to your name or mobile number needs one verification step first: we send a one-time code to the number on file and ask for the last digits of the wallet you paid from. Requests from someone who cannot pass that check are not actioned.

Team online

Account Chat

The chat panel in your account is where a data request starts. Name what needs changing — a phone number, a wallet record — and the agent passes it to the privacy desk with a reference you can follow.

Email Request

You can also write in from the email address registered on your account, with data request in the subject line. Say whether you want a copy, a correction or closure, and the team replies to that same address.

Wallet Check

Before any record leaves the building, we confirm the wallet. You will be asked for the last few digits of the bKash, Nagad or Rocket number you paid from, plus the one-time code sent to your registered mobile.

Questions About Your Data, Answered

These are the four or five things people actually message us about after reading the policy. Short answers below, and the request form sits inside your account if you want the long version for your own region.

The mobile number and name on your account, the wallet number you send from, the transaction reference the cashier shows, and device details from that session. We do not see your wallet PIN or your wallet balance.

Yes. Send a data request from inside your account and we compile it — account details, deposit and withdrawal references, login history. We verify you first with a one-time code, and the copy goes only to your registered number.

Only what a payment needs to settle: the sender number, the amount and the reference. bKash, Nagad and Rocket each hold their own agreement with you, so read their terms for what they keep on their side.

Open your browser settings, find the privacy section, and block third-party cookies first — that keeps the lobby working while stopping the tracking ones. Blocking everything signs you out of the account each time.

The account closes and lobby access stops. Cashier references and login logs stay only while a dispute or a local legal duty requires them, then they are deleted. Ask which period covers your region and we will confirm in writing.

The chat panel in your account reaches our Bangladesh support team, and a written request from your registered email works too. Say what looks wrong — a wallet reference, a login you do not recognise — and it reaches the privacy desk.
Reference

Privacy Policy

Service availability depends on eligible regions and local law. Users should check local rules before opening an account.

Access may be available only where local law permits.