Live / App
Opening an account with 7m777 means handing us a small set of personal details, and this page explains exactly what we do with them. Below you will find how we collect, store and share account data, which choices you control, and where to raise a question. Everything described here is our own practice, and access to the account area depends on your local law and eligible regions.
Running a member account means you leave a trail of personal data with us, and the shape of that trail matters. What we collect is limited to what an account needs: the email address you register with, a mobile number where you add one, the wallet reference attached to a Nagad or Upay transfer, and a record of the pages you open while signed in. We keep those records so your wallet history stays readable and so our support desk can answer you with the right context instead of asking you to repeat yourself. Our site is used from Bangladesh and elsewhere, and the rules that apply to your data are those of the country you are in when you use it. If local law sets stricter duties than this page describes, the stricter rule wins. If part of the site is unavailable where you are, that is a regional restriction, not a different standard of care for your details. We do not sell account data. We share it only with the service providers that keep the site running, such as hosting, wallet confirmation and message delivery, and only as far as each one needs to do its job. Cookies fall into two groups: the ones required for sign-in and security, and the ones that remember small preferences such as the game category you opened last. You can clear either group in your browser, though clearing the first will sign you out. This page covers privacy and nothing else. Payment terms, account rules and game availability are set out in their own pages.
Scope is where most policies go vague, so we will be plain about ours. This policy follows the account you open with us and the personal details attached to it: your sign-in email, any mobile number you add, the preferences you set, and the wallet references created when money moves through your account. It also covers the technical record of how you reach the site, such as the device and browser you use and the pages you open after signing in. It does not cover everything you touch. A wallet confirmation you see inside the dashboard is a payment event governed by the provider's own terms, and bKash, Nagad, Rocket and Upay each publish those separately. Games in our lobby come from studios such as Pragmatic Play, CQ9, Bigtime Gaming and PlayStar, and each title carries its own play rules. Follow a link away from our site and you are under that page's policy instead of ours. If you are unsure whether something sits inside this policy, ask us before assuming. We would rather answer one question than leave you guessing about your own records.
Your sign-in email, any mobile number you add and the password you set sit inside this policy. We use them to open your account, keep you signed in on your own device and reach you if something about your access changes. Update these details whenever you switch phones.
Records created when funds move in or out of your account wallet, including the amount, the time and the reference from a Nagad or Upay confirmation, sit under this policy. You can read that history in your dashboard at any time. The provider's own terms cover the transfer itself.
The pages you open, the game category you browse and the small cookie files that remember your preferences are within scope. We use them to keep the lobby working and to see which areas get used. Clearing cookies resets those preferences, and it signs you out.
Follow a link away from our site and you leave this policy behind. The page you land on sets its own rules for any details you give it. We cannot change how another operator handles your data, so read what is posted there before you enter anything.
Your account is not something you have to chase us about. Once you are signed in, the profile area shows the email address, mobile number and preferences we hold for you, and you can correct most of it yourself through a phone number change, a display name update or a language swap. Wallet history sits in the same dashboard, so the reference from a bKash deposit or a Nagad transfer is yours to read without asking anyone. Where you cannot edit something directly, you can ask. That covers copies of the account records we hold, a correction where a detail is wrong, or an explanation of why a particular entry is stored. Write to us through a published support route and tell us which account you mean, because we reply to the account holder and not to a third party. If you want your account closed and the personal details attached to it removed, say so plainly. Some records still have to be kept for as long as the law where you live requires them, and we will tell you which ones and why.
Sign in and open the profile area to see the email address, mobile number and preferences on file. Wallet history sits beside it, listing each deposit and withdrawal with its reference. Nothing is hidden behind a request; if you can sign in, you can read what we hold.
Most fields you can change yourself: a new mobile number, a display name, a language preference. Update them in the profile area and the change applies to your account straight away. If a field will not accept an edit, send us a message and we will look at it.
You can write to us and ask for a copy of the account records we hold, or ask what a particular entry is for. Tell us which account you mean so we can confirm it is yours before we reply. We answer the account holder only.
Closing an account and removing the personal details attached to it is a request you can make at any time. Some records have to stay for as long as local law requires, and we will name those and explain the reason when we respond.
Privacy questions deserve a straight answer from a person who can see your account, so we keep the routes short. Start inside the signed-in area, where the help panel sits in the same menu as your profile and the chat window opens without leaving the page you are on. If you would rather write, the support email address posted on our contact page reaches the same team. Before you send anything, have the account email ready, because we check who we are talking to before we discuss an account record and that check is quicker when the message comes from the address registered to the account. If you are writing about a wallet entry, add the date and the reference shown in your dashboard, and it saves a round of questions. We do not discuss one person's account with someone else, and we will not confirm whether an email address is registered with us. If you cannot get into your account at all, use the same support route and tell us you cannot sign in.
Open the signed-in area and the chat window sits in the same menu as your profile, so you can raise a privacy question without leaving the page you were reading. Have your account email to hand before you start the conversation.
The address posted on our contact page reaches the team that handles account records. Write from the email registered to your account where you can, and describe what you need: a copy of a record, a correction, or a removal request.
Inside your profile there is a help panel covering the common account questions, including how to update details and how to read wallet history. Read it first if you want the fastest answer, then use chat or email if your case is not covered.
How we handle your details comes down to a few repeatable habits. Access to account records is limited to the people who need it for support or to keep the platform running, and each of them works from a personal login rather than a shared one. Sign-in cookies are set to expire, so a borrowed phone does not stay logged in to your account. We keep the working set small: an email address, a mobile number where you add one, your preferences and the references attached to your wallet activity. When you ask for something, whether that is a copy of your records, a correction, or the closure of an account and its details, the request is tied to your account and answered by someone who checks the account first. Nothing about that process requires you to explain yourself twice. Cookies are the part you control most directly. Your browser settings let you block or clear them, and clearing sign-in cookies simply signs you out. If you would rather we handled a request for you, the published support routes are listed on our contact page.
Only staff who handle support or keep the platform running can open an account record, and they reach it through their own login. Nobody works from a shared account. When you raise a question about a record, we tell you which team is handling it.
Two groups of cookies run here: the ones that keep you signed in and protect the session, and the ones that remember preferences such as your last opened game category. Your browser can clear either group. Clearing the first signs you out, nothing more.
Account details stay while your account is open, and after that only for as long as the rules where you live require. Browsing records fall away sooner. A wallet reference stays longer, because it is the thing that explains a transfer when you ask about one.
Every privacy request goes to a person rather than a queue that sits untouched. Tell us what you need, a copy, a correction or a deletion, and which account it concerns, and the reply will explain what we can do and what local rules stop us from doing.
Questions about privacy tend to repeat, and the answers rarely need a legal tone. You want to know what we hold, who can open it, whether you can say no to cookies, and how to get something corrected or removed. Those four threads cover almost every message our support team receives about account data. The short answers are here. Your details are the ones an account needs to run: a sign-in email, a mobile number if you add one, your preferences, the pages you open while signed in, and the references behind wallet activity. Staff who handle support can open a record, and nobody else can. Cookies can be cleared from your browser, and doing so signs you out. Requests for a copy, a correction or a deletion go to the support team, which checks the account before replying. If your case is not covered below, the published support routes are the way to reach a person directly.
Your sign-in email, any mobile number you add, the preferences you set, and the wallet references created when funds move. We also keep a record of the pages you open while signed in and the device or browser you used. That is the working set your account needs.
You can block or clear cookies in your browser settings at any time. The sign-in and security cookies are what keep you logged in, so blocking them means you will need to sign in again on each visit. Preference cookies only remember small choices like your last opened category.
Staff who handle support or keep the platform running, working from their own logins, and the service providers that host the site, confirm wallet transfers and deliver messages. We do not sell account data and we do not discuss one account with another person.
Use a published support route, either chat in your dashboard or the email address on our contact page, and say that you want a copy of the account records we hold. Write from the email registered to your account so we can confirm it is yours before replying.
The rules that apply to your data are those of the country you are in when you use the site. Where local law sets a stricter duty than this policy describes, that stricter rule applies. Availability of the site itself depends on your local law and eligible regions.
No. Wallet confirmations you see in your dashboard are payment events, and each provider publishes its own terms for them. This policy covers the account record around that activity, including the reference, the amount and the time we store, rather than the transfer itself.