Reference

nagb88 Privacy Policy in Plain Words

One page tells you exactly what nagb88 holds about your account, why we hold it, and the three ways to ask us to change or remove it — no buried clauses, no separate app-only terms.

What we collectWhy we keep itCookie choicesYour request pathWallet checks
nagb88 nagb88 Privacy Policy in Plain Words
PRIVACY SUPPORT

Ask Us to Change Your Record

Every privacy request lands with a real person on our support desk, whether you sign in from Dhaka or anywhere else in Bangladesh — not a form that vanishes into a queue. Sign in with your one-time code, open the help tab inside your account and start a chat: the session already proves the number is yours, so we can act sooner. Prefer email? Write from the address or the bKash, Nagad or Rocket number registered on your wallet and quote your account ID. If the question is about a transfer that never landed, keep the wallet transaction ID ready.

Chat inside your account Open the help tab after your one-time code sign-in and the chat carries your account ID with it. Nothing to type twice, and the agent can see the wallet record.
Email the desk Send from the mail address or wallet number registered on your account. Quote your ID and the request — copy, correction or closure — and we reply with the next step.
Wallet transfer checks Tracing a bKash, Nagad or Rocket transfer? Keep the transaction ID from the confirmation SMS. It points straight at the record, and the check gets done faster.
ACCOUNT CARE

Check How We Guard Your Account

Security on this side starts with one rule: we never ask for your wallet PIN or your one-time code, in chat or by phone, and nobody at the desk will ever request it. Your password is stored hashed, and a sign-in from a new device asks for a code on your registered number before anything opens. Cookies on the site remember your language and keep the session alive; the ones that measure traffic are optional and sit in account settings. Records stay only while the account is open or a payment rule requires them, and you can ask what is on file at any point.

Cookies and session

The site sets a small cookie to keep your session open and remember your language. Optional traffic cookies can be switched off from account settings without breaking the wallet page.

Sign-in protection

A new device or a new browser asks for a one-time code sent to your registered mobile number. We never ask you to read that code to anyone, including our own desk.

Retention

Round IDs, wallet transaction IDs and bet records are kept while your account is active, and afterwards for the period local rules and our payment partners require.

Changes and requests

Ask for a copy, a correction or a closure from your registered number. We confirm who you are first, then tell you what can be changed and what must stay on file.

Browse the Privacy Questions We Get

These come up most often at the desk, and here is the short answer to each. Anything specific to your own account — a wallet transfer that shows twice, a sign-in you don't recognise, a request to drop a number you no longer use — moves faster through chat, because the agent can open the record while you talk. Where local law gives you a right we have not listed, say what you need and we will check it against the rules for your region.

Your name, mobile number, date of birth and the wallet or bank number you pay from, plus the device, IP address and session times recorded at each sign-in.

Yes. Message the desk from your registered number and ask for a copy of your account record. We confirm your identity first, then send it through the same channel.

Only with the wallet provider confirming your transfer, and with authorities where the law requires it. We do not sell account details to advertisers or outside lists.

While your account is open, and after closure for whatever period payment partners and local rules require. Bet slips and wallet transaction IDs usually sit in that second group.

Ask in chat or by email, clear any wallet balance first, then we close the account. Details we are not obliged to keep are deleted; the rest is marked closed and held.

The Android app stores your session token on the device instead of a browser cookie. On the web, session cookies keep you signed in and optional traffic cookies can be turned off.
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.