App / Mobile
na999 collects and stores only the account, device and transaction details needed to run your lobby session, your wallet record and your support history. This page explains what we hold, how long it stays on your account and who you can ask when a detail looks wrong, with the exact wording depending on local law and eligible regions.
This Privacy Policy sits alongside the account terms you accept when you open an na999 account, and it governs how we collect, store and use the information tied to your lobby session, your wallet balance and the payment route you choose. Availability of specific features and the way we are allowed to process your data depends on your local law and the eligible regions where na999 operates, so the exact wording that applies can shift depending on where you are logging in from. When you fund your wallet through Rocket or settle a transfer through Bank Transfer, we record the transaction reference, timestamp and status shown on your account statement, not the full credential details held by the payment provider itself. We do not sell this data to outside advertisers, and we only share it with the limited set of parties needed to process a transaction, confirm your identity on request, or respond to a support query you raised. Where a part of the lobby, a slot room, a live table, cricket markets, is accessed from a browser or app, the same account-level data practices apply regardless of which section you are using. If the law in your region requires a different disclosure, that regional version takes precedence over the general wording here.
Not every action on na999 touches your personal data the same way, so this policy draws a line between what counts as information and what does not. Browsing the lobby to compare Cricket Wicket Win against Blackjack Glory, for instance, does not require us to store anything beyond a session log, while opening your wallet to review a Rocket or Bank Transfer record does pull on your verified account details. Site content, game descriptions, cricket market framing, published pay-table notes where a studio exposes RTP information, is treated as public material, not personal data. Third-party services, like the payment rail processing your Rocket top-up or the studios supplying titles such as Crash Rush, operate under their own data handling rules once a transaction or game session leaves our platform boundary, and this policy only speaks for what na999 itself controls.
Logging into your na999 account from a mobile browser or app session falls under this policy. We note sign-in timestamps and device type to protect your wallet, but we do not treat this as marketing data, and the record sits inside your account history for you to review.
Every Rocket top-up or Bank Transfer settlement linked to your account is logged against your wallet, including the reference number, amount shown on your statement and status. This record exists to resolve a query you raise and confirm your balance, and it stays inside your account rather than external advertising systems.
Browsing categories like live tables, Chittagong Lucky Slots or cricket-led sports markets does not pull personal data beyond a session log. Pay-table or RTP information, where a game or studio exposes it, is published content and sits outside the personal-data scope this policy covers.
Payment rails processing your Rocket or Bank Transfer request, and studios supplying titles you open in the lobby, run under their own data handling terms once your session or transaction leaves na999's own systems. This policy explains our side only, not theirs.
You are not locked out of the information na999 holds on your account. If you want to see what is logged against your wallet, a Rocket deposit, a Bank Transfer settlement, a past support thread, open your account page and review the activity shown there before raising a question through the published support route. If a detail is wrong, such as a mismatched name or an outdated contact method, correcting it starts the same way: through your account settings rather than a support ticket alone, since the account page is where na999 keeps the record you are allowed to edit. Where local law gives you a further right over this data, the support route listed on our site is where that request begins, and the response depends on the law and eligible region tied to your account.
Open your account page to check the wallet and session entries na999 keeps against your profile, including Rocket deposits and Bank Transfer settlements shown on your statement.
If a contact detail or account field is wrong, update it through your account settings rather than waiting on a support reply, since that page holds the editable record.
Use the published support route on na999 to ask about a specific entry on your account, and reference the transaction or session date so we can locate it.
Where local law gives you a right beyond reviewing your record, start that request through the same support route; the outcome depends on the law in your region.
Questions about this Privacy Policy go through the same support route you would already use for a wallet or account query; we have not set up a separate channel just for data questions, because your account history and your privacy question usually sit on the same page. If you are asking about a Rocket deposit that looks off, or a Bank Transfer entry you do not recognise, mention the reference shown on your statement when you reach out, since that lets us match your question to the exact record on your account rather than guessing. The in-account message route is the one we check first; it keeps your identity verification and your question in one thread instead of splitting it across channels. Response timing depends on the volume of questions ahead of yours and on the detail you provide, so a clear reference number helps more than a general description.
Send your privacy or data question through the support message option inside your na999 account, where your wallet, your Rocket or Bank Transfer history and your session log are already linked to the thread, which helps us match your query to the right record without extra back-and-forth.
Before writing in, open your account page to check whether the record you are asking about, a deposit, a settlement, a login, is already visible there, since some privacy questions get answered by the page itself before you need to send anything.
This Privacy Policy page itself is the published reference for how na999 handles your account, wallet and session data; keep it open alongside your support thread so you can point the team to the exact section your question relates to.
Keeping your account usable across sessions is part of why na999 holds data in the first place, your login state, your wallet balance after a Rocket deposit, your preferred lobby view, rather than data collection for its own sake. We use basic cookies to keep you signed in on your mobile browser between visits and to remember lobby settings like the last category you browsed, whether that was live tables or a title such as Football BalMoney. Account security on our side relies on your login credentials and the verification steps shown when you update sensitive details; we do not publish a separate security certification here because that sits outside what this policy page can state. Retention follows the same account record you can already see; if an entry has not fallen off your account history, it is likely still part of what we hold. Any change to how we process your data gets reflected here first, with the current version replacing the old wording in place.
We use basic cookies to keep your mobile browser signed in between visits and to remember the lobby section you last opened, whether that was a live table or a slot room, so you are not re-entering details every session.
Security on your account depends on the login credentials you set and the verification prompts shown when you change a sensitive detail such as a contact method or linked Rocket or Bank Transfer reference, rather than a separate add-on service.
Your account history, wallet entries, session logs, past support threads, stays visible for as long as it remains part of your account record; once an entry drops from that record, we treat it as no longer retained.
When wording on this Privacy Policy changes, the updated version replaces the old text directly on this page rather than through a separate notice, so checking this page is how you confirm the current terms that apply to your account.
Here are the questions we hear most often when a returning account holder opens this page looking for a straight answer about data, cookies or a wallet entry tied to their na999 account.
No. na999 only shares the transaction data linked to your Rocket or Bank Transfer activity with the parties needed to process that payment or confirm your identity when asked. We do not pass your wallet history to outside advertising networks, and your account record stays tied to your own profile.
Open your account page and review the activity shown there, including session logs and payment entries tied to Rocket or Bank Transfer. If something you expect to see is missing or looks wrong, raise it through the support message route so we can check the record against your profile.
Yes. Most details, contact information, display preferences, can be updated directly through your account settings. For anything the settings page does not let you change yourself, send a support message describing the detail and we will look at the record tied to your account.
This policy covers what na999 itself does with your data. Once a Rocket deposit or Bank Transfer settlement leaves our systems and reaches the payment provider, that provider's own data handling terms apply, separate from the wording published on this page.
Use the support message option inside your na999 account, the same route you would use for a wallet or login question. Mention the date and the Rocket or Bank Transfer reference if the question relates to a transaction, so we can locate the exact record faster.
Yes, in part. Certain rights and disclosures depend on the local law and eligible region tied to your account, so the specific wording that applies to you can differ from a general reader in another region. The current published version here always reflects what applies at the time you read it.