Mobile / Sports
bcd678 is direct about how your personal information is collected, used and kept safe. This policy covers every point where your data touches our platform — from account creation to transaction records — so you know exactly where things stand.
When you open an account on bcd678, we collect the information needed to run your account — your name, contact details, and the transaction records linked to payment methods like Rocket and Bank Transfer. We use this data to process your account requests, verify your identity where required, and keep your wallet activity accurate. We do not sell your personal information to third parties for their own marketing use. Data we collect is kept for as long as your account remains active or as required by applicable rules in your region. Once an account is closed, we follow a defined retention schedule before deleting personal records. Cookies and session data are used to keep your login active and to remember your account preferences across visits. You can manage cookie settings through your browser at any time. Any data sent between your device and our servers is transmitted over encrypted connections. If you use Rocket or Bank Transfer to fund your account, the transaction details are stored in your account wallet history and are visible only to you and our internal accounts team. Access to this platform and its privacy protections depends on your local law and eligible regions.
This policy applies to every part of your bcd678 account experience — from login to withdrawal. Understanding what falls inside and outside its scope helps you know where to direct questions about your data.
Your login credentials, session history and account preferences are fully covered. We control how this data is stored and who inside our team can access it. You can review your login activity from the account security section.
All deposit and withdrawal records — including those made via Rocket or Bank Transfer — are covered under this policy. These records are visible in your wallet history and are not shared outside our payments team without your request.
How you browse game lobbies, which categories you open and your session length may be recorded as anonymised usage data. This helps us improve navigation clarity. It is not linked to your personal identity unless you are signed in.
Payment processors, game studios and any external services you connect to operate under their own privacy terms. Once you leave our platform environment, this policy no longer applies. We encourage you to review any third-party terms directly.
You have practical choices about how your data is handled, and we make those choices accessible through your account. To review the personal information we hold — including your registration details and transaction history — go to the account settings page after signing in. If any detail is incorrect, you can update it directly from the profile section or contact our support team to request a correction on records you cannot edit yourself. If you want to know what data categories we hold or how long we keep them, you can raise a data question through the support contact route below. We aim to respond to all data-related requests within a reasonable period, though timing depends on the nature of the request and the verification steps needed. Closing your account does not remove all records immediately; a retention period applies in line with applicable rules for your region. Your eligibility to exercise specific data rights may depend on your local law.
Sign in and open the account settings page to see the personal details and transaction history we hold for your account.
Update your name, contact information or address directly in the profile section. For transaction records or identity fields, contact support with your request.
If you want clarity on what we store or why, send a message through our support channel. We will confirm the data categories held and the applicable retention period.
For any privacy-related request — including account closure, data deletion queries or correction of payment records — reach our support team through the contact paths listed on the support section of this page.
If you have a question about how your data is handled, or need to submit a privacy-related request, use the contact routes below. We do not publish response-time commitments we cannot verify, but all policy queries are reviewed by our accounts and support team.
Open the chat icon from any page on bcd678 while signed in. Use this route for account-level data questions, correction requests or general privacy queries. Our team can locate your account record and respond directly.
Send a written request to the support email address published in the Contact section of our site. Include your registered account details so our team can verify your identity before accessing or modifying any records.
Sign into your bcd678 account and navigate to the Help or Support section in the account menu. From there you can submit a formal privacy request, including data review, correction or questions about your Rocket or Bank Transfer transaction history.
We keep your account and payment data handled through defined internal processes — not left open to general access. Here is how each key area works.
We use session cookies to keep your account login active and to remember your preferences. You can clear or block cookies through your browser settings at any point. Doing so may affect how certain account features behave during your next session.
Your account password and login credentials are stored in encrypted form. We do not display full payment identifiers — such as your Rocket or Bank Transfer account number — in plain text on screen after the initial entry step.
We hold account records for the period your account is active and for a defined period afterward, as required by applicable rules for your region. When that period ends and there is no outstanding query, personal records are removed from active storage.
When we make a material change to this policy, we publish the updated version on this page with a revised effective date. Continuing to use your account after a published update means you have read the revised terms. You can request a summary of changes through support.
These are the questions we hear most often about how bcd678 handles your personal data, your account records and your choices under this policy.
We collect your name, contact details and the information you provide during account registration. Once you make a deposit or withdrawal using Rocket or Bank Transfer, the transaction reference and amount are recorded in your account wallet history. We collect only what is needed to run your account.
Yes. Sign into your account and open the account settings page to review your registered details and transaction records. If you need a broader summary of what categories of data we hold, contact our support team with a written request and we will respond after verifying your identity.
We do not sell your personal data to third parties for marketing. Payment processors handling Rocket or Bank Transfer transactions receive only the information needed to complete that transaction. Game studios on the platform do not receive your personal account details.
After account closure, we retain records for a period determined by applicable rules in your region. Once that retention period ends with no outstanding query or dispute, personal data is removed from active storage. You can ask our support team for details specific to your account situation.
Open the profile section in your account settings to update contact details directly. For fields you cannot edit yourself — such as identity verification records or transaction entries — send a correction request through live chat or email support with your account details included.
This policy applies to your bcd678 account wherever you access it, but your specific data rights and our obligations depend on your local law and eligible region. If you are accessing the platform from Bangladesh, check the applicable legal requirements in your area before submitting a data request.