Casino / Slots
bgd78 collects and uses your information only to run your membership and support your access — nothing more. This policy tells you exactly what we hold, why we hold it, and how you can review or update it at any time. Availability of our service depends on your local law and eligible regions.
When you open an account, we collect the details you enter: your name, contact information, and the payment method you choose to link — which may include bKash, Nagad or Upay. We also record session activity to keep your account secure and to resolve any disputes about transactions. Device identifiers and browser signals are logged automatically when you visit; these help us detect unusual access and keep the account interface working on your mobile. We do not sell this data to advertisers. Where local law in Bangladesh or your eligible region requires us to share data with a regulatory authority, we will comply with that obligation and note it in your account record where possible. Retention periods follow the requirements of applicable law; we do not hold personal data longer than necessary. Your wallet transaction references — whether bKash, Nagad or Upay — are stored only for the period needed to verify deposits and withdrawals and to respond to account queries. If you close your account, we retain only the minimum records required by law.
This policy covers everything that happens when you use bgd78 under an active account. It draws a clear line between what we govern and what falls under a third party's own rules — so you know exactly where our responsibility starts and ends. Access to any part of the service remains subject to your local law and the eligible regions we support.
Login activity, session records and any changes you make to your account profile are all covered by this policy. We log these events to protect your account and to give you a clear history if you need to raise a dispute.
Payment references for bKash, Nagad and Upay transactions are stored within the scope of this policy. We use these records only for account verification and to respond to withdrawal or deposit queries you raise with support.
Content you browse — game lobbies, account notices and policy pages — is logged at a session level only. We do not build a profile of your content preferences for sale or for advertising purposes outside our own platform.
If you reach an external service from our platform, that service operates under its own privacy terms. We do not govern how third-party game studios or payment processors handle data on their own systems.
You have concrete actions available to you under this policy — they do not require legal knowledge, just your account credentials and a clear request. Start by logging in and opening the account settings page; your registered contact details and linked payment method are visible there and can be corrected directly. If you believe a record is inaccurate — say, a wallet reference that does not match your bKash or Nagad transaction history — raise it through the published support route and include your account ID. For a broader request, such as asking what data we hold in full or requesting that we delete records no longer needed, send the request to our listed contact address with your account details. We will acknowledge the request and confirm the outcome. Where your request involves data held under a legal-retention obligation, we will explain that limit clearly rather than refusing without reason.
Log in, open account settings and check the details we hold. Contact information and payment method references are visible there. If something looks wrong, note the discrepancy before contacting support.
Minor corrections — name spelling, contact number — can be updated directly in account settings. For changes that affect your verified wallet link, such as a bKash or Nagad number update, contact support with your account ID.
If you want to know specifically what we hold about you, send a written request to the contact address listed in this policy. Include your account ID so we can locate your records promptly and respond with specifics.
For any privacy concern that account settings cannot resolve, the support route below is the right path. We do not route privacy queries through a general chat queue — use the published contact address for documented requests.
Privacy queries need a documented trail. We keep a dedicated contact path for policy questions so your request is logged and handled separately from general account support. Use the route that matches your query type below.
Send your privacy request to the contact address published on the site. Include your account ID and a brief description of your query. This is the route for data correction, deletion requests and questions about what we hold.
For quick questions about this policy — such as which fields are visible in your account or how a bKash transaction reference is stored — use the live chat available when you are logged in. Complex requests should be followed up by email.
Many routine checks start here. Open the account settings page while logged in to review your registered details, linked wallet method and any active session information before escalating to a formal privacy request.
Keeping your account data safe is an operational requirement, not a marketing promise. Here is how we approach each area so you can check our practice against what you experience in your account.
We use cookies to keep your session active and to remember your account state between visits on mobile. We do not use third-party advertising cookies. You can adjust cookie settings in your browser, though some account functions depend on session cookies being active.
bKash, Nagad and Upay transaction references are stored in encrypted form. We do not store full wallet credentials on our systems. Your payment reference is used only to match deposits and withdrawals to your account record.
We keep your account data for as long as your account is active and for the minimum period required by applicable law after closure. We do not retain data beyond that period, and we do not archive it for commercial use after the legal-retention window closes.
If this policy changes in a way that affects how we use your data, we will post a notice in your account area before the change takes effect. Continuing to use the account after that date means you have seen the updated terms.
These are the questions we receive most often about how bgd78 handles your personal data. If your question is not here, use the email support route listed above.
We collect the contact details and identity information you enter during registration, plus session and device data logged automatically. Payment method references — such as your bKash or Nagad link — are stored to match transactions to your account. We do not collect data beyond what is needed to run the account.
Yes. Log in and check account settings first — your registered details and linked wallet information are visible there. For a full record of what we hold, send a written request to the published contact address with your account ID. We will respond with specifics.
Transaction references for bKash, Nagad and Upay are stored in encrypted form and used only to verify deposits and withdrawals. We do not store your full wallet credentials. The reference is accessible to the account support team when you raise a transaction query.
We do not sell your data. We share it only where required by applicable law or with payment processors needed to complete a transaction. Third-party game studios do not receive your personal account data. Where sharing is legally required, we note it as clearly as the obligation allows.
For simple corrections, use the account settings page directly. For deletion requests or corrections that affect your verified wallet link, contact support by email with your account ID. We will confirm receipt and explain any retention limits that apply under law.
This policy applies to your bgd78 account regardless of where you access it. However, eligibility to use the service depends on your local law and the regions we support. If your jurisdiction restricts access, that restriction applies regardless of this privacy document.