Casino / Live
bk33or is straightforward about the data it holds on you — what gets collected when you open an account, how your bKash or Upay transaction records are stored, and what controls you have over that information. Access to this platform and its features depends on your local law and eligible region.
When you open an account with us, we collect the details you provide directly — your contact information, account credentials and any wallet identifiers you link, such as a bKash or Upay number. We also collect activity data automatically: pages visited, session duration, device type and browser signals. This helps us keep the account working correctly across the devices you use. Transaction records tied to your bKash deposits or Upay transfers are retained for the period required by our internal compliance process. We do not sell or share this data with advertising networks. Where we work with payment processors to route your bKash or Upay transactions, those processors operate under their own data agreements, which we reference in the relevant section below. Cookies and similar technologies are active on the site. They handle session continuity — so the lobby state you left on mobile is where you return to on desktop — and they support our site analytics. You can adjust cookie preferences through your browser settings, though some account functions depend on session cookies to work at all. If you have questions about a specific data point we hold, the support route at the bottom of this page is where to start.
This policy applies to data we process directly through the bk33or platform — your account, your session activity and the transaction references we hold. It does not extend to third-party services you reach through links on our pages, nor does it govern how payment processors like bKash or Upay handle data on their side. Understanding the boundary helps you know where to direct a specific query.
Covered. Login activity, session tokens and account settings you configure through the platform fall within this policy. We hold this data for as long as your account remains active and for a defined period after closure.
Covered. Payment references we receive when you deposit via bKash or Upay are stored in your account record. We hold transaction identifiers, not full wallet credentials. Review these in your signed-in account area.
Covered. Pages you visit, game categories you browse and time-on-page signals are collected through our analytics layer. This data is aggregated and used to improve the lobby experience, not to build individual advertising profiles.
Not covered. Links to external payment apps, game studio interfaces or any off-site destination are governed by those parties' own policies. We have no control over data practices outside the bk33or domain and cannot be responsible for them.
You have real, actionable choices about the data we hold. These are not abstract rights sitting in a document — they are steps you can carry out through your account or by contacting us directly. Start by signing into your account and opening the profile section: personal details, linked wallet references and communication preferences are all visible and editable there. If something looks incorrect — a name, a contact number, a linked bKash reference — you can update it directly in the account settings fields shown on screen. For data you cannot edit yourself, or if you want to understand exactly what records we hold against your account, raise a query through our support route. We will confirm what we hold and, where the request is straightforward, resolve it within a reasonable time. Eligibility for specific data actions may depend on your local law and the region from which you access the platform.
Sign into your account and open the profile page. Your stored contact details, linked wallet references and recent session activity are visible there. This is the fastest way to check what we hold without raising a formal request.
Update your name, contact number or linked bKash and Upay references directly through the account settings fields. If a field is locked for security reasons, contact support with the correction and your account reference number.
If you want a full picture of the data tied to your account, or if you believe something is recorded incorrectly that you cannot fix yourself, write to us via the support channel listed on this page. Include your registered contact detail so we can locate your record.
You can request account closure through support. We will confirm what data is retained after closure, which retention period applies, and when records are scheduled for deletion under our standard process.
If a section of this policy raises a question you need answered, or if you want to act on a data right, the routes below are the ones we monitor. Use whichever channel matches how you normally reach us — we keep the same response process across all of them.
Open the chat widget from any page while signed into your account. Mention that your query relates to the privacy policy so the agent can route it correctly from the start.
Write to our support address listed in the contact section of the site. Include your account reference and a brief description of the data point or right you are asking about.
The help centre accessible from your signed-in account area contains published articles on data, cookies and account record requests. Check there first — many queries are answered without needing to raise a direct ticket.
We keep data handling practical and visible. Your account record, payment references and session history are stored in systems with access controls that limit who inside our operation can read them. Cookies are scoped to the bk33or domain and are not shared with advertising exchanges. Any updates to this policy are published on this page with a revision date at the top, so you can check whether anything has changed since you last read it.
Account data is held while your account is active and for a defined period after it closes, in line with our internal compliance schedule. Transaction references tied to bKash or Upay payments follow the same retention window. You can ask us for specifics through support.
Session cookies keep your account state consistent whether you switch from a mobile browser to a desktop tab. Analytics cookies are aggregated, not personal-profile-level. Adjust or clear them through your browser settings at any time.
Access to your account record is protected by your login credentials. We do not store full wallet numbers from bKash or Upay — only the reference identifiers needed to match a transaction to your account. If you suspect unauthorised access, contact support immediately.
When we update this policy, the revised version replaces the previous one on this page. The date shown at the top of the document reflects when the most recent change was made. Continued use of the platform after a revision means you have had the opportunity to review it.
These are the questions that come up most often when someone reads through this policy. If yours is not here, the support route in the section above is the right place to ask it directly.
We collect the details you enter during registration — contact information and account credentials — plus any wallet identifiers you link, such as a bKash or Upay number. We also collect session and device signals automatically to keep your account working across the devices you use.
We store transaction reference identifiers, not your full wallet number. When you make a deposit via bKash or Upay, the payment processor handles the full credential on their side. We receive and store only the reference needed to match the transaction to your account record.
Start by signing into your account and checking the profile section — most of your stored details are visible there. For a full picture of everything tied to your record, raise a query through live chat or email support with your account reference included.
Open your account settings and edit the relevant fields directly. If a field is locked, contact support with the correction you need and your account reference. We will review it and confirm once the update is made or explain why it cannot be changed.
We do not sell your data to advertising networks. Payment processors like bKash and Upay receive only the transaction data needed to process your deposit or withdrawal. Their handling of that data is governed by their own published policies, which are separate from ours.
After account closure, we retain certain records for a defined period as part of our internal compliance process. Once that period ends, the data is scheduled for deletion. Contact support before closing your account if you want the specific retention timeline explained.
The revision date at the top of this page is updated whenever we make a material change. We recommend checking back periodically. If a change significantly affects how we handle your account data, we aim to notify you through the contact detail registered to your account.