Mobile / Slots
9f22 publishes this page so you understand what account and lobby access actually involves — what we do with your details, how payment records sit against your wallet, and where to raise a question. Availability depends on your local law and eligible region.
This page sets out how 9f22 handles account access, record-keeping and the boundaries of what we can confirm for you. Terms differ by where you're accessing from — mobile browser or desktop — and by what local law allows in your region, so we keep the wording here general rather than promising one outcome everywhere. When you open an account on 9f22, you're agreeing to the posture described on this page and on our linked terms: we don't alter your wallet entries after the fact, and anything tied to a specific game category stays with that game, not with this policy page. If you add funds through bKash or move funds by Bank Transfer, that transaction sits in your account history exactly as your provider confirms it on their side — we don't overwrite or reinterpret those entries. Where local law restricts access from your region, that restriction applies regardless of what this page says, and we'd rather you check your own jurisdiction than rely on a blanket statement from us. Nothing here replaces the fuller terms linked from your account settings; this is the policy posture, not the full clause-by-clause text.
This policy applies wherever you're using a 9f22 account, but what it actually covers narrows down once you look closely. Account access, your transaction record and the lobby content you read on our pages all sit inside the scope of this page. What sits outside it is anything controlled by another party — your bKash or bank provider's own processing, any local law that restricts access from your region, and third-party odds or match data pulled into our sportsbook pages. We separate these deliberately: if something is inside our scope, we can check it against your account history and respond; if it sits with a provider or with local regulation, we can only point you toward where that answer actually lives. Reading the four areas below before you raise a question usually tells you which bucket your issue falls into, and that alone saves a round of back-and-forth with support.
Covers how you sign in, the identity details we hold against your profile and how your account status is shown to you; it does not cover access blocked by local law in your own region, which sits outside anything we're able to change from our side.
Covers how a bKash add-funds entry or a Bank Transfer entry shows up in your account history once it's logged; it does not cover how your own bank or wallet provider processes that transfer on their own system before it ever reaches our side.
Covers the lobby pages, game listings, category names and the written policy text you read directly on 9f22; it does not extend to third-party odds data, scores or match data shown alongside our cricket-led sportsbook pages, which come from a separate data source.
Covers what we publish about a service we link to, such as the confirmation screen your bKash or bank provider shows you after a transfer; it does not cover their own policies or process, which you'll find published on their own site, not ours.
You have a few practical options once your 9f22 account is open, and none of them require guesswork. You can check the record of your own account — your deposit and transaction history sits inside your account area, matched against whatever bKash or Bank Transfer confirmation your provider issued. You can correct account details that are wrong, like a contact field entered incorrectly at signup, by raising it through support rather than editing silently. You can ask a direct question about this page, your data or how a transaction was logged, and expect a written answer through the channel listed below. None of this is automatic moderation — a real check happens on our side before we respond, so a short, specific question gets you a faster, more useful reply than a general one.
Open your account area to see deposit and transaction entries logged against your profile, matched to whatever your bKash or Bank Transfer confirmation shows on your side.
If a contact field or account detail was entered wrong at signup, raise it through support instead of editing it yourself — we log the correction against your account history.
Ask us directly if a clause on this page is unclear or if you want to know how a specific entry was recorded; we answer in writing through our support route.
If something on your account doesn't match what you expect — a transaction entry, a detail field — contact support and describe what you're seeing, with as much specific detail as you can give.
When a question comes up about this policy — a transaction entry, an account detail, how long we hold something — the first stop is the support route listed on your account page, not a public comment thread. We read account-specific questions against your own account history, so a date, an amount or the exact wording of a form field helps us answer faster than a general message. We don't publish a fixed response window on this page, because contact volume and the nature of a question both matter, but every question submitted through the published route does reach someone who can check your account. If your question is about a bKash or Bank Transfer entry specifically, mention the payment method and the rough timing so the entry is easier to trace against what your provider confirmed. Keep the question specific — vague messages take longer to resolve than ones with a clear reference point.
Reach us through the support route listed on your account page whenever you have a question about this policy, a transaction record that looks off, or an account detail you'd like corrected after signup — give us the specifics and we'll follow up.
If a clause on this page reads unclear to you, send a specific question through the same support channel listed on your account page — we reply in writing, addressed to your actual question, not a general template answer sent out to everyone.
For a bKash or Bank Transfer entry that looks off against your account history, flag it through support with the date, the amount and what you expected to see, so we can check it against what your provider confirmed on their side.
9f22 treats your account data as something we hold to run your account, not something we repurpose for anything else. Your login credentials, your contact field and the transaction log tied to a bKash or Bank Transfer entry stay inside your account record and get used to answer the exact question you raise with support — nothing more. Cookies on your browser keep a session going so you don't have to sign in again every time you switch screens on mobile or desktop, and they don't carry payment details, which remain with your bKash or bank provider. We keep account and transaction history for long enough to resolve a support query raised about it later; we don't publish a fixed retention period on this page because that depends on the type of record involved. If you want to know what's currently held against your profile or you suspect your account access wasn't you, the support route is where that conversation starts.
We hold the account details you give us — contact field, login credentials, transaction log — only to run your account and match it against your payment confirmations from bKash or Bank Transfer, nothing stored beyond what that actually needs.
Browser cookies keep you signed in across a session on your phone or desktop and remember basic display settings; they don't carry payment credentials, which stay only with your bKash or bank provider, never passed to us directly at any point.
Your login sits behind the credentials you set at signup, on either the mobile browser or desktop; if you think your account was accessed without you, tell support straight away so we can look at the account history together and flag anything unusual.
We keep transaction and account history long enough to answer a support query about it later; if you want to know what's held against your profile, ask through the support route listed on your account page and we'll walk through it with you.
A handful of questions come up repeatedly once someone actually reads this page instead of skipping past it. Below are the ones we see most through support, written out plainly rather than left buried in clause language — on account data, payment records and how this policy sits against local law.
It applies to anyone opening a 9f22 account, but actual access always depends on your local law and whether your region is eligible — check that before you rely on anything written here.
Yes — your account area holds the deposit and transaction entries logged against your profile, including anything tied to a bKash add-funds entry or a Bank Transfer.
Raise it through support rather than editing it yourself; we log the correction against your account so there's a clear record of the change.
We hold account and transaction details to run your account and match payment confirmations; this page doesn't extend to the separate policies your bank or wallet provider applies on their own side.
Use the support route listed on your account page and ask your question directly — we answer in writing rather than through a general template response.
This page covers account access, payment records and site content; game mechanics and any third-party odds or score data sit outside what this particular policy page covers.
Yes — flag the date and amount through support and we'll check it against your account history and whatever your provider confirmed on their side.