Reference

Your Data, Explained Before You Sign In

Your account starts with a phone number, a password you set, and a wallet you already use — bKash, Nagad or Rocket.

Wallet PIN never reaches usOne-time code on a new deviceCopy, correct or delete requestsCookie settings you control
shuvowin Your Data, Explained Before You Sign In
COOKIES AND SAFEGUARDS

How We Guard Account Data

Cookies and device storage do two jobs: they keep you signed in on your phone between visits, and they show us which screens load slowly so we can fix them. Clear them from browser settings whenever you like — you will simply log in again. Inside the company, account records open only for staff who need them to settle a payment or answer your query, and every profile pull is written into a log. Retention follows the reason: play records while a dispute window is open, wallet references for as long as the payment partner requires.

Cookies you can clear A session cookie keeps your phone signed in between visits; a preference cookie remembers language and layout. Clear both from browser settings any time — you land on the login screen and carry on, nothing is lost.
Login checks Your password plus a one-time code sent to your registered number. When a device looks unfamiliar, we ask for the code again before any balance or wallet screen opens.
How long records stay Play history stays while a balance dispute could still be raised. Wallet references from bKash, Nagad and Rocket stay for the period the payment partner requires, then we clear them or strip the identifying parts.
Copies and corrections Ask for a copy of your profile, a fix to a phone number that changed, or deletion of an account you no longer use. We reply in writing and name any record that must stay for legal reasons.
DATA CONTACT POINTS

Ask Us About Your Records

Got a question about what we hold on you? Ask through live chat inside your account — the agent sees your profile and last wallet reference in the same window, so you are not retyping a bKash number. Anything written, like a copy request or a correction, goes to the support email, and you keep the ticket number it returns. Requests are handled in the order they arrive, and a payment record query moves quicker when you attach the transaction ID and the date.

Live chat in your account Open your account, tap the chat icon and pick Data and Privacy as the subject. The agent can pull your profile and last wallet reference without asking you to repeat either one.
Written requests by email For a copy, a correction or a deletion, email the data team with your registered phone number and the wallet you used last. Keep the ticket number — it follows the request from first reply to final confirmation.
Wallet record checks When the question is a payment record and not a profile field, the wallet team matches your Rocket, Nagad or Upay reference against what the app returned. Bring the transaction ID and the date you paid.

Privacy Questions We Get Asked

These come up most in chat and email, so we have answered them plainly here. If yours is not on the list, the support team can pull your own record and walk through it with you.

Your verified phone number, the password in hashed form, the profile fields you filled in, and your play records. Wallet references from bKash, Nagad or Rocket sit alongside those, but your wallet PIN never reaches us.

No. The wallet app handles the PIN on your own phone. We only receive the transaction reference and status the app sends back, and a support agent reads that reference when a payment needs checking.

Message support from inside your account, or email the data team with your registered number. We confirm in writing and send the copy through the same channel once we have verified that it is you.

Nothing is deleted the moment you go quiet. Play and login records stay while a balance question could still come up, and wallet references stay for the period our payment partners require, then we clear them.

Two kinds. A session cookie keeps you signed in between visits, and a preference cookie remembers layout and language. Clear both from your browser settings whenever you want — you simply log in again.

Only staff with a reason: the agent on your ticket, the wallet team checking a reference, and engineers fixing a fault. Each profile pull is logged, and the log is checked when a query is raised.
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.