Mobile / Slots
bf678 collects and uses your account data only to operate the platform and process transactions through payment rails like Nagad and Upay. This policy explains what we collect, why we collect it, and the choices available to you — access and use depend on your local law and eligible regions.
When you open an account on bf678, we collect the information you submit during registration — your name, contact details and any verification documents required to activate your wallet. When you make a deposit or withdrawal through Nagad or Upay, we retain the transaction reference, amount and timestamp as part of your account record. We also collect device and browser data — such as IP address, device type and session activity — to keep your account secure and to ensure the platform displays correctly on your mobile. Cookies and similar tracking tools are used to remember your session state and to understand how different parts of the lobby are navigated; you can manage cookie preferences through your browser settings. We do not sell your personal data to third parties. Where we share data with payment processors like Nagad or Upay, it is strictly to complete the transaction you initiated. All data handling is subject to the laws applicable in your region, and access to the platform itself depends on your local law and eligible regions. If you have questions about a specific data point stored on your account, the contact route in the support section below is the right place to start.
This policy covers the bf678 platform and the account, wallet and content areas operated directly by us. It does not extend to third-party services you reach from our platform. Understanding the boundary helps you know who to contact when a question arises about your data.
Any data you submit when creating or updating your bf678 account — login credentials, contact details and identity records — falls fully within this policy. We hold and process that data under the terms described here.
Payment activity routed through Nagad or Upay is recorded on your bf678 account. The transaction data we hold is covered here; the payment provider's own handling of your wallet is governed by their separate privacy terms.
Your session activity within the lobby — pages visited, games opened, time on site — is collected by us and falls inside this policy. We use it only for platform operation and security, not for profiling or resale.
Links or services outside the bf678 domain — including payment provider apps and studio websites — are not covered by this policy. Once you leave our platform, the receiving site's own policy applies, and we have no control over that handling.
You have real, practical options when it comes to the data bf678 holds on your account. You can review the personal details stored by logging in and opening the account settings page — your registered contact details and verification status are shown there. If something is wrong or out of date, you can submit a correction request through our support contact route; we will update the record or explain why a change cannot be made. Transaction history for Nagad and Upay deposits and withdrawals is visible inside your wallet section — you do not need to contact support to see that record. If you want to ask a broader question about what data we hold, or if you want to request that an account be closed and data removed where local law permits it, the published support route is the correct channel. Response handling depends on request type and the requirements of your local jurisdiction.
Log in and open account settings to see your stored contact details, verification status and any documents submitted. What is displayed there is the live record we hold.
If your contact details or verification information are incorrect, raise a correction request through the support contact route. We will action it or explain any restriction that applies.
Your Nagad and Upay transaction records are accessible directly inside the wallet section of your account without needing to contact support. Each entry shows date, amount and reference.
To ask what data we hold beyond what is visible, or to request account closure and data removal where local law permits, use the published support contact route described in the section below.
If you have a specific question about how your data is handled — or you need to raise a correction, access or removal request — use the contact routes published on the bf678 platform. We do not publish operating hours or response time commitments here; use the route that matches how you normally access the site.
The live chat option is available from within your signed-in account. Use it to raise a data or privacy question directly with the support team.
A written email request is the recommended route for formal data inquiries — correction requests, access questions or account closure requests where local law permits.
The help section inside your account lists published contact options and form submission routes. Navigate there from the account menu after logging in.
Data security on bf678 starts at the account level. Session tokens, login credentials and wallet linkage to Nagad or Upay are handled through encrypted connections. We do not store full payment credentials on our side — transaction references pass to the payment provider and only the reference and outcome are retained in your account record. Cookie data collected during your session is retained for a limited period consistent with its purpose; session cookies expire when you close the browser. Longer-retention records — such as account registration and verified identity documents — are kept for as long as your account is active and for whatever period local law requires after closure. You can ask what retention period applies to a specific data type by raising a question through the support route.
Login, account management and all payment interactions — including Nagad and Upay flows — travel over encrypted connections. We do not store full wallet credentials; only the transaction reference and outcome are kept on your account record.
Session cookies expire when you close the browser. Persistent cookies used for preference memory have a limited retention period. You can clear or block cookies at any time through your browser or device settings without losing your account access.
Verification documents and registration data are retained while your account is active and for any further period required by applicable local law. After account closure, retention follows the rules of your jurisdiction, not an arbitrary internal schedule.
When this policy changes in a material way, we will post an updated version at this address. Continuing to use your account after a notified update means you have seen the revised terms. The support route is available if you have questions about any specific change.
These are the questions we receive most often about data handling, account records and your choices under this policy. If your question is not covered here, use the support contact route from your signed-in account.
We collect the name, contact details and any verification documents you submit during registration. We also record device and browser session data for security. Payment transaction references from Nagad or Upay are stored as part of your account wallet record. No data is collected beyond what is needed to operate your account.
We share data only where necessary to complete a transaction — for example, passing a payment reference to Nagad or Upay to process a deposit or withdrawal. We do not sell personal data to third parties or share it for marketing purposes outside the platform.
Log in and open account settings to see your stored contact details and verification status. Your Nagad and Upay transaction history is visible inside the wallet section. For a broader data access request, use the email support route described on the contact page.
Some fields — like a contact number or email address — can be updated directly from account settings after login. For verified identity documents that are already on file, submit a correction request through the support contact route and we will advise on the process.
Active account data is retained while your account is open. After closure, we retain what local law requires for the applicable period in your jurisdiction. The exact retention window depends on your region and the type of record. You can ask about a specific data type by contacting support.
Yes. Access to bf678 and the applicability of any account rights under this policy depend on your local law and eligible regions. We do not make legal determinations on your behalf. If you are unsure about eligibility in your area, check the terms page or raise the question with support.