Casino / Slots
At gbd66, we keep this policy straightforward so you always know what data we hold, why we hold it, and how you can act on it. Access to our services depends on your local law and eligible regions — this policy covers how we handle your information within those boundaries.
When you open an account with us, we collect the details you provide at registration — your name, contact information, and the credentials you set. When you use payment routes such as bKash, Nagad or Upay, we record transaction references to match deposits and withdrawals to your account wallet. We do not store full wallet credentials on our side; those remain with the payment provider. We also collect device and session data — browser type, IP address and session timestamps — to keep your account secure and detect unusual activity. This data helps us verify that the person accessing your account is you. Where local law requires identity verification, we may request supporting documents; we hold these only as long as the relevant obligation exists. We use your contact details to send account notices — login alerts, transaction confirmations and policy updates. We do not use your contact details to send unsolicited commercial messages unless you have opted in. Your eligibility to use gbd66 depends on your local law and the eligible regions we serve; this policy applies within those parameters. If you have questions about what we hold, see the contact routes in the Support section below.
This policy applies to all data we process when you interact with gbd66 — from first login through to account activity and support contact. Some areas fall clearly inside it; others sit with third-party providers who run their own policies. Understanding the boundary helps you know where to direct a query.
Login records, session history and security events on your gbd66 account are covered in full. If you notice an access event you did not initiate, use the account security route to raise it with us directly.
Transaction references for bKash, Nagad and Upay payments are recorded in your account wallet history. The data we hold is the reference and amount; the payment provider holds the instrument details under their own policy.
Browsing behaviour on gbd66 pages — which sections you visit, how long you spend — is captured in aggregate for site improvement. This data does not identify you by name and is not shared with advertisers.
Game content from studios in our lobby and external links you follow operate under those parties' own terms. gbd66 does not control how those services handle data once you leave our domain.
You have concrete options when it comes to the data gbd66 holds on your account. Reviewing your account details is the first step — log in and check the personal information section to see the name, contact details and payment records currently on file. If something is wrong or out of date, you can submit a correction request through the support route; we will update the record once we have confirmed your identity. If you want to know exactly what data we hold beyond what is visible in your account, you can send a written data request to our published contact address and we will respond within the timeframe set by applicable rules. You can also ask us to delete data we no longer need to hold for legal or security reasons; we will assess this against any retention obligation that applies and inform you of the outcome. For any of these actions, having your registered contact details and account reference ready will make the process quicker.
Log into your gbd66 account and open the personal information section. Your name, contact details and transaction history are listed there; check them against what you expect to see.
If any field is wrong — contact number, name spelling or linked wallet reference — raise a correction request through our support channel with your account reference ready.
Send a written request to our published contact address to ask what data we hold on your account. We will respond within the applicable timeframe and provide a clear summary.
If you are unsure how a particular piece of your data is used, contact us through the support route below. We will answer the specific question rather than point you back to this document.
If you have a privacy question or want to act on any of the rights described above, use the published contact routes below. We will confirm receipt of your message and follow up with the information or action you have asked for. Always include your account reference so we can locate your record without delay.
Open the support chat from your logged-in account page. This is the quickest route for account-level data questions, including correction requests and access queries.
Send a written data request or policy question to our published support email. Include your registered contact detail and account reference in the message.
The Help Centre in your account area contains published policy documents and step-by-step instructions for submitting a data request or account correction.
Our approach to data protection is built around what your account actually needs — nothing more. We do not keep data beyond the period required for account management and legal compliance, and we review retention periods when policy or regulation changes. Your session is secured with standard encryption on login and throughout any transaction flow involving bKash, Nagad or Upay. Cookie use on our site is limited to session management and site-performance measurement; we do not place advertising cookies without your knowledge. If you want to know the current retention period for a specific data type, ask through the support route and we will confirm it.
Your login session and any transaction involving bKash, Nagad or Upay runs over an encrypted connection. We do not transmit account credentials in plain text at any point in the flow.
We use session cookies to keep you logged in and performance cookies to understand how the site is used in aggregate. No advertising cookies are placed without your prior consent.
We hold account data only as long as your account is active or as required by applicable rules. When retention is no longer necessary, we delete or anonymise the record and can confirm this on request.
For changes, deletion requests or any concern about how your data is used, the account support chat and published email address are the two direct routes to the team that manages this policy.
These are the questions we hear most often about how gbd66 handles account data. If your question is not listed here, use the support chat or email contact to get a direct answer from the team.
We do not sell your account data. We share data only with payment processors like bKash, Nagad and Upay to complete your transactions, and with service providers who operate under contract with us. We disclose information to authorities only where applicable law requires it.
Yes. Send a written request through our published email contact with your account reference. We will compile the data we hold on your account and respond within the timeframe set by applicable rules. Your account page also shows the most common records directly.
Log in, open your account details section and check the fields listed there. If anything is incorrect, raise a correction request through the support chat or email contact. Include your account reference so we can locate and update the record without delay.
We keep transaction records — including bKash, Nagad and Upay references — for as long as your account is active and for the period required by any applicable legal or financial obligation. You can request confirmation of the specific retention period for any data type.
We use session cookies to maintain your login state and performance cookies to measure how pages are used in aggregate. We do not place advertising cookies on your device without your prior consent. You can adjust cookie preferences through your browser settings.
This policy applies to data we process when you use our services. Your eligibility to access gbd66 depends on your local law and the eligible regions we serve. If access is permitted in your region, this policy governs how we handle the data generated by that access.