Casino / Live
bji66 collects only the account and transaction data needed to run your wallet, process payments through bKash, Nagad and Rocket, and keep your account secure. This policy explains exactly what we collect, why we hold it, and what choices you have — access and eligibility depend on your local law and the eligible regions we serve.
When you open an account with us, we collect the details you provide during registration — your name, contact information and account credentials. When you make a transaction using bKash, Nagad or Rocket, we record the payment reference, amount and timestamp so your wallet history stays accurate and traceable. We also collect device and session data — browser type, IP address and interaction logs — to protect your account from unauthorised access and to keep the lobby running correctly on your phone or desktop. We do not sell your personal data to third parties. Data shared with payment processors like bKash, Nagad or Rocket is limited to what those services need to complete your transaction. We may share account records with regulatory or legal bodies where required by applicable law in the jurisdictions we operate under. Retention periods vary by data type: transaction records are kept as long as required for financial compliance, while session logs are cleared on a rolling schedule. We aim to keep only what is necessary. If you have a question about a specific data category, contact us through the route listed in the support section of this policy.
Payment references and timestamps from bKash transfers are stored in your account wallet record. These are used to reconcile your balance and respond to any dispute you raise about a specific transaction.
Nagad payment data is handled the same way — reference number, amount and date are logged. We do not store your Nagad PIN or full mobile wallet credentials at any point in the process.
Rocket transaction identifiers are recorded against your account for wallet accuracy. If a Rocket transfer shows an unexpected status, the record in your account history is the reference point for any review.
Browser type, IP address and interaction timestamps are held for account security. These logs help us detect unusual access patterns and are not used for advertising or shared with game studios.
This policy covers data we collect and process directly through the bji66 platform — your account, your wallet activity and your session behaviour on our site. It does not extend to third-party services you connect to from our lobby, including the payment apps bKash, Nagad and Rocket, which each operate under their own privacy terms. Understanding the boundary matters: what happens inside your bji66 account is our responsibility; what happens inside your mobile wallet app is governed by that provider's policy.
Login credentials, account profile fields and session tokens created when you sign in are covered. We control how these are stored, how long they are retained and who can access them inside our systems.
Deposit and withdrawal records tied to your account wallet fall inside this policy. The payment journey that takes place inside the bKash, Nagad or Rocket app itself is outside our scope and governed by those providers.
Game studios such as Pragmatic Play, Bigtime Gaming and Spadegaming supply game content to our lobby. Their engines run within our site, but any telemetry those studios collect independently is outside the scope of this policy.
Links, embeds or external services accessible from our site — including any external cricket score feed or affiliate page — are not covered here. Follow the privacy terms of those external services separately.
You have real, actionable choices under this policy — not just abstract statements. Once signed in, you can review the personal details held against your account directly from the account settings page. If any detail is wrong — a misspelled name, an outdated contact number — you can submit a correction request through the support route listed below, and we will update the record after verifying your identity. You can also ask us to explain what data categories we hold for your account and why each one is retained. Where local law in your eligible region gives you the right to request deletion of non-essential data, you can raise that request in writing to our policy contact address. We will acknowledge the request and respond within the timeframe required by the applicable rules. Note that transaction records linked to financial compliance may be subject to mandatory retention periods regardless of a deletion request. If you are unsure which rights apply in your situation, the support section of this page is the right starting point.
Sign in and open the account settings page to see the profile data we hold. Transaction history tied to bKash, Nagad or Rocket payments is visible in your wallet section without needing to contact support.
If your name, contact number or email on file is wrong, send a correction request through our published support route. We verify your identity before making changes to keep your account secure.
You can ask which specific data types we hold for your account. Write to our policy contact with your account reference and we will describe the categories, the retention basis and any third parties involved.
Where eligible under your local law, you may request deletion of non-essential account data. Financial transaction records required for compliance may be exempt. We will confirm the outcome in writing.
If you have a question about how your data is handled, or you want to exercise any of the rights described in this policy, the routes below are the ones to use. We do not publish support hours or response-time promises we cannot verify — what we do publish is where to send your query so it reaches the right team. For account-specific questions, include your account reference so we can locate your records without delay.
Open the support section inside your signed-in account for account-level data queries. This route connects you to the team that handles wallet records, transaction history and account profile corrections.
For formal data requests — corrections, deletion requests or questions about retention — use the policy contact email published in the footer of this site. Include your account reference in the subject line.
For general privacy questions that do not require a formal written record, the live chat route visible on the site can direct your query to the appropriate team. Formal requests should still follow the email route.
Keeping your account data accurate and protected is a practical commitment we make through the way our systems are configured, not just through policy text. Cookies on this site are used for session management and to keep you signed in across pages — not for cross-site advertising. You can manage cookie preferences through your browser settings at any time. For your account, we use standard encryption on data in transit so that information exchanged between your device and our servers is not readable in plain text. Payment data connected to bKash, Nagad or Rocket transactions passes through those providers' own secure channels; we receive only the reference information needed to update your wallet. If you believe your account has been accessed without your permission, change your password immediately from the account settings page and contact support using the route listed above.
We use session cookies to keep your account active while you browse the lobby. No advertising or cross-site tracking cookies are set by us. Manage or clear them through your browser's privacy settings at any time.
Data moving between your device and our platform travels over an encrypted connection. This applies to account login, profile updates and the payment references generated when you use bKash, Nagad or Rocket.
Transaction records are kept for the period required by financial compliance rules applicable to the regions we operate in. Profile data you choose to delete is removed from active systems, subject to any mandatory retention exceptions.
When this policy changes in a material way, we post a notice on the site so you can review what has changed before continuing to use your account. The date of the most recent revision is shown at the foot of this page.
These are the questions about data handling, account records and your rights that come up most often. If your question is not covered here, use the policy contact route listed in the support section above.
We collect the name, contact details and login credentials you enter during registration. Once you are active, we also record session data — device type, IP address and interaction timestamps — for account security. We collect only what is needed to operate your account.
We pass only the transaction-specific information those payment services need to process your request — typically a reference number and amount. We do not share your full account profile, browsing history or game activity with payment providers.
Financial transaction records are retained for the period required by compliance rules in the regions we operate under. Session and device logs follow a shorter rolling schedule. If you want to know the retention period for a specific data category, contact us in writing with your account reference.
Yes. Send a written request to the policy email address published in our site footer, including your account reference. We will confirm the request and respond with the data categories we hold. Availability may depend on your local law and the eligible region you access the site from.
Sign in, go to account settings and check the fields there first — some details you can update directly. For fields that require verification before a change is made, submit a correction request through the published support route and we will update the record after confirming your identity.
Non-essential profile data is removed from active systems when you close your account. Transaction records and any data subject to mandatory financial compliance retention are kept for the required period, even after account closure. We will confirm what is retained when you submit a closure request.