Casino / Live
af22 collects and processes your information to keep your wallet, transaction records and session activity running correctly — and this page sets out exactly what we collect, why we hold it, and what you can do about it. Access to our platform depends on your local law and eligible regions.
When you open an account with us, we collect the details you provide during registration — name, contact information, and the payment method you connect, whether that is bKash, Nagad, Rocket or Bank Transfer. We also record session activity, device type and browser behaviour to keep your account secure and to resolve disputes if they arise. We do not sell your personal information to third parties. Data is held only as long as it is needed for account management, legal compliance or resolving open queries. Where you use a local payment rail such as bKash or Nagad, those providers operate under their own terms; our record covers only the transaction reference we receive, not the credentials you enter in their app. Cookies and similar tools help us remember your language setting and last-visited section. You can manage cookie preferences through your browser, though switching off functional cookies may affect how parts of the site load on your device. If you are accessing from Bangladesh, note that availability and data-handling obligations depend on local law and the eligible regions our platform is permitted to serve. Any questions about a specific record should go directly to our support channel listed in the contact section of this page.
Not every interaction on this site falls under the same set of rules. The four areas below clarify what this privacy policy directly covers and where a separate framework or third-party terms take over. Knowing the boundary helps you raise a query with the right party.
Registration details, login records and account settings are fully within scope. If you want to review, correct or remove your stored account data, the steps in the rights section below apply directly to this category.
Payment references we receive from bKash, Nagad, Rocket and Bank Transfer are covered here. We hold the reference and amount; the credentials you enter inside those apps are governed by the payment provider's own privacy terms, not ours.
Game interaction data — which titles you open, session length — is recorded for account integrity and fraud prevention. This data is not shared for advertising purposes and is subject to the same retention limits as account data.
Links to external platforms, social channels or partner pages lead to services that operate their own privacy policies. We are not responsible for how those third parties collect or use data once you leave our domain.
Your account is yours to manage. We have built clear paths so you can review what we hold, correct anything that is wrong, and raise a question without needing to navigate a lengthy process. Sign into your account and open the profile section to see the personal details currently on record. If any field — name, contact number, linked payment method — is inaccurate, you can update it directly from that screen or submit a correction request through our support channel. For data-related questions that go beyond a simple field update, our support team is the right contact point; you will find the route in the support section below. Where local law in Bangladesh gives you additional rights over your data, those apply independently of what is set out here — eligibility depends on your local legal position.
Sign in and open your account profile to see the personal and payment details we currently hold. The screen shows the fields you submitted at registration and any updates made since.
Edit your name, contact information or linked wallet reference directly in the profile section. For fields that require verification before a change is accepted, follow the instructions shown on screen.
If you have a question about a specific record — why it was collected, how long it is kept or who can see it — send your query through our support channel with your account reference so we can locate the right data set.
For formal data requests, use the same support route described in the contact section of this page. Include your registered contact detail and a brief description of what you are asking about so the query reaches the right team.
If you have a question about your data, want to correct a record or need to submit a formal request, these are the routes available. We publish only the channels we can actually respond through — we do not list hours or response-time targets we cannot verify.
Open the chat widget visible at the bottom of the screen when you are signed in. Describe your data query and include your account reference so the team can locate your record directly.
Use the support form inside your account settings to submit a written data request. This route creates a tracked record of your query and is the right path for correction or deletion requests.
Find the published support email address in the contact section of the site footer. Include your registered contact detail, the nature of your request and any relevant transaction or session reference.
We apply consistent data-handling standards across every account on the platform, from how we store your bKash or Nagad transaction references to how long we keep session logs after an account closes. The four points below cover the practices that affect your account most directly.
Personal data and payment references are stored on secured servers. We do not hold full payment credentials — only the transaction reference passed to us by bKash, Nagad, Rocket or Bank Transfer after a completed step.
Functional cookies keep your session active and remember language settings. Analytics cookies are separate and can be switched off in your browser without affecting account access or wallet functionality.
Account data is kept for as long as your account is active and for a defined period after closure, as required by applicable rules. Once the retention period ends and no open query exists, data is removed from active records.
When this policy is updated, the revised version is published at this URL with a note of what changed. Continuing to use your account after a change is posted means you have seen the updated terms.
The questions below cover what we get asked most often about data, account records and contact routes. If your question is not here, use the support channel to get a direct answer.
We collect the details you enter during registration — name, contact information and the payment method you link, such as bKash, Nagad or Rocket. We also record device type and session activity to keep your account secure and to handle any disputes that come up.
We do not sell your data. We pass only the minimum required information to payment providers — bKash, Nagad, Rocket, Bank Transfer — to process a transaction. Those providers handle that data under their own privacy terms. We do not share account data for advertising purposes.
Sign into your account and open the profile section. Most fields — name, contact number, linked wallet — can be edited directly from there. For changes that require identity verification, follow the instructions shown on screen or submit a request through the support form.
Data is kept for a defined period after account closure, as required by applicable rules. Once that period ends and no open query or dispute remains, your data is removed from active records. The exact period depends on the type of data and local legal requirements.
No. bKash, Nagad and Rocket operate independently of your af22 account. We receive only a transaction reference after a completed payment — not your wallet credentials or payment app data. Each provider's privacy policy governs what they collect on their own platform.
Yes. Availability of certain data rights depends on local law and the eligible regions our platform serves. If local law in Bangladesh gives you rights that go beyond what is described here, those apply independently. Raise any jurisdiction-specific question through our support channel for a direct response.