Reference

What We Keep and Why

Your account runs on a mobile number, a password you set and the wallet you picked for payouts — that is the short list of what we hold, and this page spells out the rest.

Sign-in dataDevice and cookie recordsWallet reference numbersChange requests
acl365 What We Keep and Why
DATA HELP DESK

Reaching Us About Your Data

Write to our data desk and say what you need: a copy of what is on file, a correction, or a request to close the account. Include the wallet reference ID from the bKash, Nagad or Rocket message if your question is about a specific transfer — it is the quickest way for us to find the record. Before we discuss anything on file we send a one-time code to the mobile number registered to you, so keep that handset nearby. If you signed in from a new phone, say so.

Data desk email Send a message from the mobile number registered to your account and describe the record you want changed. Attach nothing sensitive — no PIN, no screenshot of your wallet balance.
In-account request Signed in already? Open your profile and raise the request there. We reply on the number you used at sign-in, so a new handset still gets the answer.
Wallet reference lookup For a missing bKash, Nagad or Rocket deposit, paste the transaction ID from the SMS. That one line lets our team match your wallet transfer to the credit on your account.
HOW WE HANDLE DATA

Cookies, Access and Retention

Cookies on this site do narrow work: they keep you signed in, remember the language and wallet you last used, and show us which pages stall on slower mobile connections. Nothing in that cookie set is sold on. Session records sit on our side and are tied to your account, not to an advertising profile. When you close the account we remove what we are free to remove, and hold the rest only as long as accounting and dispute rules require. Login codes expire, and a sign-in from an unfamiliar device needs the code again.

Data we hold

Your mobile number, the password hash, the payout wallet you saved and the transaction references from bKash, Nagad or Rocket transfers. That is the working set. Gameplay records are kept for dispute checks.

Cookies and device data

Sign-in cookies, language choice, and the handset or browser you last used. These keep you logged in between visits. We do not use them to build a profile for outside advertisers.

Account access codes

A one-time code goes to the registered number at every sign-in from an unrecognised device. Codes expire quickly, and we never ask you to read one out to anyone.

Retention and changes

Ask for a copy, a correction or deletion by mail or from your profile. We act after verifying the number on the account, and we explain in writing if a record has to stay.

Answers About Your Account Data

Most of the privacy questions we get are the same few, so the plain answers sit right below. If yours is not here — a phone you no longer use, or a wallet number you changed — message the data desk and we will take it from there. Nothing on your account is discussed with anyone who has not passed the code check.

Your mobile number, a password you set, the payout wallet number, and the transaction references your bKash, Nagad or Rocket deposits produce. We also log the device and browser you sign in from.

No. Your wallet PIN stays with your wallet operator. We never ask for it by chat, email or phone, and any request for it is not from us — close that message and tell the data desk.

Message the data desk from your registered number and ask. We confirm with a one-time code to that handset, then send the record to you in writing.

Yes. Ask from your profile or by mail and we close the login. Records tied to payments stay for the period accounting and dispute rules set, then go. We tell you which ones remain.

No. The cookies we set keep your session open on this site and remember your language and last wallet. They are not used to follow you across other websites or sold to ad networks.

A new device triggers a one-time code to your registered number. If a code arrives that you did not request, contact the data desk at once — we can end the session and check the device log.
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.