App / Casino
jua99 is where you manage your Bangladesh account, wallet links and lobby activity — this Privacy Policy explains how we handle the data behind that account-to-wallet path, and what applies to you depends on your local law and eligible region.
When you fund your jua99 account, we record which route you used — Nagad, Upay or Bank Transfer — only to match the deposit to your account and keep an accurate entry on your transaction page. We never see your wallet PIN or your banking login; that step stays between you and the payment provider, and we only receive the confirmation needed to update your balance. This Privacy Policy covers the account-to-wallet path wherever it touches jua99's own systems: your sign-in details, the deposit and withdrawal entries shown on your account, and any message sent through our published support routes. How strictly certain parts of this policy apply depends on the law of the region you are accessing jua99 from — rights like correction requests or how long a record is kept can be shaped by your local rules, not by us alone. We hold transaction references long enough to resolve a disputed entry on your statement, and we do not pass your payment details to a game studio or any outside party beyond what a single route needs to process. Your account history follows your login across devices, mobile browser or desktop, not the device itself. The scope and rights sections further down set out what this covers and what you can ask us to do.
This Privacy Policy draws a line around four areas of your time on jua99: signing in, moving money, browsing the lobby, and anything that happens through a service we don't run ourselves. Account access covers your login and device pattern. Transaction records cover what's logged against your Nagad, Upay or Bank Transfer route once a deposit or withdrawal clears. Site content covers the pages you look at before and after you're signed in — lobby categories, the cricket sportsbook section, slot listings — most of which aren't tied to your identity unless you're logged in. Third-party services cover the payment providers behind your chosen route and the game studios supplying lobby content, each running its own systems for the specific service it provides. Knowing which of these four areas a question falls into is the fastest way to find the right answer below, rather than assuming one clause covers everything at once.
Your login email, password hash and device sign-in pattern fall under this policy. We use this data only to confirm it's you opening the account, and to flag unusual sign-in attempts on your profile, not to build an advertising record of your activity elsewhere.
Deposit and withdrawal entries tied to Nagad, Upay or Bank Transfer sit in your account's transaction log. We keep the reference number and amount shown there so you can match it against your own wallet statement if an entry ever looks wrong.
Pages you browse — lobby categories, the cricket sportsbook section, slot listings — are not linked to your identity unless you are signed in. Browsing our public pages before opening an account does not create a personal data record tied to you.
Payment providers behind Nagad, Upay and Bank Transfer, and game studios like PG Soft, CQ9, Joker and JDB, run their own systems for the service they supply. This policy covers jua99's own data handling; it does not extend to how those separate services manage their own records.
You're not locked out of your own account data on jua99. If something on your profile looks off — a wrong contact number, an outdated email, a transaction entry you don't recognize — the account section is where you start, and our support routes are there if the fix needs a human. We don't ask you to prove a point before you can ask a question about your own data; raising it is the first step, not the last. How we respond depends on what you're asking and the law that applies to your region, so timelines aren't fixed the same way for every request. Below are the practical paths open to you: checking what's on file, fixing what's wrong, asking us directly, and getting a support reply logged against your account.
Open your account page to see the contact details, login email and linked payment references we hold for you. If a field looks outdated, that's the first sign to update it before your next deposit or withdrawal attempt.
Wrong phone number or an old email on file can slow down a withdrawal check. Update it directly from your account settings, or raise it through support if the field won't let you change it yourself.
If you want to know why we hold a particular entry, or how long a transaction reference stays on file, send that question through our support routes rather than guessing from the FAQ alone.
For anything that needs a direct answer — a record you want explained, an account detail you can't edit yourself — our support contact is the route to use, logged against your account for follow-up.
Questions about your own data usually fall into one of two speeds: something you can check and fix yourself from your account, or something that needs a written answer from us. For the first kind, your account settings are the quickest route — contact details, linked payment references and recent transaction entries are all visible there without anyone else getting involved. For the second kind, use one of the published routes below. Each one logs your question against your signed-in account, so whoever picks it up can see your transaction history and account details without you explaining your situation twice in two different places. Keep your account details current before you write in — a correct contact detail on file makes it easier for a reply to reach the right place. We don't operate unpublished contact channels.
Your account page is where your login credentials, contact details and transaction entries live. Check it first before raising a question with us — most record checks and small profile corrections are handled right there, without waiting on a support reply at all.
When a question about your data needs a direct answer — why an entry was recorded, how long we keep a reference tied to Nagad, Upay or Bank Transfer — send it through our published support contact form and we log it against your account.
If you're already signed in, the message centre inside your account keeps a written trail of anything you ask us about your data, so the conversation stays attached to your account instead of starting over each time you write in.
Handling your data on jua99 comes down to a few plain rules rather than a long technical promise. We collect what the account-to-wallet path needs, keep transaction references only as long as a dispute reasonably requires, and treat your password and device pattern as account security data rather than something to share outward. Cookies and session data on mobile or desktop exist to keep your lobby signed in as you move between pages — they aren't built into an outside advertising profile. None of this is static: if a payment route, a support channel or a retention practice changes, this page is where the current wording lives, not a separate announcement. Read the four points below for the specific pieces — handling, device data, security and retention — rather than one blanket statement covering all of them at once.
We collect only what the account-to-wallet path needs — your login, contact details, and the transaction entries linked to Nagad, Upay or Bank Transfer. We don't sell this to outside advertisers, and we don't share it with a game studio beyond what a single transaction route requires.
Browsing jua99 on mobile or desktop sets basic session data so your lobby stays signed in as you move between pages — slot listings, your account tab, support routes. This is navigation data on your own session, not a tracking profile built for outside advertising networks.
Your password and sign-in pattern are treated as account security data, not shared data — used only to confirm it's you logging in, and to flag a sign-in attempt that doesn't match your usual device, location pattern or login time.
We keep transaction references long enough to resolve a disputed entry on your account, and update this policy when our own routes change — Nagad, Upay or Bank Transfer handling included. Check this page for the current wording rather than relying on an old screenshot.
Here are the questions we get asked most about privacy on jua99 — what we see when you fund your account through Nagad, Upay or Bank Transfer, how long a transaction record stays visible, and who to contact if something on your profile needs fixing. Treat this list as a starting point rather than the full wording of the policy itself — the sections above go into more detail on scope, your account actions and how support handles a written question.
No. The payment provider behind Nagad, Upay or Bank Transfer handles your wallet PIN or banking login on its own side. jua99 only receives the confirmation needed to match your deposit against your account and update the entry shown on your transaction page.
We hold transaction references long enough to resolve a disputed entry on your account statement. Specific retention periods can depend on the law of the region you're accessing jua99 from, so they aren't the same length for every account.
Yes. Open your account settings and update the field directly where that option is available — email, phone number, linked contact details. If a field is locked, raise it through our support contact routes and we log the correction request against your account.
No, not directly. Those studios supply the game content you see in the lobby — slots, tables and similar titles — and this policy covers jua99's own account and wallet data, not how a separate studio runs its own systems.
Use the support contact form or the message centre inside your signed-in account. Both routes log your question against your account record, so we can match your request to the correct profile and transaction history without you repeating details.
Parts of it can. What you're able to ask for, how long certain records are kept and how a correction request is handled depend on the law of your region and whether you fall within the eligible areas we can serve.