Slots / Casino
4bd678 keeps this policy straightforward — what data we collect from your account, how we use it, and what choices you have over it. Access to our platform and the rights described here depend on your local law and eligible regions.
When you open an account with 4bd678, we collect the information needed to run that account — your registration details, device identifiers, session activity and any payment context associated with your wallet interactions, including Nagad and Upay transactions where those rails are active. We do not sell your personal data to third parties. We do not share it with advertisers. Data we hold is used to verify your identity, process your account actions, respond to support requests and meet obligations that apply under the law of the jurisdiction governing your access. Retention periods follow what is reasonably required by those obligations — we do not keep data longer than necessary. Cookies and similar tracking tools are used on the site to maintain your session state, remember account preferences and measure how pages perform; you can adjust browser-level cookie settings at any time. If you connect through a mobile device — which is the primary access route for most of our Bangladesh members — the same data standards apply regardless of whether you are on a browser or a cached session. Where a specific data use requires your consent, we ask for it separately and clearly before proceeding.
Nagad payment context appears in your account transaction record. We hold only what is needed to match your deposit or withdrawal entry to your account; we do not store full wallet credentials.
When Upay is used as your settlement method, the reference data from that transfer is logged in your account history. You can review this record from the transaction section of your account.
bKash deposit references, where used, appear in your account ledger. These are retained for the period required by our operational and compliance obligations, then removed from active records.
We record device and session identifiers to protect your account from unauthorised access. These are not shared externally and are used solely for account security and session continuity purposes.
This policy governs data we collect and process directly through 4bd678. It does not extend to third-party services you reach from our platform, and it does not override the local laws that apply in your region. Understanding the boundaries helps you know exactly what we are responsible for and where to look for other terms.
Login events, session timestamps and device data collected when you access your 4bd678 account fall squarely inside this policy. We control this data and apply the standards described here to how it is stored and used.
Transaction references from Nagad, Upay and other configured payment rails are covered here to the extent they appear in your account record. The payment provider's own privacy terms govern what happens on their side of the transfer.
Activity data from game sessions — rounds played, stakes, outcomes — is logged in your account history under this policy. Game content is supplied by studios; their own data practices apply to any data processed on their infrastructure.
Links or services that take you away from 4bd678 — including external payment gateways or support tools not hosted by us — are not covered by this policy. Check those services' own terms before submitting data there.
Your account gives you direct access to most of the information we hold about you. From the account settings area, you can view your registration details, check transaction history and review the contact information tied to your profile. If any detail is wrong — your name, your email address or your linked mobile number — you can submit a correction request through the support route. We aim to process straightforward corrections promptly, though the timeline depends on the verification steps required. For data you cannot update directly in your account, raising a query with our support team is the right path. If you want to understand what data we hold beyond what is visible in your account, you can request a summary through the same support channel. Deletion requests are handled case by case; some data cannot be removed while your account remains active or while we hold it to meet legal obligations.
Open the account section after logging in to see your personal details, transaction history and session data. Most of what we hold about you is visible there without needing to contact support.
If your registered name, mobile number or email is incorrect, contact support with the correct information and any verification we ask for. We update the record once identity is confirmed.
For questions about what we hold, how long we keep it or why a specific data point appears in your record, send a message through the support channel. We respond with the detail we can share under applicable law.
If you want to close your account or ask about data removal, contact support directly. We will explain what can be removed, what must be retained and the steps involved based on your account status.
Any question about this policy — data access, corrections, deletions or how a specific data point is used — can be directed to our support team through the routes below. We do not publish a dedicated privacy email address separate from general support; all policy queries go through the same channels your account queries do, handled with the same response process.
The live chat window inside your account is the fastest route for policy questions. Open it from the account menu, describe what you need and the team will either answer directly or route your query to the right place.
For queries that need a written record — correction requests, data summaries or account review questions — submit a support ticket. Include your account details and a clear description of the request so we can handle it without unnecessary back-and-forth.
If your query relates to a specific transaction — such as a Nagad or Upay payment reference appearing in your record — use the message centre linked to your transaction history. This keeps the relevant context in one place.
We apply consistent data handling standards across your account — from the moment you register to the point where data is no longer needed. The specifics below describe each area of our approach so you know what to expect rather than having to ask.
We use session cookies to keep your account active while you browse and functional cookies to remember your preferences. Analytics tools measure page performance in aggregate. You control cookie behaviour through your browser settings; adjusting them may affect some account functions.
Login activity is monitored for unusual patterns. If access from an unrecognised device is detected, your account may prompt additional verification. You can review recent login events from the security section of your account settings.
We keep account data for as long as your account is active and for the period required after closure by the legal obligations that apply to us. Transaction references — including Nagad and Upay entries — follow the same retention schedule and are not kept beyond what is necessary.
When this policy changes in a material way, we notify you through your account or by the contact method you have registered. Continued use of your account after a notified update means you have seen the revised terms; check the date at the top of this page for the current version.
These are the questions we hear most often about how this policy works. If your question is not here, contact support through the routes described in the policy contact section above.
We collect the details you enter at registration — name, email address, mobile number and any identity verification data we ask for. We also log device and session identifiers each time you access your account. We do not collect data beyond what your account requires.
We do not sell your data or share it with advertisers. Data may be shared with payment processors — such as Nagad or Upay — only to the extent needed to process your transaction. Legal obligations in the applicable jurisdiction may also require disclosure in specific circumstances.
Log in and open the account section. Your registration details, transaction history and contact information are visible there. For data that does not appear in your account view, contact support and request a summary. We will share what we are permitted to share under applicable law.
Yes. Contact support with the correct detail and the verification we ask for. We update your record once we confirm your identity. Some fields — like your registered name — may require supporting documentation before we can make the change.
The transaction references that appear in your 4bd678 account record are covered by this policy. What Nagad or Upay collect and process on their own side of the transfer is governed by their respective privacy terms, not ours. Review their policies directly for that side of the data.
Retention after closure follows the legal obligations that apply to us in the relevant jurisdiction. We do not keep data indefinitely — once the required retention period ends, the data is removed from active records. Contact support if you want to understand the timeline for your specific account.