Slots / Live
fg80 com publishes these legal terms so you know exactly where you stand — what this policy covers, how your account data is handled, and which steps are open to you if something needs to change. Access to our platform and its services depends on your local law and the eligible regions listed in the policy.
Our policy is written to reflect the real conditions of operating an account-based platform for Bangladesh. Nothing in these terms creates a legal certainty that overrides your own jurisdiction — access, eligibility and permitted activity all depend on the laws and regulations that apply where you are located. We do not make claims that override local law, and we do not promise outcomes that local regulation may restrict. When you fund your account through bKash, Nagad or Upay, the transaction record that appears in your account history is governed by the terms you accepted at registration. Those records are the reference point for any dispute or correction request — not a verbal conversation or a cached browser state. If a transaction appears incorrectly, the account history page is the right place to start, and our support route is the next step. We update these terms when our policy or the platform changes in a material way. The version published on this page is the current one. We do not backdate changes, and we do not apply a new version to a dispute that arose under a previous version. Checking this page after any major account change is the practical habit we recommend.
These terms define four distinct areas of coverage. Understanding which area your question falls into helps you find the right answer faster — whether that is an account access question, a payment record query, a content question or something involving a third-party service we do not directly control.
Covers login, registration, identity verification and account suspension. Any decision about your account access — including region eligibility — falls under this section. Access remains subject to local law and the eligible regions we are able to serve.
Covers deposits made via bKash, Nagad or Upay and the withdrawal path back to your wallet. Your account history is the authoritative record. Disputes about a specific transfer amount reference the transaction ID shown in your account.
Covers game availability, lobby display and any notices published on the platform. Content we host — including games from JDB, Bigtime Gaming, CQ9 and Microgaming — is governed by these terms and by each provider's own licence conditions.
Payment processors, mobile wallet operators and any linked external service operate under their own terms. We are not liable for conditions set by bKash, Nagad or Upay beyond our own platform boundary. Review those providers' published terms separately.
This policy is not only a statement of our obligations — it also sets out the concrete steps you can take when something does not look right. You are not limited to reading; you can act. The four areas below cover the most common situations we see from account holders. Reviewing your transaction history is always the first step for a payment question. The account history page shows every deposit and withdrawal with a date, method label — bKash, Nagad or Upay — and a status. If a record looks wrong, note the transaction ID before contacting support. For account detail corrections such as a phone number or email address, the account settings section shows the fields you can edit directly. Changes that require identity re-verification are flagged in the same view. If your question is about policy interpretation rather than a transaction, our published support route handles written queries — see the contact section below.
Open your account history to check every deposit and withdrawal. Each entry shows the payment method used — bKash, Nagad or Upay — along with the date and current status. This is the reference point for any payment question.
Account settings let you update contact information directly. Fields that require additional verification are clearly marked in that view. Do not send sensitive account details through an unverified channel.
If you have a question about how a specific term applies to your account, send it through the support route listed on this page. Include your account reference and the specific section you are asking about so we can respond with precision.
For access issues, suspended accounts or a change request that account settings cannot handle, contact support directly. We handle these through the published routes below — not through social media or third-party channels.
We publish specific contact routes for policy-related questions. Use the channel that matches your question type — account access issues and transaction disputes each have a different priority path. We do not publish response time commitments we cannot consistently keep, so we describe the route rather than a timeframe.
The live chat icon on the platform connects you to our support team for account and policy questions. Have your account reference and the relevant transaction ID ready before you start the conversation.
Written policy questions — including requests to correct account data or clarify a specific term — can be sent through the email contact form in the support section of your account. Include the policy section reference in your subject line.
The help centre inside your account covers the most common policy questions with step-by-step answers. Check there first before raising a direct support request — your question may already be answered in the published guidance.
We handle account data with a clear retention and access framework. This section explains what we store, how long we keep it, and the practical controls you hold over your own information. Nothing here is a general statement — each point maps to a real account function you can check or act on.
Account records — including transaction history for bKash, Nagad and Upay deposits — are retained for the period required by our operational policy. You can view your own history at any time through the account section. Retention periods are not shortened on request where a transaction is under review.
We use cookies to maintain your session, remember your account login state and record which lobby sections you have visited. The cookie notice shown on first visit explains the categories in use. You can manage non-essential cookies through your browser settings without affecting your account access.
Your account is protected by the credentials you set at registration. We do not ask for your password through chat or email. If you receive a message claiming to be from us and asking for login details, report it through the live chat route — that is not a communication we send.
Requests to update, correct or remove account data follow the process described in the rights section above. Changes that cannot be made through account settings are handled by the policy support team via the email contact form. We confirm every accepted change in writing.
These are the questions we receive most often about our legal terms, account rights and data handling. If your question is not covered here, the support routes in the contact section above are the right next step.
Access to fg80 com and the applicability of these terms depend on your local law and whether Bangladesh falls within our eligible regions. We do not make a blanket eligibility claim. Check the account registration flow for the current region list before proceeding.
Every deposit made through bKash, Nagad or Upay generates a record in your account history. That record shows the date, method, amount and status. It is the reference point for any dispute. We retain these records for the period set out in our operational policy.
Yes. Contact details and certain account fields can be updated directly in account settings. For corrections that require identity re-verification or that cannot be changed through the settings page, submit a written request through the email contact form with your account reference included.
Start by noting the transaction ID from your account history page — the entry that shows your bKash, Nagad or Upay reference. Then contact support via live chat or the email form, providing that ID. A verbal description without the transaction ID slows the review process.
We use cookies for session management, login state and lobby navigation records. The categories are disclosed in the cookie notice on first visit. Non-essential cookies can be turned off through your browser settings. Essential session cookies are required for the platform to function correctly.
We never ask for your password through chat, email or any other channel. If you receive such a message, do not respond. Report it through the live chat support route on the platform so our team can flag it. Change your password immediately through your account security settings.