Reference

What Our Privacy Policy Actually Covers

Your abc365 account runs on a mobile number, a wallet balance and a short trail of payment records, and this page states plainly what we keep, why we keep it and who can see it.

What we storeCookie controlsRequest rightsWallet records
abc365 What Our Privacy Policy Actually Covers
REACH THE DESK

Where to Send a Privacy Request

Privacy requests do not need a special form. Open live chat from your logged-in account and tell the agent you want your data looked at; the chat thread is tied to your account, so nothing has to be proved twice. If you would rather write it out, email us from the address on your profile and we reply on that same thread. Keep the message to one ask — a correction, a copy of your records, or a closure — so the reply comes back from the desk that can act on it.

Live chat Signed-in chat is the shortest route: your session already identifies the account, so the agent can open your record while you talk and confirm what changed before the chat closes.
Email request Write from the address on your profile so we can match it to the account. State the one thing you want done and we reply on that thread, keeping the exchange in one place.
Wallet verification desk Questions about the bKash, Nagad or Rocket records attached to your account go to the same team that checks wallet payments, so they can read the transaction line with you instead of guessing.
DATA WE KEEP

Cookies, Logins and Kept Records

Three things sit behind this policy: the session cookie that keeps you logged in, the login checks that protect your wallet, and the retention clock on old transaction lines. Each one has a plain answer in the cards below, written the way we would explain it at the counter. Nothing hides behind a second document either — when a change alters how your account behaves, we flag it in your account notices before it takes effect, not after.

Cookies that matter The cookie that keeps your session alive is the one you would notice missing. Analytics cookies run separately and you can block them in your browser without losing access to the lobby.
Login and device checks A one-time code sent to your registered number confirms each new device. Fail that check and the session stops, which is why a stolen password alone will not open your wallet.
How long records stay Transaction lines for bKash, Nagad and Rocket payments stay on file for the period payment rules require, then drop off. Closing your account does not erase lines we are still required to keep.
Changing what we hold Ask for a copy of your account data, a correction to a misspelled name, or a closure request through chat or email. We confirm in writing once the change is done.

Privacy Questions We Get Asked

You send these in every week, and the answers below are the ones we give at the desk. Read them before you write to support — most requests are settled right here.

Your mobile number, the name on the account, wallet and bank transaction lines, and the device data that supports login checks. That is the working set support reads from when you write in.

No. We share it only with the payment and platform providers needed to run your account, or when a lawful request from an authority requires it, and we keep that sharing to the minimum.

You can block analytics and marketing cookies in your browser settings. The session cookie has to stay on, or the lobby will not recognise you between pages.

Open chat while signed in, or email from the address on your profile, and say you want a copy of your account data. We reply on the same thread once the record is pulled.

Not everything. Records tied to bKash, Nagad or Rocket payments stay for the period payment rules set, then come off. The rest of your profile is removed once the closure is processed.

Support handles it, not a separate department. Send the correction with the exact spelling or number you want on file and the team checking wallet verification can amend it.
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.