Sports / App
Access to fachai777 depends on your local law and the eligible region where you open your account — we set out that clearly here, before anything else. This page covers how our policy applies to your account, what controls you hold, and where to reach us when a question comes up.
fachai777 operates under the understanding that access to our platform is conditional on your local law and the region in which your account is registered. We do not make blanket eligibility claims. If the law where you are located restricts or prohibits this type of platform, that restriction takes precedence over anything written here, and it is your responsibility to check before proceeding. Where your account is active and your region is eligible, this policy governs how we handle your account data, how we process transactions through verified payment rails such as bKash and Upay, and how session activity is recorded. Every transaction through your wallet — whether a bKash deposit or an Upay transfer — is logged under your account record and held according to the retention terms described on this page. We do not alter policy terms retroactively without notice. When a material change occurs, we post the updated version and indicate the effective date. Continuing to use your account after that date counts as acceptance of the revised terms. If you disagree with any change, the correct step is to contact support before the effective date — not after — so we can note your objection and discuss your options.
bKash deposits and transfers are logged as account transactions under your registered wallet number. The record appears in your account history after each confirmed transaction.
Upay transfers follow the same logging process. Each confirmed Upay transaction is attached to your account record and is available for review in your dashboard.
Access eligibility is determined by your local law. We do not override local legal restrictions; you confirm eligibility when you open your account.
Changes are posted with an effective date. Continued use after that date constitutes acceptance. Raise objections with support before the date shown.
Not every aspect of your experience falls under this single policy document. Understanding where the boundaries sit helps you find the right route when something needs to be resolved. The four areas below clarify what is inside scope, what sits adjacent to it, and what falls outside it entirely — so you go to the right place the first time.
Your login credentials, session state and account security settings are inside scope. This policy governs how we store that data, how long we hold it, and the steps you take to update or close your account through the dashboard.
Wallet transactions processed through bKash or Upay are inside scope as account records. The policy covers how those records are retained and how you request a review. It does not set the processing rules of the payment provider itself.
Game content supplied by studios in our lobby — including titles from Spadegaming, PG Soft and CQ9 — is inside scope for account-session logging. Game mechanics and prize structures are governed by the provider's rules, which are shown inside the game itself.
Links to third-party sites, external payment gateways beyond our verified rails, and any off-platform service are outside scope. We hold no policy authority over third-party data practices; check their own terms directly.
This policy is not just a document we hold — it translates into specific actions you can take from your account. You can review your transaction history at any point after login; the record includes every confirmed bKash and Upay transaction attached to your wallet. If a detail on your account — such as a registered contact number or display name — is incorrect, the correction path runs through the account settings page, where the fields are editable with verification. For questions about how your data is held or what records we retain, the support channel is the right route: raise it there and we log it as a formal policy enquiry, not a general chat message. Session limit preferences — the controls that let you set how long a session runs before a prompt appears — are found in your account dashboard after login. We do not bury those controls; they are part of the account interface by design.
Log in and open the account history section. Every transaction — bKash deposit, Upay transfer, game session — appears there in chronological order with timestamps.
Go to account settings after login. Editable fields include contact number and display name. Some changes require a verification step; follow the instructions shown in the field.
Contact support and state that your message is a policy enquiry. We log it separately from general support tickets so the right team sees it and responds with the relevant detail.
If you need to pause your account or update your session control settings, start with the dashboard controls. If those do not cover your situation, support can escalate the request on your behalf.
When your question is specifically about this policy — data retention, account records, eligibility or a transaction dispute — use one of the three paths below. Each route reaches a team that can log a formal response rather than a general reply. For wallet-specific questions involving bKash or Upay transactions, include your registered wallet number in the message so we can pull the correct account record without delay.
Open the support chat from any page after login. State that your message is a policy or account enquiry at the start so it is routed correctly. Available for active account holders.
Many policy-related actions — session controls, account detail edits, transaction history — are self-service inside your dashboard. Check there first; it is the fastest path for standard requests.
For data requests, objections to policy changes or escalated disputes, contact support and mark your message as a formal policy enquiry. We log it and respond with a documented reply.
We hold account data only for as long as it is needed to maintain your record and comply with the obligations that apply to our platform. Transaction logs — including bKash and Upay records — are retained for the period set out in the version of this policy current at the time of the transaction. Cookies are used to maintain your session state across devices; you can manage cookie preferences through your browser settings. Account security uses credential verification at login; if you access the account from a new device, you may be prompted to confirm your identity through the verification step shown on screen. Requests to update held data or to ask what we retain about your account should go through the support channel marked as a policy enquiry.
Account and transaction records are held for the period specified in the current policy version. The retention period for bKash and Upay transaction logs is tied to your account status.
Cookies keep your session active across devices. Manage them in your browser at any time. Disabling certain cookies may affect how your account dashboard loads between sessions.
Credential checks apply at login. Accessing your account from a new device may trigger a verification prompt. Follow the on-screen instructions shown at that step to confirm your identity.
To ask what data we hold or to request a correction, contact support with a clear policy enquiry label. We respond with a documented reply rather than a general support message.
The questions below come from account holders who wanted a clearer picture of how this policy works in practice. If your question is not listed here, reach out through the support chat and mark it as a policy enquiry.
Yes. Access depends on your local law and the eligible region where your account is registered. If the law in your location restricts this type of platform, that restriction applies regardless of your account status. Check your local regulations before proceeding.
Log in and open the account history section. Every confirmed bKash deposit and Upay transfer is listed there with a timestamp and transaction reference. If a record appears missing, contact support with the wallet number and approximate date.
Go to account settings after login. Fields such as your registered contact number are editable there. Some changes require a verification step — follow the instructions shown in the field at the time you make the edit.
We retain your account and transaction records for the period specified in the current policy version. That period is tied to your account status and applicable obligations at the time. Contact support to ask specifically what is held and for how long.
When we post a policy update, we include an effective date. Raise your objection through support before that date and mark it as a formal policy enquiry. We log it and discuss your options with you before the change takes effect.
Cookies maintain your session state so your account dashboard loads correctly whether you are on a phone or a desktop. Manage cookie preferences in your browser settings. Disabling certain cookies may affect dashboard functionality between sessions.