Reference

Privacy Policy: What We Keep and Why

This page sets out, in plain words, the account and wallet information bet9999 holds when you open an account and use it from your phone.

Account dataWallet referencesCookie choicesDeletion requests
bet9999 Privacy Policy: What We Keep and Why
PRIVACY REQUESTS

Where to Send a Data Request

A privacy request should reach a person, not a form that disappears. Use live chat inside your signed-in account and tell the agent you are writing about account data; that route already knows which account is yours, so nothing sensitive has to be typed twice. For a written record, the support email works and we reply to the address on file. Either way, say what you want — a copy of your data, a correction, or account closure — and confirm your mobile number so the request can be verified before any change is made.

Team online

In-account live chat

Signed-in chat is the quickest route for a data question. The agent can already see your account, so you only confirm your mobile number instead of resending documents.

Support email

Send a written request and keep the thread. We answer the address registered on your account so the reply does not land with someone else.

Account closure request

Ask for closure in the same channel you use for payment issues. We confirm identity first, then tell you what is deleted and what local rules make us retain.

HOW DATA IS HELD

Cookies, Security and Retention in Practice

Login runs on a one-time code sent to your registered mobile number, so a password alone will not open the account. Sessions on your phone can be ended from the device list if you lend the handset or sell it. Cookies keep you signed in and remember language and wallet preference; you can clear them in the browser, though some parts of the lobby will then ask you to sign in again. Transaction rows are kept for reconciliation and for the retention period local rules set, then removed. Nobody at bet9999 asks for your bKash, Nagad or Rocket PIN, and any message that does is not from us.

One-time code login

A code goes to your registered number at each new sign-in. If a code arrives when you did not try to log in, contact support and we will lock the session.

Device and session list

Your account shows the handsets signed in. Remove any you do not recognise, then change the number-linked login from the same screen.

Cookie control

Essential cookies hold your session and security checks; preference cookies remember language and payment choice. Clearing them signs you out of the browser.

Retention and removal

Wallet and deposit records stay while the account is open and through the required period after closure. Marketing data goes when you opt out.

Privacy Questions We Get Asked

Your name, mobile number, date of birth, login device details and payment references from bKash, Nagad, Rocket, Upay or Bank Transfer. We keep the transaction ID and sending wallet number so a top-up can be traced if it does not land.

No. We never ask for your bKash, Nagad or Rocket PIN, and we never ask you to read out a login code. Any call or message requesting either is not from us — end it and report it through in-account chat.

Yes. Open live chat from your signed-in account, say you want a copy or a correction, and confirm your mobile number. We verify first, then send the record or update the field you point out.

We remove profile and marketing data. Deposit and withdrawal records stay for the period local rules require, because they back the money trail. We tell you which records are kept and why when the closure is confirmed.

They stay while the account is open and through the retention period your local law sets after closure. After that they are deleted. You can ask at any time which records are still held against your name.

Yes. What we may collect, and how long we keep it, follows the law where you are. Access to bet9999 itself depends on your local law and eligible regions, so check that before you open an account.
Reference

Privacy Policy

Service availability depends on eligible regions and local law. Users should check local rules before opening an account.

Access may be available only where local law permits.