Casino / App
bf2222 is straightforward about what data we collect from your account, how we use it, and what choices you have — because your trust in this platform starts with knowing exactly where your information goes. Access to this platform and its features depends on your local law and eligible regions.
When you create an account on bf2222, we collect the details you provide during registration — your name, contact information and account credentials. When you make a deposit or withdrawal through bKash, Rocket or Upay, we record transaction identifiers and wallet references necessary to process and reconcile those movements. We do not store your full mobile wallet PIN or any authentication credential belonging to those payment services. Beyond transactional data, we collect session information such as device type, browser version and pages visited within the platform. This helps us keep the lobby working correctly across different mobile devices and screen sizes. We also collect IP address data for security purposes — specifically to detect unusual access patterns that might indicate unauthorised account activity. Data collected through bKash, Rocket and Upay transactions is processed in line with the applicable payment provider's own policies, which apply independently of this privacy policy. Our use of your data is limited to operating your account, processing payments, maintaining platform security and, where you have opted in, sending account-related notices. We do not sell your personal data to third parties. Availability of account features depends on your local law and eligible regions.
This policy covers the data bf2222 collects and processes directly. It does not extend to third-party services you access through our platform, and it does not override the independent policies of payment providers like bKash, Rocket or Upay. Understanding the boundaries helps you know exactly who is responsible for which part of your data.
Any data you submit when creating, verifying or updating your bf2222 account falls inside this policy. That includes login credentials, contact details and account preferences you set directly inside the platform.
Transaction references generated when you move funds via bKash, Rocket or Upay are recorded by bf2222 for reconciliation. The payment providers themselves govern how they handle your wallet data on their side.
Session and navigation data collected while you browse the lobby, open game categories or review account history is processed under this policy. This data supports platform performance and security monitoring only.
Links or integrations that take you away from bf2222 — including game studio environments and external support tools — are outside this policy's scope. Check the relevant third-party policy directly for those services.
You have concrete choices about the personal data bf2222 holds on your account. The first is access: you can request a summary of the personal information we hold by contacting our support team through the channel listed on the site. The second is correction: if any detail on your account — name, contact number, linked wallet reference — is inaccurate, you can update it directly inside your account settings or ask support to make the change for you. The third is a query right: if you are unsure why a specific piece of data was collected or how it is being used, submit a written question and we will respond with a clear explanation. The fourth is a deletion request: where deletion is technically possible and does not conflict with our obligation to retain transaction records, we will action it. Note that transaction records tied to bKash, Rocket or Upay movements may have retention requirements that limit immediate deletion. What you can do depends on your local law and eligible regions.
Request a summary of the data we hold on your account by contacting support directly. We will confirm what categories of data are stored and how they are being used.
Update your name, contact number or linked wallet reference inside account settings. If you cannot access the settings screen, support can make corrections after identity confirmation.
If something about how your data is used is unclear, send a written question through the published support route. We will reply with a factual explanation, not a generic policy reference.
Ask us to remove data where it is not required for active account operations or transaction records. We will confirm what can be actioned and what falls under retention requirements.
If you have a question about this policy, want to make a data request or need to report a concern about how your information is handled, use the contact routes published on the bf2222 site. We do not invent channels or response windows that are not visible there — use only what the site shows you.
Open the chat widget from any page inside the platform. Describe your privacy question or data request clearly so the team can route it correctly.
Send a written privacy or data request to the support email address listed on the Contact page. Include your account identifier so we can locate your records.
The Help Centre on the bf2222 site contains published policy documents and submission forms for formal data requests. Start there if you want a written record of your request.
bf2222 applies consistent data handling standards across account registration, payment processing and platform security. These four areas reflect what we actually do — not a list of promises we cannot back with a process.
We use session cookies to keep your login active and to remember lobby preferences within a single visit. You can adjust cookie permissions through your browser settings. Disabling cookies may affect how some account features load on your device.
Access to your account data inside our systems is restricted to staff who need it to operate or support the platform. We do not give external parties access to your account records outside of transaction processing through bKash, Rocket or Upay.
We keep account records for as long as your account is active and for the period required by applicable transaction record rules. When an account is closed, data that is no longer operationally required is removed on a scheduled basis.
If this privacy policy changes in a way that affects how your data is used, we will publish the updated version on this page. Continuing to use your account after a posted update means you have seen the revised terms.
These are the questions we get most often about how bf2222 handles personal data — answered directly, without circular references back to legal text.
We collect your name, contact details and account credentials at registration. Once you transact via bKash, Rocket or Upay, we also record payment references needed to process and reconcile those movements. We do not collect your wallet PIN from any payment provider.
We do not sell your personal data. Transaction data passes to bKash, Rocket or Upay only to the extent required to process payments. Game content providers receive session identifiers where technically necessary, but not your full account or payment profile.
Contact support through live chat or the email address on the Contact page. Include your account identifier in the message. We will confirm the categories of data stored on your account and explain how each category is being used.
Yes, for data that is not required for active account operations or transaction records. Deletion requests can be sent through the Help Centre form. Transaction records tied to bKash, Rocket or Upay movements may be subject to retention requirements that affect the timeline.
We use session cookies to maintain your login state and lobby preferences during a visit. You can disable them in your browser settings. Turning cookies off may affect how your account loads and whether some features remain accessible on your device.
Data that is no longer operationally required is removed on a scheduled basis after account closure. Transaction records that fall under applicable retention rules are kept for the required period, then removed. You can ask support to confirm what remains after closure.