Slots / Sports
This policy explains what information bb39 collects when you access our platform, how we store it, and what choices you have over your own account records. Access and eligibility depend on local law and apply only where permitted in your region.
When you create or access an account on bb39, we collect the details you provide during registration — your name, contact information and the payment method you choose to use. For Malaysia-eligible accounts, this includes transaction context tied to Touch 'n Go eWallet, GrabPay and Bank Transfer. We collect this to process your account requests, confirm identity where required and maintain a record of your activity on the platform. We also collect device and session data — browser type, access timestamps and page interactions — to keep the platform working correctly for you. This data is not sold to third parties. We may share limited information with payment processors where your selected method requires it, but only to complete the transaction you initiated. Retention periods follow what is required by applicable law; once that period passes, data is removed from active storage. Cookie use is covered separately in the cookie section of this policy. If you have questions about any of these practices, the support contact paths at the bottom of this page are the right place to start.
Not every interaction on bb39 falls under the same privacy rules. Some areas are governed entirely by this policy; others involve third-party services with their own terms. Knowing the difference helps you understand exactly where your data sits and who is responsible for it.
Login activity, session history and account preferences are covered fully by this policy. We hold these records and you can request a review or correction through the support channels listed here.
Payment data linked to Touch 'n Go eWallet, GrabPay or Bank Transfer is shared with the relevant payment processor only to complete your request. Their own privacy terms apply to how they handle data on their side.
Game loading, page navigation and lobby interactions generate session data that we retain for platform operation. This falls inside our policy scope and is not shared outside the platform without your request.
Links to external services or embedded third-party tools operate under their own privacy frameworks. We do not control what those services collect, and this policy does not extend to them once you leave our platform.
You have real, actionable choices over your account data on bb39. Reviewing what we hold is straightforward — log in and go to your account dashboard to see the profile details and payment method records stored there. If something looks incorrect, you can submit a correction request through the support contact form; our team will verify and update the record. Raising a question about how a specific piece of data is used does not require you to close your account — a support query is enough. If at any point you want to request removal of data that is no longer required by applicable law to be retained, that request should go in writing through the same contact route. We aim to respond to data queries within a reasonable period; the current response window is shown in the support section. Availability of these rights may depend on local law and the region from which your account is accessed.
Log into your account dashboard to see the profile and transaction records we hold. The dashboard reflects the current state of your stored information after login.
If your name, contact details or linked payment method record is wrong, raise a correction request via the support contact form. We will verify and update the record.
Questions about how a specific piece of data is used can be submitted through the support channel without needing to take any other account action. We will respond with the relevant detail.
Where local law no longer requires us to retain a specific record, you can request its removal in writing. Submit through the support contact path listed in this page's support section.
Three contact routes are available for privacy-related queries on bb39. Each one routes directly to the team responsible for account and data matters. Use the channel that suits the type of query — account corrections work well over live chat; formal data requests are better handled by email so there is a written record.
Open the live chat window from any page after login to reach account support directly. This is the quickest path for account data questions and correction requests.
Send formal data requests or removal queries by email using the address shown in your account settings. Email creates a written record that is useful for data-rights requests.
The current state of your stored profile and payment method records is visible in your account dashboard after login. Start there before raising a support query — it may answer the question directly.
We handle your account data with clear practices: what we collect, how long we keep it, and who can see it are all defined in this policy rather than left open. Account security uses standard encryption on data in transit; login sessions are protected at the session level and expire after a period of inactivity. Cookies on bb39 are used to keep your session active and to record basic navigation behaviour — they are not used to build advertising profiles. The current cookie preference controls are accessible from the footer of any page. Data is retained only as long as required for account operation or as mandated by applicable law. Once that period passes, records are removed from active storage. Contact for data matters goes through the support paths listed above.
Information moving between your device and our platform is encrypted in transit. This covers login credentials, account form submissions and payment method details entered during a session.
Cookies keep your session active and record basic page navigation. They are not used for advertising profiling. Current cookie preference controls are accessible from the footer of any page on the platform.
Account data is held for as long as your account is active and for the period required by applicable law afterward. Once that period passes, records are removed from active storage — no indefinite retention.
Privacy and data-rights queries go to account support via live chat or email. For formal written requests — including data removal — email is the right route so a record of the request and response is maintained.
Common questions about how bb39 handles your account data, what rights you have and how to act on them.
We collect the details you provide at registration — name, contact information and your chosen payment method, such as Touch 'n Go eWallet, GrabPay or Bank Transfer. We also collect session and device data to keep the platform working correctly for your account.
We do not sell your data. Limited information is shared with payment processors only where your selected method requires it to complete a transaction. Each payment processor operates under its own privacy framework for the data it handles on their side.
Account data is retained for as long as your account is active and for the period required by applicable law after that. Once the retention period passes, data is removed from active storage. The exact period depends on the type of record and local legal requirements.
Log into your account dashboard to review the profile and payment method records we hold. The dashboard shows the current state of your stored information. If something looks wrong, raise a correction request through the live chat or email support channel.
Where local law no longer requires a specific record to be retained, you can submit a written removal request through our email support channel. This route is recommended over live chat so a written record of the request and response is maintained for reference.
Cookies on the platform are used to keep your session active and to record basic navigation behaviour — not for advertising profiles. Cookie preference controls are accessible from the footer on any page. Adjust your preferences there; changes take effect on your next page load.