Casino / App
betssen collects and uses your information only to run your wallet, process transactions through bKash, Rocket, and Upay, and keep your session secure across devices. Access to this platform and its services depends on your local law and eligible regions.
This policy applies to all personal data betssen collects when you create an account, log in, make a deposit or withdrawal, or contact support. The data we collect includes your name, contact details, account credentials, and transaction records tied to your wallet activity — including payments made through bKash, Rocket, and Upay. We collect this data to verify your identity, process your transactions, and maintain the security of your account across sessions and devices. We do not sell your personal data to third parties. Data shared with payment processors is limited to what those processors require to complete your transaction. We retain your account records for as long as your account remains active and for a period thereafter as required by applicable regulations. Where local law in Bangladesh governs data handling, we follow those requirements. If you access this platform from a region where local law restricts online gaming or data processing, your eligibility and the applicable rules depend on that jurisdiction. We recommend reviewing your local regulations before registering. For questions about how your data is handled, you can reach our support team through the contact routes listed on this site.
Payment data passed to bKash is limited to what is needed to complete your deposit or withdrawal. We do not store your bKash PIN or full wallet credentials on our servers.
When you use Rocket to fund your account, transaction identifiers are logged against your account record for reconciliation. No additional Rocket account data is retained beyond what the transaction requires.
Upay payment references are stored in your transaction history, visible in your signed-in account area. This record exists so you can verify and dispute transactions if needed.
Access and data rights depend on your local law and eligible regions. If you are in Bangladesh, local data protection rules apply alongside this policy where they set a higher standard.
Not every service you reach from betssen falls under this policy. Understanding the boundary helps you know where your data rights apply and where a third party's own policy governs instead.
Your registration details, login history, and session data are fully covered. This includes device continuity records that let your session resume after a switch between mobile and desktop.
Deposits and withdrawals processed through bKash, Rocket, and Upay are covered for the data we hold. The payment provider's own policy governs data on their side of the transaction.
Game content delivered by studios such as Pragmatic Play, Habanero, Bigtime Gaming, and PlayStar is covered for session and preference data we log. Game mechanics and RNG are governed by the studio, not this policy.
Any external site you reach by following a link from betssen operates under its own privacy terms. We are not responsible for data practices on sites we do not operate.
You have concrete options for managing the data betssen holds on your account. Reviewing your transaction history is straightforward: open your signed-in account area and navigate to the transaction log, where deposits, withdrawals, and wallet references are listed by date. If a record looks incorrect — a name spelling, a contact detail, or a linked payment method — you can submit a correction request through our support channel and we will update it after verifying your identity. If you want to know exactly what data we hold, you can request a summary by contacting support directly. We will respond through the same channel you used to ask. Closing your account does not erase all records immediately; some transaction data is retained for the period required under applicable regulations, and we will tell you what remains when you make the request. For any question about data access, correction, or deletion, the support routes on this site are the right starting point.
Log in and open the transaction history section of your account. Deposits and withdrawals linked to bKash, Rocket, or Upay are listed there with dates and reference numbers.
Submit a correction request through support with the specific field you want updated. Identity verification is required before we make changes to name or contact information.
Contact support to ask what personal data we hold on your account. We will provide a summary through the same channel within a reasonable period.
You can request account closure and ask which records are retained afterward. We will explain what data remains and why, based on applicable regulatory requirements.
If you have a question about your data or this policy, use the contact routes published on this site. We do not list channels or hours we cannot confirm.
Open the chat widget on this site to reach support directly. Use this route for account-specific data questions that need a quick response.
Send your data or policy question to the support email address listed in the contact section of this site. Include your registered account email so we can locate your record.
The help section of this site covers common account and policy questions. Check there first — many data access and correction questions are answered without needing to contact support.
We apply standard security measures to protect the data stored against your account, including encrypted connections for login and payment flows.
We use cookies to keep your session active across page loads and to remember your device so you do not have to log in again on the same browser. You can clear cookies through your browser settings at any time, though this will end your current session.
Your account credentials are stored in hashed form. We do not have access to your plain-text password. If you suspect unauthorised access, change your password immediately through the account settings page and contact support.
Active account data is retained while your account is open. Transaction records may be kept for a further period after closure as required by applicable regulations. We do not retain payment credentials such as bKash PINs or Rocket wallet passwords.
When this policy changes in a material way, we will post the updated version on this page with a revised date. Continued use of your account after a policy update means you have seen the new terms. Contact support if you have questions about a specific change.
Answers to the questions we hear most often about data, account records, and your rights under this policy.
We collect your name, contact details, date of birth, and the credentials you use to log in. Once you make a transaction, payment references from bKash, Rocket, or Upay are also logged against your account record for reconciliation purposes.
Yes. Contact support through the live chat or email route on this site and request a data summary. We will identify your account, compile the relevant records, and send them to you through the same channel you used to ask.
We share data only where it is necessary to process your transaction — for example, passing a payment reference to bKash or Rocket to complete a deposit. We do not sell personal data. Game studios on the platform receive session data only as needed to run the game.
Open a support request through live chat or email and specify which field needs correcting. We will ask you to verify your identity before making the change. Name and contact corrections are usually handled within a few business days of verification.
Some transaction and identity records are retained after closure for the period required under applicable regulations. When you request closure, we will tell you which records remain and for how long. Data not subject to a retention requirement is deleted.
Access and eligibility depend on your local law and eligible regions. If local law in your region sets stricter data protection requirements than this policy, those requirements apply. We recommend checking your local regulations before using the platform from another jurisdiction.