Reference

What Our Privacy Policy Covers

Everything you give us — your mobile number, the wallet you pay from, the games you open — sits in one short policy that says what we hold, why, and how to get it changed.

Sign-up detailsWallet recordsCookie controlsClosure requests
take999 What Our Privacy Policy Covers
REACHING SUPPORT

Where To Send A Data Question

Data questions do not belong in a general queue, so we route them by channel. Chat is quickest when you want to know what we hold or why a record shows a certain figure. Anything that changes your record — a copy request, a correction, a closure — goes through the request form so there is a written trail on both sides. Wallet mismatches sit with the verification desk, because a name that does not match your bKash, Nagad or Rocket account is a records problem as much as a payment one.

In-app chat Open the chat from your account wallet screen and describe the data question. We log every thread against your account, so you never have to explain the same background twice to a second agent.
Request form For a copy, correction or closure, the form in your account area reaches the team that keeps records. Add your wallet type — bKash, Nagad or Rocket — so we can match the request quickly.
Wallet verification desk If a withdrawal is held because the wallet name does not match your account name, send the matching document through the verification desk and we release the record once it lines up.
LOCKS AND RECORDS

How We Lock Your Records

Account security and data handling are the same job here. We tie every record to the mobile number you registered, so a login from a new handset asks for a one-time code before the lobby opens. Cookies stay lean: a session cookie for the lobby, an analytics cookie for page speed. Records are kept while the account is live plus whatever local accounting rules demand, and closure requests are actioned against that same trail. Nothing is deleted quietly, and nothing leaves us without a reason we can name.

Login OTP Every sign-in on a new phone asks for a one-time code sent to your registered number. That code is the main lock on the account, so keep the number active.
Cookies Session cookies keep you inside the lobby between pages; analytics cookies show us where a mobile page stalls. Clear them any time from browser settings and you log in again with a fresh code.
Retention Transaction records stay with us while the account is open and for the period local accounting rules require afterwards. Ask for closure and we stop using your details past that legal record.
Corrections Wrong name or an old number? Request a change and we ask for one matching document before the record is updated, which stops anyone else from rewriting your account details.

The Data Questions We Get Most

Short answers to what people actually ask us, in the order they usually ask it. If your situation is not here — a shared handset, an old number you no longer use, a wallet registered in another name — take it to chat and we will work it out against your own account rather than guess.

Your name, mobile number, the wallet you pay from — bKash, Nagad, Rocket or Upay — plus your transaction history and the device you sign in on. We collect what the account needs to run and to verify a withdrawal.

Yes. Send the request from the form inside your account so we know it is you, and we compile the account details, wallet records and login history linked to your registered number.

Only with the payment provider that processes the transfer, and with anyone the law requires us to answer. We do not sell account or wallet data to outside list brokers.

Ask from the request form and we close access, then hold the transaction record for the period local rules set. After that the details come out of active systems.

A session cookie and basic device data, enough to load pages correctly and see which ones stall on mobile. Nothing links that visit to a wallet until you log in.

Use the in-app chat or the request form and say which field is wrong. We ask for one matching document, update the record, and confirm the change on your account.
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.