Mobile / Sports
ld777 sets out its legal framework here so you know exactly where you stand — what this platform covers, how your account data is handled, and which contact paths are open when you have a policy question. Access and eligibility depend on your local law and applicable eligible regions.
This policy applies to every account held on ld777 and governs how we collect, store and act on the information you provide when you register, deposit or raise a support request. Because Bangladesh has its own regulatory landscape, whether a particular feature or transaction route is available to you depends on your local law and the eligible regions we can serve at any given time. We do not make blanket eligibility claims; instead, the account area reflects the routes and services confirmed for your region at the time you log in. For deposit and withdrawal activity, the payment context shown in your account — Nagad, Upay and Bank Transfer where configured — determines which routes appear. We keep records of account actions in line with standard retention practice; those records are accessible to you on request through the support paths listed on this page. Where a third-party payment processor handles a transaction, their own terms also apply alongside ours, and we note that clearly in the relevant account flow. Nothing in this policy overrides applicable local law. If a term conflicts with a local legal requirement that applies to you, the local requirement takes precedence to the extent of that conflict.
Not every interaction on ld777 sits under the same rule set. This section maps which areas this policy directly governs and where separate terms or third-party rules take over, so you can navigate your account with a clear picture of who is responsible for what.
Registration, login, identity checks and account-level settings fall fully within this policy. We handle those steps directly, and the rules here apply end-to-end. If you need to update account details, the process is described in the rights section below.
Deposits and withdrawals processed through Nagad, Upay or Bank Transfer are subject to this policy for the ld777 side of the transaction. The payment processor or bank handling the transfer applies its own terms simultaneously; we cannot override those. Your account transaction log reflects our record.
Games, odds, editorial copy and promotional notices published on ld777 are within our editorial scope. Content availability, including game titles from studios in our lobby, may vary by region. We update the lobby and notice board; third-party studios supply the game engines under their own licensing.
External links, embedded feeds or partner services accessed from this site operate under the terms of those third parties. We are not responsible for their data practices or content. Where a third party is involved in a core flow — such as payment processing — we note that clearly at the relevant step.
Knowing your rights is one thing; knowing how to act on them is what matters day to day. Under this policy, you can review the personal data held against your account, request corrections where something is wrong, and ask us to clarify how a specific piece of information is used. The request process starts through the support routes listed on this page — email is the most reliable channel for anything that requires a written record. For account corrections, the fastest path is the account settings area in the signed-in view, where you can update contact details and wallet associations directly. If a correction requires identity verification before we can act on it, the account area will prompt you through the fields and documents needed. For anything that cannot be resolved in self-service — a data access request, a question about retention, or a dispute over a recorded transaction — raise it through support and we will route it to the right team. We aim to acknowledge policy-related requests and provide a substantive response, though processing time depends on the nature of the request and any verification steps required.
Request a summary of the personal data held on your account by contacting support in writing. We will confirm what is stored and how it is categorised.
Update contact information or wallet associations directly in the account settings area. Identity-sensitive changes prompt a verification step before the update is saved.
For questions about how a specific data point is used or retained, contact support by email. Include your registered account identifier so we can locate the relevant records promptly.
If an initial support response does not resolve your question, ask for escalation in your reply. We route escalated policy requests to a dedicated review step separate from general account support.
When you have a policy question that cannot be resolved in the account area, these are the contact routes available. Use the channel that matches the nature of your query — written requests for data or corrections, live chat for quick clarification on policy scope.
Send written policy requests, data access queries or correction requests to the support email address published in the site's contact section. Include your account reference for faster routing.
The live chat channel on the site is available for policy clarification questions and to check the status of an open support request. It is the fastest path for straightforward queries about scope or account settings.
The support centre accessible from the signed-in account area contains policy documents, account guides and a request form for data and correction queries. Start here before raising a direct contact.
Behind the policy text, there are concrete operational practices that govern how information moves, where it is held and how long it stays. This section describes those practices at a level you can verify through your own account activity.
Account and transaction records are retained for the period required by applicable operating standards. You can request a summary of what is held at any time through the support email path. Records tied to payment activity — including Nagad, Upay and Bank Transfer transactions — are held for as long as required for reconciliation.
We use session cookies to keep your account state while you navigate the lobby or account area. Analytics cookies operate under a separate consent layer. You can review and adjust cookie preferences through the privacy settings link in the site footer.
Password changes, wallet updates and identity-sensitive edits require confirmation through the verification step shown in your account settings. We do not send unsolicited requests for account credentials by email or chat; if you receive such a message, report it through support immediately.
When this policy is updated, a notice is posted in the account area and, where the change is material, communicated to the registered contact address. Continued use of the account after a notified update constitutes acceptance of the revised terms, so check the account notice board periodically.
These are the questions we see most often from account holders who want to understand their rights, how data is handled and what to do when something needs to change. If your question is not here, the support routes above can help.
Access and eligibility depend on your local law and the eligible regions we serve. The account area reflects services confirmed for your region when you log in. If a feature or payment route is not shown in your account, it is not currently available to your region.
Send a written request to the support email address in the site's contact section, including your registered account identifier. We will confirm what data categories are held, how they are used and for how long they are retained, in line with our standard data handling practice.
Yes. Most contact and wallet details can be updated directly in the account settings area when you are signed in. Changes that affect identity-sensitive fields trigger a verification step before the update is saved. For corrections that cannot be completed in self-service, contact support by email with the account reference and the specific correction needed.
Transaction records, including deposit and withdrawal entries tied to Nagad, Upay and Bank Transfer, are retained for the period required by applicable operating standards even after account closure. You may request a summary of those records before closing your account through the support email channel.
For transactions through Nagad, Upay or Bank Transfer, the payment processor or bank involved applies its own terms alongside ours. We hold the transaction record on the ld777 side; the processor holds its own. The account transaction log reflects our record only. For disputes about the processor's side, their support channel is the appropriate route.
Policy updates are posted as notices in the account area. For material changes, we also send a communication to the contact address registered on your account. Check the account notice board periodically, particularly before making significant account or payment changes. Continued account use after a notified update confirms acceptance.