Live / Casino
88fi operates under a defined policy framework that sets out how we handle your account, your data and your transactions. Access to this platform depends on your local law and eligible region — read these terms before you proceed.
Our legal framework is built around the principle that you should always know where you stand with us. This means we document how your account is created, how your session data is handled, and how payment transactions — including those made via Nagad and Upay — are recorded and retained. We do not make claims about jurisdictions where we cannot confirm eligibility. If you are accessing this platform from Bangladesh, availability is subject to your local law and the eligible regions we are authorised to serve at the time of your visit. We do not override local regulation; we align with it. Any action you take on this platform — opening an account, completing a transaction, engaging with our content — is covered by the terms set out across this legal section. These terms are updated when our obligations or practices change. We recommend you review them each time you return after a significant gap. If any section is unclear, our support route is the right place to raise a question — not assumptions drawn from third-party sources. Nagad and Upay transaction records are stored in line with our data retention schedule and are accessible through your account history.
Not every aspect of your interaction with 88fi falls under a single policy clause. This section maps out clearly what is inside and outside the scope of our legal terms, so you can identify which route applies to your question.
Creating, suspending or closing your account is fully within the scope of our legal terms. The conditions for account access, session control options and eligibility checks are set out in the account policy section of your profile area.
All payment activity processed through your wallet — including transfers via Nagad and Upay — falls within our transaction policy. Records are retained and can be reviewed from your account history at any time without contacting support.
Game titles, odds displays, promotional notices and editorial content published on this platform are governed by our content policy. Accuracy standards apply to all published figures; if you spot a discrepancy, use the support route to flag it.
External links, payment network infrastructure operated by Nagad or Upay, and any third-party tools accessed via this platform are outside our direct legal scope. Their own terms govern those interactions; we are not liable for third-party policy decisions.
Your rights under our policy are practical, not just procedural. You can review your transaction history — including Nagad and Upay records — directly from the account wallet section without raising a formal request. If the details held on your account are incorrect, you can update personal information through the account settings page; fields that are locked for security reasons require a support request with verification. Raising a question about how your data is used or retained is always a valid action. We respond through the support channels listed on this platform, and we do not dismiss policy questions as out of scope. If you want to request the correction of a material error in your account record, open a support ticket and specify the field and the correct value. We aim to acknowledge policy queries and will direct you to the relevant section of our terms for context.
Open your account wallet to view the full transaction log, including Nagad and Upay payment entries. No additional request is needed to access your own history.
Editable fields can be updated directly in account settings. Locked fields — such as registered mobile number or identity details — require a verified support request before any change is applied.
If any clause in our terms is unclear or you need clarification on how a specific rule applies to your account, contact us via the support route. We will point you to the relevant published clause.
For account closures, data queries or correction requests that require internal review, open a formal support ticket. Include your account reference and the specific section of the policy your query relates to.
Policy questions deserve a direct route, not a general inbox. Use the channels below to reach the right part of our support team. We do not publish contact hours we cannot verify, and we do not promise response windows we cannot consistently meet. What we can confirm is that these are the routes visibly available on this platform.
Open the live chat widget from any page on the platform. Use it to ask about a specific policy clause, flag a data concern or request guidance on the account correction process. This is the fastest route for straightforward questions.
For formal policy requests — including data queries, correction requests and account closure — use the email route published in the Help section of your account. Include your account reference and a clear description of the issue.
The Help Centre holds published policy articles that answer common questions about account access, transaction records and data retention. Check there first; if your answer is not covered, escalate via live chat or email.
How we protect and manage the information attached to your account is not a footnote — it is a core part of our policy. Here is how we approach the four areas that matter most to your account.
Account data and transaction records — including Nagad and Upay payment entries — are retained for the period required by our operational and compliance obligations. You can view your own records in the account wallet section at any time.
We use session cookies to keep you signed in and to record page interaction for performance purposes. You can review and adjust cookie preferences through your browser settings. Disabling cookies may affect how parts of the platform function.
Account security controls are accessible through the settings area of your profile. If you believe your account has been accessed without your permission, contact support immediately via live chat and follow the steps shown in the account security section.
To request a change to data we hold that you cannot edit directly, open a support ticket via email with your account reference. We will confirm receipt and guide you through the verification steps required before any change is applied.
These are the questions we see most often from people reading our legal section for the first time. If yours is not here, the support route is the right next step.
Yes. Access to 88fi depends on your local law and the eligible regions we serve. If local regulation in your area restricts access, these terms do not override that. Check the eligibility conditions in the account area before completing registration.
Your full transaction history — including Nagad and Upay entries — is available in the account wallet section once you are signed in. No support request is needed to view your own records; they are held there for the retention period stated in our data policy.
Open account settings and edit any field that is not locked. For locked fields — such as your registered identity or mobile number — submit a support request via the email route with your account reference and the correct value you want applied. Verification is required before changes are made.
Closing your account does not automatically delete all data we hold. Transaction records and identity information are retained for the period required by our obligations. You can request details of what is held and how long it is kept by contacting support through the email route.
Raise it through the live chat or email support route with the specific policy section and your account reference. We will review the application of the clause and respond with reference to the published terms. We do not resolve disputes by phone.
Session cookies are needed to keep you signed in and to record basic page interaction. You can adjust cookie settings in your browser, but disabling them may limit some functions. Preference and analytics cookies are optional and can be turned off without affecting core account access.