Live / App
When you create an account with bet622 and use payment methods like bKash or Rocket, we collect certain information to keep your account working and 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 eligible regions.
This policy applies to information we collect when you open an account, log in, browse the game catalogue, or carry out a wallet transaction — including when you use bKash or Rocket to move funds. The information we collect falls into three categories: account identity data (name, contact details, login credentials), transaction data (amounts moved via your linked wallet, timestamps, reference IDs), and usage data (pages visited, game sessions opened, device type used to access the site). We use this data to operate your account, process payments, detect unusual activity, and respond to your support requests. We do not sell your personal data to third parties, and we do not share it with studios such as Spadegaming, PG Soft or Pragmatic Play beyond what is necessary for them to deliver game content to your session. Retention periods vary by data type and are governed by applicable law in eligible regions. You may request a summary of what we hold at any time by contacting our support team through the channels listed on this page. Any updates to this policy are posted here; continuing to use your account after a change means you have seen the updated terms.
Every bKash deposit and withdrawal linked to your account is logged with a reference ID and timestamp. These records are held for the period required by applicable law and are visible in your account transaction history after login.
Rocket transfers are recorded in the same way as bKash entries. The reference number, amount and date are stored against your account and are available for you to review at any time through your account dashboard.
We record login timestamps and the device type used each session. This helps us flag access from unfamiliar devices and lets you verify your own login history. No location beyond region-level is stored without your consent.
Not every service you touch when using bet622 falls under this policy. Understanding the boundary helps you know where to direct a question about your data. The four areas below set out what is inside our policy scope and what sits outside it — particularly for third-party links and payment processors you interact with separately.
Covered fully. All data collected at login, account creation and password reset is governed by this policy. You can review, correct or query this data by contacting us directly.
Partially covered. We hold the transaction record on our side; however, the data held by bKash or Rocket within their own platforms is governed by their respective privacy terms, not ours.
Outside this policy's core scope. Studios such as PG Soft, CQ9 and Pragmatic Play may process session data to deliver game content. Their data practices are defined in their own terms; we do not control that processing.
Not covered. If you follow a link from our site to an external page, this policy stops at the point you leave. We have no responsibility for how external sites collect or use data.
You have several concrete actions available to you regarding the data we hold. These are not abstract rights — each one has a real step you can take right now. Start by logging into your account: your transaction history, wallet records and basic account details are visible there without needing to contact us. If something looks wrong — an incorrect contact detail, an unrecognised transaction reference — you can correct it directly in your account settings or raise it with support. For data you cannot edit yourself, submit a written request via our support channel and we will respond within the period set by applicable law. If your question concerns how a bKash or Rocket record appears in your history, include the reference ID from your wallet app so we can match it to our records quickly. Availability of these actions depends on your local law and eligible regions.
Log into your account dashboard to see transaction history, login timestamps and stored contact details. No request needed — it is visible after authentication.
Update your name, contact number or email directly in account settings. For fields locked after verification, contact support with the corrected detail and we will process it.
Send your question through the support channel shown on this page. Include your account reference and the specific record you are asking about so we can locate it without delay.
Where applicable law in your eligible region permits, you may request deletion of certain personal data. Submit this in writing via support; we will confirm what can be removed and what must be retained under legal obligation.
If you have a question about this policy, want to review the data we hold on your account, or need to report something that does not look right, use the contact paths below. For the fastest response, include your account username and a brief description of the specific record or concern. Our team handles policy-related queries through the same channels as general account support — no separate form is needed.
Open the chat widget from any page while logged in. Mention that your query is privacy-related so the agent can route it correctly.
Send your written data request or policy question to our support email. Include your account reference and the detail you are asking about for a quicker response.
Many records — transaction history, login timestamps, stored contact details — are already visible after login. Check there first before raising a formal request.
We take a straightforward approach: collect only what is needed to run your account, protect it with standard technical measures, and give you clear ways to review or question it. Cookies are used to keep your session active and to remember your login state; you can manage cookie preferences through your browser settings. We do not use cookies to build advertising profiles. Account security measures include session timeouts on inactive logins and logging of device type per session — details visible in your account history. Data retention follows the period required by applicable law in eligible regions; we do not hold personal data beyond that period without a legal basis.
Cookies on bet622 maintain your login session and remember display preferences. No third-party advertising cookies are set by us. Manage them through your browser's cookie settings at any time.
Each login is recorded with a timestamp and device type. Review your login history in your account dashboard after authentication. Flag any entry you do not recognise to support immediately.
We keep your data for the period required by applicable law. Transaction records linked to bKash or Rocket payments follow the retention rules for financial records in eligible regions.
When this policy changes, the updated version is posted here with a revised date. Continuing to use your account after a change indicates you have reviewed the updated terms.
The questions below cover what we are asked most often about how we handle account data, cookies, payment records and your rights. If your question is not here, contact us through live chat or email with your account reference.
We collect the details you enter during registration — name, contact number and login credentials — along with device type and login timestamps. When you make a bKash or Rocket transaction, we also record the reference ID, amount and date. We do not collect more than what is needed to run and secure your account.
Your transaction history, login timestamps and stored contact details are visible in your account dashboard after you log in. For a full summary of everything we hold, send a written request through live chat or email with your account username. We respond within the period set by applicable law in your eligible region.
Studios receive only the session data needed to deliver game content to your account — such as game state and session token. They do not receive your payment details, wallet information or full identity data. Their handling of session data is governed by their own terms, not this policy.
Yes. We hold a record of each transaction on our side — reference ID, amount and timestamp — which you can view in your account history. The data held inside the bKash or Rocket platform itself is governed by their own privacy terms, which are separate from ours.
Most fields — contact number, email address — can be updated directly in account settings after login. Fields that are locked after identity verification require a support request. Contact us via live chat or email with the corrected detail and your account reference; we will process it and confirm once done.
Where applicable law in your eligible region permits deletion, you can request it in writing through our support channel. We will confirm which data can be removed and which must be retained for legal or financial compliance reasons, such as transaction records linked to bKash or Rocket payments.