Reference

Read What We Hold

Our privacy policy is deliberately short: it lists the account details we store, why a bKash or Nagad transfer leaves a reference on your record, and how to ask us to correct or delete what's held.

Account data listedPayment references keptCookie choiceDeletion on request
nagas88 Read What We Hold
KEEPING IT SAFE

See How We Guard Account Data

Handling personal data well is mostly ordinary discipline: collect what the wallet needs, restrict who can read it, and remove it when its purpose ends. Our staff see the account fields required to verify a transfer or answer you — not the whole record by default. Access is logged, so a lookup has a name and a time against it. You stay in control of the rest: ask for a correction, request a copy, or tell us to close the account and delete what local law allows us to delete. If a request can't be met, we say which rule blocks it.

What we store

Account name, verified mobile number, the wallet or bank detail you pay with, transaction references and game session logs. That's the working set we need to run your wallet and answer a dispute.

Cookies you control

A session cookie holds your login, a preference cookie remembers your language view, and a measurement cookie counts lobby opens. Clear or block any of them from your browser settings whenever you like.

Login security

Every login is tied to your mobile number and a one-time code. If a session jumps to a new device or a different region, we flag it and may ask you to verify the number again.

Retention and changes

Records tied to a completed transfer stay for as long as local law requires. The rest goes once the account closes. Ask for a correction and we log the change with a date.

ASK US DIRECTLY

Ask Us to Change Your Record

A question about your data shouldn't need a ticket number. Message our Bangladesh support desk from the chat panel inside your account, or write to the address listed on this page, and say plainly what you want changed. If you're asking us to correct a name, attach the same document you used at wallet verification. If you want a copy of what we hold, give the mobile number on the account so we can match the request. We reply in English and keep the thread open until you confirm we got it right.

In-account chat Tap the chat bubble on your wallet screen and type your question. The thread stays attached to your account, so whoever picks it up can see your verification state before replying.
Email the data desk Write from an address you can access, include the mobile number on the account, and say whether you want a copy, a correction or a deletion. Vague requests slow the check down.
Wallet reference fixes If a bKash, Nagad or Rocket reference needs correcting, send the transaction ID plus a screenshot of the transfer page. We match it against the deposit record and update the entry.

Check the Answers First

Most data questions come down to four things: what we keep, who reads it, how long it stays, and how you get it changed. The answers below cover those in plain terms, including what happens when local law and your own request pull in different directions. If your situation isn't handled here, message support from inside your account.

The mobile number and name you verify when you open the account, the wallet or bank detail used for bKash, Nagad and Rocket transfers, your transaction references, and the game sessions and devices tied to your login.

Yes. Message support from inside your account and ask for a copy of what we hold. We match the request to your verified mobile number first, so the file never goes to someone else.

Ask us in chat or by email. We close the account, remove what we're allowed to remove, and tell you which records local law still requires us to keep, such as completed transaction logs.

Only the reference and amount needed to settle a transfer or clear a withdrawal check. We don't hand your game history to a payment partner, and we don't sell data to anyone.

It stays under our retention rule until the holding period runs out, then gets deleted or anonymised. You can shorten that by asking us to close the account yourself.

A session cookie keeps you signed in, a preference cookie remembers your language and currency view, and a measurement cookie shows which lobby tiles get opened. All three can be blocked in your browser.
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.