Reference

Privacy Policy for Your ck444r Account

Your account runs on a phone number and the wallet you pay with, so this page spells out what we store, why we keep it, and how to ask for a change.

Account data, spelled outCookie controls you setWallet records explainedHow to request a change
ck444r Privacy Policy for Your ck444r Account
DATA REQUESTS

Where to Send a Data Request

Every privacy question has a route to a person. Start in the app: open your profile, choose the data and privacy label, and the chat carries your account reference automatically. From a browser, sign in first — we will not discuss account data on an unverified session. Email works when you want a written trail you can keep. Say what you want changed, not just that something feels wrong; a clear request gets a clear answer faster, whether you are in Dhaka or Chattogram.

In-app data and privacy chat Open your profile, tap support, and choose the data and privacy label. Your account reference travels with the chat, so you never retype the bKash or Nagad number you signed up with.
Email with a written trail Prefer email? Send the request from the address registered on your account so we can match it. If the question is about a wallet record, add the date and the transaction ID.
Wallet record questions Asking about a Rocket or Upay transfer? Have the transaction ID ready before you write in. Our desk can find the entry from that ID, so you never need to share a PIN or wallet balance.
HOW WE STORE IT

How Your Records Are Held and Changed

Cookies are the small part most people ask about first. We use two kinds: the essential ones that keep you signed in and remember your language, and optional measurement cookies you can switch off without losing access to the lobby. Session data is encrypted on our side, and signing out on a shared phone clears it. Ask for a copy of what we hold, or for a correction, through the support desk and we confirm what we did in writing.

What cookies do here The essential ones keep you signed in and remember your language. The optional measurement ones we leave to you, and switching them off in your browser settings does not block the lobby or your account wallet.
Sign-in checks Every sign-in asks for your password and a one-time code sent to the number on file. That code expires quickly, and we log the device so an unfamiliar login stands out to you.
How long records stay Wallet transfer records stay while your account is open, then for the period local rules require. Session logs live for less time. Ask us and we will name the period that applies to your request.
Copy, correction or closure Write to the support desk and say which you want. We confirm receipt, then reply in writing once the change is done. Closure removes your profile and wallet history, minus anything we must keep.

Privacy Questions We Answer Most

The same few questions come up again and again at the support desk. They cover what we hold, who sees your wallet number, how to get a copy, and what happens when you close the account. Read the answers below before you write in — most requests move faster when you name the exact field or transaction. If your question is not here, the chat in your profile is the shortest route to a person who can answer it properly.

The mobile number you verify, the name on your account, your sign-in history, and a record of each bKash, Nagad, Rocket, Upay or bank transfer you make so your balance matches the payment screen.

No. Your bKash, Nagad or Rocket number sits with the payment path that processes the transfer, and our support desk reads it only when you raise a question about a deposit or a withdrawal.

Yes. Ask through the in-app support chat or by email from your registered address. We confirm the request, then send a written summary covering your profile, wallet history and sign-in log.

Send a closure request from your registered email. We remove your profile, saved wallet details and session data, then tell you in writing what local record-keeping rules require us to keep.

It covers the account behind them. Your cricket bets on BPL and international fixtures sit in your betting history, tied to the same profile, so a data request reaches them as well as your wallet entries.

The support desk handles corrections. Say which field is wrong and what it should read, and attach the transaction ID if a wallet entry is involved. You get a reply in writing once it is fixed.
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.