Slots / Casino
Your account data belongs to you. We want you to know exactly what we collect, where it goes, and how you can manage it — before your first session and at any point after. Access and eligibility depend on your local law and eligible region.
When you open an account on naga99, a few categories of data come into play: the details you submit at registration, the device and browser signals your session sends, and the payment route you use — whether that is bKash, Nagad, Rocket, or a bank transfer.
Privacy on naga99 is not a single checkbox — it covers several distinct data types, each with its own handling path. Understanding these categories helps you make informed choices about your account.
The name, contact details and verification information you provide when you open an account.
Browser type, device model and session timestamps are collected automatically. This helps us serve the mobile interface correctly — important when you switch between a phone browse
When you fund your account through bKash, Nagad, Rocket or a bank transfer, transaction references are recorded against your wallet. We do not store full payment credentials on our side — the wallet provider handles that leg. Check your wallet app's own privacy terms alongside ours.
Messages sent through our support channel are retained to resolve your query and to improve response quality. If you want a record of a support conversation, note the ticket reference shown during the interaction. You can ask support to clarify how long interaction data is kept.
Knowing data exists is one thing; being able to manage it is what counts. Your naga99 account includes a settings area where several privacy-relevant controls are available. These are not hidden behind a support ticket — they sit in your signed-in account panel.
Inside account settings, you can adjust whether promotional messages reach your registered contact. Toggle this off if you want account-only communications. Changes apply from the next scheduled send cycle, not retroactively.
Your account history panel shows session timestamps and wallet movement records. This is read-access — you can review but not edit the log. It is the same log our support team references when you raise a query.
If you want a copy of the data we hold against your account, raise the request through our support channel. The published policy outlines the process and the timeframe we aim to follow. Eligibility and applicable rules depend on your local law.
Closing your account triggers a data retention review in line with our published policy. Some transaction records are kept for a period required by applicable rules. Support can walk you through what is retained and for how long before you close.
Privacy questions are handled through the same support routes we use for account and payment queries. If you have a specific concern about how your data is processed — whether it is about your bKash transaction records, your r
Open the live chat icon from your signed-in account page and describe your privacy concern in plain terms. The agent will either resolve it directly or escalate to the relevant team. Have your account reference ready to speed up the process.
For detailed data requests — such as asking for a copy of your account data or requesting deletion — email is the more appropriate route. Use the contact address published in the footer. Include your account ID and a clear description of what you are asking for.
Many privacy questions are answered inside our published policy itself. Access it from the footer link on any page — no login needed. It is written to be read directly, not as a legal document you need a lawyer to decode.
A privacy policy is only worth reading if the information in it is accurate and up to date. We update our published policy when anything material changes — a new data category, a change in how payment routes are processed, or a shift in the support co
The privacy policy linked in the footer reflects what is active today. We do not maintain separate versions for different account types. What you read there applies to your account regardless of whether you joined recently or have been active for some time.
bKash, Nagad and Rocket handle their own credential security on their side. We record only the transaction reference and wallet-type against your account — not your mobile banking PIN or full wallet number. Check the respective wallet app for its own data terms.
Access to naga99 and the data rights that come with it depend on your local law and eligible region. The published policy notes where regional rules affect what controls are available to you. We do not make blanket promises that override local legal requirements.
If anything in the privacy policy reads as ambiguous, our support team is a direct verification route. Ask the agent to confirm the specific clause or data handling step you are unsure about. We prefer a clear answer over a vague reassurance.
Privacy documents use a specific vocabulary that is not always obvious. These definitions cover the terms you are most likely to encounter when reading the naga99 privacy policy or managing your account data settings.
Personal data means any information that can identify you directly or indirectly — your name, contact details, device ID, or transaction reference. On naga99, this includes the details you provide at registration and the payment references tied to your wallet.
Data processing covers any action taken with your information — collecting it, storing it, using it to verify your account, or passing it to a payment partner like bKash or Nagad. The published policy lists which processing activities apply to your account type.
The data controller is the party that decides why and how your personal data is used. On naga99, the platform operates as the data controller for account and session data. Payment wallet providers like Nagad and Rocket are controllers for their own transaction data.
Consent means you have actively agreed to receive promotional messages from us. You can withdraw that consent at any time through account settings. Withdrawing consent does not affect your account access or any transactional communications tied to your wallet activity.
Data retention is how long we keep records after they are created or after your account closes. Some records — particularly payment transaction logs — are kept for a period required by applicable rules. The published policy states the retention periods that apply.
Third-party sharing means passing your data to an external party — such as a payment processor or fraud-screening service. We share only what is necessary for your account to operate. We do not sell your data to advertisers or unrelated third parties.
These are the questions we hear most often from account holders about how their data is managed on naga99. The answers draw directly from our published policy and account settings — not from generic privacy language that could apply to any platform.
The privacy policy is linked in the footer on every page — no login required. Open the footer, look for the privacy or legal links section, and the current policy document loads directly. It is the same document that applies to all active accounts regardless of region.
We record the transaction reference and wallet type that your bKash or Nagad app sends us when a transfer completes.
Yes. Raise the request through our email support route using the address in the footer. Include your account ID and specify that you are requesting a data copy.
Log into your account and open the settings panel. The marketing preferences section lets you toggle off promotional communications. Changes apply from the next send cycle. Your account access and transactional messages — like payment confirmations — are not affected by this change.
Closing your account does not delete all records immediately. Transaction logs and identity verification data may be retained for a period required by applicable rules in your e
Your account data and privacy settings remain the same across devices — the same policy applies whether you log in from your phone browser or a desktop. Device and session data collected may differ slightly by browser type, but your account-level controls and preferences carry over.