Reference

What Your 4999bit Privacy Policy Covers

Your account, your wallet, your data — this page sets out exactly what 4999bit records when you sign up from Dhaka, and the choices you have over it.

What we collectHow it is usedWallet dataYour requestsCookie choices
4999bit What Your 4999bit Privacy Policy Covers
COOKIE AND RETENTION

Cookies, Sign-In Security and Retention

Cookies do most of the quiet work: they hold your sign-in between tabs, remember your language, and show us which lobby sections stall on a slow mobile connection. Clearing them from your browser is your call, though the next visit will ask for an OTP. Sign-in security sits with both of us — we run the OTP check on wallet verification, you keep that number to yourself.

Cookies We Set

Session cookies keep you signed in, preference cookies remember language and lobby filters, analytics cookies flag pages that load slowly on mobile data. You can clear them from browser settings whenever you like.

Keeping the Account Yours

Verification runs on an OTP to your registered number, and we never ask for your bKash, Nagad or Rocket PIN. If an old handset still holds a session, sign out of every device from account settings.

How Long Records Stay

Transaction references, game session logs and chat transcripts sit on file only as long as your local rules require, then they go. When a retention window closes, the record is removed rather than archived indefinitely.

Changing or Removing Details

Ask for a copy, a correction or a deletion by writing from the email on your account. We confirm receipt, tell you what can be actioned under your local law, and explain anything that must stay for audit.

DATA REQUEST ROUTES

Reaching the Team About Your Data

Three routes reach the people who handle privacy requests, and each one leaves a record you can point back to. Use the in-account help desk while you are signed in: it ties your message to your account, so nobody has to ask for your registered number twice. Email works when you are locked out and cannot open the desk at all. For anything urgent — an old handset still sitting in your active sessions, for example — the live chat queue is where a person picks it up.

In-Account Help Desk Signed in already? Open Help from the account menu and raise a data request. It attaches your account ID automatically, so the agent sees your wallet history and sign-in devices without a round of questions.
Privacy Desk Email Locked out or writing on behalf of a closed account, use email instead. Send from the registered address and include your account number. You get a written reply you can keep, which matters if you later dispute a record.
Live Chat on Account Access For a session you do not recognise, a device to be signed out, or a verification that stalled mid-way, chat gets a person in real time. Have your registered number ready before you open the window.

Privacy Questions We Get Asked

Most privacy questions come down to three things: what leaves your phone, what our payment partners see, and how long a record sits on file. Here is what we tell people who ask us directly. If your case is not covered, send it through the help desk with your account number attached and we will answer in writing, not in a callback you cannot save.

Your name, mobile number, date of birth, wallet transaction references, sign-in device data and the games you open. Support messages are kept too, so a second agent can pick up your case without repeating the same questions.

No. A deposit is confirmed by the transaction reference and the OTP sent to your registered number, never by your wallet PIN. Anyone asking for that PIN, in chat or over the phone, is not speaking for us.

Write from the email linked to your account and we will confirm what can be removed under your local law. Records tied to an open transaction or a legal requirement may have to stay until that window closes.

Open the live chat queue or the help desk and ask for a full sign-out. We end every active session, then send a fresh OTP before you set a new password on your own device.

The same rules apply on Android, iOS and the mobile browser. The app adds crash logs and a device identifier so a failed wallet verification can be traced. Payment providers see nothing beyond the transfer itself.

Sign-in and wallet pages need session cookies to work. Preference and analytics cookies are optional, so removing them keeps the account usable but resets your language, lobby filters and saved views on the next visit.
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.