Reference

See What Our Privacy Policy Covers

One page spells out what we collect, why each field exists, and how to get a copy or a correction without legal fog.

Plain-language policyCopy of your record on requestCookie control on your phoneWallet details never sold
x400 See What Our Privacy Policy Covers
ASK ABOUT YOUR DATA

Reach the Team About Your Data

You don't have to draft a formal letter to ask about your own record. Start in the help tab inside your account and your message lands with the team that also handles wallet checks for Dhaka and the rest of Bangladesh. Say what you need — a copy of your record, a correction, or the reason we hold a particular field. For anything touching money, add the transaction ID from bKash, Nagad or Rocket so the payment trail can be matched in one pass.

Team online

Account help desk

Open the help tab, quote the mobile number on the account, and the team will point you to the right form for a data request, a correction or an access question.

Wallet and payment queries

If a bKash, Nagad or Rocket transfer looks wrong on your statement, send the transaction ID through the same thread. We match it to your account record and explain what we keep.

Device and login checks

Signed in from a phone you don't recognise? Message us from the app before you change anything. A quick check of the session log usually settles it.

HOW WE GUARD IT

Explore How x400 Guards Account Data

Guarding a record is mostly unglamorous work: short sessions, a one-time code at every sign-in, and payment details confined to the rail that processes them. We would rather explain a rule than hide behind one. When a request can't be met straight away — asking us to delete a payment confirmation the week it cleared, for example — we say why in the same reply instead of leaving you with silence. Cookie data, device logs and account history get the same treatment: kept while there is a reason, removed when there isn't. Signing in still depends on local law and eligible regions.

Cookie control

Cookies keep your session alive when you move between the app and the browser. Clear them any time in your phone settings; you'll simply sign in again with the usual one-time code.

Code-based sign-in

Every sign-in asks for the code sent to your mobile. That code is the main lock on your record, so never forward it, even to someone who says they are calling from us.

Retention windows

Payment confirmations sit longer than browsing logs because a dispute can surface months later. Ask us to delete the rest and we'll tell you plainly what we are required to keep.

Changes and corrections

Spotted a wrong spelling or an old number on your record? Request the change through the help tab and we'll confirm once the saved version is updated on our side.

Ask Us Anything About Your Data

These are the questions that land in our help tab most often, answered the way we would answer them in a chat rather than in a contract. If yours isn't here, send it over and we'll reply with the specific answer for your account, not a link to the policy you just read.

Your name, mobile number and wallet reference, plus the login and payment records tied to those. We don't ask for extra documents unless a withdrawal check or a local rule requires them.

Yes. Message the help tab, quote the mobile number on the account, and we'll send your record in readable form so you can check each field against what you remember.

Only with the payment rail processing that transfer, and with authorities where the law in your region requires it. Your wallet number never leaves for advertising or list building.

They keep you signed in as you move between pages, so you aren't re-entering the code every time you switch tabs. Clear them in your phone settings and you just sign in again.

Confirmations stay longer than browsing logs, since a dispute can surface months after a transfer. Ask us to remove anything we aren't required to hold and we'll confirm what goes.

Send the request from the help tab while you can still sign in. We close the record, keep only what local law expects us to keep, and confirm by message once it's done.
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.