Live / Mobile
gq66 keeps one privacy policy for your account, your wallet activity and the games you open on this site. Read it once and you will know what we record when you log in, what we keep when you move money through bKash, Nagad or Bank Transfer, and how to ask us to change or remove what we hold.
This policy explains how gq66 handles personal data. It applies to everyone who opens an account here, whether you read the lobby from a phone browser or from a desktop. Privacy rules differ from country to country, so we cannot promise identical treatment everywhere. Access to the site, and the data practices described here, depend on your local law and the eligible regions we serve. If a rule in your country conflicts with a line in this policy, your local law sets the standard we follow, and we may limit certain features where the law requires it. We collect the details you give us when you open an account, the records that build up as you use your wallet, and the technical data your browser sends with each visit. We use that to run your account, to match deposits and withdrawals against the payment route you chose, and to keep the site working. Payment context matters here: bKash, Nagad and Bank Transfer each return a reference that we attach to your account so a transaction can be traced. We do not sell your data. We share it only with the service providers that help us operate, and only where the law allows. Nothing in this policy changes your rights under the law that applies to you. Where the two disagree, the local rule wins. Questions about the wording below can be sent through the support route published in your account area.
One policy cannot reach everything a site touches, so it helps to see where ours ends. It follows your account from the moment you create a password to the day you ask us to close it. It covers the deposit or withdrawal record tied to the route you used, whether that was bKash, Nagad or a Bank Transfer, because that record lives on your account. It also covers the lobby itself: what we log when you open a page, which browser you came from, and how game content from Microgaming, PG Soft, PlayStar, Spadegaming, Habanero and CQ9 reaches your phone. It does not cover the payment providers themselves. bKash and Nagad hold their own account data under their own rules, and your bank keeps its own records. When you leave our site through an external link, the destination site answers for what it does with your data. Our policy also says nothing about third-party messaging apps or browser extensions you add yourself. If a page here points elsewhere, read that destination's own policy before you hand over details.
This policy follows your account from registration to closure. It covers the email and phone number you sign in with, the password you set, the sessions opened from your phone or desktop, and the profile edits you make. If you ask us to close the account, the same rules govern what happens to what remains.
Deposits and withdrawals made through bKash, Nagad or Bank Transfer sit inside this policy. We hold the transaction reference, the amount, the time and the status of each entry, because that is what lets you match a payment to your account. The money itself stays with the provider.
What you see in the lobby is also covered, in a narrow way. We log page views and the game titles you open, and we serve titles from Microgaming, PG Soft, PlayStar, Spadegaming, Habanero and CQ9 to your browser. Session handling on those screens follows the same account rules.
Outside our own systems, your data is governed by whoever holds it. bKash, Nagad and your bank run their own privacy terms, and any site you reach through an external link answers for its own handling. Our policy ends at the point where you leave gq66, so read the destination's page first.
Your account is not a locked box. Sign in and you can see the profile details we hold, then change the ones that are wrong, such as a phone number or an email address. If a field is fixed and cannot be edited, that is usually because we matched it against a payment record or a verification check. Ask us and we will tell you which one. Every record attached to your account, from a bKash deposit to the last game you opened, sits behind the same login. You can request a copy of what we hold, ask for a correction, or ask us to remove data we no longer need to keep. Write from the email address on your account so we can match the request without exposing your details to someone else. We may need to confirm who you are before we act, and some records have to stay for as long as the law requires. Where a request touches a wallet transaction, we will point you to bKash, Nagad or your bank for their own copy.
Sign in and open your profile to see the details on file, then check the transaction entries attached to your account. If you want a fuller copy of what we keep, write from your account email and say so, and we will tell you what can be shared.
Has your phone number or email changed? Update the fields we let you edit from your profile page. For anything locked, ask us through the help area and we will explain whether it was matched against a payment record or a verification step before it can move.
You can ask us to delete data we no longer need. Some entries tied to deposits and withdrawals have to stay for the period local law sets, and we will say plainly which ones and why. Requests come through the support route shown in your account.
Not sure whether something counts as your data? Ask. A short message through the help area, naming the page or record you mean, gets a straight answer. You do not need to quote this policy back to us; describing what you saw is enough.
Reach us the way the site shows, and your privacy question lands with the people who can act on it. Every support route we publish is meant for account matters, including data questions, so you do not need a separate channel for this policy. Start in the help area inside your signed-in account. That path already knows who you are, which cuts the back and forth when you ask about a specific record. If you cannot sign in, the contact details listed on this site are the other way in. Write from the email address on your account where you can, and put the short version in the subject line. Mention which part of the policy you are asking about, whether that is account data, cookies, a bKash or Nagad transaction record, or a deletion request. Payments sitting with a wallet provider are the one case we cannot answer alone. If your question is about money inside bKash, Nagad or your bank account rather than inside our wallet ledger, those providers hold the record, and we will still tell you what our side shows.
Sign in and open the help section inside your account. That route already knows which account you are writing from, so a privacy question about a specific record reaches us without extra back and forth. Include the part of the policy you are asking about.
If you cannot get into your account, use the contact details printed on this site. Write from the address linked to your account where possible, keep the message short, and mention bKash, Nagad or Bank Transfer if the question is about a transaction record.
When a payment sits with the wallet provider rather than inside our ledger, the same support route still helps. Tell us what your bKash, Nagad or bank screen shows and what your account shows, and we will point to where each side keeps its own record.
Data handling on this site is built around one account and one login. We keep what we need to run your account: the details you entered, the wallet records created when you use bKash, Nagad or Bank Transfer, and basic technical logs such as the browser and device that reached us. Keep your password private; we will never ask you to send it in a support message, and no genuine message from us will ask for a wallet PIN either. Cookies do the small jobs. Some keep you signed in between pages, some remember your language and display choices, and some help us see which pages load slowly on mobile. You can clear or block cookies in your browser settings, though signing in may fail if you block the ones tied to your session. Retention follows the same logic. Account records stay while your account is open and for the period local law asks us to keep transaction history. After that we remove or anonymise what we no longer need. To ask about a change, use the support route published in your account area and tell us which record you mean.
We hold the profile details you entered, your sign-in credentials, the wallet entries created through bKash, Nagad or Bank Transfer, and basic logs such as the browser and device used. That list exists to run your account and to let a transaction be matched if you query it.
Session cookies keep you signed in between pages. Others remember your language and display choices, and a few show us which pages load slowly on mobile. You can block or clear them in your browser settings, though signing in may fail if the session cookie is blocked.
Your password is yours alone. We never ask you to send it through a support message, and no genuine message from us asks for a wallet PIN from bKash, Nagad or your bank app. If something looks wrong on your account, change the password and tell us through the help area.
Account records stay while your account is open, and transaction history stays for the period local law requires. After that we remove or anonymise what we no longer need. To ask about a specific entry, write from your account email and name the record you mean.
Below are the questions that come up most often when someone reads this policy for the first time. Each answer is short on purpose, and each one points back to a page or a route you can check yourself. If your question is not here, the support route inside your account area will reach us, and you can ask about a specific record rather than the policy as a whole. Keep your account email handy, because that is what lets us match a question to your file without asking you to prove who you are twice. Read the questions in whatever order suits you; the list is not ranked. And remember that what we can do with your data, and what you can ask us to do, depends on your local law and the eligible regions we serve.
Your account details such as the email and phone number you registered with, the record of games you open, and the transaction entries created when you deposit or withdraw through bKash, Nagad or Bank Transfer. We also keep basic technical logs, including the device and browser used to reach the site.
We keep the reference your payment returns and the amount it carried, tied to your account so you can match it later. We do not hold your wallet password or the PIN you use inside bKash, Nagad or your bank app, and we will never ask you to send those through a support message.
Yes. Write from your account email and say which records you want removed. We will clear what we no longer need, but some entries tied to deposits and withdrawals have to stay for the period local law requires. We will tell you what we kept and why.
Sign in and open your profile to change the details you can edit, such as a phone number or an email address. If a field is fixed, ask us through the support route shown in your account area, and we will explain what it was matched against.
Your local law still sets the standard. Access to gq66, and the way we handle your data, depends on your local law and the eligible regions we serve, so some features may be limited from certain locations. If the rules that apply to you differ from this page, they take priority.
Some cookies keep you signed in, others remember your display choices, and a few help us see how pages load on mobile. You can block or clear them in your browser settings. Blocking the session cookie may stop sign-in from working, but nothing else needs a cookie you cannot control.