Reference

Your Data and Our Privacy Policy

One page, one job: tell you what we keep when you use ace555, and what you can do about it. Your mobile number, your wallet reference for bKash, Nagad or Rocket, your device model and your login history make up the core record, and…

bKash, Nagad, RocketCookie choicesAccount data accessMobile-first pagesBangladesh support
ace555 Your Data and Our Privacy Policy
DATA PRACTICE

How We Handle Your Data

Three habits sit behind how we handle your record. Passwords and one-time codes are stored so our own staff cannot read them back, and a new device login always asks for a fresh code before the session opens. Cookies stay limited to session, language and our own page counts. We also log who on our side opens an account record and when, so any request you make can be traced to a named handler.

Cookie control

Session and language cookies keep you signed in, while page-count cookies show us where the mobile lobby stalls. Clear them any time in browser settings, then expect a new login code.

Account security

A one-time code goes to your registered number on every new device. If you never asked for that code, change your password from account settings and tell support the same day.

Record retention

We hold account and wallet records while your account stays open, plus the stretch local rules require. Ask us to remove what is not needed and we say plainly what stays.

Changes and corrections

Wrong number, unused device, old wallet reference? Request the correction through chat or email, and we update it, then confirm the change back to you in writing.

POLICY CONTACT

Reaching Our Privacy Desk

Privacy questions should reach a person, not a form that vanishes. Open the chat from your account menu and quote the mobile number on the account, so we can pull your record without asking you to send the same documents twice. Written requests work too. Keep the account number in the subject line and tell us the exact field you want changed, and the reply comes back tied to that same reference.

In-app privacy chat Open your account, tap the help icon, then pick the privacy tag. Tell us the mobile number on the account and the exact field you want changed or removed.
Email for data requests Write to our privacy mailbox with your account number, a short description of the request, and the wallet you use, bKash, Nagad or Rocket, so the record matches on our side.
Wallet verification desk If a wallet check is holding your request back, this desk clears it. Send the transaction reference from your bKash, Nagad or Rocket app and we match it before replying.

Questions About Your Privacy

These are the privacy questions that land in our chat inbox most often, answered the way we would answer them there. If yours is not on the list, send it across with your account number and we will write back with a specific reply rather than a link to this page.

Your mobile number, login history, device and browser type, wallet references from bKash, Nagad or Rocket, and the games or cricket markets you open. That is the core record, and nothing sits outside it.

Yes. Ask through the in-app chat or our privacy mailbox and we send a copy of the account data we hold, once we confirm the number on the account belongs to you.

Only the reference needed to clear or reverse a transfer. When you pay through bKash, Nagad or Rocket, the operator sees the transaction and we receive the confirmation code it returns.

Send a correction or deletion request from the account itself. We update what can be updated, explain anything local rules require us to keep, and confirm the outcome in writing.

No. Our cookies hold your session and language setting and count page loads on our own pages. They do not track you elsewhere, and you can clear them from your browser freely.

Reply in the same chat thread with your account number and we move it to the person already handling your case. Written requests keep their reference number until closed.
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.