App / Casino
44cb publishes one written policy for the data behind your account, from the email you register with to the records created when you move money through bKash, Nagad, Rocket, Upay or Bank Transfer. Read it once before you open an account, and treat access as something your local law and eligible regions decide.
Privacy is a working promise on our side, not a slogan. When you open an account we collect what the account needs to run: your email address, your device and browser details, your sign-in activity, and the transaction records built from bKash, Nagad, Rocket, Upay or Bank Transfer movements. We use that to keep your wallet accurate, to answer your questions about a specific record, and to meet whatever record-keeping duties apply where you live. We do not sell your data, and we do not pass it to advertisers to build profiles about you. Sharing is limited to the providers that keep the account working — payment processing, hosting and support tooling — and only as far as the task requires. Your local law and eligible regions set how far those duties reach, so the practical scope can differ for someone signing in here and someone signing in while travelling. We give you the general position; your account area shows the steps that apply to you. When this policy changes, what you read on this page is the current version. Keep it as your reference for asking us anything about the data we hold on your account.
Not everything you touch here sits inside this policy. Anything tied to your account — the email you register with, the wallet balance, your session activity — is covered. So are the transaction records we create when money moves through bKash, Nagad, Rocket, Upay or Bank Transfer. The games you open and the pages you read are covered for the data we collect while you are signed in. Outside the scope are the services other companies run for you. When you tap into a wallet app, a bank page or a payment provider's own screens, their policy governs what happens next, not ours. A link we publish to a third-party page works the same way. Your browser privacy controls and the settings on your handset sit with you as well. That split matters when a question comes up. Bring anything inside your account to us, and take anything that happens on a partner's screen to that partner. Where access depends on local law and eligible regions, both halves follow the same rule: we describe the general position, and your own jurisdiction decides the detail.
Your email address, your login details, your session activity and the wallet balance shown inside your account sit inside this policy. We keep them so you can sign in, check what you hold and follow the steps your account area asks of you. If a detail looks wrong, that same area is where the fix starts.
Every funding or withdrawal record created through bKash, Nagad, Rocket, Upay or Bank Transfer becomes part of your account history. We keep it to reconcile your wallet, to answer a query about one specific movement, and to meet record-keeping duties. Your own view of that history lives in your account area.
Gameplay activity, the pages you open and the device you open them on are handled under this policy while you are signed in with us. We use that to run the site, keep your session working and notice behaviour that looks unusual. It does not follow you once you leave our pages.
Wallets, banks and payment partners run their own platforms under their own terms. Anything you enter on their screens is governed by their policy, not this one. Our part ends at the handover, so read their terms before you confirm a transfer in their app or on their page.
You are not stuck waiting on us to act. Sign in and your account area shows the wallet, the transaction history and the profile fields you filled in at registration, so the same screen lets you check them yourself. If your email address or mobile number changes, update it there. When a movement in your history does not match what you expected, write down the date and the amount before you contact us. One small step like that saves a round of messages. Anything to do with this policy — what we hold, why we hold it, who sees it — can go through the support route linked from the site, and we will treat it as a policy question. Where the law in your region gives you a right to ask for a copy, a correction, or a deletion of what we are not required to keep, say plainly which one you want. We will tell you what we can do, what we must keep, and what your local law and eligible regions decide.
Sign in and open your account area to see the wallet balance and the history built from your bKash, Nagad, Rocket, Upay or Bank Transfer activity. Checking it yourself is the quickest way to confirm a movement landed as you expected before anything else happens.
If your email address or mobile number changes, update the field in your account area so our messages reach you. The same page shows which details you can edit yourself and which ones need a message to support before we change them on our side.
Write in through the support route linked from the site and ask what data we hold on your account, why we hold it, or how a particular record was created. Name the account and the period you mean, and we will answer the policy point directly.
Where the law in your region gives you a right to a copy, a correction or a deletion, say which one you want in your message. We will explain what we can action, what we are bound to keep, and how your local law and eligible regions affect the outcome.
Policy questions run through the same places you already use for account help, so there is no separate desk to find. If the question is about a record, a balance or a profile field, start inside your account: the signed-in area shows what we hold, which gives you the detail you need to describe the exact entry you mean. If you would rather write, use the support route linked from the site and put your account email, the date and the amount in the first message. That is usually enough for us to locate the record without a back-and-forth. Mark anything about this policy itself — what is collected, how long we keep it, who receives it — and we will handle it as a policy query. Our contact routes are published on the site and stay there. We will not ask you to message an unknown number or a personal account. If someone contacts you claiming to represent us and asks for your password, a code, or a payment outside the app, that is not us — report it through the published route.
Log in and open your account to see the wallet, the transaction records and the profile fields we hold. Most policy questions start and end here, because the data is on screen and you can point at the exact entry you want explained. Take the date from that screen before you write.
Write to us through the support route linked from the site, using the email address on your account. Give the date and the amount when a transfer is involved, and mark policy questions clearly so your message reaches someone who handles data rather than gameplay.
When a step happens inside a wallet or bank screen — bKash, Nagad, Rocket, Upay or a Bank Transfer confirmation — that provider's own help channel handles it, and we will say so rather than promise something we cannot see. Bring us the reference afterwards.
Data handling is a set of habits here. Registering gives us your email; using the account adds device and browser details, sign-in activity, and the payment records created through bKash, Nagad, Rocket, Upay or Bank Transfer. None of it goes to advertisers, and we do not sell it. Where a partner must see part of it — a payment processor confirming a move, a hosting provider keeping the site up — we limit what they receive to the task in front of them. The quiet work happens through cookies. They keep you signed in, hold your language setting and show us whether a page loaded properly on your phone. You can clear or block them from your browser at any time. We hold account data while your account is open and for whatever period the applicable rules require after that, then clear what is no longer needed. To see what we hold, correct something, or ask us to delete what we are allowed to delete, write through the support route and say which request you are making.
Registering gives us your email address. Using the account adds device and browser details, sign-in activity, and the transaction records from bKash, Nagad, Rocket, Upay or Bank Transfer. That set is what we work from when you ask us about a movement on your wallet.
Cookies keep your sign-in active, hold your language choice and show us how a page performed on your handset. You control them from your browser settings. Blocking them is your call, and some parts of the account flow may stop behaving the same way.
Your password belongs to you, and you can change it from your account area whenever you want. No one from us will ask for it in a message, and nobody legitimate will request a code or a payment outside the app. Report anything that looks like that through the support route.
We hold account data while your account runs, and for the period the applicable rules require afterwards, then clear what is no longer needed. To ask for a copy, a correction or a deletion, write to us through the published support route and we will set out what we can do.
These are the policy questions we get asked most often, answered in the same plain wording we use everywhere else on the site. If yours is not here, the support route linked from the site will reach the team that handles account data.
We hold the email address you registered with, the device and browser details your sessions produce, your sign-in activity, and the transaction records created when you fund or withdraw through bKash, Nagad, Rocket, Upay or Bank Transfer. Most of it is visible to you inside your account area once you sign in.
Yes, where the law in your region gives you that right. Send the request through the support route linked from the site and say plainly that you want a copy of your account data. We will explain what we can provide and anything we are bound to keep.
Sign in and update whatever the account area lets you edit, such as your email address or mobile number, so our messages reach you. For a field the page does not let you change, write through the support route with the correction and the reason behind it.
Only the record we create on your account. When you confirm a transfer inside a wallet app, a bank page or a payment provider's screens, that company's policy governs the session. Bring us the reference afterwards and we can explain the entry that appears on your side.
Account data stays with us while your account is open, and for whatever period the rules that apply to us require afterwards. Once that ends we clear what is no longer needed. If you want to know whether one specific record is still held, ask us through the support route.
Use the support route linked from the site and mark the message as a policy question, including your account email. If it concerns a wallet movement, add the date and the amount so we can find the record. There is no separate desk to chase.