Reference

How jeetbuzx Handles Your Account Data

Your account data stays tied to the wallet you funded from, whether that was bKash, Nagad or Rocket, and that is the whole design.

Wallet recordsCookie choicesOTP sign-inMobile accessChange requests
jeetbuzx How jeetbuzx Handles Your Account Data
COOKIES AND LOGINS

How We Guard Account and Wallet Details

We treat account data the way a cashier treats a ledger: written down once, kept tidy, shown to the person it belongs to. Nothing about your wallet is shared with advertisers, and game studios only see the round they are dealing, not your payment details. Sign-in is guarded by a one-time code on your registered number, and a fresh device has to pass the same check. When you want something corrected or removed, one request starts it and we come back to you with the outcome in writing.

Details we hold

Your name, mobile number and the transaction ID from each bKash, Nagad or Rocket transfer. Gameplay lines stay on file too, so a stake question gets answered from a log, not from memory.

Cookies we set

One session cookie keeps you signed in; a small preference cookie remembers your language. Clear your browser and you are signed out, and the next login asks for a fresh code.

Logins and codes

Every sign-in sends a one-time code to your registered number. A new device has to pass the same check, so a copied password on its own will not open your wallet.

Keeping and removing

Records sit with your open account, then for the period local financial rules require. Ask us to close the wallet and we tell you exactly what stays behind and why.

DATA CONTACT PATHS

Ask Us About Your Own Data

Getting a privacy question answered should not take three messages. Start with the mobile number your wallet is registered to and tell us the thing that looks off: a payment reference that never landed, a login you did not make, a name spelled wrong. Our team works from the same record you can see, and every request gets a ticket number, so keep it. Writing about a bKash or Nagad transfer? Paste the confirmation text, because the transaction ID is what lets us find the entry.

In-app chat Open chat from your account menu and quote the wallet you funded from. Attach the bKash or Nagad confirmation text if you still have it, and we pull the right record without guesswork.
Email request Write to our support desk with the mobile number on your account and the change you want. Replies come back to the same address, so keep the thread in one place.
Access request Ask for a copy of what we hold, or ask us to delete what we no longer need to keep. We confirm identity first, then send the file to your registered number.

Privacy Questions We Answer Most

These are the questions that land in our chat queue most often, answered the way we would answer them there. If yours is not on the list, the support desk takes it directly. You do not need an open ticket to ask about your own data, and you do not have to explain why you want to know.

Your name, mobile number, age confirmation and the wallet you fund from. Each bKash, Nagad or Rocket payment adds a transaction reference, so the money can be traced back to you.

No. You type the PIN inside the wallet app, not on our pages. We receive only the confirmation and its transaction ID, which is all we need to credit your balance.

Yes. Send the request from your registered mobile number and we verify you first, usually with a one-time code. The file then goes to that same number.

While your account is open, plus the retention window local record-keeping rules set. That window differs by country, so we confirm the exact period when you ask.

Our support desk, through chat or email. Give the mobile number on the account and the field you want corrected; we log the change and confirm it back to you.

It can, when a payment rail or a local rule shifts. When that happens we post the new wording on this page and flag it inside your account, before your next session.
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.