App / Mobile
bubu8 collects only the account and transaction data needed to run your sessions, process wallet activity through bKash, Rocket or Upay, and keep your account secure. Access to this platform depends on your local law and eligible regions, and this policy explains exactly how we handle what you share with us.
When you open an account on bubu8, you share certain information with us — your contact details, the device you use to log in, and the payment methods you connect to your wallet. We collect this data for three reasons: to verify your account, to process transactions through payment rails like bKash, Rocket and Upay, and to keep the platform stable across the devices you use. We do not sell your personal data to third parties. We do not share your wallet or transaction history with advertisers. Where we engage third-party service providers — for example, payment processors that route your bKash or Rocket transfer — those providers receive only the minimum data needed to complete that specific task, and they operate under data-handling obligations consistent with ours. Session data, including your device type and browser behaviour, is logged to maintain continuity across mobile and desktop access. We retain account records for as long as your account remains active and for a further period required by applicable obligations. All access to this platform depends on your local law and eligible regions, and we apply this policy within the bounds that your jurisdiction allows.
This policy covers the data bubu8 handles directly — your account, your device sessions and your wallet transactions. It does not extend to third-party services you navigate to from our pages, and it does not govern how payment providers process data on their own platforms once a transfer leaves our system. Understanding the boundary helps you know where to direct a query.
Data you submit when opening or logging into your account — email, contact details and device identifiers — falls inside this policy. We control how this data is stored, used and deleted.
When you initiate a bKash, Rocket or Upay transaction, we handle the instruction data on our side. Once the transfer moves to the payment provider's network, their own privacy terms apply to that segment.
Your browsing behaviour within the bubu8 platform — pages opened, session duration, game lobbies accessed — is logged by us and covered by this policy, not by any external analytics provider's public terms.
Links to external pages, game studio interfaces loaded inside the lobby, or payment provider portals you visit directly are outside our control. Read the privacy notices of those services separately.
You have practical options when it comes to the data we hold on your account. You can request a summary of what we have recorded — this includes your registration details, your device session history and the transaction references logged against your wallet. If any detail is inaccurate, you can ask us to correct it by raising a request through the account support channel. Where you have a question about how a specific piece of data was used — for instance, why a particular device fingerprint was flagged during a login — you can put that question to our support team and we will respond with the information we hold. Requesting deletion of your account data is also an option; we will process that request in line with applicable obligations and let you know if any portion must be retained for legal or compliance reasons. Availability of these rights depends on your local law and the eligible region from which you access the platform.
Open a data-access request through our support channel. We will return the account details, session logs and transaction references held against your profile.
If a name, contact address or wallet reference is recorded incorrectly, contact support with the correct detail and we will update it after verifying your identity.
For any question about how a specific data point was collected or used — including device identifiers tied to your mobile sessions — submit your query through the published support route.
You can ask us to delete your account data. We will confirm what can be removed immediately and what we must retain under applicable obligations before proceeding.
If you need to act on this policy — whether that is reviewing your data, correcting a detail or asking how your bKash transaction record is stored — use the contact routes published on the bubu8 platform. We do not list channels or response windows we cannot confirm, so check the published contact page for the routes currently active.
The live chat widget is accessible from the account area. Use it to raise a privacy question or request account data directly with the support team.
For written privacy requests — including data-access or deletion requests — email the address listed on the Contact page. Keep a copy of your submission reference.
The Help Centre within your account contains published answers to common privacy questions and links to the request forms for data review and correction.
We keep the data we collect limited to what the platform actually needs. Cookies are used to maintain your login session and remember device preferences across mobile and desktop — they are not used to build advertising profiles. Your account password is stored in a hashed form; we do not hold it in plain text and our team cannot retrieve it, only reset it through the verified account flow. Retention periods are tied to account activity: active accounts retain their data while the account is open; closed accounts are subject to a retention window determined by applicable legal obligations. If you want to know the specific retention period applied to your account data, raise the question through the support channel and we will provide the details on record.
Session and preference cookies keep your login active and carry your device settings between visits. We do not deploy advertising cookies or share cookie data with third-party ad networks.
Passwords are hashed on storage. Login sessions are tied to device identifiers, so an unfamiliar device triggers a verification step before access is granted to your account.
We keep your account records while your account is active. After closure, a retention window applies in line with legal obligations. You can request the specific period through support.
When this policy changes in a material way, we post a notice in the account area. Continuing to use the platform after that notice constitutes acknowledgment of the updated terms.
Below are the questions we hear most often about this policy — covering what we collect, how long we keep it, and what you can do about it.
We collect your contact details, the device and browser you use to log in, and the payment method references you connect to your wallet — such as your bKash or Rocket account identifier. We do not collect payment card numbers or store full wallet credentials on our servers.
We share data only with service providers that directly operate our platform — payment processors for bKash, Rocket and Upay transfers, and technical providers that run account infrastructure. We do not sell your data. Third parties receive only the minimum required for each specific task.
After account closure, we apply a retention window set by applicable legal obligations. The exact period depends on the type of data and the jurisdiction. You can ask for your specific retention details by contacting support through the published channel.
Yes. Submit a data-access request through the support channel — live chat or the email address on the Contact page. We will return the account details, session logs and wallet transaction references recorded against your profile. Eligibility depends on your local law and region.
Contact our support team with the accurate information. We will verify your identity through the standard account process before making any change. Corrections to contact details or wallet references are processed once verification is complete.
We use session cookies to keep you logged in and preference cookies to remember your device settings. These are not advertising cookies. You can adjust cookie behaviour in your browser settings, though disabling session cookies may affect how your account loads across mobile and desktop.