Reference

What Our Privacy Policy Covers

One page, plain terms: what account data cvc444 keeps, why a bKash or Nagad transfer reference sits in your record, and how to get a copy or ask for a change.

bKashNagadRocketOne-time sign-in codeDated policy updates
cvc444 What Our Privacy Policy Covers
ASK US DIRECTLY

Ways to Reach Our Privacy Desk

You do not need to hunt for a hidden form. Every privacy request goes through a channel tied to your own account, so we can confirm it is really you before anything is copied, corrected or closed. Support agents in Bangladesh handle wallet questions daily and see the same ticket you see, which means you are not repeating yourself to a second person. Tell us which wallet you used — bKash, Nagad or Rocket — and the date of the transfer, and the reply comes back quicker. A one-thumb layout means you can raise it from a moving bus.

Chat from your signed-in account Open the chat panel while signed in and your account is already attached to the thread, so there is no reference number to copy. Ask for a data copy, a correction or a removal request here.
Write to the privacy desk Send from the phone number or email on your account. Include the wallet you use — bKash, Nagad or Rocket — and the date involved, and we match the request without a long back-and-forth.
Wallet and payment queries If a deposit or withdrawal reference looks wrong on your record, raise it through support before asking for a data change. We check the wallet side first, then correct the entry on your account.
HOW WE HANDLE IT

Cookies, Sign-In and Retention Rules

Three things decide how long we keep a piece of data: what the law requires, what a payment dispute needs, and whether you still hold an account. Close your account and your play history stops being used for anything beyond record-keeping, though wallet and tax entries sit for the period the rules set. Cookies get the same split treatment — sign-in cookies are the ones that matter. Check the item that matches your own case, and ask if a line is unclear.

Account data we hold

Your sign-in number, wallet name, transaction references and bet history from titles like Baccarat Circle or Crash Hyper. That set is what we need to run the account and match a payment.

Cookie split

Sign-in and security cookies keep your session alive in a phone browser. Analytics cookies show us where a mobile page stalls; you can clear those from browser settings without losing account access.

Sign-in and device safety

A one-time code goes to your registered number at each fresh login. Open the site on a new handset and you will be asked to confirm it, which is how a borrowed number gets caught early.

Retention and removal requests

Ask us to delete what we are allowed to delete. Payment and wallet records stay for the period local rules set, and we name exactly which items those are when we reply.

Privacy Questions Bangladesh Customers Ask

Most of what lands in our inbox is the same handful of questions, so here they are with plain answers. If yours is not listed, send it from inside your account and we will add the wording to this page once it is settled. Nothing here overrides local law: where a rule in your region says otherwise, that rule decides what we can hold and for how long.

Your phone number, the name on your wallet, and the payment reference your bKash, Nagad or Rocket transfer generates. We also log the device and browser you sign in from, so an unusual login can be spotted.

Yes. Message support from inside your signed-in account and ask for a copy. We confirm it is you first, then send the record tied to that account as a file in the same thread.

Only the reference needed to match a transfer, and only with the wallet involved in that transfer. We do not hand your play history to a wallet provider or to advertising lists.

Send a closure request from your account. Play history and any marketing use stop at once; payment records stay for the period local rules require, and we name those items when we confirm the closure.

We date the top of this page and post the revised text here before it takes effect. Anything that touches how wallet data is used also gets a line in your account messages.

Sign out when you finish, and never approve a one-time code you did not request. On a shared handset, use a private browser window so the sign-in cookie is not left behind for the next person.
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.