Live / Slots
gf22 is built around your account — and that means being clear about what information we collect, why we hold it, and how you can review or update it at any time. This policy covers every interaction your account has with our platform, from wallet transactions using bKash or Nagad to session activity across mobile and desktop.
When you open an account on gf22, we collect the information needed to operate that account — your registration details, session logs, and the transaction records connected to your chosen payment method, whether that is bKash, Nagad or Upay. We hold this data to process your transactions, keep your account secure, and respond to any support request you raise. We do not sell your personal information to third parties, and we do not share it beyond what is necessary to process a payment or verify an account action. Cookies and similar tracking tools are used to keep your session active and to understand how our platform is navigated — you can manage cookie preferences through your browser settings at any time. Data retention periods follow the requirements of the jurisdiction in which you access the service; because availability depends on your local law and eligible regions, the exact retention schedule that applies to your records will reflect those local requirements. If you want to understand which category of data we hold on your account, the support contact routes listed on this page are the right place to start. We review this policy periodically; any material change will be noted clearly in the updated document.
Not every part of your experience on gf22 falls under a single privacy rule. Some areas are covered directly by this policy; others involve third-party services that operate under their own terms. Understanding the boundary helps you know where to direct a question about how your data is handled and who is responsible for it.
Your login credentials, session history and account settings are held directly by gf22 and fall fully within this policy. If you need to review or correct this information, the account settings page is the starting point.
Deposits and withdrawals processed through bKash, Nagad or Upay generate transaction records on our side. The payment provider also holds their own record under their separate privacy terms, which we do not control.
Your activity inside game sessions — rounds played, wagers placed, session duration — is logged in your account history. This data stays within the scope of this policy and can be reviewed through your account transaction log.
Links from our pages to external services, including game studio sites or payment provider help pages, are outside this policy's scope. Once you leave gf22's domain, the third party's own privacy policy governs how your data is handled there.
You have concrete actions available to you at any point under this policy — not just abstract entitlements. If you want to see what account data we hold, log in and open the account history section; your transaction records, session logs and registered details are displayed there. If any detail on your account is incorrect — your registered name, contact address or linked mobile number — you can update it through the account settings fields. Where a change requires identity verification, the page will show you what documents or steps are needed; follow the instructions shown rather than assuming a specific process. For questions that go beyond self-service — such as asking what data we retain after account closure or requesting a copy of records not visible in your dashboard — our support routes are the right channel. We aim to acknowledge data-related questions promptly, though response times are not fixed and depend on query complexity. Eligibility to exercise specific rights may also depend on your local law and the region in which you access the service.
Log in and open the account history section to see transaction logs, session data and registered details held on your account.
Update your registered name, contact number or linked mobile wallet through account settings. Follow the verification steps shown on that page.
For questions not answered in your dashboard — such as retention periods or post-closure data — contact support using the routes listed on this page.
If you believe your data has been handled incorrectly, raise it through our support channel with your account reference. We will review and respond through the same route.
Privacy questions can come up at any stage — when you are setting up your account, after a bKash or Nagad transaction, or when you want to understand what records we hold. The routes below are the ones published on this site. We do not invent additional channels or hours; use the route that matches your situation and include your account reference so we can locate your records quickly.
Open the chat widget from any page while logged in. Include your account reference and describe your privacy question clearly so the team can route it correctly.
Send your data or privacy query to the support email address listed in the Help section of your account. Email is suitable for detailed requests, such as asking for a record copy or raising a correction that requires documentation.
The Help section inside your logged-in account lists current contact options and any published guidance on data requests. Check there first — it reflects the most current routes available to your account.
Handling account data carefully is not a secondary concern — it is part of how we keep your account working reliably. We apply access controls so that only the processes that need your data can reach it, and we review those controls when the platform changes. Cookie data is used for session management and navigation analytics; it is not used to build a profile for third-party advertising. If you want to limit cookies, your browser settings give you that control without affecting your ability to log in.
We restrict access to personal account data to the internal processes that require it — payment processing, account verification and support handling. No broader internal access is granted without a specific operational reason.
Cookies keep your session active and help us understand navigation patterns. You can adjust or clear cookie preferences through your browser at any time. Adjusting cookies does not log you out or change your account records.
How long we retain your account data depends on the legal requirements that apply in your region and the type of record in question. Transaction logs connected to bKash, Nagad or Upay payments may be subject to different retention rules than session data.
When this policy changes in a material way, we publish the updated version on this page with a clear note of what changed. Continuing to use your account after a published update means you have had the opportunity to review the new terms.
The questions below cover what we hear most often about how gf22 handles account data, who can access it, and what steps you can take. If your question is not answered here, the support routes listed above are the right next step.
We collect the details you enter during registration — name, contact information and your chosen login credentials — along with session activity and transaction records generated when you use your account. Payment records from bKash, Nagad or Upay are also logged on our side.
Your account history section shows transaction logs, session records and your registered details. For data not visible in the dashboard — such as archived records — contact support through live chat or the support email and include your account reference.
We share data only where it is necessary to process a transaction or verify an account action — for example, with the payment provider when you deposit via Nagad or bKash. We do not sell your personal information or share it for advertising purposes.
Open account settings while logged in and update the relevant field. If the correction needs identity verification, the page will show the required steps. For changes that cannot be made through self-service, raise a request through the email support route.
Retention periods depend on your local law and the type of record. Transaction logs may be held longer than session data due to financial record-keeping requirements. If you want specifics for your account, contact support with your account reference after closure.
The policy applies to your account activity on gf22. Whether accessing the platform is permitted depends on your local law and eligible regions. The data handling described here covers how we process information when an account is active, regardless of the device or location used.