App / Mobile
At fb22bet, your account data — including payment records linked to Nagad, Upay and Bank Transfer — is collected and held only for the purposes set out in this policy. Access to our platform and the rights described here depend on your local law and eligible regions.
When you open an account with us, we collect the information you provide directly — your name, contact details, and any payment identifiers used during a Nagad, Upay or Bank Transfer transaction. We also collect technical data your device sends automatically, such as your IP address, browser type and session activity, so that the account service can function correctly and we can detect any unusual access patterns. We use this information for three main purposes: operating your account, processing transactions you initiate, and meeting any compliance obligations that apply in the regions where access is permitted. We do not sell your personal data to third parties for their own marketing. Where we share data with payment processors — for example, to complete a Bank Transfer or verify a Nagad wallet — we share only what is necessary for that specific step. Data is stored on servers with access controls in place. Retention periods vary by data type: active account data is kept while your account remains open; transaction logs are held as required by applicable compliance rules. You may ask us what data we hold about you at any time through our support route.
This policy covers data we collect and process directly through fb22bet. It does not extend to third-party services you access from our platform, whose own policies govern how they handle your information. Understanding the boundaries helps you know who to contact when a data question arises.
Data you submit when creating or managing your account — login credentials, contact details and wallet verification steps — falls within this policy. We control how that information is stored and who inside our team can view it.
Payment-related data linked to Nagad, Upay or Bank Transfer is covered here up to the point it leaves our system. Once a transaction is handed to a payment processor, that processor's own policy applies to the data they hold.
Technical cookies and session data collected while you browse the platform are within our policy scope. We use these to keep your session active and to understand how account pages are used, not to profile you for external advertising.
Game content providers and any external links you follow from the platform operate independently. Their data practices are outside fb22bet's control. We recommend reading their own privacy notices before sharing information with them directly.
You have practical choices about the personal data we hold. You can ask us to confirm what information is stored against your account, and where we have the ability to correct or update it, we will do so upon a verified request through the support route below. If you believe a record is inaccurate — say, a contact detail or a payment identifier — you should raise that directly so it can be reviewed. You may also ask questions about how a specific piece of data is used or how long it is retained. We will respond through the same channel you use to reach us. Please note that some data — particularly transaction logs tied to Nagad, Upay or Bank Transfer activity — may need to be kept for a period set by applicable compliance rules, even after an account is closed. Where a restriction or deletion request conflicts with those obligations, we will explain the specific reason. None of these rights depend on you making a formal legal claim; a clear written question through support is enough to start the process.
Send a written request through our support route asking which data we hold for your account. We will confirm the categories of information stored and, where possible, provide a summary.
If a contact detail, payment identifier or profile field is wrong, raise it through support with the correct information. After identity verification, we will update what we are able to change.
You can ask how long a specific type of data — such as a Bank Transfer record or session log — is kept and under what rule. We will give you a clear answer rather than a generic response.
If you are unsure which right applies to your situation, our support team can point you to the relevant part of this policy or escalate your query to the team that manages data records directly.
If you have a question about how your data is handled, or you want to exercise one of the rights described above, the routes below are the ones we actively monitor for policy-related queries. Choose the channel that works for your situation and include your account reference so we can locate your records without delay.
Start a conversation through the live chat widget on the fb22bet site. State that your query is about the Privacy Policy so it reaches the right team member.
Send your privacy query to our published support email address. Include your registered account email and a brief description of the data question or correction you need.
The Help Centre in your signed-in account area contains a category for data and policy queries. Use the form there if you prefer a structured submission route over open chat.
Knowing how your information is secured is a reasonable expectation. Here is how we approach each area of data handling on the platform.
Account and transaction data is stored with access restricted to team members who need it to operate your account or respond to a verified support request. We do not grant open internal access to personal records.
We use session cookies to keep you logged in and to understand how account pages perform. We do not use cookies to build profiles shared with external advertising networks. You can manage cookie settings through your browser.
Active account data is held while your account is open. Transaction records linked to Nagad, Upay or Bank Transfer are kept for as long as compliance obligations in applicable regions require. When those periods end, records are removed from active systems.
If this policy changes in a material way, we will post the updated version on this page with a revised date. For significant changes, we may also send a notice to your registered contact. Check back here if you have a specific question about current practice.
These are the questions we receive most often about data, account records and your rights under this policy. If your question is not covered here, reach out through the support routes listed above.
We collect the details you enter during registration — name, contact information and account credentials. When you make a payment through Nagad, Upay or Bank Transfer, we also collect the transaction identifiers needed to process and record that activity. Technical session data is collected automatically.
We share data only where it is necessary — for example, passing a payment reference to a processor to complete a Nagad or Bank Transfer transaction. We do not sell personal data to external parties for their own marketing or profiling purposes.
Send a written request through live chat, email support or the Help Centre form in your signed-in account area. Include your registered contact details so we can locate your records. We will confirm the categories of data held and explain how each type is used.
Yes. If a detail is wrong — a contact field, a wallet identifier or a profile entry — raise it through our support route with the accurate information. After we verify your identity, we will update what the system allows us to change and explain any exceptions.
Transaction logs, including those related to Nagad, Upay and Bank Transfer activity, are kept for the period required by compliance rules that apply in the regions where access is permitted. Once that period ends, records are removed. You can ask about the retention period for a specific data type via support.
No. This policy covers data collected and processed directly by fb22bet. Game content providers and any external services you reach through links on the platform operate under their own privacy notices. We recommend reviewing those notices before sharing information with those services.