Live / App
nagay88 explains in this policy how we handle your account details, your wallet activity on bKash, Nagad or Rocket, and the records tied to the time you spend on the site; what applies to you depends on your local law and eligible region.
This policy sets out how nagay88 handles the information tied to your account, your wallet activity and your time on the site. We collect only what is needed to open and run your account, confirm transactions you make through bKash, Nagad or Rocket, and keep the service working the way you expect on mobile or desktop. What applies to you can shift depending on where you are logging in from, because access and data handling on this page follow your local law and the rules that cover your region. We do not sell your account data to outside advertisers, and any record kept for a payment route stays attached to that transaction history rather than any marketing list. Where we use cookies or similar device markers, it is to keep your session active, remember your preferred language and recognise returning browsers rather than to build a public profile. If a page or a feature changes how it reads your data, we update this policy and the date attached to it, so checking back here before a deposit or withdrawal step is a reasonable habit, not an inconvenience. Nothing on this page overrides terms that are jurisdiction-specific; where local law sets a stricter rule on data retention, consent or payment-record handling, that stricter rule is the one that applies to your account.
Our policy covers what happens from the moment you open the login page to the moment you close a game table or step away from the sportsbook. Account access, the wallet activity you run through bKash, Nagad or Rocket, and the pages you browse inside the lobby all sit inside this policy. What sits outside it is anything handled by a third party once you leave our pages — for instance a payment app's own data rules once a transfer leaves our interface. We do not claim to control how bKash, Nagad or Rocket process a transaction on their own systems; our policy covers the record we keep on our side of that transaction. Site content such as game pages, support articles and account screens falls under this policy, while external links or third-party widgets follow their own separate terms, which we encourage you to read before you continue through them.
Logging into your nagay88 account, resetting a password or updating contact details on your profile sits inside this policy, because that activity happens directly on pages we control and the data stays tied to your account record rather than any outside system.
When you move funds through bKash, Nagad or Rocket to fund your account or withdraw from it, we keep a record of that transaction on our side; the policy covers that record, not the internal processing each wallet provider runs on its own app.
Pages you open inside the lobby, game screens, support articles and the account dashboard are covered here, including how your browser or device behaviour is read to keep a session active while you move between a slot room and the sportsbook.
Where a page links out to a payment provider's own app or a separate verification step, that service runs under its own terms once you leave our interface; this policy does not extend to data handling performed entirely outside nagay88.
You are not left guessing once your account is open. If you want to see what sits against your profile, you can ask us to check it; if a detail is wrong — a phone number tied to your bKash deposit history, for instance — you can have it corrected. Raising a question about how your data is used does not require a formal process on your side: it starts with a message through a published support route. We treat a request to correct account details the same way we treat a request to explain a wallet record, by checking it against the account you are signed into. Where local law gives you a stronger right over your own data, that right sits above anything written here, and we work from the stricter rule rather than our own default.
Ask us to show what account and transaction details are attached to your profile, including entries connected to a bKash deposit, a Nagad transfer or a Rocket payment, so you can check it against your own records.
If a phone number, email address or payment reference on your account is wrong, tell us through a published support route and we will update it against the account you are signed into, once we can confirm it is yours.
Send a question about how a specific record, cookie or wallet entry is used; we read it against the policy in force at the time and reply through the same support route you contacted us on.
Where you need help understanding an entry tied to a transaction or login history, our support route is the way to ask; we check the request against your signed-in account before responding.
Questions about this policy don't need a separate channel from everything else on your account. If something about a bKash deposit record, a Nagad transfer entry or a browser cookie setting is unclear, the same published support route handles it. We keep the path simple on purpose: find the support option visible from your account area, describe what you want checked — a data entry, a correction, a question about retention — and we work from the account you are signed into rather than asking you to prove anything twice. We don't operate a separate privacy desk with its own hours or ticketing system; data questions go through the same route as any other account question, which keeps the record of your request attached to one account history instead of scattered across different channels.
Open the support option shown inside your signed-in account area to raise a question about any data entry, cookie setting or record tied to your profile; replies come back through that same route so the request stays attached to your account.
If a bKash deposit, Nagad transfer or Rocket payment entry on your account needs checking, use the published support route rather than the payment app itself, since the record on our side is what this policy actually covers, not the processing each wallet app runs internally.
Where a line in this policy is unclear against your own situation, send that specific question through the support route listed on the site; we respond against the version of the policy that was active when you asked, not a later update that hadn't been published yet.
Keeping your account data orderly matters more to us than any single feature on the lobby page. We hold account and transaction details only as long as they are needed to keep your history accurate — a bKash deposit record, for example, stays attached to your account rather than floating in a separate marketing database. Cookies on this site mostly do the quiet work: holding your session, remembering a language setting, recognising a returning device. Account security on your side still matters — using a password you don't reuse elsewhere and checking you're on the right page before entering wallet details both reduce risk on your end. If you want a change made to how a record is held, that request goes through the same support route as any other account question, checked against the account you're signed into.
We keep account and transaction records, including entries tied to a bKash deposit or Nagad transfer, only for as long as they support your account history; we don't carry that data past what the account and local law require, and we adjust that window whenever this policy is updated.
Cookies on nagay88 keep your login session active, remember a language setting and help recognise a returning browser or device; they are not used to build a profile for outside advertisers to buy or trade, and clearing them from your browser simply means signing in again on your next visit.
Your account is only as protected as the password and device behind it; avoid reusing a password from another site and confirm you are on the correct page before entering a bKash, Nagad or Rocket detail, since the address bar and the padlock icon are the two things worth checking each time.
To correct a detail or ask about a record, use the support route visible inside your signed-in account; we check every request against that account before updating anything on your profile, rather than acting on a message sent from an email address or number that isn't attached to it.
A few questions come up more than others when you're checking how nagay88 handles account data, so we've answered them directly here rather than leaving them scattered across the site.
We collect the details needed to open and run your account — contact details, login credentials and the transaction history tied to a bKash deposit, Nagad transfer or Rocket payment. We don't collect more than is needed to keep your account and its wallet activity accurate and traceable to you.
We don't sell account or wallet data to outside advertisers. Any record connected to a bKash deposit or Nagad transfer stays attached to your transaction history on our side, and is only shared further where local law requires it or where a payment route itself needs it to process.
Yes. Send that request through the support route visible inside your signed-in account, and we'll check it against the account you're logged into before sharing or correcting anything. This applies to login details, contact details and the record tied to any bKash, Nagad or Rocket entry.
Yes — access and data handling can shift depending on your local law and the rules covering your region, so part of what applies to your account depends on where you are signing in from rather than one fixed rule for every visitor.
Logging out ends the session cookie that kept you signed in, though a device-recognition cookie may still remember your browser the next time you visit. Clearing cookies from your browser settings removes that memory, and you'll simply be asked to sign in again on your next visit.
Raise it through the same support route you'd use for any account question — describe the record, the date and what seems off, and we'll check it against the account you're signed into. We don't run a separate channel just for data questions.