Sports / Slots
43ok handles your information with a clear and documented approach — what we collect, how we use it, and the choices available to you are all set out here. Access and eligibility depend on your local law and the regions where this platform operates.
When you create an account on 43ok, we collect the information needed to operate that account — your registered name, contact details, login credentials and any wallet identifiers linked to your payment methods, including bKash, Upay or Bank Transfer. This data is used for account authentication, transaction processing and communicating with you about your account status. We do not sell your personal information to third parties for their own marketing purposes. Data shared with payment processors — such as those handling bKash or Upay transactions — is limited to what those processors need to complete or verify your transaction. We retain transactional records as required by the obligations that apply to platform operators serving supported regions. Cookies and similar tracking tools are active on 43ok pages. These help us understand how the lobby is navigated, which categories you open and whether your session stays stable across page loads on mobile. You can adjust cookie preferences through your browser settings, though doing so may affect how parts of the site function. By continuing to use 43ok after reading this policy, you acknowledge its terms. Availability of this platform depends on your local law and eligible regions.
This policy covers data processed directly by 43ok across the four areas below. Third-party services linked from our platform operate under their own privacy terms, which we do not control. Review each area to understand what falls inside and outside this policy's reach.
Data collected when you register, log in or update your account details on 43ok falls within this policy. This includes your email address, password hash and any identity verification steps shown in your account area.
Payment data processed when you move funds through bKash, Upay or Bank Transfer is covered here to the extent 43ok handles it. Payment processors themselves operate under their own separate terms and data practices.
Session data, page-view events and lobby navigation patterns collected while you browse the 43ok platform are within scope. This includes which game categories you open and how long your session runs on mobile or desktop.
External links, game studio interfaces from providers like JDB, Habanero or Microgaming, and any off-platform tools operate outside this policy's scope. Those services collect and manage data according to their own published terms.
You have several concrete options regarding your personal data on 43ok. The account settings area is where most of these actions begin — you can review the profile information we hold, correct details that have changed and update contact preferences directly from the fields shown there. If you want a record of the data associated with your account, you can submit a request through our support route and we will respond with what we hold under your registered account identifier. For questions about how a specific transaction record appears — for instance, a bKash deposit that shows an unexpected reference — the support route is the right path. Where local law and eligible-region rules give you a right to request deletion of certain data, you can raise that request formally through the same support channel. We will confirm receipt and handle it according to the obligations that apply in supported regions. We cannot always honour deletion requests where retention is required for transaction compliance or account integrity.
Open the account settings page to see the profile data 43ok holds on your registered account. Fields for name, contact and linked wallet identifiers are visible there.
Update your contact details or wallet reference directly in account settings. For changes that require identity re-verification, follow the steps shown in the account area at the time.
Submit a data query via the support route published on the site. Include your registered account identifier so we can locate your records and respond accurately.
Where local law and eligible-region rules permit it, submit a deletion request through support. We will confirm receipt and advise on which records can be removed and which must be retained.
If this policy raises questions you cannot resolve through account settings, the routes below are the ones we publish. Use the channel that suits how you prefer to communicate — each one connects to the same team handling data and account queries.
Open the live chat widget on the 43ok site while you are logged in. Use this for account-specific data questions or to start a formal data request. Have your registered email ready to confirm your identity.
Send a message to the support email address published in the 43ok help section. For privacy queries, include your account identifier and describe the specific record or action you are asking about.
The help section of the 43ok site carries written answers to common account and data questions. Check there first — many data access and correction questions are answered with step-by-step account navigation instructions.
Security and retention practices on 43ok are built around the requirements of operating a platform that processes bKash, Upay and Bank Transfer transactions in supported Bangladesh regions. Each element below reflects how we actually handle data, not a general statement of intent.
Cookies on 43ok track session state, lobby navigation and login persistence. They do not store payment credentials. Adjust cookie behaviour in your browser settings; note that disabling session cookies may affect login stability on mobile.
Login credentials are stored using one-way hashing — 43ok staff cannot read your password in plain text. If you suspect your account has been accessed without your knowledge, use the account recovery route shown on the login page.
Transaction records — including bKash and Upay payment references — are retained for the period required by the compliance obligations that apply to operators in supported regions. Account data tied to an inactive account may be subject to deletion on request where local rules allow.
When this policy changes in a material way, we update the version date shown at the top of this page. Continued use of the 43ok platform after an update means you have seen the revised terms. Check this page if you want to confirm you are reading the current version.
These questions reflect what people actually ask when they read through the 43ok privacy policy. If your question is not here, the support routes in the section above are the right next step.
We collect your registered name, email address, login credentials and any wallet identifiers you link for payment — such as a bKash or Upay number. We also collect session and navigation data while you use the platform, as described in the cookie section of this policy.
We share data only where necessary to operate the platform. Payment processors handling bKash, Upay or Bank Transfer transactions receive only the data needed to process or verify your transaction. We do not sell personal data to third parties for marketing purposes.
Open account settings while logged in to review the profile information we hold. For a full data record, submit a request through the live chat or email support route. Include your registered account identifier so we can locate the correct records.
Where your local law and eligible-region rules support a deletion right, you can submit a request via the support channel. We will confirm receipt. Some records — particularly transaction references tied to bKash or Bank Transfer payments — may need to be retained under compliance obligations.
Cookies on the 43ok platform manage session state, maintain your login across pages and record lobby navigation patterns. You can adjust or block cookies in your browser settings, but disabling session cookies may affect how reliably the site loads and keeps you logged in on mobile.
This policy covers data that 43ok processes directly. When a game from a studio such as JDB, Habanero or Microgaming loads within the platform, that studio's own data practices may also apply. We do not control how individual game providers handle session data on their side.