Sports / Mobile
An account on gb996 leaves a trail of records, and this policy explains what we hold and what you can do about it. Skim it before you register, then check back from your phone whenever your account details change.
An account on gb996 leaves a trail of records, and this policy sets out what sits inside them and what we do with it. When you register, sign in with your email, or move money between the lobby and your wallet on a phone, we keep what is needed to hold that session together: account identifiers, device and browser signals, and the payment references that appear when you use a local rail such as bKash, Nagad, Rocket or Upay. Support reads those records to trace a question you raise. Your account view reads the same data, which is why the balance and history you see there should match what our systems hold. How much we can process, where it is held and which choices you have depend on the law that applies where you live and on the regions we are able to serve. Nothing here replaces that local position or promises a particular outcome. If your jurisdiction gives you a right we have not described, tell us through a published support route and we will work through the steps with you. We do not sell your account data. We share it only where a service provider needs it to run something you asked for, such as completing a wallet transfer, or where we are required to by law. You can ask to see what we hold, ask us to correct an entry, or ask for the account to be closed, and we will explain what applies in your case.
Our privacy policy travels with your gb996 account, not with the device you happen to open it on. Sign in from a phone browser today and from a desktop tomorrow, and the same rules follow the session, the wallet and the history attached to that account. What falls outside the scope is anything you reach by leaving our pages. Some of it feels continuous — a game client loading inside the lobby, a link in a footer, a payment step handled on a wallet's own screen — but the operator of that service decides how it treats you there, and its own terms apply. Inside the scope we treat four areas separately, because each collects something different and each gives you a different way to ask about it. The list below sets out what we hold in each case. Unsure where your question belongs? Raise it through the support route we publish and we will point you to the right one. Whether you can use any part of this depends on local law and eligible regions.
This is the part you touch first. It holds the email you register with, the sign-in records that keep a phone session alive, and the device and browser signals our systems read when you return from a new device. Change phones and those access records update.
Every wallet move creates a reference: the amount you sent, the rail you used, the time, and the status our systems recorded. We hold those references so a transfer can be matched to your account, and so you and our support team can read the same trail when a question comes up.
Pages you open, the language you read the lobby in, and the cookie identifiers that stop a session breaking mid-navigation sit in this group. We use them to serve the page you asked for and to remember simple preferences between visits, not to follow you across unrelated sites.
Follow a link off our pages, or let a wallet handle a step on its own screen, and you are outside this policy. That operator sets its own rules and answers its own requests. We cannot change, delete or explain records another service holds, so take those questions to that service directly.
Being able to act on your own data matters more than a list of promises. The account area is your starting point: sign in and you can look at your profile, your session history and the transaction entries your wallet moves created. If something there is wrong — a spelling in your name, an old phone number, a mismatched reference — raise it and we will correct it once we have checked the request comes from the account holder. For anything you cannot settle from the account area, use a support route published on this site. Say plainly what you want done: show me what you hold, change this detail, close my account. We will reply with the steps that apply in your case. What we can do depends on the law where you live and on eligible regions, and a request sent from outside the registered email takes longer to confirm.
Sign in and open your profile to see account details, session records and the entries your wallet moves created. For a fuller picture than the account area shows, ask through a published support route and we will say what we can provide.
A misspelled name, an old phone number or a mismatched reference is usually a quick update. Write from the email registered to the account, describe the single detail that is wrong, and we will check the request before changing the record.
Unsure which part of the policy your question falls under? Send it anyway through a support route and name the record you mean. We will route it to the right place and tell you what steps apply in your case.
You can request that the account be closed. Write from the registered email and say so plainly. We will explain the steps, what stays on file afterwards, and how long that depends on the law where you live.
Privacy questions reach the right person faster when they arrive through a route we actually run. Our support page lists those routes, and that list is the current one — if a channel is not shown there, we have not opened it. Describe the account you are writing about, and keep the reply thread together so whoever handles it can see what has already been checked. Two habits help. Write from the email registered to the account, and name the exact record you mean rather than describing it loosely — a reference from a bKash, Nagad, Rocket or Upay wallet move is easier to trace than "my payment". If your question concerns something already visible in the account area, look there first; the entry often answers it. Anything touching eligibility or local law depends on your jurisdiction and on the regions we are able to serve.
Our support page carries the contact routes we currently run, and it is the only place we publish them. Open it from your phone and you will see the same entries a desktop visit shows. Pick the one that matches your question about data, records or your account.
Where an email address is published for privacy requests, writing from the address registered to your account speeds things up. Include your account name, the records you are asking about and what you want changed, so the first reply can be a useful one.
Help reached from inside the account area sits next to the profile and history views it relates to. Raising a question there keeps your account name attached automatically, which removes one round of back-and-forth before anyone can start looking at the records.
Keeping account records safe is mostly about limiting who can open them and clearing out what we no longer need. Only staff whose work requires it can view an account record, and each look-up is logged against the person who made it. Your own sign-in email and password are the keys to the account, so keep them off shared phones and browsers, and sign out when you hand a device to someone else. Cookies do a narrow job here. A session cookie keeps you signed in while you move between the lobby, a game and your wallet. A preference cookie remembers how you left the page. Browser settings let you clear both, though clearing the session cookie means signing in again next time. We hold account data while the account is open, and afterwards only as long as we must. To find out what we still hold, or to ask for a change, use the support route published on this site. What we can do depends on local law and eligible regions.
Only staff whose work requires it can open an account record, and each look-up is logged against the person who made it. Access is tied to the job, so an agent handling your question sees only what answering it needs.
A session cookie keeps you signed in as you move between the lobby, a game and your wallet. A preference cookie remembers how you left the page. Both can be cleared in your browser settings, though clearing the session cookie means a fresh sign-in.
Your sign-in email and password are the keys to the account. Keep them off shared phones, avoid saving them in a browser you do not control, and sign out before handing a device to someone else. Tell us promptly if you think another person has them.
We hold account data while the account is open, and afterwards only as long as we must or while a question is still live. To find out what remains, or to ask for a correction, use the support route published on this site.
Three groups, roughly. Account details cover your registered email, sign-in records and the device signals your browser sends. Transaction records cover the references behind wallet moves on bKash, Nagad, Rocket or Upay. A small set of cookie identifiers keeps a session alive between pages — nothing beyond what running the account requires.
Sign in and your profile already shows account details, session history and transaction entries. For anything the account area does not display, ask through a support route published on our site and write from the registered email. We will tell you what we can provide; how far that goes depends on the law where you live.
Raise it and we will correct it. A misspelled name, an old phone number or a mismatched wallet reference is usually a quick update once we have checked the request comes from the account holder. Write from the email registered to the account and describe the single detail you want changed.
Only where a service provider needs it to run something you asked for, such as completing a wallet transfer, or where we are required to by law. We do not sell account data. Follow a link away from our pages and that operator's own terms apply instead of ours.
Send the request through a published support route and write from the registered email. We will explain the steps that apply and what stays on file afterwards — some transaction records have to be kept for a period, and that period depends on local law. Closing an account does not erase everything the same day.
Our support page carries the contact routes we currently run, so start there and use the one that matches your question. Keep your account name and the exact record you are asking about in the message. If the answer already sits in your account area, checking there first is often quicker.