Casino / App
456ba collects and uses account data only to operate your account, process transactions through bKash, Nagad, and Upay, and keep your session secure. This policy tells you exactly what we collect, why we hold it, and what you can do about it — availability of our services depends on your local law and eligible regions.
When you open an account on 456ba, we collect the information you provide during registration — your name, contact details, and the credentials you set. When you fund your account using bKash, Nagad, or Upay, our payment processing layer records the transaction reference and amount to reconcile your wallet balance. We do not store your full mobile banking PIN or password; only the transaction identifiers our system needs to confirm a completed transfer reach our records. Beyond registration and payment data, we collect standard session information: device type, browser version, IP address, and pages visited. This helps us serve the correct version of the site to your device and investigate any account access issue you raise with support. We also use cookies to keep your session active between pages and remember your account preferences. You can review cookie behaviour through your browser settings at any time. We retain your account data for as long as your account remains active and for the period required by applicable rules in your region. If you close your account, we will tell you what is retained, for how long, and the reason for each category. Access to our platform depends on your local law and the eligible regions we serve.
This policy applies to every interaction you have with 456ba through the website — from first visit to active account use. It does not govern third-party services that open in a separate window or app, even if you reach them through a link on our site. The four areas below define the boundary clearly so you know when 456ba's obligations apply and when a separate party's terms take over.
Any data you enter during login, registration or account settings changes falls under this policy. That includes the email address, password hash and any verification step visible in your account area. We control this data directly and apply the rules stated here.
Deposits and withdrawals processed through bKash, Nagad, or Upay generate transaction records on both our system and your mobile wallet provider's system. Our policy covers our copy of those records. The wallet provider's own privacy terms govern their copy independently.
Pages, game lobbies, sports markets and any content rendered inside the 456ba domain are covered by this policy. Your browsing behaviour within those pages — which sections you open, how long you spend — is logged and subject to the retention rules described here.
Game studios whose titles appear in the lobby operate their own data environments. If a game engine contacts a studio's server to run a round, that interaction is governed by the studio's own policy, not ours. We do not share your personal account details with studios beyond what a session token requires.
You are not a passive subject of this policy — there are concrete steps you can take at any time. If you want to see what data we hold on your account, raise a request through the support contact route and we will supply a summary of your stored records. If any detail is wrong — a name spelling, a contact number, an address entry — you can ask us to correct it, and we will update the relevant field after confirming your identity through the account verification path shown in your settings. If you believe we are holding data we no longer need, you can ask us to review the retention basis. We will check against our obligations under applicable rules and tell you the outcome. Use the published support routes described in the Support section of this page; do not send account data through unverified channels. Your rights depend on applicable local law and the eligible region your account is registered under, and we will always tell you if a requested action is limited by those rules.
Submit a data access request through support. We will supply a summary of the personal information stored against your account, including registration data and the transaction references linked to bKash, Nagad, or Upay deposits.
If your name, contact number, or any other field is recorded incorrectly, raise a correction request. We will verify your identity through the step shown in account settings before making any change to your stored record.
If you believe we are holding data beyond the period we described, ask us to review it. We will check the retention basis against applicable rules and respond with the specific reason we are keeping each data category.
All privacy-related requests go through the contact routes published on this site. Keep your account reference ready when you write — it allows our team to locate your records without asking for sensitive details over an open channel.
Privacy questions, data access requests, and correction notices should go through the contact routes listed below. These are the paths visible on the 456ba site — we do not ask you to send account credentials through any channel not listed here. For any request involving bKash, Nagad, or Upay transaction records, include the transaction reference shown in your account history so our team can locate the correct record quickly.
Open the chat widget from any page on the site. State your account reference and describe your privacy request. A team member will confirm receipt and tell you the next step.
Send your written request to the support email address published on the Contact page. Include your registered email address and the nature of the data request so we can route it to the right team.
The Help Centre linked in your signed-in account area contains the current contact form for data and privacy requests. Using the form ensures your request is logged with a reference number for follow-up.
We approach data handling through four areas: what we collect and store, how cookies work on the site, how your account session is kept secure, and who to contact if something needs to change. Each area has a specific route so nothing is left to a vague promise.
Account registration data and transaction references — including records from bKash, Nagad, and Upay transfers — are stored on servers restricted to authorised system processes. We do not sell or share personal records with advertising networks. Retention periods follow applicable rules in your region.
We use session cookies to keep you logged in as you move between sports markets and the casino lobby. Preference cookies remember your account settings between visits. You can clear or block cookies through your browser at any time; doing so will require you to log in again on your next visit.
Your account session uses an encrypted token that expires after a period of inactivity. If you access 456ba from a shared device, use the sign-out option visible in the account menu before leaving the device. We do not store your mobile banking credentials — only the transaction reference your wallet provider returns after a completed transfer.
If this policy changes in a way that affects how we use your data, we will post a notice in the account area before the change takes effect. You can request a plain-language summary of any update through the support contact routes described in the Support section above.
The questions below cover what real account holders ask when they read this policy for the first time. If your question is not answered here, use the support contact routes in the Support section above.
We collect the name, contact details, and login credentials you enter during registration. When you use bKash, Nagad, or Upay, we record the transaction reference returned by your wallet provider. We also log standard session data — device type, browser, and IP address — to manage your account access securely.
We pass only the session token needed to run a game round. We do not share your name, contact details, wallet information, or full account record with any studio. Each studio operates its own data environment under its own policy; we have no control over how they handle the session token on their end.
Retention after account closure depends on applicable rules in your region. We will tell you the specific period and the reason for each data category when you request closure. If you want that information before you decide to close, raise the question through live chat or the support email published on the Contact page.
Yes. Send a correction or deletion request through the support contact routes on this site. Include your account reference. We will verify your identity through the step shown in your account settings before making any change, and we will tell you if a deletion request is limited by applicable retention rules in your region.
Session cookies keep you logged in as you move between pages. Preference cookies store your account settings between visits. We do not use third-party advertising cookies. You can clear or block all cookies through your browser settings at any time — this will log you out and reset your saved preferences on the next visit.
Contact us immediately through live chat or the support email address on the Contact page. Provide your account reference and the details of what you noticed. Do not share your password or mobile banking credentials in your message. We will investigate and update you through the contact method you used to raise the issue.