Mobile / Live
1777bft sets out its legal framework here so you know exactly what rules apply to your account, how we handle your data, and where to go when something needs clarifying. Access to this platform depends on your local law and eligible regions.
Our legal terms govern every interaction between you and this platform — from account creation and session activity to the records attached to your wallet. These terms are written for members accessing the platform from Bangladesh or other eligible regions, and your continued use of the account confirms that you have read and understood them. Where local law restricts access, these terms do not override that restriction; eligibility is always subject to the laws of your jurisdiction. Transactions processed through Nagad, Upay and Bank Transfer are governed by the specific conditions set out in our payment policy, which sits alongside these terms. Your transaction history, account status and any policy notices are visible inside your signed-in account area — that is the authoritative record, not third-party commentary. If a term appears unclear, you are entitled to request a plain-language explanation through our published support routes before taking any account action. We update these terms when our policy changes; the version displayed in your account at the time of any transaction is the one that applies. Checking the policy section periodically keeps you current with any amendments we have published.
Understanding the boundary of our policy helps you know which questions we can answer directly and which fall to external parties. The four areas below define what is inside and outside our legal responsibility.
Account creation, login, session management and wallet operations are fully within our policy scope. Any eligibility question — such as whether access is permitted in your region — is governed by local law, which our terms cannot override.
Deposits and withdrawals processed through Nagad, Upay or Bank Transfer are covered by our payment policy. Processing rules set by the payment provider sit outside our direct control, though we document the steps visible to you in the account area.
Game content supplied by studios in our lobby — and the session data those games generate — falls under this policy. RTP figures are shown only where the game or provider exposes them; we do not publish figures that are not sourced directly from the title.
External links, wallet apps such as Nagad or Upay, and any third-party service you reach from within your account operate under their own terms. We are not responsible for the policies, availability or conduct of services outside our platform.
You hold several practical rights in relation to the data and records tied to your account. These are not abstract entitlements — each one maps to a specific action you can take through the signed-in area or through our support routes. Reviewing your account activity log gives you a full picture of session history, wallet movements and any policy notices we have issued. If a detail in your profile is incorrect — name spelling, contact address, linked payment method — you can raise a correction request through the support channel; we will confirm the change or explain why it cannot be made. Where you have a question about how a specific piece of data is held or used, submitting a written query through our published contact route puts your question on record. We aim to respond clearly and within the timeframe published in our support policy. Your right to request account closure, data review or a policy clarification does not depend on having an active wallet balance.
Open the account history section after signing in to see every session, wallet movement and policy notice on your account. This log is the authoritative record for any dispute or clarification request.
If a profile field — such as a linked Nagad number or contact email — holds incorrect information, raise a correction request through support. We confirm changes or explain any restriction that prevents them.
Submit a written query through our published support route. Your question goes on record and receives a plain-language response. You do not need to take any account action before asking — querying first is the right approach.
You may request full account closure at any time regardless of wallet balance. The request path is available through the account settings area or directly via support. We process closures in line with the retention period stated in our policy.
All policy-related questions should come through the routes published on our platform. We do not accept legal queries through unofficial channels or social handles not listed on the site.
Start a live chat session from any signed-in page. Use this route for account-level policy questions, correction requests or clarification on how a specific term applies to your situation.
Send a written policy query to the email address published in the contact section of your account area. Email is the right channel for formal requests, such as data review, account closure or a documented correction.
The help centre inside your signed-in account lists published policy articles, step-by-step process paths and answers to common account questions. Check this before raising a support ticket — many policy questions are already answered there.
Our approach to data handling, cookies and account security follows the principles set out in our published privacy policy. We keep only what is necessary for account operation and policy compliance.
We hold account and transaction records for the period required by our policy. Once that period passes and your account is closed, we remove or anonymise data in line with the schedule described in the privacy section of your account area.
We use cookies to maintain your login session, remember your preferences and monitor for unusual account activity. Cookie settings and their purposes are described in the cookie notice accessible from the site footer.
Changing your account password, updating a linked payment method such as Upay or Bank Transfer, and reviewing active sessions are all actions you can complete from the security section inside your signed-in account.
When we update a legal term or privacy condition, we publish the new version in your account and, where material, send a notice to your registered contact. The version in force at the time of a transaction is the one that governs that transaction.
These questions reflect what members typically ask when they read through our legal terms for the first time. If your question is not covered here, use the support routes listed above to put it on record.
Yes. Access and eligibility depend on your local law and the eligible regions defined in our terms. We cannot override local legal restrictions, so you should confirm that using the platform is permitted under the laws that apply to you before opening or continuing an account.
The version displayed in the policy section of your signed-in account at the time of any transaction is the one that governs that transaction. We publish the effective date alongside each version, so you can check when the current terms came into force.
Yes. Submit a written data request through our published email support route. We will confirm what records we hold, the basis on which we hold them, and the retention period that applies. No account action is required before making this request.
We retain transaction and account records for the period required by our policy, then remove or anonymise them. The specific retention schedule is described in the privacy section inside your account. After the retention period, the data is no longer accessible.
The transaction records we hold on our side — amounts, timestamps and wallet references linked to Nagad, Upay or Bank Transfer — are covered by our policy. The records held by Nagad or Upay themselves fall under their own terms, which operate independently of ours.
Send a written query to the email address published in your account's contact section. State the policy point in question and the action you are objecting to. We log every formal query and respond with a plain-language explanation of our position and any available next steps.