Reference

Privacy Policy for Your Account

This policy spells out what we record when you hold a joya70 account — your mobile number, the bKash, Nagad or Rocket wallet behind your transfers, the device you sign in from and the lobby panels you open — and who is allowed to…

Plain-English policy wordingWallet data kept minimalCookie control on your phoneRequests handled by our data desk
joya70 Privacy Policy for Your Account
YOUR DATA CONTROLS

Cookies, Logins and Kept Records

Privacy is mostly housekeeping. Your account is tied to an OTP sent to the mobile number you registered, so a new device has to prove itself before it reaches your wallet. Cookies split into two groups: the ones that keep you signed in, and the ones that show us which lobby panels you skip. You can clear the second group from your phone browser settings. Deposit, withdrawal and login records stay on file because payment partners and local rules require them, and we drop what we no longer need. To correct or remove anything, write from your registered number.

Cookies you can switch off

Sign-in cookies keep your session alive; the rest measure which lobby panels get used. Clear that second group in your phone browser settings — the site still loads, you just lose the tuned panels.

Login checks on new devices

A fresh device needs the OTP sent to your registered mobile number before your wallet appears. That single step is the main reason a stolen password alone cannot reach your balance.

Records we must keep

Deposit, withdrawal and login logs stay with us for as long as payment partners and local rules require. Once that window closes we remove them rather than holding archives we have no use for.

Asking for a change

Write from your registered number or email and say what is wrong. Name or wallet corrections are handled after a quick check; deletion follows once any legal holding period has ended.

POLICY CONTACT DESK

Reaching Our Data Desk

Pick the route that fits your question. Anything about your data, cookie choices or a deletion request goes to the data desk; a bKash, Nagad or Rocket deposit that has not landed goes to wallet support. Both reach people who can open your account and act, not a script reader. Keep your registered mobile number to hand — it is how we confirm we are talking to the account holder before we touch anything on file.

Chat inside your account Open the chat window from a signed-in session and ask for the data desk. Because your login is live, we can see which account you mean and skip the identity back-and-forth.
Email for policy requests Send deletion, correction or cookie questions from the email tied to your account. Put privacy in the subject line and include your registered mobile number so it reaches the right file.
Wallet verification line Use this route when a bKash, Nagad or Rocket transfer is stuck. It covers payment records rather than profile changes, so your request lands with the team that can trace the transaction.

Questions About Your Account Data

These are the questions our support desk hears most about this policy — what we hold, who sees it and how to get it changed. If yours is not covered, send it through the chat window inside your account and we will reply to your registered mobile number. Nothing written on this page overrides the law where you live.

Your name, mobile number, date of birth, the wallet number behind your bKash, Nagad or Rocket transfers, device and login records, and which cricket markets or tables you open. That is what running and protecting an account takes.

Only with the payment handling that moves your money, and with a regulator or court when one legally asks. We do not sell your details or hand them to outside marketing lists.

Ask from your registered number through the in-account chat or the data desk email. We match the request to your login, then send back what we hold and fix anything that is wrong.

You can ask us to close it at any time. Profile data goes once any holding period required by payment partners or local rules ends; deposit and withdrawal records stay until that point.

Because access depends on your local law and eligible regions. Retention periods, verification steps and whether we can serve you at all change with jurisdiction, and the local rule takes precedence over this page.

You stay signed in for that session, but panels tuned to your play history no longer appear and some checks may ask you to log in again. The lobby itself still loads fine.
Reference

Privacy Policy

Service availability depends on eligible regions and local law. Users should check local rules before opening an account.

Access may be available only where local law permits.