Live / Sports
q777a keeps this page so you can see what we collect when you open an account, deposit through bKash, Nagad, Rocket or Upay, and move around the lobby. What we may collect and hold depends on your local law and the eligible regions we can serve, so read this as our posture rather than a promise that every feature is open to you.
Here is the plain position. q777a keeps this page so you can see, in one place, what account data we hold and what we do with it. When you open an account, deposit through bKash, Nagad or Rocket, or move money to your Upay wallet, those records sit with your profile. We keep them to run your account, to show your transaction history back to you, and to answer you when something looks wrong. Nothing here overrides the law where you live. What we may collect and hold depends on your local law and the eligible regions we can serve, so read this page next to the terms shown in your account. If a rule in your country asks for something different, that rule comes first. We do not sell your personal data. We do not hand your wallet details to game studios; studios supply game content only, and they never see your payment records. Payment names you see on this site - bKash, Nagad, Rocket, Upay and Bank Transfer - appear as the routes our account area is configured for, and the final list you can use sits inside your signed-in account. Cookies and similar storage do a few narrow jobs: keep you signed in, remember your language and device choices, and help us see which lobby sections cause errors so we can fix them. You can clear or block cookies in your browser, though parts of the signed-in area may then stop working. Questions about any of this go through the support route published on this site.
A policy is only useful when you can tell how far it reaches, so here is ours in plain terms. It covers what happens on q777a itself: the profile details you type when you open an account, the transaction lines created when you deposit or withdraw through bKash, Nagad, Rocket, Upay or Bank Transfer, the small cookies our pages set, and the messages you send us through the published support route. It does not cover anyone else's service. Tap out to a studio page, a wallet app or a bank screen and that company's own policy decides what happens to your data - we cannot change it and we cannot answer for it. The money in your wallet after it leaves our account area is theirs to hold. So read this page next to the account area you are signed into, because the fields, limits and verification steps shown there are the ones that actually apply to you. Where your country's rules differ from our general posture, those rules come first.
The profile you build on q777a: contact details you type, the password you set, and the wallet numbers you link. It also covers the session data our pages need to keep you signed in while you browse slots, live tables or the sportsbook.
Every deposit or withdrawal instruction you send from the account area leaves a line in your account, whether it runs through bKash, Nagad, Rocket, Upay or Bank Transfer. This policy covers our copy of that line, not the record your wallet app keeps.
Game titles such as BPL Powerplay Slots, Crash Dice Roller or Baccarat Circle, the pages they sit on, and the small cookies that remember your language and device choices. Block cookies in your browser and parts of the signed-in area may stop responding.
Wallet apps, bank screens and any studio's own pages sit outside this policy. Once you leave our pages, that provider's rules decide what happens to your data, and we have no say in them. Check those policies wherever you need certainty.
Under this policy you can do a few concrete things, and none of them need a special reason. Open your account area and read the profile fields we hold, starting with your contact details and the wallet numbers linked to deposits. If something there is wrong, correct it on the same page and save; the change takes effect once the fields pass the checks shown. When you want a copy of your account and transaction records, or you want the account closed, send the request through the support route published on this site so it arrives with your account reference attached. We may need to confirm the request came from you before we act, and we keep some records for as long as local law and our accounting rules require, even after an account is closed. If your question is about the law in your country rather than about our pages, we can only point you to the route shown in your account.
Open your account area and look through the profile fields: contact details, linked wallet numbers and the transaction lines created by your deposits. That page is the closest thing to a live record, so start there before writing to us about it.
Wrong mobile number, a misspelt name, an old wallet number still attached? Edit the field on the same account page and save. If a field will not save, send the correction through support with your account reference and a short description.
You can request a copy of your account profile and transaction records. Send it through the published support route and quote your account reference. We may confirm the request came from you before releasing anything, and the reply arrives on the same route.
Ask us to close your account whenever you want. We stop using the profile for day-to-day service, and records that local law or our accounting rules require us to keep stay for that period only before removal or anonymisation. Request it through support.
Policy questions are not a special queue. Use the same support route you use for anything else on the site, the contact option published in the account area and on the footer of these pages. Nothing on this page invents hours, phone lines or chat windows we have not published, so treat the routes you can actually see as the full list. When you write in, put your account reference in the message and say plainly what you want: a copy of your records, a correction to a profile field, or an account closure. That saves a round trip. If the message is about a payment, mention which route you used, bKash, Nagad, Rocket, Upay or Bank Transfer, and the date shown on the transaction line in your wallet. We read requests in the order they arrive, and replies come back through the route you wrote in on.
Signed in, the contact option inside your account area is the route we answer on. Put your account reference in the first line and say what you need: a copy, a correction or a closure. Replies come back the same way.
Not signed in? The footer of this page and the rest of the site carries the same support link. Use it for policy questions about cookies, retention or what we hold on your profile. We do not run separate privacy channels.
Whichever route you pick, include your account reference and, for payment questions, the wallet you used - bKash, Nagad, Rocket, Upay or Bank Transfer - plus the date on the transaction line in your wallet app. It matches your message to the right record.
How we handle data, in four short pieces. Storage: your profile and transaction lines sit in the account system behind the signed-in area, and staff open them for support and accounting work rather than by default. Cookies: small files keep your session alive, remember your language and device choices, and show us where pages break. Block them in your browser and expect parts of the signed-in area to stop responding. Security: keep your password to yourself, sign out on shared phones, and treat any message asking for your password or wallet PIN as someone else's, not ours. Retention and contact: we keep account records while your account is open and for the period local law and our accounting rules ask for afterwards, then remove or anonymise what we no longer need. To ask about any of it, or to request a change, write through the support route published here and quote your account reference.
Profile data and transaction lines sit in the account system behind the signed-in area. Staff open them for support and accounting work, not for browsing, and what each person can see follows the role they hold rather than convenience.
Cookies keep your session alive, remember language and device choices, and show us where pages break. They do not read your wallet app. Clear or block them in your browser settings, and expect parts of the signed-in area to stop working.
Your password is yours alone. Sign out on shared phones, avoid saving credentials on devices you do not control, and treat any message asking for your password or wallet PIN as not from us. We will not ask you for a wallet PIN.
We keep account records while your account is open and for the period local law and our accounting rules require afterwards, then remove or anonymise what we no longer need. Ask for a copy, a correction or a removal through the published support route.
Before you write to us, run through the short list below, because most policy questions people send are answered here already. Three habits make the rest easy. First, read this page next to your own account area, since the fields, limits and verification steps you can see there are the ones that actually apply to you. Second, keep the wallet line from your bKash, Nagad, Rocket or Upay history when you raise a payment question, so we can match it against our own record instead of working from a description. Third, use your account reference in every message; it ties the question to the right profile without a second exchange. Where a question turns on the law where you live, remember that access and what we can offer depend on your local law and the eligible regions we can serve.
Your profile details, the contact details you entered, the wallet numbers linked to your deposits, and the transaction lines created when you move money through bKash, Nagad, Rocket, Upay or Bank Transfer. Your signed-in account area shows these fields, so start there.
Yes. Send the request through the support route published on this site and quote your account reference. We may confirm the request came from you before releasing anything, and the answer comes back on the route you wrote in on.
Open your account area, edit the field and save. Most changes take effect once the details pass the checks shown on the page. If a field will not save, write to support with your account reference and describe what needs changing.
No. Studios supply game content only, meaning slots, live tables and table games. They do not receive your wallet numbers, your transaction lines or your account records. Your payment data stays with us and with the wallet or bank you used.
We close the account and stop using the profile for day-to-day service. Some records, transaction lines in particular, stay with us for the period local law and our accounting rules require, then get removed or anonymised. Ask through support to have this confirmed for your account.
Use the contact option published in your account area or on the footer of this page. Include your account reference, and say which wallet you used if the question is about a payment. Replies come back through the same route you used.