Reference

Your Privacy Policy, Written Plainly

Your mobile number, your wallet reference and your device details sit in one account record, and this page spells out what we keep, why we keep it and how you get it changed.

Wallet references explainedOne-time code at loginCorrection requests openCookie control in your hands
vipbajee Your Privacy Policy, Written Plainly
ASK US DIRECTLY

Reach Our Team About Your Data

Questions about your own data should not sit behind a general help queue. Message us from the number registered on the account and the request lands with the team that handles privacy, not the payments desk. Write in from a handset we have not seen before and we ask for a one-time code before discussing anything on the profile — that check protects you, not us. Tell us what needs changing and we will say what we can do and what evidence we need first.

Chat from your handset Open the chat window inside your signed-in account and ask about the data we hold. Because your device is already verified, the agent can pull up your profile and answer without a second round of checks.
Email the privacy desk Write from the address tied to your account so we can match the request without questions. Attach the wallet screenshot if the issue is a bKash, Nagad or Rocket reference that looks wrong on your statement.
Message centre requests Lodge a data request from the message centre and it stays on the account as a record you can follow. Use this route for corrections, deletion requests or a copy of what we hold.
SECURITY IN PRACTICE

Cookies, Security and Account Changes

Cookies on the site do two jobs: they keep you signed in when you move from phone to desktop, and they show us which pages load slowly on a mobile connection — whether that is a cricket market page or a slot lobby. You can clear or block them from browser settings, though the login cookie is the one holding your session. Password changes, device logouts and wallet edits all run through the same verification step, so nobody slips a new payout number onto your profile quietly. Retention follows the account rather than a calendar: records stay while it is open, then for the close-out window our payment partners need.

What we hold

Your profile, verified mobile number, wallet references and device logs sit in one account record. Transaction strings from bKash, Nagad and Rocket are kept so a payment query can be settled with evidence rather than memory.

Cookies and sessions

One cookie keeps you signed in; others count page loads and remember your language choice. Clear them from your browser any time, but expect to enter a one-time code on your next visit.

Login and device checks

A password change, a new handset or a wallet edit each triggers a one-time code before the change lands. Log out a device you no longer use from the same screen, and the session drops immediately.

Keeping records, closing out

Account and wallet records stay while your account is open, plus the close-out window our payment partners need for pending transfers. Ask us to correct or remove something and we log that request on your profile.

Privacy Questions You Send Us Often

Most of what reaches the privacy desk is the same handful of questions, so we answer them here instead of hiding them in a long document. If your case is different — a shared handset, a wallet registered in a family member's name, a transfer that shows twice — message the desk and describe it in your own words. We read every request against the account record before we reply.

Yes. Ask from your registered number or through the message centre and the privacy desk sends a summary of the profile, wallet references and device log tied to that account.

Send the correction from the verified number and attach a photo of the document you want us to use. We change the record only after that check, because a wrong wallet number can redirect your money.

The reference number and amount from a deposit or withdrawal are stored against your account so a disputed transfer can be traced with the wallet provider. We keep the reference, not your wallet PIN.

Yes. Tell us in writing and we close the account once any open wallet transfer settles. Profile and device records are then deleted, though the transaction trail our payment partners must keep stays on file.

Only where a step needs it: the wallet provider confirming your payment, a document-verification service, or a lawful request. We do not sell account data, and we do not hand your number to advertisers.

A revised version appears on this page with the date it takes effect, and we flag the change in your message centre. Using the account after that date means the new wording applies.
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.