Reference

How We Handle Your Personal Data

Our privacy policy is short on purpose: it says what we collect, why we keep it, and how you can ask us to change it.

What we collectCookie controlsData requestsWallet records
na33 bat How We Handle Your Personal Data
ASK ABOUT YOUR DATA

Reaching na33 bat About Your Data

Every data question starts in the same place: the support channel inside your account. Open the help tab, choose the privacy option and your ticket carries your account ID, so nobody asks you to repeat the story twice. If you would rather write from outside the app, the same address works from any browser on your phone. Keep your wallet PIN out of the message — we never ask for it, and a request for it is not from us.

In-Account Support Ticket Open the help tab after you sign in and choose the privacy category. Your ticket carries your account ID and recent login history, so stored-data questions get answered without you repeating anything.
Privacy Request by Email Write to our privacy address from the mobile number on your account. We reply there, ask for one confirmation step, and log every request so you hold a dated record of when you asked.
Wallet Confirmation Desk If a bKash, Nagad or Rocket transfer looks wrong, send the transaction ID with your request. We check it against the wallet statement before changing any record tied to your account wallet.
DATA HANDLING RULES

Cookies, Logins and Record Removal

Three things decide how long a record lives: what it was collected for, what local financial rules require, and whether your account is still open. Cookies here split into the ones that keep you signed in and the ones that measure page load; the first group is required, the second you can switch off in your browser without losing access. Device logs match a new sign-in against your usual handset. When something looks off, we ask for one verification step before anything changes. Send a correction or deletion request and you get a written outcome either way.

Cookie Controls Session cookies keep you signed in between the app and your browser. Measurement cookies show which pages load slowly on mobile networks. Block the second group in browser settings and your account wallet still opens.
Login and Device Checks Each sign-in is matched against your usual handset and one-time code. A new device triggers an extra confirmation before any stored record is shown. That check is why we ask for a code again.
Retention by Record Type Transaction records stay while your account is open, and for the period local financial rules set afterwards. Login and device logs run for a shorter term. We delete or anonymise whatever is not needed after that.
Correcting or Removing Data Send a correction request through your support ticket and we check it against the wallet statement or your ID document. You get the outcome in writing, plus a copy of what changed.

Data Questions We Get Often

These are the four or five things people raise after their first week on the site, answered the way we answer them in a ticket. If your question is about a specific transfer, add the wallet reference so it can be traced in one pass rather than three.

Your name, mobile number, date of birth, the payment reference from your bKash, Nagad or Rocket transfer, plus login and device records. That set is what keeps an account wallet running and a sign-in checkable.

Yes. Raise a ticket under the privacy subject and we send a summary of the account record to the mobile number and address already on file, after one confirmation step.

Only to match or correct a transfer — the wallet operator sees the reference, and our fraud checks see it when a duplicate or a chargeback appears. We do not sell data.

Ask through the support ticket and we close the account once your balance is settled. Records tied to local financial rules are kept for their set period; everything else is deleted or anonymised.

Two kinds. Session cookies keep you signed in as you move between the app and your browser. Measurement cookies show page load on mobile networks and can be blocked in your browser settings.

Possibly. Rules differ across regions, so what we may hold and which services we can offer depends on local law and eligible regions. Where a stricter rule applies to you, that rule wins.
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.