Reference

Open Your Account, Know What Data We Keep

Your account runs on the data you hand over — mobile number, wallet ID, bet slips, nothing exotic. We hold what the cashier desk and the game floor need and not a field more, and this page is the record of who sees it.

What we collectWhy we hold itHow to change itWho to ask
pook Open Your Account, Know What Data We Keep
DATA CONTACT DESK

Reach the Desk That Handles Privacy Requests

Where do you send a data request? Straight to the desk that handles it, not to a general inbox that routes three times before anyone reads it. Use the chat inside your account so the thread carries your account ID, or email our privacy contact from the number registered on the profile. Both paths reach the same small team, and every message stays attached to your record so you never repeat yourself. Wallet queries about bKash, Nagad or Rocket references go down the same thread.

In-account support chat Open your account, pick Help, and you land in a live chat queue. Ask for a copy of your stored record, a correction, or a deletion request, and the thread keeps every reply on file.
Email the privacy desk Write to our privacy contact from the address tied to your account so we can match the request without extra checks. Include your registered mobile number and what you want changed.
Wallet and login issues If a bKash, Nagad or Rocket deposit reference looks wrong, flag it in the same thread. We check the sending number on our side before anything is corrected on your record.
HANDLING YOUR RECORD

See How We Store, Secure and Delete Data

Data handling here is boring on purpose. Sign-in needs a one-time code, wallet references are stored so a dispute can be checked rather than to build a profile of you, and cookie choices sit in your own settings. Retention follows the periods local rules set, then records go. Want a copy, a correction, a deletion? Ask and we answer in writing. That is the whole posture — we do not sell contact lists, and your number does not go to outside marketers.

Store what we need Your mobile number, wallet transaction references, device and browser type, and your bet and game history. Wallet PINs and card credentials never sit with us; payment partners handle that step.
Cookies you control We set cookies that keep you signed in and remember your language choice. Anything used to measure traffic is optional, and the banner lets you switch it off without losing your session.
Sign-in and device checks Every sign-in needs a one-time code sent to your mobile number. A login from a handset we have not seen before can be held while our team confirms it with you directly.
Retention and requests We keep account and transaction records only as long as your local rules require, then remove or anonymise them. Ask for a copy, a correction or a deletion and we answer in writing.

Ask Us About Your Data and Access

These are the questions we get asked most at the desk, answered the same way we answer them in chat. If yours is not here — say, what happens to a wallet reference after a failed bKash transfer — ask directly and we will put the answer in writing. Read it once before you open an account and once after; the second pass makes more sense. Nothing on this page overrides your local law, and eligibility still depends on where you are.

Your mobile number, wallet references from bKash, Nagad or Rocket, the device you sign in from, and your game and bet history. We ask for nothing else unless a payment check genuinely needs it.

Yes. Message the privacy desk from your registered contact and ask for your account record. We send back what we hold on your profile, wallet references and play history, in a readable format.

Only with payment partners and service providers acting for us, and only the detail that task needs. They work under confidentiality terms. Some processing sits outside Bangladesh, so your local law still governs what we hold.

Message us from your registered number, name the detail that is wrong, and we check it against the transaction record before editing. Where local rules require retention, we restrict access rather than delete.

Your bet history on cricket markets, including BPL and international fixtures, sits in the same ledger as your slot rounds. Support only opens that ledger when you raise a query, and the access is logged.

The account closes, but transaction records stay for the period local rules set, because payment disputes can arrive later. After that we delete or anonymise the rest. Ask us to confirm which stage your file is at.
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.