Casino / App
bet167 collects only what it needs to run your account — login activity, wallet transactions through bKash, Rocket or Bank Transfer, and device identifiers used to keep your session secure. Access to this service depends on your local law and eligible regions.
This policy sets out what data bet167 collects when you open an account, make a deposit using bKash or Rocket, complete a Bank Transfer, or browse the lobby on your mobile device. We collect account registration fields (your contact address, chosen username and verified identity documents where required), transactional records tied to each wallet payment you initiate, and technical signals from your device such as browser type, session timestamps and connection metadata. We do not sell your personal data to third parties. We share records only where required by the operational systems that process your transactions or where a lawful request compels disclosure. Data is retained for as long as your account remains active and for a period afterward as required by applicable record-keeping obligations. The scope of this policy is limited to activity on bet167. If you reach a third-party page through a link on our site, their own privacy terms govern that session — not ours. Availability of this service depends on your local law and the eligible regions at the time you access it. If you have questions about how a specific data category is used, the contact route at the bottom of this page is the right starting point.
Each bKash deposit or withdrawal generates a transaction record stored against your account. This record includes the amount, timestamp and reference code visible in your account wallet history.
Rocket payment events are logged with the same reference structure as other wallet transactions. You can review these entries directly inside your signed-in account under transaction history.
Bank Transfer instructions and confirmation references are retained as part of your account record for reconciliation purposes. Check the wallet section of your account to see the current status.
We store browser type, device identifiers and session timestamps to detect unusual login patterns and keep your account accessible only to you. This data is not used for advertising profiling.
Not every interaction you have online falls under this policy. Knowing the boundary helps you understand exactly what we are responsible for and where another party's terms take over. The four categories below draw a clear line between what bet167 controls and what sits outside our remit. If something is not listed here as covered, assume the relevant third party holds the applicable policy for that data.
Login events, password changes and two-step verification steps on bet167 are within this policy. We record these for security purposes and you can request a review of your login history through support.
Deposits and withdrawals processed through bKash, Rocket or Bank Transfer generate records covered by this policy. The payment provider's own terms also apply to the transfer on their side.
Pages you visit, game lobbies you open and any content you load on bet167 fall within this policy's data collection scope. This includes lobby navigation and session duration on the site.
Links to external payment apps, game studio pages or any off-site destination are outside this policy. Once you leave bet167, the destination's own privacy terms govern your data from that point forward.
You have concrete options when it comes to your personal data held by bet167. Reviewing what we store, correcting an error in your account record, or raising a question about how a particular data category is used — all of these are steps you can initiate. To review the data held against your account, open your account settings page while signed in; the profile and transaction sections show the primary records we maintain. If you notice an error — a mismatched contact address or an outdated document on file — the correction process starts in the same account section. Submit the corrected detail and our support team will verify and update it. For questions that go beyond self-service, the support contact route listed in this policy is the right channel. We aim to respond to data-related queries with the same attention we give account and wallet questions. Your right to ask how data is used does not depend on your account status — you may raise it whether your account is active or not. Access to this service and the rights available to you may vary depending on your local law and eligible regions.
Sign in and open the account settings page to see the profile data, contact details and transaction history we hold. This is the fastest way to check what is stored.
If any saved detail is wrong — name spelling, contact address or identity document — update it in the account profile section and our team will process the correction after verification.
For anything not visible in your account settings, reach out through the support contact route on this page. Describe the data category you are asking about and we will respond with the relevant detail.
If you want to understand the retention period for a specific data type or ask about a deletion request, contact support with your account reference so we can locate the right records quickly.
If your question is about data access, a correction to your account record, or the way we handle wallet payment information, the routes below are where to start. Use the channel that suits how you prefer to communicate — we aim to treat privacy queries with the same attention as account and payment questions. Do not share your full password or full wallet PIN through any support channel.
Open the chat widget on bet167 while signed in. State that your question relates to the privacy policy or your account data so the agent can route it correctly from the start.
Send your query to the support email address published on the Contact page of bet167. Include your account username and a brief description of the data point you are asking about.
The Help section inside your signed-in account lists self-service steps for common data queries including transaction history access and profile correction without needing to contact support.
The way we handle data is shaped by the practical need to keep your account secure and your wallet transactions accurate. Cookies on bet167 are used to maintain your login session and remember your lobby preferences — not for cross-site advertising. You can adjust cookie behaviour through your browser settings, though doing so may affect how the site loads on your device. Account security measures include session expiry on inactive periods and login monitoring to flag access from unfamiliar devices. We retain transaction data — including bKash, Rocket and Bank Transfer records — for reconciliation and for the period required by applicable obligations. We do not retain data beyond what those requirements specify. If you want to know how long a specific data category is kept, contact support with your account reference and the data type you are asking about.
Cookies on bet167 support session continuity and lobby preference memory. They are not used to build advertising profiles. Browser-level cookie controls let you manage or clear them at any time.
Login monitoring and session expiry on inactive accounts reduce the risk of unauthorised access. If you notice a login you do not recognise, contact support immediately with your account reference.
We keep transactional records — including wallet payment logs for bKash, Rocket and Bank Transfer — for as long as your account is active and for the period required by applicable record-keeping obligations afterward.
Data handling questions go to the support team via live chat or the email address on the Contact page of bet167. Mention your account reference so the right records can be located without delay.
The questions below cover what Bangladesh account holders most commonly ask about how bet167 handles their data, what rights they have and how to act on them. If your question is not answered here, the support contact routes listed earlier in this page are the next step.
We collect the registration details you submit — contact address, username and any identity documents required for account verification. We also store device and session data to keep your login secure. Payment records for bKash, Rocket and Bank Transfer transactions are held against your account wallet.
We share data only where the operational systems processing your transactions require it, or where a lawful request compels disclosure. We do not sell personal data. If a third-party service is involved in a specific transaction, their own privacy terms also apply to that portion of the data.
Sign in to your account and open the profile and transaction sections — these show the primary records we maintain. For data categories not visible in self-service, contact support via live chat or email with your account reference and the specific data type you want to review.
Yes. Open the account settings page while signed in and update the incorrect detail. Our team will verify the change before it is applied. For identity document corrections, contact support directly and provide the replacement document so verification can be completed correctly.
Transaction records — including wallet history for bKash, Rocket and Bank Transfer payments — are retained while your account is active and for the period required by applicable record-keeping obligations after account closure. Contact support with your account reference to ask about a specific data category's retention period.
Yes. The policy covers all activity on bet167 regardless of whether you access it on a mobile browser or a desktop. Session and device data collected on mobile follows the same rules as desktop access. Availability of the service depends on your local law and eligible regions.