Casino / App
648bd collects only the information needed to run your account, process transactions through Upay or Bank Transfer, and keep your session secure across devices. What we collect, why we hold it, and how you can request changes — this page covers all of it. Access to our platform depends on your local law and eligible regions.
When you open an account with us, we collect the details you provide during registration: your name, contact information, and the payment method you choose — whether that is Upay or Bank Transfer. We also collect session data automatically, including your device type, browser, and the pages you visit within the lobby. This data helps us deliver the account experience you expect: correct wallet balances, transaction records, and support history tied to your profile. We do not sell your personal data to third parties for marketing. Where we share data — for example, with a payment processor handling your Upay or Bank Transfer transaction — that sharing is limited to what is necessary for the transaction to complete. Your transaction history stays visible inside your signed-in account area, and we retain it for as long as your account remains active or as required by applicable rules. If you contact our support team, the conversation record is stored against your account. Eligibility to use our platform and the scope of this policy both depend on your local law and the eligible regions we serve.
Not every data point falls under the same rule. Understanding what this policy does and does not cover helps you know where to direct questions about your information. Four areas are worth distinguishing clearly.
Login credentials, session tokens and device identifiers are covered fully. We use these to verify returning sessions and keep your account accessible whether you switch from mobile browser to desktop without losing your place.
Payment records linked to Upay or Bank Transfer deposits and withdrawals are covered. These records are stored in your signed-in account history and are not shared outside the processing chain needed to complete the transfer.
Game titles, lobby categories and promotional notices are platform content — not personal data. This policy does not govern how game content is delivered; that sits under our general terms. Your interaction logs with content are covered.
If you follow a link that takes you outside 648bd's domain, this policy stops at that boundary. Third-party payment processors and external sites operate under their own separate policies, which we do not control or warrant.
You have concrete actions available to you at any point your account is active. Reviewing what we hold is straightforward: sign in and open the account settings area, where your registered details, linked payment methods and transaction history are displayed. If something is incorrect — a misspelled name, an outdated contact number — you can edit those fields directly from the settings screen or request a correction through our support channel. For questions about how long we keep specific data, or to ask us to remove records that are no longer needed, reach out via the published support route. We will confirm receipt and respond within the timeframe our support team can commit to at that point. Eligibility for certain data actions may depend on your local law and the eligible region your account falls under. Do not hesitate to raise a question — our support team handles account and data queries alongside general account help.
Sign in and open account settings to see your registered details, linked payment options including Upay or Bank Transfer, and your full transaction log. No special request is needed for this view.
Edit your name, contact information or linked payment method from the settings screen. For fields that cannot be self-edited, contact support with the correction you need and we will process it.
If you want to understand how a specific data point is used or retained, contact support directly. Describe the data in question and we will give you a clear, account-specific answer rather than a generic response.
Where local law and eligible region rules permit, you can request deletion of records we no longer need to hold. Submit the request through our published support route with your account details for verification.
If your question about this policy cannot be resolved through the account settings screen, these are the contact paths we publish. Use the one that suits you — all of them connect to the same support team that handles account and data questions.
Open the chat icon from any page on 648bd while signed in. Your account is identified automatically so the agent sees your profile context without you needing to repeat your details.
Send your question to the email address listed on the Contact page. Include your registered account name and a clear description of the data query. We will reply to the same address.
The Help Centre, accessible from the footer while signed in or out, contains published articles on account data, transaction records and how to update your profile details without contacting support.
These four areas reflect how we manage information day to day. Each one maps to a real part of your account experience rather than abstract policy language.
We use cookies to keep your session active as you move between lobby sections and to remember your device across return visits. You can manage cookie preferences from the settings available in your browser. Disabling certain cookies may affect how your session behaves.
Transaction details linked to Upay or Bank Transfer are passed only to the processor completing that transfer. We store a record in your account history but do not retain full payment credentials on our side beyond what the transaction requires.
Account access uses credential verification at login. If you sign in from a new device, the session is tracked and visible in your account activity log. If you notice a session you did not start, contact support immediately through the published live chat or email route.
We keep your account data for as long as your account is open and for any period required by applicable rules after closure. When you request deletion, we will confirm which records can be removed and which must be kept under applicable obligations before processing.
These are the questions we receive most often about how 648bd handles account data, cookies and your rights. If your question is not here, our support team can answer it directly.
We collect the name, contact details and payment method information you provide at registration. We also collect session data automatically — device type, browser and your activity within the signed-in account area. We keep this to the minimum needed to run your account correctly.
We share data only where it is necessary to complete a transaction — for example, with the processor handling your Upay or Bank Transfer payment. We do not sell your personal data to third parties for marketing or any unrelated purpose.
Sign in and open your account settings page. Your registered details, linked payment methods and transaction history are all visible there. No special request is needed to view this information — it is available directly from your signed-in account area at any time.
Yes. Many fields — contact number, linked payment method — can be edited from your settings screen. For fields that are locked after registration, contact support via live chat or email with the correction you need. We will process it after verifying your identity against the account.
We retain records for the period required by applicable rules after account closure. The exact period depends on the type of data and your eligible region. If you want a specific answer for your account, raise the question through our published email or live chat support route.
Our policy covers the data we handle on our side of the transaction. Once your request passes to a payment processor — such as one handling Bank Transfer — their own policy applies to how they process your information. We do not control or warrant third-party data practices.