Reference

What This Privacy Policy Covers

Your account, your wallet and your payment history sit under one plain privacy policy, written to be read once rather than skimmed. Here is what we collect, why we keep it, and the exact steps you take to see, correct or close it.

What we collectPayment referencesCookie controlsYour request rights
www5555 What This Privacy Policy Covers
SECURITY BASICS

Cookies, Retention and Account Security

None of this stays in the abstract. A one-time code goes to your registered mobile at sign-in, session cookies hold that login while you move between lobby pages, and your account shows the devices that have used it. Ask for closure and the login ends immediately, while wallet references tied to bKash, Nagad or Rocket payments remain on file for the stretch that local record-keeping rules demand, then go.

Login codes and devices

A sign-in from an unknown phone asks for a one-time code sent to your registered number. Nobody reaches your wallet balance or payment history without it, so keep the SIM tied to your account.

Cookies we set

Session cookies keep you signed in and remember your language choice. Analytics cookies show which lobby pages stall on mobile data. Clear them from browser settings at any time; you will just sign in again.

How long records stay

Deposit and withdrawal references tied to bKash, Nagad or Rocket payments stay on file for the stretch local record-keeping rules require, then come off. Close your account and everything outside that scope is removed.

Correcting your details

You can fix your email or address yourself in the profile. Changing your name, mobile number or date of birth needs a support ticket and a wallet reference check, since those fields anchor your payment identity.

REACHING OUR DESK

Where to Ask About Your Data

Data requests go through the same desk that answers wallet questions, so you are not hunting a separate inbox. Write from the email address registered on your account, give the mobile number linked to your bKash, Nagad or Rocket wallet, and say what you want done — a copy of your records, a correction, or closure. Tickets stay open on the same thread until the answer reaches you, and we reply in English.

In-account support chat Sign in, open the help tab in your account menu and raise a ticket. Quote the wallet number you pay from through bKash or Nagad so we can find your file without a round of back-and-forth.
Email request Send it from your registered address with 'Privacy request' in the subject line and your account mobile number in the message. We confirm receipt on that thread and tell you what we still need.
Wallet reference check If the question is about a payment record, attach the bKash, Nagad or Rocket transaction ID. Matching that reference is the quickest route for us to pull the exact entry you are asking about.

Questions We Get About Your Data

Most privacy questions we get are short and practical: what is stored, who sees it, and how to get rid of it. The answers below cover the ones that come up most. If yours is not here, the support desk takes it from there, checks your account and comes back with the specifics that apply to you rather than a general line. We keep the wording plain on purpose.

Your name, date of birth, mobile number and email, plus the wallet number you pay from. After that we keep transaction references from bKash, Nagad or Rocket transfers and the basic device details your browser sends.

Yes. Send the request from your registered email with your account mobile number, and we pull the profile, wallet references and support history tied to you, then return it on the same thread.

Studios such as Pragmatic Play and Evolution see the game session, not your wallet number or email. Payment partners get the transaction reference needed to clear your bKash, Nagad or Rocket transfer. Nothing else goes out.

Ask through the in-account chat or from your registered email. We close the login, end account messaging, and keep only the payment records that local rules require us to hold.

Session cookies are what keep you signed in, so the lobby needs them. Analytics and language cookies are optional: clear them in your browser and you simply sign in again on the next visit.

The rules where you live decide what we can collect and which rights you can exercise. Access depends on your local law and eligible regions, and a stricter local rule takes precedence over anything written here.
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.