Mobile / Sports
ld777 publishes this legal page so you can see how account access, transactions and site content are handled under one notice before you open or continue a session. It is written for members in Bangladesh, and what applies to you turns on your local law and on the regions we are able to serve.
Written for members in Bangladesh, this notice sets out the ground rules we hold ourselves to when you use ld777. Access is not automatic everywhere: whether you can open an account, deposit or play turns on your local law and on the regions we are able to serve, so check the rules where you live before you carry on. Where a rule in your jurisdiction conflicts with something written here, the local rule comes first. We keep the wording plain on purpose, so you can read one screen and understand what we ask of you and what you can ask of us. Money movement sits inside the same notice. bKash, Nagad, Rocket and Bank Transfer are the routes we show inside your wallet area, and each one leaves a reference or confirmation you can find again in your transaction history. We do not publish a processing time here, because it depends on the rail and on the checks we run on your account. What we can say is that every movement keeps a record you can open later. If a transfer is held for a check, your account area tells you what is still missing rather than leaving you to guess. This page changes when the rules around a payment route, a game category or a market change. When that happens, the wording you read here replaces anything older, so today's version is the one that applies to your account.
A policy only helps if you know what it governs, so here is the boundary in plain words. Account access means your sign-in details, the contact information saved to your profile, the devices we recognise and the session settings you control once you are in. Wallet transactions means every deposit or withdrawal you make through bKash, Nagad, Rocket or Bank Transfer, together with the reference each route leaves behind. Site content means the games, tables and pages we publish, including how we describe availability in each region. It does not reach outside our own service. If a payment provider is slow, or your network drops mid-session, that sits with the provider or the network and not with this notice. A third-party site you reach through a link we publish keeps its own rules. Your local law also sits above anything written here. When in doubt, treat this page as the rule for your account and the provider's own terms as the rule for their service.
Everything tied to getting into your profile sits under this notice: your sign-in details, the contact information saved there, the devices we recognise and the settings you control once you are in. If a sign-in fails or a device looks unfamiliar, this is the wording we work from with you.
Deposits and withdrawals through bKash, Nagad, Rocket or Bank Transfer are part of the same notice. Each route leaves a reference you can open later, and any check we run on a transfer follows the wording published here rather than something decided case by case.
The games, tables and pages we publish are included as well, along with the category names and any wording we use about availability. If a category is not open to your region, that comes from the eligibility rules described on this page rather than a separate set of house terms.
A payment provider, a network operator or a site you reach through a link we publish keeps its own terms. We cannot rewrite those or answer for them. If something breaks on their side, raise it with them first, then tell us through support so we can check our own record of the same event.
You have more control over your account than most people use. Start with your own records: your transaction history, your session settings and the contact details saved to your profile are all visible once you sign in. If a phone number, an email address or the spelling of your name has changed, update it yourself in the profile area so our checks match reality. A wrong email address is the most common reason a confirmation never reaches you. When something looks off, you do not have to guess. Raise it through the support route published on this site and include the reference number from the transaction, the date and the device you used. That is enough for us to trace the entry. If you want to know how a decision was reached, ask, and we will explain the wording behind it. If you want a detail corrected, or removed where the law allows, put the request in writing and we will tell you what we can do and what we cannot.
Once you sign in, your wallet history and session details are yours to look at. Open the transaction list and match the reference number against the confirmation you received. If the two do not line up, keep them side by side — that comparison makes the entry easy to trace.
A phone number, email address or name spelling that no longer matches reality causes failed confirmations. Update it in your profile area before you raise anything else. For changes you cannot make yourself, send the request through the published support route and tell us what should read differently.
You can ask why a transaction was checked, why a session ended, or how a decision was reached under this policy. Include the date, the reference and the device. We answer from the published wording rather than from memory, so what you get back matches what is written here.
You may ask what we hold, ask us to fix a detail that is wrong, and ask us to remove what we are allowed to remove. Put the request in writing so it carries a date. We will say clearly what we can do and what local law requires us to keep.
Questions about a policy are easier to raise from inside your account, because that is where the details already sit. Sign in first, then open the support route shown on our support page — the same route you would use for a wallet question. Have the reference number, the date and the device you were on ready; those three details let us trace what happened instead of asking you to explain it twice. If your question is about access rather than money, tell us which screen you saw and what you expected. A screenshot helps. If it is about data, say plainly what you want changed. We answer policy questions in English, and we answer from the same published wording you are reading on this page. We do not publish a fixed response time, and we will not invent one here. What we can say is that every message sent through the published route stays attached to your account, so a thread does not disappear between one question and the next.
The help route inside your account is the one to use first, because the record of your session is already attached to it. Open it from the account area after you sign in, describe what you saw on screen, and add the reference number if money is involved.
Our support page carries the contact option we publish for members. Use it for policy questions, access problems or anything about your data. Keep the message to one issue where you can, and include the date and the device, so the thread stays easy to follow from either side.
For anything about your data, or a formal question about this notice, put the request in writing through the published support route. Say what you want changed and why. A written request gives us something concrete to act on and gives you a dated record of what you asked for.
Your details exist so that we can run an account, not for anything else. We hold what you give us at sign-up — name, contact details and the record of what moves through your wallet — because that is what a wallet needs in order to work. Cookies on our pages keep you signed in and remember the device you used last time, which is why a return visit on the same phone feels quicker. Security is shared work. Keep your sign-in details to yourself, use a screen lock on the phone you play from, and sign out on a shared device. If you think someone else has your details, tell us through the published support route so we can go through the session history with you. We keep records for as long as the law and our own checks require, then remove what we no longer need. You can ask what we hold, ask for a correction, or ask us to delete what we are allowed to delete.
We keep the details you give at sign-up, the record of what moves through your wallet, and basic session data such as the device and browser you used. That is what an account needs in order to work, and what we need to answer a question about your own history.
Cookies keep you signed in between visits and remember the device you came back on. They let the lobby load in the state you left it. You can clear them in your browser settings at any time, though you will need to sign in again afterwards and the return visit will feel less familiar.
Use a screen lock, keep your sign-in details private, and sign out when you hand the phone to someone else. If a session starts that you did not begin, tell us through the published support route and we will go through the session history with you rather than leaving you to work it out alone.
Records stay while the law and our own checks require them, then we remove what is no longer needed. You can ask what we hold, ask for a correction, or ask for deletion where the law allows it. Send those requests in writing so each one is dated and traceable.
These are the policy questions we hear most often from members in Bangladesh, answered from the same wording you have just read. If yours is not here, the support route above is the place to send it. Nothing on this page replaces the rules that apply where you live, so read it alongside them.
Whether an account is available to you turns on the rules where you live and on the regions we are able to serve. Where local law and this page point in different directions, local law decides. If you are unsure, send your question through the published support route and we will set out what we can and cannot do.
The wallet routes we show members here — bKash, Nagad, Rocket and Bank Transfer. Each one leaves a reference trail you can open in your transaction list. This notice covers how we handle that record, while the provider's own terms cover their side of the transfer.
Yes, for most of them. Your phone number, email address and name spelling sit in your profile area and you can update them yourself. Anything you cannot change there can be requested in writing through the support route, and we will tell you what we need from you to act on it.
We keep records while the law and our own checks require them, then remove what we no longer need. If you want a detail corrected or deleted earlier, ask in writing. We will say plainly what we can act on and what has to stay with us.
Open your transaction list, find the entry, and copy the reference number. Then raise it through the published support route with the date and the device you used. With those details we can trace the record and tell you what happened on our side of it.
It can. When payment rules, game categories or regional requirements change, the wording here is updated and the newest version replaces older ones. The page you read today is the one that applies to your account, so look it over again after a long break and raise anything unclear.