Sports / Casino
This page sets out what odds9 collects when you open an account, how a bKash, Nagad or Rocket transfer gets recorded, and the choices you keep over those details. Access depends on your local law and eligible regions, so check what applies where you are before you register.
Your odds9 account holds details you would not pass around: your name, mobile number, the wallet you use for a bKash or Nagad transfer, and the record of what you have funded or withdrawn. This policy sets out what we collect, why we need it, and the choices you keep. It is written in plain English so you can read it on a phone. Access depends on where you are. Nothing here invites you to open an account where local law does not allow it, and any feature — including Rocket, Upay or Bank Transfer rails — follows the rules of your eligible region. If a payment route is not shown inside your signed-in account, it is not available to you, whatever a marketing page suggests. Data reaches us two ways. You hand some over when you register, verify wallet details or contact support. The rest arrives on its own: device type, browser, approximate location, and the pages you open in the lobby. We use it to keep the account secure, to match a transaction with the wallet it came from, and to fix anything that breaks on a small screen. We do not sell your details. Limited data goes to the payment partners handling a transfer you started, and to game providers whose titles you open, only as far as the transaction needs. Where records must be kept, we keep them for the period the law in your jurisdiction sets. Raise a question through support and a person answers about your own account.
A privacy policy is only useful if you can tell where it stops. It follows you from the moment you tap the account page to the moment a wallet transfer settles, and it stays over the record afterwards. Four areas sit inside it. Your account access covers the email or number you sign in with, the password you set, and the session your browser keeps. Transactions cover every bKash, Nagad, Rocket, Upay or Bank Transfer movement linked to your account wallet. Lobby content covers the screens you open — slot rooms, live tables, the sportsbook — along with the cookie preferences stored on your device. Third-party services sit partly outside. A game provider builds the table you play on and a payment partner moves the money, each under its own terms. We cannot rewrite what they do with data they receive lawfully. What we can do is limit what we hand over, tie it to the transaction, and tell you which part of your journey this page covers.
Your sign-in email or mobile number, the password you set and the session your browser keeps. We hold these to confirm it is you coming back, and to close a session you no longer want open. You can change your sign-in details from the account page whenever you need to.
Every bKash, Nagad, Rocket, Upay or Bank Transfer movement tied to your account wallet, with the amount, the time and the reference the payment partner returns. We keep this so a missing transfer can be traced and a cashout matched to the right record.
The slot, live table and sportsbook pages you open, plus the cookie and language preferences stored on your device. This tells us which screens load slowly on mobile data and which game categories you come back to, so the lobby opens where you left it.
A game provider runs the table you play on; a payment partner moves your money. Each receives only what the service needs and follows its own privacy terms, which we do not control. Read those terms before you rely on them for your own records.
You are not stuck with whatever we hold. Open your account page and you can see the profile details we keep, change a mobile number that has moved with you, or update the wallet you use for deposits. If something looks wrong — a transfer recorded twice, an old number still attached — tell support and we will correct it against the payment reference. You can also ask what we hold, ask for a copy for your own records, or ask us to stop sending you lobby notices. Requests about your data go through the same support route, and we answer about your own account. Keep one thing in mind: a payment record tied to a completed transfer may have to stay with us for the period local law requires, so some requests are limited. Deletion is not always possible while an account is open and active. Where a request cannot be met, we say why in the reply.
Sign in and open your account page to read the profile data we hold: name, mobile number, wallet reference and the notification settings attached to your login. If a field is out of date, edit it there rather than opening a second account you do not need.
Wrong mobile number, mistyped wallet reference, a transfer logged against the wrong record — raise it with support and we will correct it against the payment reference. Bring the transaction time and the wallet you used so the matching goes quickly.
Questions about how we use your data, how long a record stays, or who receives it during a transfer can be sent through the published support route. You will get a reply about your own account, not a general statement copied from this page.
If a session will not close, a login email stops arriving or wallet verification stalls, contact support with the mobile number your account is registered under. We look at the account itself and tell you what we find on it.
Every odds9 page carries the same support route, and that is where a privacy question goes. You do not need to hunt for a special form. Open the support link from your account menu or the site footer, say what you want to know, and include the mobile number your account is registered under so we can find you. Two things speed up a reply. Describe the record you mean: which wallet you used, roughly when the transfer happened, and the reference the payment partner returned. Then say what outcome you want — a copy of your data, a correction, or an answer about who received it. If your question is about a game provider's own handling of your play, we can tell you which provider runs that table but not change their terms. The same holds for a payment partner's processing. We answer for our own part of the journey. Never send your account password to anyone claiming to be from support.
Signed in or not, the support link in your account menu and the site footer opens the route we answer from. Send your question with your registered mobile number and the wallet you used, so we can pull the right record instead of guessing at it.
Prefer a written thread? Use the contact route published on the support page and include the transaction reference with a short description of what you need. The reply comes from a person reading your account, not from an automated queue.
Once you are signed in, the help entry inside the account area is the shortest path. It already knows which account is asking, so you skip the identity questions that slow a written message down, and the thread stays linked to your record.
Security here is mostly boring on purpose. Your sign-in is protected by the password you set and by the session your browser holds; when you log out on a shared phone, that session ends. Keep the password to yourself. Nobody from odds9 will ask for it in a chat or a call, and a message that does is not from us. Cookies do two jobs. Some keep you signed in and remember your language; others show us which parts of the lobby load badly on mobile data. You can clear or block them in your browser settings, though a blocked sign-in cookie means you log in again on every visit. Personal data stays with us only while it has a purpose. An active account needs its profile, and a completed transaction needs its record for the period local law sets. After that, records are removed or cut down to what we must retain. You keep control of what happens next: edit your details, ask for a copy, ask us to stop lobby notices, or close the account. The support route handles all four.
Your password and your session are the two gates. Choose a password you do not reuse on other sites, sign out on shared phones, and treat any message asking for that password as a fraud attempt rather than us checking in with you.
Sign-in cookies keep you logged in; preference cookies remember your language and region view. Analytics cookies show us slow pages on mobile data. Manage all three in your browser settings, and expect to log in again each visit if you block the sign-in ones.
An active profile stays while your account is open. Transactions are held for the period local law requires, because a payment query can surface later. When that period ends, the record is removed or cut down to the minimum we are obliged to keep.
One published support route covers data questions, corrections, copies and account closure. Write with your registered mobile number and the record you mean, and the reply will name what we can change and what local law keeps in place.
The five questions below come up most often from account holders in Bangladesh. Each answer follows the same data rules described above, so if your situation is not covered, send the question through the support route and we will answer it against your own record.
Your name, mobile number and email, plus the wallet reference you give us. Device data arrives on its own: browser type, approximate location and the lobby pages you open. Transfers made through bKash, Nagad, Rocket, Upay or Bank Transfer add an amount, a time and a payment reference matched to your account.
Sign in and open your account page to read the profile details attached to your login, including your registered mobile number, wallet reference and notification settings. Anything you cannot see there can be requested through the support route, and the reply names what we hold.
Only what a transfer needs. When you fund the account through a local wallet or a bank transfer, the partner processing it receives the amount, your wallet reference and the matching identifiers. Your password and your full profile stay with us rather than travelling with the payment.
An active account keeps its profile while it stays open. A completed transaction is held for the period the law in your jurisdiction sets, because a payment query can surface later. Once that period ends, the record is removed or reduced to what we must keep.
Edit your mobile number, email or wallet reference from the account page yourself. For a copy of your data, a correction we cannot make from our side, or closure of the account, use the published support route. Records tied to completed transfers are held for the period local law requires.
Access depends on your local law and eligible regions. If the site or a payment route is not offered where you are, this policy does not create a right to use it. Where access is allowed, the data rules on this page apply to your account in full.