Live / Sports
ab367 is clear about what data we collect, why we collect it, and how you can review or correct it at any time through your account. Access to our platform and the scope of this policy depend on your local law and eligible regions.
When you open an account with ab367, we collect the details you submit during registration — your name, contact information and the payment method you choose to fund your wallet. For payments processed through Rocket or Upay, we retain transaction identifiers, timestamps and status records so your account history stays accurate and auditable. We do not store your Rocket or Upay PIN or mobile banking credentials; those remain with the respective payment service at all times. We also collect standard device and session data — browser type, IP address and page interaction logs — to keep the platform working correctly across different mobile connections common in Bangladesh. This data is used for account verification, transaction reconciliation and fraud prevention. We do not sell your personal data to third parties. Where we share data with payment processors or identity verification services, we do so only to the extent required to complete your requested transaction or to comply with applicable legal obligations. How long we retain this data depends on the nature of the record: active account data is held for the life of the account, while transaction logs follow retention periods required by applicable rules in your eligible region.
This policy covers the data ab367 processes directly. It does not extend to third-party services you access through links from our site. Understanding the boundary helps you know exactly where your data rights under this document begin and end.
Your registration details, login records and account settings fall fully within this policy. You can review the data we hold against your account at any time by visiting the account section after signing in.
Transaction records tied to Rocket or Upay deposits and withdrawals are covered here. We hold identifiers and status logs only; your wallet credentials stay with the payment provider and are outside our data scope.
Session cookies and interaction logs collected while you browse the lobby or game pages are covered by this policy. You can adjust cookie preferences through your browser settings at any point.
Links to external payment providers, game studios or verification services lead away from our platform. Once you leave ab367, the data practices of those external services are governed by their own policies, not this one.
You have concrete actions available to you under this policy — not just abstract rights. Sign in to your account to see the personal details we hold. If anything looks incorrect — a contact number, an email address or a linked payment method — use the account settings page to submit a correction request directly. We review correction requests and update records where the change can be verified against our records. If you want to know specifically what data categories we hold on your account, you can raise a data inquiry through our published support route. For questions about transaction records tied to Rocket or Upay payments, the account history section shows each deposit and withdrawal entry with its status. If a record appears missing or incorrectly labelled, raise it through the support contact listed on-site. Your ability to exercise these steps may vary depending on your local law and the eligible region your account is registered under.
Sign in and open your account section to see the personal data and transaction history we hold. Each Rocket or Upay entry is listed with a date, amount and status.
If your name, contact details or linked payment method is wrong, use the account settings page to submit the correction. We verify and update records based on what you submit.
For a specific question about what data categories we hold, contact us through the support route published on-site. Name your account and describe the data category you are asking about.
If a transaction record linked to Rocket or Upay appears incorrect in your history, open a support ticket through the published contact route. Include the transaction date and status shown in your account.
If you have a question about this policy, your account data or a transaction record, use one of the contact routes published on the ab367 site. We respond to data-related questions through the same channels as general account support. Availability depends on your eligible region and local conditions.
Open the live chat widget on the ab367 site to raise a data or account query directly. Describe your question clearly and include your registered contact detail so we can locate your account record.
Send a written inquiry to the support email address listed on the ab367 contact page. For data-related requests, include your account identifier and specify whether your question relates to personal data, transaction records or cookie settings.
The ab367 help section on-site covers common questions about account data, payment records and policy scope. Check there first — many data-access questions have a direct answer referencing the exact account step involved.
We use standard security measures to protect the data stored against your ab367 account. This covers both your registration details and the transaction logs tied to Rocket or Upay activity. Here is how each area works in practice.
We use session cookies to keep your account active while you browse. Persistent cookies support preference storage. You can clear or block cookies through your browser settings; doing so may affect how certain account pages load.
Account credentials are stored in hashed form. We do not hold your Rocket or Upay mobile banking passwords. If you suspect unauthorised access to your account, change your password immediately and contact support through the published route.
Active account data is retained for the duration your account remains open. Transaction records — including Rocket and Upay entries — are kept for the period required under applicable rules in your eligible region, then deleted or anonymised.
When we update this policy, the revised version is published on this page with the update date shown at the top. Continuing to use your account after an update is posted means you have seen the revised terms. Check this page periodically for changes.
These questions cover what real account holders ask about how ab367 handles their data. If your question is not here, reach us through the support contact published on-site.
We collect your name, contact details and the payment method you register — such as Rocket or Upay. We also log session and device data to keep the platform working. We do not collect your mobile banking PIN or wallet password.
Yes. Sign in and open your account history section. Each Rocket and Upay transaction is listed with a date, status and transaction identifier. If a record appears wrong, contact support through the published route with the date and status shown.
Go to your account settings page after signing in. You can submit a correction request for your name, contact information or linked payment method from there. We verify the change against your account records before updating it.
We share data only where required to process a transaction or meet a legal obligation in your eligible region. Payment processors like Rocket or Upay receive only what is needed to complete your transaction. We do not sell your personal data.
Active account data stays on record while your account is open. Transaction logs follow retention periods set by applicable rules in your eligible region. Once that period expires, records are deleted or anonymised. Contact support if you need specifics for your region.
Change your account password straight away. Then contact us through the live chat or email route published on-site. Describe what you saw in your account history. We will review the session logs tied to your account and advise on next steps.