Reference

What Our Privacy Policy Covers

This policy tells you exactly what bge333 collects when you open an account — your mobile number, sign-in records, and the bKash, Nagad or Rocket reference behind each wallet movement — and what we do with it afterwards.

Sign-in recordsWallet referencesCookie and device dataDeletion requests
bge333 What Our Privacy Policy Covers
SECURITY AND RETENTION

Open the Settings That Control Access

Account security starts with the sign-in check, not with the policy text. Your password, your one-time code and your device history work together: a login from a handset we have not seen triggers a fresh code to your registered number. Cookies do the lighter work — they keep you signed in on your own browser and remember your language choice, without holding your wallet details. Clear them and the session ends, which is exactly what you want on a phone you share with family.

Sign-in checks

One-time codes go to the mobile number on the account only. A new handset or browser triggers a fresh code, which is the step that keeps a borrowed phone from becoming a borrowed account.

Cookies and device data

Session cookies keep you signed in on your own browser and remember your language setting. Clearing them ends the session, so a shared or resold handset never carries your account into someone else's hands.

Retention windows

Wallet and payout records stay longer than browsing logs because payment disputes can surface later. When a record passes its retention point we delete it, and we do not keep copies for marketing purposes.

Contact and changes

The support tab is the single route for corrections, copies and deletions, and it logs each request. If a detail on your account is wrong, tell us there and we correct it at source.

PRIVACY CONTACT PATHS

Reach Support About Your Data

You do not need to write a long email to get a data question moving. Open your account on your phone, head to the support tab and pick the privacy option — the chat window carries your account ID with it, so you will not be typing your number and wallet reference twice. The same desk handles wallet verification questions from Bangladesh players, which means one thread can cover both a payment record and a data request. Ask for a copy, a correction or a deletion, and quote the reference you see in your wallet app so the record can be matched without guesswork.

Team online

In-account chat

Sign in, open the support tab and choose the privacy option. Your account ID and bKash, Nagad or Rocket references attach to the message, so the team can locate the right record on the first reply.

Wallet proof requests

If a deposit or withdrawal reference needs checking, send the transaction ID from your wallet app. We match it against the account wallet ledger, so a disputed balance settles without anyone asking for your PIN.

Deletion and copy requests

Ask for a copy of your account data or a deletion in the same chat. We confirm it on your registered mobile number, then tell you what was removed and what we still have to keep.

Questions You Ask About Your Data

The six questions below come up most often in our support chat. Each answer is written so you can check it against your own account — open the support tab, quote the reference you see, and the team can pull the same record we describe here. If your question is about one specific wallet movement, say that at the start of the thread. Anything we cannot settle in the chat we confirm by message to your registered number.

Your mobile number, sign-in records, wallet transaction references from bKash, Nagad or Rocket, and gameplay logs such as tables opened and session length. We do not hold your wallet PIN at any point.

Yes. Ask in the support tab and we confirm the request on your registered mobile number. You get the copy in the same chat thread once the identity check clears.

Only what a transaction needs — the reference, the amount and the account it belongs to. bKash, Nagad and Rocket process the money; we never pass on your wallet PIN or your full login details.

They keep you signed in on a browser you have used before and remember your language choice. Clear them and the session closes, so the next login asks for a fresh one-time code.

You can ask. We verify the request on your registered number, close the account wallet, then delete what retention rules allow. Payment records may stay longer where a dispute could still be raised.

Storage and access rules follow the law where you live, so availability depends on your local law and eligible regions. If your region is not eligible we do not open an account or keep the data.
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.