Reference

What Our Privacy Policy Covers

Your account, your wallet, your call — this page spells out exactly what 999taka records when you register, why we keep it, and how you get it corrected or removed.

Account detailsWallet recordsCookie choicesAccess requests
999taka What Our Privacy Policy Covers
CARE AND RETENTION

How We Look After Your Records

Most account problems are dull rather than dramatic: a shared handset, a screenshot left in the gallery, a password carried over from an old email. Our side of that is encrypted connections, hashed passwords and a one-time code at each new sign-in. Yours is not reusing a password and not forwarding codes to anyone. The four points below mark where our duty ends and yours starts, and how to make us change something we hold.

Data handling

We collect what a working account needs: mobile number, password hash, nominated wallet and the transaction IDs behind your bKash, Nagad or Rocket deposits. Anything extra is optional and clearly marked as such.

Cookies

A session cookie holds you signed in, while a security cookie flags a login from a device we have not seen before. Clear them through your browser settings any time and you will just log in again.

Sign-in security

Passwords are stored hashed, and a one-time code goes to your registered number on each new sign-in. If a code arrives while you are not logging in, change the password and message us that day.

Retention and change requests

Payment records stay while a transaction could still be queried. Ask us to fix your details or close the account and we tell you plainly what can be deleted and what we must keep.

DATA HELP DESK

Reaching Us About Your Data

A privacy question deserves a real person on the other end, not a form that swallows itself. Sign in, open the menu inside your account area and tap Support — the chat window and the message thread land on the same desk that handles wallet verification, so nothing is passed around. Tell us the mobile number on the account and the specific ask: a copy of your records, a correction, or a sign-in you do not recognise. We answer on that same thread, which keeps the history in one place.

Team online

In-account chat

Sign in, open the menu in your account area and start a chat. Attach the mobile number on the account so we can locate your record without asking for it twice.

Support email

Write from the mailbox linked to your account and mark the subject line as a privacy request. That sends it straight to the team that deals with data questions.

Wallet verification desk

Anything involving a bKash, Nagad or Rocket transaction ID is handled by the desk that checks deposits, which is where most data queries about payments begin.

Questions We Hear About Privacy

Six privacy questions fill our support desk more than any others, so they are answered here instead of buried in a long document. If yours is not among them, the chat inside your account area is the quicker route — quote the mobile number on the account and we pull up the record while you wait.

A mobile number, a password and the wallet you want withdrawals sent to. We confirm the number with a one-time code before the account goes live, so nothing opens on a number you do not control.

Only to the payment provider handling your own transaction, and to authorities where the law requires it. We do not trade contact lists, and we do not sell account data to advertisers.

Message us from inside the account, or from the mailbox linked to it, and say plainly what you need. We confirm what we hold and correct anything that is wrong.

Your profile goes inactive and your login stops working. Transaction records tied to deposits and withdrawals stay for as long as local rules require, then they are removed.

You can clear or block cookies in your phone's browser settings, but the sign-in cookie is what keeps you logged in. Blocking everything means entering your code on every visit.

Change your password from the account area straight away, then contact support with the time and device you noticed. We check the session history and can lock the account while we look.
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.