Mobile / Live
bi222 collects only the data needed to run your account, process payments through Upay or Bank Transfer, and keep your transaction records accurate. What we collect, why we keep it, and how you can review or correct it — that is what this policy covers. Access and eligibility depend on your local law and the eligible regions we serve.
When you register with bi222, we collect the details you enter during account creation — your name, contact address, and the payment method you choose, whether that is Upay, Bank Transfer, bKash, Nagad or Rocket. We log each deposit and withdrawal against your account wallet so you can review the full transaction history from your account page at any time. Device identifiers and session data are recorded automatically when you connect through a mobile browser or desktop. We use this to keep your session stable and to detect irregular access patterns. We do not sell your personal data to third parties for marketing. Data shared with payment processors — such as the details passed during an Upay or Bank Transfer transaction — is governed by those processors' own policies, and we recommend you read them. Retention periods follow our internal data schedule; you can request details of how long specific data is kept by contacting our support team through the published channel. This policy applies where local law and regional eligibility allow; if you are uncertain whether it applies to you, reach out before continuing.
This policy covers data processed through your bi222 account — from login to wallet activity. It does not extend to third-party services linked from our pages, and it does not override the terms of any payment processor you use. Scope depends on your location and the eligible regions we currently serve.
Data collected when you log in, update your profile or change your password is fully within this policy's scope. Your account page shows the details we hold; you can request corrections at any time through the support channel we publish.
Every deposit and withdrawal made through Upay or Bank Transfer is logged and tied to your account wallet. These records fall inside this policy. You can view your history from the account section; contact support if a record appears incorrect.
Pages you browse, game lobbies you open and categories you explore generate session data. That data is used internally to maintain site performance. It is covered here, though it does not personally identify you beyond the account session.
Payment processors, game content providers and any external link you follow operate under their own privacy terms. bi222 is not responsible for how those services handle your data. Read their published policies separately before sharing information with them.
You have clear, actionable options when it comes to the data we hold about your account. Reviewing your records is the starting point — log in and open the account section to see the transaction history, registered details and wallet entries we have stored. If anything looks incorrect, you can raise a correction request directly with our support team. This covers your name, contact details or payment method records tied to Upay or Bank Transfer transactions. Requesting a copy of your data or asking what we retain is also straightforward; submit the request through our published support route and we will respond with the details applicable to your account. Eligibility for certain rights may depend on the applicable law in your region, so we recommend checking whether your local rules extend additional protections. We do not make these processes complicated — every step goes through the same support contact we publish on the site.
Log in and go to the account section. Your transaction history, registered name and contact details are visible there. If a record is missing or appears wrong, note the specific entry before you contact us.
Submit a correction request through our published support route. Include the account detail you want changed and the correct version. We verify against the information on file and confirm once updated.
Want to know how long we keep a specific data point? Send the question to support. We will tell you the retention period that applies to that category and explain why we hold it for that duration.
You can ask for a summary of what we hold on your account. This is handled through the same support contact. Response times depend on the complexity of the request and your region's applicable rules.
If you have a question about this privacy policy, the data we hold, or how a payment record appears on your account, contact us through the routes published on the bi222 site. We do not respond to requests sent through unverified channels. Use only the contact options visible when you are logged in or on the published contact page.
Log in to your account and use the support option shown in the account menu. This is the fastest route for questions about your specific data, transaction records or correction requests.
Our contact page lists the current support channels available for your region. Privacy questions, data access requests and correction submissions should go through one of those listed routes, not through social channels.
If a contact email is published on the site for policy queries, use that address. Include your account reference and a clear description of your request. We aim to confirm receipt and provide a substantive response in line with applicable regional rules.
Our approach to data management follows the principle of collecting only what is needed and keeping it no longer than necessary. We apply access controls so that your account details and payment records — whether from Upay transactions or Bank Transfer history — are not exposed to parties outside the processing chain. Cookie use on the site is limited to session management and performance monitoring; no third-party advertising cookies are set without disclosure. If our data handling practices change in a material way, we update this page and note the change date at the top of the policy.
Your account data is accessible only to the processes and personnel needed to run your account and handle support requests. Payment record access is restricted to the transaction processing flow.
We use cookies for session stability and to keep your account logged in as you move between lobby sections. We do not use cookies to build advertising profiles or share browsing data with marketing networks.
We keep account and transaction data for as long as required by our operational needs and any applicable legal obligation. When data is no longer needed, we remove it from active systems. You can ask about the retention period for any specific record.
When this policy changes, the updated version is published here with a revision note. Continued use of your account after a material update means you have read the revised terms. Contact support if you have questions about any change.
These are the questions we hear most often about how bi222 handles your data. If your question is not here, send it to us through the published support route.
We collect the name, contact details and payment method information you provide at registration. We also log device and session data automatically when you connect. Nothing beyond what is needed to run your account and process payments through Upay or Bank Transfer is collected.
Yes. Log in and open the account section to view your transaction history and registered details. For a fuller summary of all data we hold, submit a request through the published support contact and we will provide the relevant account-level information.
Contact support through the route shown on the published contact page or inside your account menu. Include the detail that needs correcting and what the correct version should be. We verify against your account records and confirm once the update is done.
Payment details passed during Upay or Bank Transfer transactions go to the relevant payment processor as needed to complete the transaction. We do not sell your data for marketing. Each processor operates under its own policy, which we recommend you read separately.
Retention periods follow our internal data schedule and any applicable legal requirements. If you want to know how long a specific record or data category is kept, ask through the support channel and we will give you the details that apply to your account.
This policy applies to accounts in eligible regions under applicable local law. If you are in Bangladesh, your access and the rights available to you depend on whether your region is currently eligible. Check the site or contact support if you are uncertain about your eligibility.