Live / Casino
1177bet collects only the account, payment and support details needed to run your bKash, Nagad or Bank Transfer deposit, confirm a transaction and keep your lobby session signed in. This policy sets out what we hold, how long we hold it and the routes you have to question it; access to any part of your account still depends on your local law and eligible region.
This Privacy Policy sets out how 1177bet handles the details tied to your account, your deposit history and the pages you open inside the lobby. We record the details needed to open and verify an account, to confirm a bKash, Nagad or Bank Transfer transaction against your wallet, and to respond when you raise a support question. We do not sell this data, and we only share it with a payment partner, a game studio or a support tool where that sharing is needed to complete the step you asked for — crediting a deposit, loading a table, or answering a ticket. Where local law in your region sets stricter rules than this page describes, those rules apply instead, and your access to specific account or payment features depends on your local law and eligible region. We keep transaction records long enough to resolve a payment query or a disputed round, and we keep account details long enough to keep your login working across sessions. You can ask us, through the support routes below, what data tied to your account we currently hold, or to correct a detail that's wrong. This page sits alongside our Terms; where the two overlap on payment or account wording, read them together rather than in isolation.
This policy follows your account through four areas: how you sign in, how a transaction clears, what the lobby itself records, and where a partner's own rules take over. Account access covers login and device signals that keep your session recognised across visits. Transactions cover the bKash, Nagad or Bank Transfer record attached to a deposit or withdrawal, including the confirmation your account page shows once a transfer settles. Site content covers which pages you open — a slot room, a live table, a sportsbook market — logged only to keep your session running smoothly, not to build an outside profile. Third-party services mark the edge of what we control: once your payment partner or a game studio needs a detail to complete a step, their own privacy terms take over for that piece of data. Reading these four areas separately helps you see exactly which part of your account this policy speaks for.
Covers the login details, device signals and session data tied to opening your account and staying signed in across visits to the lobby. This is where identity checks and access controls sit, separate from anything tied to a specific deposit or game round.
Covers deposit and withdrawal records linked to bKash, Nagad or Bank Transfer, including the confirmation details your account page shows once a transfer clears. This is the record you'd check first if a payment entry doesn't match what left or reached your wallet.
Covers how we log which lobby pages, slot rooms or sportsbook sections you open, used only to keep the site running and your session recognised. It's not used to build a profile of you beyond your own account activity across the pages you've visited.
Covers data shared with a payment partner or a game studio only to complete a step you started — crediting a deposit or loading a table — and falls outside this policy once it reaches that partner's own privacy terms.
You're not locked out of what we hold on your account. If a transaction record looks wrong — a bKash or Nagad entry that doesn't match what left your wallet — you can raise it through support and ask us to check the entry against our records before anything else happens. If a detail on your account page is outdated, you can request a correction rather than opening a new account. You can also ask what categories of data we currently hold against your account, in plain terms, without needing to know our internal process first. Support can also tell you which account fields are editable directly and which need a manual check first. We treat every request this way, whether it touches a login detail or a Bank Transfer confirmation on your history.
Ask support to confirm what account and transaction details are currently on file, including your latest bKash, Nagad or Bank Transfer entries, before you decide anything else.
Flag an outdated name, contact detail or wallet reference on your account page and ask us to update it rather than opening a fresh account.
Report a deposit or withdrawal entry that looks off so we can check it against the payment record tied to your account.
Send a question through the support route and expect a reply tied to your account ticket, not a generic auto-response.
Every question about this policy runs through the same support route you already use for an account or payment question — we don't split privacy questions into a separate channel you'd have to search for. Open the support option from your account area, describe what you're asking about — a record, a correction, a transaction you don't recognise — and reference your account so we can match the reply to the right file. We don't publish a fixed response time here because we'd rather describe the route accurately than promise a figure we can't hold to. If your question touches a bKash, Nagad or Bank Transfer entry specifically, mention the method and the approximate date so we can locate the record faster. This applies whether you're writing from a mobile browser or desktop, and whether the question is about a specific transaction or about this policy in general.
Open the support option from your account menu to ask about data tied to your login, your session or your account details directly — reference your account so we can match the question to the right record without back-and-forth, and expect the reply to land on the same ticket thread you opened.
Use the same support route to question a bKash, Nagad or Bank Transfer entry you don't recognise on your transaction history, and include the approximate date and amount so we can trace it against your account record without delay.
Send a written question about this Privacy Policy through support and reference your account so we can match the reply to your record rather than treating it as a one-off, unlinked message that's harder for us to track back to your account.
We treat data handling, cookies, account security and retention as four separate jobs rather than one blanket promise. Account and transaction data sit on systems built to support the lobby and the payment confirmation flow, with access limited to what a given task needs. Session cookies keep you signed in across slot rooms, live tables and the sportsbook without asking for repeated logins, and they don't track you once you leave the site. Verification steps shown during a bKash, Nagad or Bank Transfer deposit or withdrawal exist to confirm the request is actually yours — follow the fields as they appear rather than skipping ahead. We hold records only as long as resolving a payment or login question reasonably needs, and support can tell you more about a specific record on request. None of this changes depending on which device you use to sign in.
We store account and transaction details on systems built to run the lobby and payment confirmation flow, and we limit who inside that process can view a given record, keeping access tied to the step that record is needed for.
We use session identifiers to keep you signed in across the lobby and sportsbook pages without asking you to log in again on every click, and these cookies don't follow you to sites outside 1177bet or feed an external advertising profile.
Your login and payment confirmation sit behind the account verification steps shown on screen when you deposit or withdraw. Follow those fields exactly as they appear, and treat any step asking for extra confirmation as part of keeping the account yours.
We keep records long enough to resolve a payment or login question, and you can reach us through support to ask how long a specific record stays active on your account. We'll answer in plain terms rather than quoting a fixed retention table.
The questions below cover what we actually get asked about this policy — your bKash or Nagad details, how long a transaction record stays on file, and what happens to your account data once you stop using it. If your question isn't answered here, the same support route covers it; reference your account so we can match the reply to your record rather than treating it as a general message. Access to specific account or payment features still depends on your local law and eligible region, so a few answers below point back to that condition rather than giving one fixed rule for every reader.
We share payment details only with the payment partner needed to confirm your bKash, Nagad or Bank Transfer transaction — that's the minimum required to credit a deposit or process a withdrawal. We don't sell this information or pass it to any unrelated third party for marketing or other use.
Yes — raise this through our support route and reference your account details; we'll confirm the categories of data currently on file, including recent bKash, Nagad or Bank Transfer entries, so you can check them against what you expect to see.
We keep transaction records long enough to resolve a payment query or a disputed entry on your account, which can mean holding a bKash or Nagad confirmation past the day it settled. We don't publish one fixed deletion date because retention depends on the type of record involved.
Your account and its transaction history stay on file in case you sign back in or raise a question later about a past bKash, Nagad or Bank Transfer entry. It isn't actively used for anything beyond keeping that record consistent and available to you.
Yes — contact support to update a wrong name, contact detail or wallet reference tied to your account rather than opening a new one. We'll apply the correction to your existing account record once we've confirmed it's actually you asking, matched against the details already on file.
Access to specific account or payment features depends on your local law and eligible region, so parts of this policy may apply a little differently depending on where you're signing in from. If you're unsure, check your account page or ask support directly for your region's position.