Sports / Casino
bd44com is straightforward about what data we collect, why we collect it, and how you stay in control of it. This policy sets out our obligations to you and the choices available to you — access and use depend on your local law and eligible regions.
When you open an account with us, we collect certain information to make that account work — your registration details, the payment methods you connect (such as bKash, Nagad, or Bank Transfer), your transaction history, and the device and browser you use to access the platform. We collect this information for one practical reason: to operate your account, process your wallet activity, and respond to your support requests. We do not sell your personal data to third parties. We do not share it with advertisers. Where we work with third-party service providers — for example, payment processors handling your bKash or Nagad transfers — those providers are bound by data-handling obligations that limit how they may use what we pass to them. We store your account records for as long as your account remains open and for a period after closure as required by the applicable rules governing our operations. You can ask us what we hold, ask us to correct something that is wrong, and ask questions about how your data moves through our systems. All of those requests go through the contact route described in the support section of this policy. Availability of this service and the rights described here depend on your local law and eligible regions.
Not every interaction on or around the platform falls under the same data rules. Understanding the boundary helps you know which questions to bring to us and which to take elsewhere. The four areas below set out what sits inside this policy and what falls outside it.
Any data created when you register, log in, or update your account details is covered by this policy. That includes your contact information, password records and the authentication steps you complete each session.
Records of deposits and withdrawals made through bKash, Nagad, Rocket or Bank Transfer sit within scope here. However, the payment provider's own privacy terms also apply to data they handle on their side of the transfer.
The game sessions you start, the categories you browse and the tables you open are logged at account level under this policy. We use that activity data to keep your session running correctly, not to profile you for external advertising.
If you follow a link away from bd44com — for instance to a payment app or a game provider page — that destination has its own privacy terms. We are not responsible for how external sites or apps handle your data once you leave ours.
This policy is not only a statement of what we do — it is also a description of what you can do. You have concrete actions available to you, and we want those to be findable without hunting. First, you can ask to see the personal data we hold against your account. Second, if something is recorded incorrectly — a name, a contact number, a linked wallet identifier — you can ask us to correct it. Third, you can raise a question about how a specific piece of your data is being used, and we will respond through the same support channel you already use. Fourth, if your account is closed, you can ask what data is retained and for how long. Each of these requests is handled through the contact route shown in the support section below. We aim to respond to data enquiries in a reasonable time, though the exact period depends on the nature of the request. None of these rights override the legal or regulatory obligations that require us to keep certain records. What they do is give you visibility and a clear route to raise concerns.
Ask us to provide a summary of the personal data held on your account. We will confirm what categories of data we store and, where practical, give you access to review them.
If your name, contact details or linked payment identifier contains an error, contact support with the correct information and we will update the record after verifying it belongs to you.
Not sure how a transaction log or session record is being used? Send the question through our support route and we will explain how that data category is handled within our systems.
After an account is closed, certain records are retained. You can ask which ones and why. We will explain the retention basis in plain terms, referencing the applicable obligations that apply in your eligible region.
If you have a question about this policy, a request about your data, or a concern you want to raise, there are clear routes to reach us. Use the channel that suits you — we handle privacy-related messages the same way we handle account support requests.
The live chat option is visible once you are signed in to your account. Use it to ask a privacy question or submit a data request directly to the support team.
Send a written request or detailed query to the support email address published on the Contact page of this site. Written requests are useful when you want a record of the exchange.
The Help section inside your signed-in account area carries answers to common privacy questions and a form you can use to submit a data access or correction request without leaving the platform.
We approach data handling as an operational discipline, not just a compliance exercise. The practical details below describe how your information is protected at each stage of its life on our systems.
We use cookies to keep your session active, remember your account preferences and measure how pages load on your device. You can manage cookie settings through your browser. Disabling certain cookies may affect how the account area functions.
Your password is stored in encrypted form. We do not display it to support staff. If you suspect your account has been accessed without your permission, contact support immediately using the live chat or email route shown above.
We keep your account records while your account is open. After closure, records are retained for the period required by the obligations applicable to our operations in eligible regions. We do not retain data longer than those requirements demand.
When this policy changes in a way that affects your rights, we update the published version on this page and note the revision date. Continuing to use your account after a published update means you have seen the current version.
The questions below cover what we get asked most often about data, account records and how this policy works in practice. If your question is not here, use the support routes described in this page.
We do not sell or share your data with advertisers. We pass limited data to payment processors — such as those handling bKash or Nagad transfers — only as needed to complete your transaction. Those processors are bound by their own data obligations.
Submit a data access request through the Help section inside your signed-in account, or send the request by email to the address on our Contact page. We will confirm what categories of data we hold against your account and how to review them.
After closure, we retain records for the period required by applicable obligations in your eligible region. You can ask us which records are kept and why by contacting support after your account is closed. We do not retain data beyond what those obligations require.
Yes. Payment transaction records — whether through bKash, Nagad, Rocket or Bank Transfer — are stored within our account systems and are not exposed to staff outside the roles that need them. The payment provider also holds records on their side under their own privacy terms.
Yes. If your name, contact number or wallet identifier is recorded incorrectly, contact support with the correct details. We will verify the update belongs to your account before making any change, then confirm once the correction is done.
This policy describes how we handle data for accounts registered through bd44com. Your ability to hold and use an account, and the specific rights available to you, depend on your local law and the eligible regions covered by our operations at the time you use the platform.