App / Casino
bd133 is clear about what data we collect, why we collect it, and how you can review or update it at any time through your account. Access to this platform and its features depends on your local law and eligible regions.
When you create an account with us, we collect the information you provide directly — your contact details, account credentials, and the transaction records tied to your wallet activity. Payment methods like Nagad and Rocket generate transaction references that we retain as part of your account history; we do not store full wallet credentials on our servers. We also collect technical data automatically: device type, browser session identifiers, and the pages you visit within the platform. This is used to keep your session active and to understand how the interface is being used. We do not sell your personal data to third parties. Data shared with payment processors — including Nagad and Rocket — is governed by their own policies for the purpose of completing your transactions. Where our platform is accessed from Bangladesh, local data handling norms and applicable regulations shape how we manage retention and deletion. If you believe information we hold is incorrect, you can raise a correction request through the account support route. Your continued use of the platform after any policy update constitutes acceptance of the revised terms, and we will notify you of material changes via your registered contact.
Transaction references from Nagad transfers are stored as part of your account ledger. Full wallet credentials are never retained on our end.
Rocket payment records appear in your transaction history. These entries help reconcile deposits and withdrawals shown in your account wallet.
Your wallet balance and movement history are part of your account record. You can review them at any time from the wallet section when signed in.
Session data tied to your mobile or desktop browser helps us keep your account secure and your lobby preferences intact between visits.
This policy covers data we collect and process through bd133 and the account services directly attached to it. It does not extend to third-party services you reach from links on our platform, and it does not govern how payment processors handle your data on their own systems. Understanding the boundary helps you know exactly where your rights under this policy apply.
Login activity, session tokens, and account preference data gathered when you sign in fall fully within this policy. You can request a record of this data through account support.
Payment references created when you deposit or withdraw via Nagad or Rocket are covered here. The payment processors' own policies govern what happens on their side of the transfer.
Your browsing activity within the platform — which game lobbies you visit, how long you stay — is captured under this policy for session and security purposes only.
Any service you access by leaving bd133 operates under its own privacy terms. We have no control over data collected once you leave our domain.
You have real, actionable choices over the data we hold. Signed-in account holders can review their profile details directly from the account settings page — the fields shown there reflect what we have on record. If something looks wrong, you can edit it in place or raise a correction request with our support team. For data you believe should no longer be held, submit a removal request through the support contact route; we will confirm receipt and respond within the window stated in your account documentation. Requests related to payment history — such as transaction records tied to Nagad or Rocket transfers — may be subject to retention periods required under applicable financial handling rules. In those cases, we will explain what can be removed immediately and what must be retained, and for how long. Eligibility to exercise these rights may depend on your local law and the region from which you access the platform.
Open the account settings page when signed in to see the contact details, preferences, and verification status we currently hold for your profile.
Update your name, contact information, or account preferences directly in the fields shown under your profile. Changes take effect immediately on save.
Use the support contact route to ask about specific data points — what we hold, why we hold it, and how long it is kept before removal or archiving.
Submit a removal request through support. Payment transaction references may have mandatory retention periods; we will explain any applicable limits clearly in our reply.
If you have a question about this privacy policy, need to submit a data request, or want to flag something about your account record, use the contact routes listed below. We respond through the same channel you use to reach us.
Open the chat widget on bd133 when signed in to speak with a support agent about your account data or a specific policy question.
Send your data request or policy query to the support email address listed in your account dashboard under the help section.
The help section inside your signed-in account lists current contact routes and explains how to submit a formal data correction or removal request.
We apply technical measures to protect the data you share with us, and we limit access to your account records to the processes that need them to function. Cookies and session identifiers are used to keep your login active and to remember your lobby state between visits — you can manage cookie preferences through your browser settings. Account security relies on the credentials you set; we recommend using a unique password and reviewing your active sessions from the security section of your account when signed in. Data retention periods vary by data type: account profile data is held while your account is active, and transaction references may be kept for a period required under applicable financial handling rules. To request a change to how your data is handled, use the support routes listed on this page.
Session cookies keep your account active and your game lobby preferences in place. You can clear or block them via browser settings, though some account functions may be affected.
Your account credentials are your first line of protection. Review active sessions and update your password from the security section inside your signed-in account.
Profile data is held while your account remains active. Transaction records tied to Nagad and Rocket payments may be retained beyond account closure where required by applicable rules.
Material changes to this policy are communicated via your registered contact details before they take effect. Continued use after notification means you have accepted the updated terms.
Answers to the questions we hear most often about data, account records, and your rights under this policy.
We collect the contact details and credentials you enter during registration, along with technical data like your device type and session identifiers. Payment references from Nagad or Rocket transactions are also stored as part of your account transaction history.
Yes. Sign in and open your account settings to review what is on record. For a more complete data summary, submit a request through the support contact route listed in the help section of your account dashboard.
Most profile fields — contact details, display preferences, and verification information — can be edited directly from the account settings page when signed in. If a field is locked, raise a correction request with support and we will handle it from there.
We do not sell your data. Payment processors like Nagad and Rocket receive only the references needed to complete your transactions, and they handle that data under their own privacy terms. We do not share your data with advertisers or unrelated third parties.
Account profile data is held while your account is active. Transaction records may be retained beyond account closure where applicable financial handling rules require it. Contact support to ask about the specific retention period for any data type.
This policy applies to anyone using bd133, but your ability to exercise data rights depends on your local law and the eligible regions from which the platform is accessible. Where local rules differ from this policy, we apply the stricter standard.