Slots / Mobile
xg666 keeps a single privacy policy for the whole site, covering your account, the payment references behind a bKash or Rocket transfer, and the pages you open in the lobby. Read it once and you know exactly where your details sit.
xg666 publishes this policy so you can see how we treat the details you give us, and this page is the only place we state those positions. We hold what you enter when opening an account, what your device sends when a page loads, and the payment references tied to a bKash or Rocket transfer. Nothing here describes another operator's practices, or pages we do not run. Where you play from matters. Our policy follows the law that applies where you are, and access to the site depends on your local law and eligible regions. If a rule in your area differs from what this page sets out, your local law takes priority, and we revise the wording here when the position changes. We do not claim our practices meet every regulator in every country. The wording stays short on purpose. Instead of stacking clauses, we list what you can actually do: read this policy before you deposit, check the details we hold on your account page, and message the support route shown on the site when something looks wrong. Updated wording appears on this page with the date it took effect, and continuing to use the site after an update means you accept the revised text. Your wallet keeps its own record too, so a bKash or Rocket statement is an independent copy you can match against your account entries.
This policy covers the parts of xg666 we control: the account you open, the pages you load on our domain, the lobby you reach once you sign in, and the records we keep of your deposits and game activity. It does not reach past our own walls, and knowing the boundary saves you a support message later. Take account access first. When you sign in with the email address you registered, we hold that session and the profile fields you filled in. Those are ours to protect and yours to check. Transactions are a shared record: we log the reference for a bKash or Rocket transfer, while the wallet provider holds the balance side of the same movement. Site content, from game tiles to sportsbook views, is delivered from our side, so what you see there follows this policy. Third-party services are the exception. If a page sends you to an external link, that operator answers for its own data handling, and their terms apply from the moment you leave us.
Signing in with the email address you registered creates a session we manage. Your profile fields, display name and any contact details you add sit on the account page, where you can read them back. If something there is wrong, ask us to correct it through the published support route.
Every bKash or Rocket transfer you make carries a reference number. We store that reference alongside the time and the side of the movement we can see, and your wallet app keeps its own copy. Matching the two is the quickest way to settle a question about a deposit.
Pages, game tiles, sportsbook views and anything else you load on our domain fall inside this policy, including the lobby you reach after signing in and the help pages linked from your account area. What you see there is delivered from our side.
Links that leave our domain belong to somebody else. Once you follow one, that operator sets its own rules on data and cookies, and this policy stops applying. Check their notice before you enter your own details on a page we do not run.
You have more control here than most people assume, and all of it runs through your own account. Start by opening the account page while signed in. Everything we hold in your profile, from the email you registered with to your display and contact fields, shows there, and you can change what needs changing instead of waiting on a reply. When a correction is not something you can make on screen, write to the support route published on the site and describe what is wrong. Give us the wallet reference if the question touches a bKash or Rocket transfer, because that number lets us find the entry quickly. You can also ask what we hold, ask us to delete an account you no longer want, or raise a question about how a page handled your details. We answer from the same support route every time, and we will tell you when a request cannot be met, and why.
Sign in and open your account page to see the profile fields and contact details we keep for you. Wallet references for a bKash or Rocket transfer sit with the matching entry, so you can compare them against your own statement and flag anything that looks out of place.
Display details and contact fields are editable from the same account screen, and the change applies to your profile straight away. When a field is locked and you need it changed, message the support route with the entry you mean and we take it from there.
Send a request through the support route asking what account data we store, why we store it and who processes it for us. We reply through the same channel and explain anything a request cannot cover, including records we are required to keep.
If you no longer want the account, ask us to delete it through the support route. We remove the profile details you can see and stop using the account. Wallet and transaction references may stay in our records for the interval the applicable law expects.
Reaching us about privacy should not depend on guessing an address, so we keep the routes published and the wording plain. Two paths cover almost everything: the help link inside your signed-in account area, and the support email shown on the site. Both land with the same team, and both accept a question about this policy. Before you write, gather two things. Use the email address you registered with, because that is how we find your profile, and copy the wallet reference if the question concerns a bKash or Rocket transfer. A message carrying those two details usually gets answered without a round of follow-up questions. We do not set out response times here, because we would rather you look at the channel itself than read a promise we cannot keep. What we can describe is how a request moves: your message arrives, we look up the account, and we reply through the same channel you used. If your question belongs to a service we do not run, we will say so instead of passing it along.
Sign in and open the help link inside your account area. It carries the shortest path to the pages covering signing in, wallet records and the settings you can change yourself. If a step there does not match what you see on screen, tell us through the support route.
Write to the email address published on the site, and describe your question about this policy. Include the wallet reference when it concerns a bKash or Rocket transfer, and the email you registered with, so the reply reaches the right account without extra back and forth.
Use the same published channel for anything about how we handle data, cookies or account retention. We answer from there and will point you to the wording on this page that covers your question. Questions about another operator's site have to go to that operator.
Handling your data well comes down to a few habits we follow, and none of them are hidden. When you sign in, the session stays tied to your account and ends when you sign out or your device clears it. On the page side, cookies do the ordinary work: keeping you signed in between screens, remembering the language you read, and showing us which pages load slowly. We keep profile details while your account is open, and payment references for the interval the applicable law expects. Account safety sits with both of us. We hold the session and the sign-in side; you hold your password and the device you carry. If you believe someone else has reached your account, change the password from the account page first, then tell us through the published support route. Requests about your own data are welcome at any point, and you can make them without giving a reason. We answer from the same channel and explain anything we cannot do.
Your email address, the display details you entered and the wallet references behind your bKash or Rocket transfers make up most of what we store. Device and page data tells us how the site performs. Your profile fields are visible to you on the account page.
Cookies keep you signed in while you move between lobby pages and remember the settings you chose. Some also measure how quickly pages load. You can clear them from your browser at any time, though you will need to sign in again afterwards.
Your password and the device you carry are the two things only you control, so keep the password to yourself and sign out on shared phones. If a session ever looks unfamiliar, change the password from the account page and tell us.
Profile details stay while the account is open. Wallet and transaction references are kept for the interval the applicable law expects, then removed. Ask through the support route what applies to your own account and we will explain the position in writing.
This page gathers the questions we get most often about data, in the order people usually ask them. Read the six below and you will know what we store, what you can change yourself, how to reach us, and what happens to an account you close. Each answer points at a route you can actually open today: your account page while signed in, the support route published on the site, or the wording further up this policy. One thing worth saying plainly. Access to the site, and the law that applies to your data, both depend on your local law and eligible regions, so a general answer here cannot override a rule where you live. If your situation is unusual, write and ask rather than guessing from the common case. We reply through the same channel you used to reach us.
Your registered email, the profile and contact fields you entered, wallet references behind any bKash or Rocket transfer, and basic device and page data from your visits. You can see the profile side for yourself on the account page once you sign in.
Yes, most of them. Display details and contact fields are editable from your account screen and the change applies to your profile straight away. For a field you cannot edit yourself, send the correction through the support route published on the site.
Message the support route from the email you registered with and say what you want to see. We tell you which records we hold and why, explain what a request cannot cover, then follow up through the same channel you used to write in.
No. Once you leave our domain, the operator behind that page handles its own data and sets its own cookies. Read their notice before you enter your details there, and come back to this page for anything about your xg666 account.
We store the reference attached to a transfer you make, along with the date and the side of the movement we can see. Your wallet app keeps its own copy, and matching the two is the simplest way to settle a question about a deposit.
Ask through the support route from your registered email. We remove the profile details you can see and stop using the account. Wallet and transaction references may be held for the interval the applicable law expects before they are cleared.