Casino / Sports
At bet266, your information — including the details you provide when connecting through bKash, Nagad, or Rocket — is handled with clear rules about what we collect, why we collect it, and how you can review or update it. Access and eligibility depend on your local law and the regions where this service is available.
This policy sets out how bet266 collects, uses, and retains information tied to your account. When you register and link a local payment method — bKash, Nagad, or Rocket — we receive the transaction reference and wallet identifier needed to process your deposit or withdrawal request. We do not store full wallet credentials on our servers; the payment rail handles authentication on its own platform. Beyond payment context, we collect the email address and device identifiers you provide at registration, plus session logs that help us detect unusual access patterns on your account. We use this data to operate your account, respond to support requests, and meet any reporting obligations that apply in the regions where we are permitted to operate. We do not sell your personal data to third parties for marketing purposes. Retention periods vary by data type: session logs are kept for a shorter window, while account identity records are held for as long as your account remains active and for a period after closure as required by applicable rules. This policy applies to accounts opened through bet266 and is subject to the laws of the jurisdiction governing your eligible region.
Payment reference only
Transaction context stored
Wallet ID for reconciliation
Account identity and support
Not every interaction with bet266 falls under the same data rules. The table below distinguishes what this policy covers directly, what sits with a third-party service, and what falls outside our control entirely. If you are unsure whether a specific data point is covered, the support route in the section below is the right place to ask.
Registration details, login history, and device identifiers collected when you open or use your bet266 account are fully within this policy's scope.
Payment references from bKash, Nagad, and Rocket are stored for reconciliation. The payment platforms themselves govern how they handle your wallet data on their side.
Browsing behaviour on bet266 — pages visited, game lobby navigation, session duration — is logged by us and covered here, including cookie use described in the trust section below.
Links to external sites, game studio interfaces, and any third-party tools operate under their own privacy terms. We do not control or take responsibility for those data practices.
You have concrete options when it comes to the data we hold on your account. Reviewing what we store, correcting an error, or raising a question does not require legal language — it requires knowing the right path inside your account or through our support channel. Start with the account settings area, where your registered email, contact details, and linked payment references are visible. If something looks wrong, you can submit a correction request directly through the support route. For data that cannot be changed through self-service — such as historical transaction references tied to a bKash or Nagad payment — contact us in writing and we will confirm what we hold and what can be amended within the rules that apply to your region. If you want to close your account and understand what happens to your data after closure, that process is also handled through the same support channel. Response times depend on the nature of the request and the verification steps required.
Open the account settings page to see the personal details and payment references currently held against your profile.
Submit a correction through the support channel if your registered name, email, or contact information needs updating.
Use the published support route to ask what specific data we hold, how long we keep it, or whether a particular record can be removed.
Contact support to initiate account closure and receive confirmation of what data is retained after the account is deactivated, in line with applicable rules.
If you have a question about this policy, want to review the data we hold, or need to raise a concern, use the contact routes published on bet266. We do not handle privacy requests through social media or unofficial channels.
Open the chat widget on bet266 to reach the support team directly. State that your query is about account data or this privacy policy so it is routed correctly.
Send your privacy or data request to the email address listed in the Contact section of bet266. Include your registered email so we can locate your account record.
The help centre on bet266 covers common data and account questions. Check there first — many requests about reviewing or updating details can be resolved without contacting support.
Understanding the mechanics behind this policy helps you make informed choices about your account. Here are the four areas that matter most to how your data is handled day to day.
We use session cookies to keep you logged in and functional cookies to remember your lobby preferences. Analytics cookies track aggregate page behaviour. You can manage cookie preferences through your browser settings; disabling functional cookies may affect how your account session behaves.
Login attempts, device identifiers, and IP addresses are logged to detect unauthorised access. If we detect an unusual login pattern on your account, we may prompt re-verification through your registered email before restoring access.
Active account data is held for as long as your account is open. After closure, identity and transaction records are retained for the period required under the rules applicable to your eligible region, then deleted or anonymised.
To request a correction, deletion, or export of your data, contact us through the published support route with your registered email. We will confirm receipt and outline the steps and timeline that apply to your specific request.
These are the questions we hear most often about how bet266 handles account data. If your question is not here, the support route in the section above is the right next step.
We collect the email address and contact details you enter at registration, plus the device identifier and IP address associated with your session. If you link a local payment method like bKash or Nagad, we store the transaction reference returned by that payment platform — not your full wallet credentials.
We do not sell your data to third parties for marketing. We may share data with payment processors like bKash, Nagad, or Rocket to complete a transaction, and with service providers who operate parts of the platform under confidentiality obligations. Any sharing is limited to what is needed to run your account.
Open your account settings page on bet266 to view the personal details and payment references currently stored. For a fuller picture of what we hold — including session logs or historical records — submit a request through the published support channel with your registered email address.
Yes. Contact support through the routes listed on bet266 and request account closure along with data deletion. We will confirm what can be removed immediately and what must be retained for the period required under the rules applicable to your eligible region before deletion.
This policy applies to accounts opened through bet266. Whether you can access the service depends on your local law and the regions where bet266 is permitted to operate. If you are in Bangladesh, check the eligibility information on the site before opening an account.
Go to account settings on bet266 to edit the details you can update through self-service. For changes that require identity verification — such as updating the name on your account — contact support through the published email or live chat route and follow the verification steps they outline.