Reference

Privacy Policy: What We Hold On File

This page spells out what we record when you open an account — your contact number, device details, and the bKash, Nagad or Rocket references behind each payment.

What we storeWallet referencesCookie choicesRemoval requests
9777dbt Privacy Policy: What We Hold On File
HOW WE HANDLE IT

Wallet Records and Login Security

Everything that touches your records runs through the same account flow you already use. Your password is hashed at rest, a one-time code checks new devices, and the wallet number on a payout request must match the one on file. Cookies stay under your control in browser settings. Records are kept only for the purpose they were collected, then dropped once that purpose ends or the law stops asking. Want something removed early? Tell us and we will explain what can go and what has to stay.

Wallet matching

Before a payout moves, we check that the bKash, Nagad or Rocket number you request matches the number saved on your account. A mismatch goes to a manual check first.

Login protection

Passwords are stored hashed, never in plain text. Signing in from an unrecognised device triggers a one-time code to your registered number, so keep that SIM with you.

Cookie settings

Session cookies keep you signed in; counting cookies show which lobbies and cricket markets get opened. You can clear or block either type in your browser, though blocking session cookies signs you out.

Holding and removal

Records are held only as long as their purpose needs — access, payment reconciliation, dispute checks, legal duty. Ask us to remove an account and we will say what can go now and what has to stay.

CONTACT OUR DESK

Send a Privacy Request

Privacy requests go to one desk, so nothing gets lost between teams. Open the chat window from the lobby footer, or write to the support address listed in the same place — both land in the same queue and both take messages in English. Include your registered number and the wallet you paid with (bKash, Nagad or Rocket) so we can find the right account without asking twice. We work through requests in the order they arrive and reply with the verification step.

Team online

Live chat

Open the chat window from the lobby footer. Paste your registered number and the transaction ID from your bKash, Nagad or Rocket payment so the agent can pull the right record.

Email

Write to the support address in the lobby footer with a privacy request in the subject line. Add your registered number and a screenshot of the wallet payment if you have one.

Profile area

From the profile area you can see the number and email we hold, and fix a typo on the spot. Anything deeper goes through the chat or email queue.

Privacy Questions You Send Us

Most of what lands in the queue is the same handful of worries, so here are the straight answers. Nothing below changes with your wallet: bKash, Nagad, Rocket and Upay requests are all handled the same way. If your case is not covered, the desk is one message away.

Your contact number or email, device and browser type, sign-in times, and the transaction IDs behind bKash, Nagad and Rocket payments. We do not store your wallet PIN at any point.

No. The wallet app sends us a confirmation and a transaction ID, nothing more. Any message asking for your PIN is not from us — report it to the support desk straight away.

Message the support desk from your registered number and ask for an account data copy. We verify the request first, then send what we hold to the contact details on file.

You can ask us to close it. Some payment and dispute records have to stay for a set period under the law that applies where you live; we will tell you which ones.

Only where it is needed to run the service — the wallet confirming your transfer, or a provider handling account checks — and where a lawful request requires it. We do not sell records.

Access depends on your local law and eligible regions, so it is not open everywhere. If the service is restricted where you are, please do not open an account or send a payment.
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.