Casino / Live
This page sets out what 777acc records when you open an account, move money through your wallet or send us a message, and what you can ask us to change. Access to the platform depends on your local law and eligible regions.
Privacy at 777acc starts from one position: we collect what an account needs to work, and little beyond that. Opening an account gives us your contact details and the credentials you sign in with. Using the wallet adds transaction records from whichever rail you pick, whether that is bKash, Nagad, Rocket or Upay. Taking part in the lobby logs the session, so you can check your own history later rather than take our word for it. Local law changes what we may do with those records, which is why the rules here are written to bend with your jurisdiction. One region may require longer retention, another may require quicker deletion. Where a local rule and this page disagree, the local rule wins, and we say so in the account notice rather than quietly applying it. Availability of the platform itself also depends on your local law and eligible regions; if the site is not offered where you are, this page does not create a right to use it. Payment rails stay with their providers. A bKash or Nagad transfer returns a confirmation reference to us, and the provider keeps its own record under its own rules. We cannot edit what they store on their side, and we never ask for a wallet PIN or a card number in a support message. Your side of the arrangement is simple: ask when something looks wrong, and tell us when your details change. Everything after that runs through the routes published on the site.
Not everything you touch on the site works the same way, and the edges matter when you raise a question. Your account sits inside this policy: the contact details you enter, the credentials you sign in with, the messages you send us. Wallet activity sits inside it too, so when money moves through bKash, Nagad, Rocket or Upay, we hold the reference we receive and the entry attached to your account. The lobby is a separate case. Sessions on a slots round or a board such as Cricket Live Lines are logged so you can check your own history, and the studios that supply our game content are not involved in your payments, your sign-in or your support tickets. Outside the policy are the services you reach through a link, including your wallet provider's own app and any payment page hosted elsewhere. Those carry their own terms, and their records are theirs to control. Being clear about the split tells you who to ask, and that is usually the fastest route to an answer.
Everything you enter when you open an account is covered here: your name, contact details, the email you sign in with and the credentials attached to it. Messages you send us sit inside the policy too, including the ones you raise about a wallet entry or a session.
When you move money through bKash, Nagad, Rocket or Upay, we hold the reference the provider returns and the entry it creates in your account. That record is what we look at if a transaction is queried. What the provider stores on its own side stays under its own terms.
Slots rounds, live tables and a board such as Cricket Live Lines produce session logs attached to your account, so you can check your own history rather than take our word for it. The studios that supply our game content do not see your payments, your details or your support messages.
Anything you open through a link is outside this page. Your wallet provider's app, a payment page hosted elsewhere and any site we link to carry their own terms and their own records. We cannot read, change or delete what they hold, and we will say so when that is the answer.
You have four practical moves under this policy, and none of them need a middleman. First, open your account area and look at the records we hold: saved contact details, wallet entries, session history. Second, correct anything wrong from the same screen, a phone number or a name spelling, and the entry updates with it. Third, when a question is not about a field you can edit yourself, send it through the support route published on the site and tell us which record you mean. Fourth, if you want active collection to end, ask for the account to be closed; we then keep only what local rules require us to retain, and we tell you what that is. Nothing here sits behind a fee or a second request. Keep your sign-in credentials private, because anyone holding them can see the same records you can.
Open your account area while signed in and you can read the working set: saved contact details, wallet entries and session history. That view is the quickest way to answer most questions about your own records, and it is available from a phone browser without an extra request.
If a phone number, address or name spelling is wrong, correct it from the same screen where it appears and the record updates with it. For anything you cannot edit yourself, send the correction through support with the email you signed up with attached.
When you want an explanation rather than a change, such as who sees a record, why something is kept or what happens after closure, send it through the support route published on the site. Pick a privacy subject so it reaches the people who handle records.
Asking us to close the account ends active collection. Some records then have to stay for a period set by local rules, and we tell you which ones and why. Nothing about that request depends on a fee or on a second message from you.
Questions about your records come to one place, and we answer them from there. Signed in, open the support option shown in your account and pick a privacy subject, so the message lands with the people who handle account and wallet records rather than a general queue. Say which entry you mean, whether that is a bKash or Nagad reference, a saved phone number or a session you want checked, and add the email you signed up with. That is usually all we need to find it. If you would rather write than chat, use the contact address we publish on the site. We would rather give you the real position on timing than a number we cannot hold to. What we can say is that every request is logged against your account, so you can follow it up later with the same reference.
Signed in, open the support option shown in your account area and choose a privacy subject. Mention the record you mean, whether that is a transaction reference, a saved phone number or a session you want checked, plus the email you signed up with. That is normally enough for us to find it. That is easy to follow.
If writing suits you better than chat, use the contact address we publish on the site. It reaches the same team, and the request is logged against your account, so you can follow it up later with the same reference without repeating the whole story from the beginning.
Questions about money you moved through bKash, Nagad, Rocket or Upay need the reference the provider gave you. Add it to your message and tell us what you expected to see. We can look at our own record and explain what it shows; anything held on the provider's side is theirs.
Data handling at 777acc follows what the account actually needs. Contact details support sign-in and support; wallet references support reconciliation with bKash, Nagad, Rocket and Upay; session logs let you settle your own history. Cookies are the smaller piece: they keep you signed in between pages, remember your language choice and show us which pages load slowly on a phone. You can clear them in your browser at any time, though the signed-in area will ask for your credentials again. Account security is shared work. We keep your records behind the sign-in, and you keep the password to yourself and sign out on shared devices. Retention follows local rules, so some records must be held for a set period while others go when the account closes. To change what we hold, use the same support route that handles every other request, and we will tell you what can be edited, what has to stay and why.
Contact details, wallet references from bKash, Nagad, Rocket or Upay, and session logs tied to your account. That is the working set. We do not ask for your wallet PIN, we do not store card numbers from support messages, and we do not hold records with no use for sign-in, payments or your own history.
Cookies keep your session alive between pages, remember the language you picked and show us where mobile pages load slowly. They are not used to sell your details on. Clear them in your browser whenever you like, and expect the signed-in area to ask for your credentials again on the next visit.
Your records sit behind the sign-in, so the password matters more than anything else. Keep it to yourself, change it if you think someone else has seen it, and sign out on shared phones. If you spot wallet history you do not recognise, send us the reference through support.
Some records have to stay for a period set by local rules; others go once the account closes. We tell you which is which when you ask. To change a saved detail, use the support route published on the site and we confirm what can be edited and what has to be kept.
Most privacy questions we get from players in Bangladesh fall into a handful of shapes: what we keep, who sees it, and how to change it. The answers below cover the ones that come up again and again, written the way we would explain them over chat rather than the way a contract would. Where an answer depends on your local law or on the region you are in, we say so plainly instead of guessing on your behalf. Two things are worth knowing before you read on. Your account area is the first place to look, because most of what we hold is visible there while you are signed in. And every request you send is tied to your account, so we can follow it up without you repeating the whole story. If your question is not covered below, send it through the support route published on the site and we will answer it directly.
Your contact details, the email you sign in with and the credentials attached to the account. Once you use the wallet, transaction references from bKash, Nagad, Rocket or Upay are added, and sessions in the lobby are logged. We never ask for your wallet PIN or your card numbers.
Yes, from the account area once you are signed in. Wallet entries and session history are shown there, which is the fastest way to look at what we hold. If something seems unfamiliar, keep the reference handy and send it through support so we can look at our side of it.
Change what you can from the same screen where the detail appears, including your phone number, address or name spelling. For anything you cannot edit yourself, send the correction through the support route published on the site and say which record you mean.
We receive the reference a provider returns when a transfer completes, and that reference sits in your account record. What the provider keeps on its own side stays under its own terms. We cannot read or change that, and we will tell you when a question belongs there instead.
Closing the account ends active collection. Some records then have to be held for a period set by local rules, and others go. Ask through support and we will tell you which categories stay in your case, and why. We do not keep records with no purpose left.
The policy describes how we handle records wherever the platform is offered, but availability depends on your local law and eligible regions. If the service is not offered where you are, this page does not create a right to use it. Ask support if your region is unclear.