Reference

Your Privacy Policy, Written Plainly

This page sets out what gdb333 records when you open an account, top up with bKash, Nagad or Rocket, and move through the lobby — and what we never touch.

Account data explainedCookie behaviour spelled outWallet data kept minimalRequest changes anytime

See the lobby Read FAQ

What We Collect and Why

gdb333 Service availability depends on eligible regions and local law. Users should check local rules before opening an account.

We keep the policy narrow on purpose. To run your account we hold your name, mobile number, date of birth and the wallet reference tied to a bKash, Nagad or Rocket transfer, because a cashier desk cannot match a deposit without it. Gameplay records — which

1
tables you opened, session length, device type — help us settle disputes and spot a stolen login before it costs you. We do not ask for your wallet PIN, and you should never send it to anyone claiming to be support. How long we hold each
2
item depends on what it is for: transaction records stay while accounting and dispute rules require them, marketing preferences clear as soon as you switch them off. Your rights over this data, and the exact wording of them, follow the law where you live. Access to
3
gdb333 depends on your local law and eligible regions, so the protections described here apply only where we are permitted to serve you. If you are outside an eligible region, we cannot open an account for you regardless of what you send us.

Service availability depends on eligible regions and local law. Users should check local rules before opening an account.

HOW WE HANDLE IT

Cookies, Logins and Record Keeping

Cookie handling is deliberately boring here. The session cookie holds your login, a preference cookie remembers language and layout, and nothing else follows you around the web from our side. Your login itself runs on a one-time code to your registered mobile — that code is the last gate, so never forward it. Gameplay logs tell us which table you were on if a round is disputed, and wallet references let us match a Nagad or Rocket transfer to your account wallet. When you want something corrected or removed, you ask and we act on the same profile; retention follows accounting and dispute rules, not habit.

Access and Correction

Ask for a copy of what we hold, or tell us a number or name is wrong. We check the request against your account email and registered mobile before changing anything.

Cookie Control

Block or delete cookies in your browser settings. The session cookie will drop and you sign in again; your account and wallet history stay untouched.

Marketing Preferences

Switch off messages about cricket nights or slot features from your account settings. Your transaction and security notices still reach you, because those are part of running the account.

Retention Window

Transaction and gameplay records stay as long as accounting and dispute rules require. After that they are removed or stripped of anything that points back to you.

REACH THE DESK

How to Contact Us About Data

Privacy questions go to a real desk, not a black hole. Write in from the email address on your account so we can match you without asking for extra documents, and tell us the mobile number you registered with. If your request is about a bKash or Nagad payment record, add the transaction reference from your wallet history — that one string usually closes the case on the first reply.

Account Email Send data requests from the address linked to your gdb333 account so we can verify you without collecting anything new. Include your registered mobile number.

Payment Reference For questions about a bKash, Nagad or Rocket record we hold, paste the transaction ID from your wallet history into the message. It speeds up matching.

In-App Support Log in and open the support panel from your account menu. The thread stays tied to your profile, so you do not have to repeat your details each time.

Privacy Questions We Get Asked

These are the ones that land in the support panel most often, answered the way we would answer them at the desk. If yours is not here, send it in from your account email and we will reply in writing.

No. We never see it and never ask for it. A wallet transfer gives us a transaction reference and the sending number, which is all a cashier desk needs to match your deposit. Anyone requesting your PIN is not us.

Yes. Write from your registered account email and ask for a copy of your profile data. We verify the request against your account mobile, then send the details in writing to that same address.

Ask us and we remove what we can. Transaction and gameplay records tied to accounting or an open dispute have to stay for the period the rules set, and we will tell you which items those are.

The profile stays closed rather than erased while retention rules apply. Marketing messages stop as soon as you switch them off, and the security notices tied to the account also end once it is closed.

We share only what a payment or verification step genuinely requires, and only with the parties handling that step. We do not sell your profile, and we do not hand your number to outside marketing lists.

It can, when a payment rail or a rule shifts. The current wording always sits on this page, and a material change is flagged inside your account so you see it before you deposit again.

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.

InfoLegal InfoBangladesh Fast Table 508 InfoGdb333 Banking

Your Privacy Policy, Written Plainly

Cookies, Logins and Record Keeping

How to Contact Us About Data

Privacy Questions We Get Asked

01 Do you keep my bKash or Nagad PIN?

02 Can I see what data you hold about me?

03 How do I get my details deleted?

04 What happens to my data if I stop using the account?

05 Do you share my details with anyone else?

06 Does the policy change?

Privacy Policy

Related pages

Related pages