Mobile / App
bd33g collects only the information needed to run your account, process wallet transactions through bKash and Rocket, and keep your session secure. This policy explains what we collect, why we keep it, and what you can do about it — access and eligibility depend on your local law and eligible region.
When you register an account on bd33g, we collect the details you enter in the sign-up fields — name, email address, and the mobile number linked to your wallet. If you fund your account through bKash or Rocket, we record the transaction reference and the amount posted to your wallet, but we do not store your full mobile banking PIN or any credential that belongs to those payment platforms. We also collect device and session data — browser type, IP address and the pages you visit — to maintain session integrity and detect unusual access patterns. This data is held for as long as your account remains active, plus any period required by applicable law in your eligible region. You can request a summary of the personal data we hold for your account at any time through the support route listed in this policy. We do not sell your personal information to third parties. Sharing occurs only where required by applicable legal process or where a contracted service provider processes data strictly on our behalf. All data handling is subject to your local law and the eligible-region terms under which your account was opened.
This policy covers the bd33g platform and the data flows that run through it. It does not extend to third-party services you reach from our pages. Understanding the boundary between what we control and what we do not is important before you share any personal information.
Any personal data you submit when opening or managing your bd33g account — email, mobile number, wallet reference — falls inside this policy. We control how that data is stored, accessed and deleted.
Transaction records generated when you move funds through bKash or Rocket are covered here. The payment platforms themselves operate under their own privacy terms, which are separate from this policy.
Cookies placed by bd33g on your browser for session management and analytics sit inside this policy. You can review cookie settings in your browser at any time without contacting us.
Links, embedded content or external tools not hosted by bd33g fall outside this policy. We have no control over data collected by those services and encourage you to read their own privacy terms before engaging.
Your account comes with a set of data rights you can act on directly. Start by signing in and opening the account settings page — from there you can review the registration details we hold and correct anything that is out of date. If you spot a transaction record in your wallet history that looks wrong, raise it through the support channel described in this policy; we will check it against the bKash or Rocket reference on file. Beyond corrections, you can ask us what personal data we hold for your account, request that we restrict how we use it in certain circumstances, or ask for deletion where your local law and eligible-region terms allow it. We aim to respond to data requests within the period required by applicable rules. These rights are subject to the jurisdiction your account is registered under, so access and scope may vary.
Sign in and go to account settings to see the personal details and transaction history we hold. The fields shown there reflect the live data on your account.
If any registered information is wrong — name, email or linked mobile number — update it in account settings or contact support with the correct details and your account reference.
For questions about how your data is used, what we retain or how long we keep it, send a written request through the support route on this page. Include your registered email in the request.
Where your local law and eligible-region terms permit it, you can ask us to delete or restrict personal data. We will confirm in writing what action we can take and any limitations that apply.
If this policy raises a question your account settings page cannot answer, use the routes below. Include your registered email address and a brief description of your request so the right team picks it up without delay. All contacts relate to privacy and data matters only; for game or wallet support, use the general help channel.
Send your data or privacy question to our support email address listed on the Contact page. Include your account email and the specific data matter you are raising.
Open the live chat icon from any page on bd33g while signed in. Describe your privacy concern and the agent will route it to the data team or confirm what action you can take from account settings.
For straightforward corrections — name, email, linked mobile number — the fastest route is your own account settings page. No support ticket needed; changes take effect as soon as you save them.
We apply a few specific practices to keep your data handled consistently. Cookies are used for session authentication and basic analytics; they do not track your activity outside the bd33g domain. Data retention periods follow the requirements of applicable law in your eligible region — we do not keep personal data longer than those periods allow. Account security relies on the login credentials you set; we do not store your bKash or Rocket mobile banking passwords at any point. If you believe your account has been accessed without your permission, contact support immediately using the routes on this page.
Cookies on bd33g cover session authentication and basic traffic analytics. You can manage or clear them through your browser settings at any time. We do not use cookies to track you across other websites.
We keep your personal data for as long as your account is active and for any additional period required under applicable law for your region. Once that period ends, data is removed from our active systems.
Your login credentials protect your account. We do not store mobile banking PINs or passwords from bKash or Rocket. If you share your device with others, sign out after each session to protect your account access.
When we update this policy, the revised version is posted here with a note at the top of the page. Continued use of your account after a change is posted means you have had the opportunity to review the new terms.
The questions below cover the data and privacy matters we hear most often from account holders. If your question is not listed here, use the support contact route described in the policy above.
At registration we collect the name, email address and mobile number you enter in the sign-up fields. If you link a bKash or Rocket wallet, we record the transaction reference generated by that deposit — not your mobile banking login or PIN.
We do not sell your personal data. Sharing happens only where required by a legal process in your eligible region, or where a contracted service provider processes data strictly on our behalf under a data-handling agreement. Third-party game studios do not receive your personal account data.
We hold your data for as long as your account is active. After account closure, we retain records only for the period required under applicable law in your eligible region. Once that retention period passes, personal data is removed from our active systems.
Yes, where your local law and eligible-region terms allow it. Send a deletion request through email support with your registered account email and a brief description. We will confirm in writing what we can action and whether any legal retention obligation prevents full deletion.
Sign in, open account settings and update the relevant field directly. If the field is locked or the change does not save, contact support via live chat or email with the correct details and your account reference. We will update the record and confirm the change.
It covers the transaction records we hold on our side — the reference number and amount posted to your bd33g wallet. The bKash and Rocket platforms themselves operate under their own privacy policies. We encourage you to read those separately before using those payment rails.