Casino / Sports
collects only what we need to keep your account, wallet and session history linked across devices — this page explains what we hold, why, and how you can check or correct it, subject to local law and eligible regions.
This policy sits alongside our terms and covers how 99bet handles the data tied to your account on this site. What applies to you can depend on where you're accessing 99bet from, since availability and data handling obligations shift with local law and eligible regions — we don't claim a single blanket rule covers every visitor. When you register, log in, or move between pages on your phone or desktop, we record the account and session details needed to keep your lobby, wallet balance and transaction history consistent. If your wallet shows a Nagad transfer or a Bank Transfer entry, that record stays tied to your account so you can check it later instead of re-entering details each time you return. We don't share your account details with outside parties beyond what's needed to process a transaction or respond to a support request you've raised. This page describes our general posture — not a jurisdiction-specific legal opinion — and you should treat it as a starting point, not a substitute for checking the terms published alongside it. If something here reads unclear against your local rules, raise it with support before relying on it.
Not every part of your visit falls under the same rules, so here's how we draw the line. This matters most once you're moving between devices, since account access, transaction entries and lobby content don't always get handled the same way behind the scenes. Opening your account, loading a game category or checking a payment record each sit in a different part of this policy, even though they all live inside the same session on your phone or desktop. We separate login and account activity from transaction records, and we separate on-site content such as a sportsbook market like Live Cricket Bet from any linked service we don't operate directly. A payment step that runs through Nagad or Bank Transfer, for instance, has its own handling once it leaves our system. If you're unsure whether an entry belongs to account data or transaction history, check the item descriptions below before raising a support request with our team.
Covers login, registration fields and the session details that let your lobby and account wallet stay matched to your device when you return on mobile or desktop. This is the record set we check first whenever a login looks unusual or a session needs confirming.
Covers deposit and withdrawal entries tied to Nagad or Bank Transfer records visible in your account, including the history you can check against your wallet balance. These entries stay visible after the transaction clears, so you don't need to request a separate statement for routine checking.
Covers game categories like Roulette Star, Holdem Highroll and Live Cricket Bet as they appear in your lobby. This policy explains what's recorded when you open a category, not the mechanics of a specific game, and it doesn't extend to a separate sportsbook data feed.
Covers data handled outside 99bet when a linked service, such as a payment provider, processes part of a transaction; that service's own policy applies to its portion of the data. We don't control what that service records, but we only pass along the minimum needed to complete your request.
You don't need to guess what we hold — most of it is visible from your own account. Open your account page to check the details you registered with, confirm which device sessions are active, and look at the transaction entries tied to Nagad or Bank Transfer activity. If something looks wrong, like a mismatched phone number or an outdated detail, you can raise a correction request rather than opening a new account. Questions about how a specific record is used, or why an entry appears the way it does, go through the same support route listed on this page. We treat a correction request and a general question differently, so be specific about which one you're sending. This keeps the process predictable, since a support reply tied to the wrong request type only slows things down for you.
Check your registered details, device sessions and transaction history directly from your account page before contacting support about an entry you don't recognise.
Submit a correction request if your registered phone number, name or linked wallet detail is outdated or entered incorrectly at signup.
Ask us directly if you're unsure why a record appears or how long an entry stays attached to your account before assuming it's an error.
If a correction or question hasn't been resolved, reply through the same support channel you used so the thread stays linked to your original request.
If this page doesn't answer your specific question, you don't have to dig through the whole site to find a way to ask. That's especially true if your question touches a specific transaction, since a general message without account context takes longer to sort out. We've kept support reachable from inside your account, so a question about a data record stays attached to your login rather than getting lost in a general inbox. Pick the route that matches how urgent the question feels — a quick chat for something you need checked right away, or a written message if you want a record of the exchange. Either way, mention your account and the specific record you're asking about so the reply doesn't come back asking you to repeat it. We don't publish fixed response windows here, so treat each route as a way to get your specific question in front of the right person rather than a timed promise.
Open the support chat from inside your account to ask about a specific record or correction without leaving the page you're on. This keeps the question tied to your login, so support can pull up the exact record you're referring to instead of asking you to describe it from scratch.
Check the published help section for answers to common account and data questions before sending a direct message. It's worth a look first if your question is about something general, rather than a specific entry on your account.
Send a message through the support route listed on the site if you want a written record of your data question and our reply. A written thread is useful if the matter involves a correction request, since you'll have the exchange on hand if you need to follow up later.
Keeping your account consistent across a phone and a desktop browser means we hold a working set of details — not just what you typed at signup, but session markers that let 99bet recognise your device the next time you open the lobby. Cookies and similar session tools do that recognition work; they don't rebuild your wallet balance from nothing. Account security on our side depends partly on you keeping your login details to yourself and signing out on shared devices. We keep records for as long as they're needed to support your account and resolve any dispute tied to it, not indefinitely by default. None of this changes what's visible in your own account — the account page stays the fastest way to check a specific entry. If you want to understand how a record is kept, or who inside support can act on a request, ask through the contact route on this page rather than guessing.
Includes registration details, wallet balance history and the records tied to a Nagad or Bank Transfer entry on your account. These stay linked to your login rather than floating as a separate file, so a single check of your account page covers most of what you'd ask about.
Used to keep your login and lobby preferences recognised across a return visit on mobile or desktop without re-entering details each time. Clearing them on a shared device means you'll likely need to log in again next time, a reasonable trade-off for shared phones.
Depends on you keeping login credentials private and signing out of shared devices; we don't store your password in plain readable form. If you suspect a device was accessed without your permission, change your login details and raise it with support rather than waiting.
We keep account and transaction records for as long as needed to support your account or resolve a dispute, not beyond that purpose. Once a record is no longer tied to an open account or an active dispute, it doesn't serve a reason to stay on file.
Here are the questions we hear most about how 99bet handles account and wallet data. If your situation isn't covered below, the support routes on this page are the fastest way to get a direct answer tied to your own account rather than a general statement.
We keep the registration details you provided, your transaction history linked to records like Nagad or Bank Transfer, and session details that recognise your device when you return to the lobby. This set of details is what lets your account wallet and lobby stay consistent whether you open 99bet from a phone browser or a desktop.
Yes — open your account page to check your wallet balance history and transaction entries. If an entry looks wrong, raise a correction request through support rather than creating a new account. Opening a second account won't fix a mismatched entry and can slow down a correction instead.
We don't share account details beyond what's needed to process a transaction or answer a support request you've raised yourself. Any linked payment service handles its own portion under its own policy. We don't sell account details to outside marketers or attach your activity to a wider profile.
Send a correction request through the support route on this page, mentioning the exact detail that's wrong. We handle corrections separately from general questions, so be specific about what needs fixing. A clear subject line, like 'phone number correction,' helps the request move faster.
It can. What's available and how data is handled depends on local law and eligible regions, so treat this page as a general posture rather than a fixed rule. Check the terms published alongside this page if you're unsure what applies in your case.
We keep transaction and account records for as long as they're needed to support your account or resolve a dispute tied to it — not longer than that purpose requires. This applies whether the record involves a Nagad transfer, a Bank Transfer entry, or general account activity.