Mobile / App
77hats publishes these terms so you know exactly where you stand when you use the platform. Access and eligibility depend on your local law and the eligible regions we serve — read the sections below to understand what applies to your account.
These terms govern the relationship between you and 77hats when you access or use our platform. Whether you reach us through a mobile browser, manage your account wallet, or process a transaction via Nagad or Upay, the same policy framework applies. Availability of the platform — and the extent to which these terms are enforceable — depends entirely on the laws of the region where you are located. We do not represent that access is lawful in every jurisdiction, and it is your responsibility to confirm that using 77hats is permitted under the laws applicable to you. Nothing in these terms overrides local legislation. Where a conflict exists between any clause here and the law of your region, local law takes precedence. We may update sections of this policy from time to time; material changes will be visible in this page before they take effect. If you continue using the platform after a published change, we treat that as acknowledgment of the updated terms. Questions about a specific clause can be directed to our support team via the contact routes listed further down this page.
Not every part of your experience falls under the same policy clause. The table below outlines what is inside this policy's scope, what sits outside it, and why the distinction matters when you raise a question or dispute.
Login, session management and account settings are fully within scope. Any issue with your credentials, active session or account controls is handled under this policy and can be raised with our support team directly.
Wallet movements — including Nagad and Upay transfers in and out of your account — are covered. Third-party payment network rules sit outside our policy; we cannot override charges or holds applied by the network itself.
Game content, published odds, promotional notices and account-area text are all within scope. We are responsible for what we publish on the platform, and you can raise a concern if you believe published content is inaccurate or misleading.
External links, studio software operated by Habanero, CQ9 or other providers, and payment network infrastructure fall outside the direct scope of this policy. Their own terms apply to those services, and we cannot accept liability for third-party conduct.
Your rights under this policy are practical, not abstract. You can review your transaction records at any time by opening the account history section — every Nagad or Upay movement is logged with a timestamp and status. If the details on your account are incorrect — name, contact address, registered mobile number — you can request a correction by contacting support with the relevant documentation. We will confirm receipt and tell you what steps follow. If you have a question about how a specific clause applies to your situation, open a support ticket and reference the clause number or section heading; we will respond through the same channel. Eligibility questions — whether the platform is available to you under local law — are your responsibility to verify, but our team can point you toward the published eligibility language if you need to locate it. Account closure is also your right; submit a written request via the support route and we will process it in line with the retention schedule described in the trust section below.
Transaction history, session logs and account-change records are accessible from within your signed-in account area. Open the history tab to see the full log of activity on your wallet.
Submit a correction request through support if any registered detail is wrong. Include the field to be changed and the evidence we ask for; we will confirm the update once verified.
Reference the specific section heading or clause when you contact us — it moves the conversation faster. Our support team can clarify how any clause applies to your account without requiring you to submit a formal complaint.
Write to us through any published support route to close your account. We process closure requests in line with our data retention schedule and will confirm once your account is deactivated.
When a policy question cannot be resolved by reading this page, these are the routes to reach us. Use the channel that suits your situation — written queries about account data or correction requests are best handled over email or ticket, while live chat suits faster clarifications.
Open the chat widget from any signed-in page on the platform. Use this route for straightforward clarification of a clause or to get directed to the right section of this policy.
Submit a ticket through the account help section for correction requests, account closure or any written record you need. Reference the policy section in your message to speed up the response.
Send written queries — particularly those involving account data or formal correction requests — through the email address published in the account help area. Keep your registered mobile number in the message for verification.
Data handling at 77hats follows a defined retention schedule and a clear contact path for any query about what we hold. We collect only the information needed to operate your account and process transactions — session data, wallet activity and the details you provide at registration. Cookies are used to maintain your session and remember your account preferences; you can review the cookie notice published on the platform for a full breakdown. Account data is retained for a period consistent with our operational and legal obligations — it is not deleted the moment an account closes. If you want to know what we hold about you, submit a request through the support routes listed above.
We use session cookies to keep you signed in and preference cookies to remember your account settings. The full cookie breakdown is in the published cookie notice accessible from the footer of the platform.
Your account is protected by credential verification at login. If you suspect unauthorised access, contact support immediately through live chat or a support ticket so we can review the session log.
We retain account and transaction records for the period required by our operational obligations. Closed accounts are not immediately purged — records are held for the duration set out in the retention schedule before deletion.
For any question about what data we hold or how it is used, reach out through the support ticket route. For a formal written request, use the email contact published in the account help section.
Real questions about your rights, data, access and how to contact us — answered here so you do not need to raise a ticket for every clarification.
Access to 77hats and the enforceability of these terms depend on your local law and eligible region. We do not confirm legality in any specific jurisdiction — it is your responsibility to verify that using the platform is permitted where you are located.
Sign in and open the account history section. Every wallet movement — including Nagad and Upay transfers — is recorded with a timestamp and status. If an entry looks wrong, contact support and reference the transaction in question.
Yes. Submit a written request through the email support route published in the account help area. Include your registered mobile number so we can verify identity. We will confirm what data we hold and how it is used.
Contact support via live chat or a support ticket, name the field to be corrected and provide the evidence we ask for. We confirm the update once verification is complete. Do not attempt to edit restricted fields directly — changes go through the support team.
Account and transaction records are retained for a period consistent with our operational and legal obligations — they are not immediately deleted. After the retention period lapses, records are removed. You can ask for the specific schedule through the support ticket route.
Submit a support ticket and reference the exact section heading or clause you are disputing. Written disputes are handled through the ticket or email channel so there is a full record on both sides. Live chat handles clarifications; formal disputes need a written trail.