Live / Casino
These terms set out the rules that apply when you open and use a bd368 account. Read them carefully — your access to the platform, your transactions, and how we handle disputes are all governed by what is written here.
By completing account registration on bd368, you confirm that you have read, understood and accepted these terms in full. These terms form a binding agreement between you and bd368 covering every action you take on the platform — including depositing funds via bKash, Upay or Bank Transfer, placing activity, withdrawing a balance, and contacting support. Access to bd368 and the availability of specific features depends on your local law and the eligible regions in which the service operates. If the law in your location does not permit this type of platform, you must not open or continue using an account. We reserve the right to update these terms at any time. When we do, we will indicate the revision on this page. Continuing to use your account after a change has been posted means you accept the updated version. If you disagree with any revision, the correct action is to close your account and stop using the service. For payment-related disputes — including any transaction made through bKash, Upay or Bank Transfer — the transaction record visible in your account wallet history is the reference we use when reviewing a complaint. Keep your account credentials secure; any action taken under your login is treated as your action under these terms.
These terms do not cover everything uniformly. Understanding what falls inside and outside their scope helps you know where to direct a question or dispute.
Rules for creating, verifying and maintaining your bd368 account are fully covered here. This includes login credentials, identity checks requested by the platform, account suspension conditions and how you can request closure of your account at any time.
Every deposit and withdrawal processed through bd368 — whether via bKash, Upay or Bank Transfer — falls within these terms. Disputed amounts, processing instructions and the order in which payments are recorded are all governed by this agreement and the records in your wallet history.
Game content supplied by studios available on bd368, promotional notices displayed on the platform, and any text or media published under the bd368 domain are covered by these terms. You may not copy, redistribute or commercially use that content without written permission.
Payment processors, mobile wallet operators such as bKash and Upay, and banking institutions operate under their own separate terms. bd368 is not responsible for how those third parties process a transaction on their end. Check the relevant provider's own policy for questions about wallet-side behaviour.
These terms are not one-sided. You have clear, practical options available at each stage of your account relationship with bd368. If you want to review what data we hold about your account activity, open the account history section while signed in — your transaction log, including bKash and Bank Transfer entries, is visible there in full. If any account detail is incorrect — name spelling, contact number, linked wallet number — raise a correction request through our support channel before submitting a withdrawal, not after. For billing or payment questions that the account history does not resolve, contact support directly with the transaction reference shown in your wallet. You also have the right to request account closure at any time; once confirmed, we will process the closure and settle any remaining eligible balance according to the steps outlined in the withdrawal section of these terms. We do not make that process difficult — a single written request to support is enough to start it.
Sign in and open the account history page. Every deposit and withdrawal — bKash, Upay or Bank Transfer — is listed with a reference number and timestamp you can use in any support query.
If your registered name, phone number or linked wallet number needs updating, contact support with the correction before your next withdrawal request. Do not attempt a withdrawal while a detail mismatch is unresolved.
Send a written query to our support team referencing the specific clause or transaction you are asking about. Vague queries take longer to resolve; a reference number or date range moves the process forward faster.
A written request to support is all that is needed. We will confirm receipt, settle any outstanding eligible balance, and close the account. You will receive a closure confirmation to the contact address on your account.
If these terms raise a question you cannot resolve by reading this page, the routes below are how you contact bd368 directly. Use the channel that matches your question type — payment disputes go to live chat with your transaction reference ready; account closure or data requests go to email so there is a written record on both sides.
Open the chat widget from any page while signed in. For payment-related queries, have your bKash, Upay or Bank Transfer transaction reference visible before you start the conversation.
Send account or policy questions to the support email address published in your signed-in account area. Email is the correct route for account closure requests and written correction submissions.
The help section inside your signed-in account covers common policy questions, transaction status checks and step-by-step instructions for updating account details without needing to contact support.
We hold account data only for the period required to operate your account and to meet the record-keeping obligations that apply to our service. When your account is closed, data retention follows the schedule stated in our privacy policy, which sits alongside these terms.
We collect and store only the information needed to operate your wallet, process bKash or Bank Transfer transactions and respond to support queries. We do not sell account data to third parties. Your wallet history is accessible to you at any time while the account is active.
bd368 uses session cookies to keep you signed in across pages and to remember your wallet preferences. Functional cookies are required for the account to operate. You can review cookie behaviour in your browser settings, though disabling functional cookies will affect account access.
You are responsible for keeping your login credentials private. Any transaction or action taken under your account credentials is treated as authorised by you under these terms. If you suspect unauthorised access, contact support immediately and change your password from the account settings page.
When these terms are updated, the revised version is published on this page with a note indicating the change. We do not notify by push or wallet message for every minor correction, so checking this page before a large transaction is a practical habit worth keeping.
These answers address the questions most commonly raised about how these terms work in practice. If your question is not here, contact support with the specific clause or transaction reference you are asking about.
Yes. Every transaction processed through your bd368 account — including bKash deposits, Upay transfers and Bank Transfer withdrawals — is governed by these terms. The record in your account wallet history is the reference point for any payment dispute we review.
We update this page when terms change and note the revision here. We do not send individual notifications for every update. It is your responsibility to check these terms before major transactions. Continuing to use your account after a change is posted means you accept the revised version.
After closure we retain account data for the period required under our privacy policy and applicable record-keeping obligations. You will not have active access to the account after closure, but you can request a summary of your transaction history before the closure is confirmed.
bd368 covers the platform side of a transaction. If a bKash or Upay issue originates with the wallet provider — network errors, wallet limits, service outages — that falls under the wallet provider's own terms. Contact both bd368 support and your wallet provider with the transaction reference to resolve it.
Open the account history page and locate the transaction reference. Send that reference to bd368 support via live chat or email with a written description of the issue. Do this as soon as you notice the problem — delayed reports make records harder to cross-check on both sides.
Yes. Access to bd368 and the availability of specific account features depends on your local law and the eligible regions in which the service operates. If the service is not permitted under the law applicable in your location, you must not open or use an account.