Casino / App
This Privacy Policy spells out what nafad88 records when you open an account, sign in, or move money through your wallet, and what say you keep over those records. Below you will find the record types, how long we hold them, and the published support path to use for a copy, a correction, or a closure request.
Privacy rules differ between countries, so what we can collect and store depends on your local law and on the eligible regions where accounts are opened. If you register from Bangladesh, this is the position we apply to you; if you move elsewhere, check what your own jurisdiction allows before you continue using the account. We treat your registration details, sign-in activity and wallet records as the core of this Policy, and we keep them because an account cannot run without them. We do not sell those records to outside parties. Some details reach us indirectly — browser type, approximate location, and the cookies that keep you signed in between sessions. Where a payment route such as bKash or Nagad is involved, the wallet operator handles the transfer on its own terms, and its policy sits alongside ours rather than inside it. You can ask what we hold, ask us to correct a mistake, or ask us to close the account, and we will tell you whether local law lets us act on that request. We update this page when our handling changes, and the version showing here is the one that applies to your account today. Nothing in this Policy alters the terms you accept when you create the account; the two documents are meant to be read together.
Think of this Policy as the boundary around everything you do once you hold an account with us. Opening the account, signing in from your phone, funding the wallet and reading your transaction history all sit inside it. What sits outside are the services we do not run: the wallet app on your handset, the browser you use, and any page you land on after tapping a link away from our lobby. A bKash deposit, for example, is a record we hold on our side and a separate record your wallet provider keeps on theirs; a question about the second one belongs with them. Games you launch, such as Live Cricket Stadium or Spice Bazaar Slots, load inside our pages, so your in-session activity there is covered here. If a category is not named on this page, ask us before you assume it is covered, and we will tell you plainly which document applies.
Everything tied to the account you open sits inside this Policy — the email and password you set, the sign-in activity on your device, and the preferences saved against your profile. If someone else uses the same phone, their activity is treated as part of your account until you sign out.
Movement through your account wallet — a bKash deposit, a Nagad transfer, or a withdrawal request — creates a record we keep against your profile. We hold those entries to answer your own questions about what entered and left the account, and to meet record-keeping duties that apply where you live.
Small files saved in your browser keep you signed in, remember the language and lobby view you chose, and tell us which pages load slowly on your connection. You can clear them from your browser settings at any time; signing in again will simply create a fresh session.
Wallet operators, your mobile network and any site you reach through a link from our pages run under their own rules. We cannot change how a wallet provider or a browser handles your data, so read the terms published there before you share anything. Access depends on your local law and eligible regions.
You are not locked out of your own records. Sign in and open your account profile to see the details we hold on you, then use the support path published on the site if something there is wrong or out of date. Ask us to change a misspelled name, a phone number that has moved on, or an email you no longer read, and we will make the change where local law allows. Want a copy of what we hold? Ask for it through the same channel and we will tell you what we can send. Want the account closed? Tell us, and we will explain what happens to the wallet balance and to the records we are required to keep afterwards. If you believe we have handled something badly, raise it with support first — most disagreements end there, and we would rather fix a problem than argue about it. We answer privacy questions in English so nothing gets lost in translation.
Sign in, open your profile and check the contact details, device sessions and wallet entries listed there. If a field looks wrong, keep the page open and quote it when you contact support — a copied reference number makes the reply quicker and easier to track.
Names spelled differently from your wallet, an old phone number, or an email you have stopped using are the changes we handle most often. Contact support from the signed-in account, describe what should change and why, and we will confirm the change in the same thread we started with you.
You can request a copy of the account records we hold. Send the request through the support route published on the site, from the address registered on your account, and tell us which records you need. We will confirm what we can send under the law that applies where you live.
If you want to stop using the site, tell support from the signed-in account. Check the wallet balance first so nothing is stranded, and read what we are required to keep afterwards for record-keeping. Closure does not erase duties that local law places on us.
Questions about this Policy reach a small team, and every published route below works from a normal mobile browser — no app install is needed. The quickest path is the support chat inside your signed-in account, because the agent can see the profile you are asking about without you explaining it twice. If you would rather write it out, use the support email address listed on our contact page; put your registered email and a one-line summary in the message so it lands with the right person. Signed-in help pages answer the routine questions — how a bKash deposit appears in the wallet, why a session was signed out, how to change a phone number — and reading them first often saves a round trip. We do not publish separate phone lines or fixed hours, so please use the routes named here rather than a number you find elsewhere. Nothing here changes how your wallet provider handles a transfer on its own side.
Open the chat from the account area once you have signed in. Because the agent already sees the profile you are writing about, you can keep the message short — the account email plus one line about what you need is usually enough to start.
The address published on our contact page is the right place for anything you want in writing, including a request about your records. Send it from the email registered on your account so we can match the message to the right profile without asking you again.
Inside the account you will find short pages covering the questions that come up most — how a wallet deposit is recorded, why a session ended, how to change contact details. Many of you will find the answer there before you need to open a chat at all.
Handling records properly is mostly about limits. We collect what an account needs — the email and password you set, the contact number on your profile, wallet entries for bKash and Nagad activity, and the device details that keep a session honest. We keep sign-in and transaction records for as long as the account is open and for the period afterwards that record-keeping rules require where you live; cookie preferences and browsing data on our own pages are cleared or refreshed on much shorter cycles. Cookies do the small jobs: keeping you signed in, remembering the lobby view you chose, and showing which pages struggle on a slow connection. Account security is shared work — use a password you have not used elsewhere, keep your email inbox locked down, and sign out on a shared phone when you finish. When you write to us, you reach the team named in the support section above, and any correction or closure request is handled through the same published routes. We do not sell the records you create.
Account details you type in, wallet entries created by a bKash or Nagad movement, and the basic device and connection data a browser sends when you open a page. That set is what this Policy covers; anything outside it is described in the scope section above.
Our own cookies keep a signed-in session alive, remember your chosen lobby view, and measure which pages load slowly. You can clear them from browser settings whenever you like; the next sign-in simply starts a fresh session, and no part of the account disappears.
Transaction entries stay while the account is open and for the record-keeping period that applies where you live. Cookie data on our pages clears or refreshes on far shorter cycles. When a retention period ends, the record stops being part of the working account.
Use a password you have not used on another site, keep the email on your profile reachable, and sign out when you hand the phone to someone else. If you think a session was not yours, contact support from the signed-in account and we will look at it with you.
These are the privacy questions we get asked most, answered the way we would answer them in a chat. If your situation is not covered here, the support route in the section above is the place to take it — a short message with your account email is enough to start. We keep the answers plain on purpose: what we hold, what you can ask us to change, how long records stay, and who handles the wallet side of a transfer. Read the scope section above if you are unsure whether something falls inside this Policy at all. Nothing on this page replaces the law where you live; where the two disagree, local law decides what we can and cannot do with your records. We will say so plainly if that happens. If an answer here ever looks out of step with the signed-in help pages, treat the help pages as the more current version and tell support so we can correct this page.
Send the request through the support route published on the site, from the email registered on your account. Tell us which records you want — profile details, wallet entries, or sign-in activity. We will confirm what we can send under the law that applies where you live.
You can ask us to close the account from the signed-in support chat. Check the wallet balance first so nothing is left behind. Closure stops new activity, but record-keeping duties where you live may require us to keep transaction entries for a set period afterwards.
We share only what a transfer needs to complete, and the wallet operator then handles that movement under its own policy. We do not sell the records your account creates, and we do not hand your details to unrelated advertisers. Questions about the wallet side belong with the provider.
Ours cover three jobs: keeping a signed-in session alive, storing the lobby view and language you picked, and measuring page load on your connection. You can clear them from your browser settings at any time, and a fresh sign-in will start a new session without affecting your account balance.
Use the signed-in support chat first, because the agent can see the profile you are asking about. If you prefer writing, use the support email on the contact page. Give the account email and one line describing the problem, and we will take it from there.
The account belongs to whoever is signed in, so anything done on a shared phone is recorded against your profile until you sign out. Set a password you keep to yourself, avoid saving it in the browser, and sign out when you hand the handset back.