Reference

What We Keep and Why

Your tabajee account runs on a mobile number, a password and the wallet you cash in with — bKash, Nagad or Rocket — and this page sets out exactly how those details are stored.

Mobile wallet referencesCookie choicesAccess requestsDevice and OTP logs
tabajee What We Keep and Why
TALK TO US

Reaching the Privacy Desk

Questions about your data go to one desk, not four. Open the Help tab inside your account and pick the privacy topic; the ticket records a reference you can quote if you follow up later. If you cannot sign in, use the contact form on this site and give the mobile number tied to the account. Either path reaches the same team that handles wallet verification, so they can already see your last bKash, Nagad or Rocket cash-in without you explaining it twice.

Team online

Help tab inside your account

Sign in, open Help and choose the privacy option. The ticket carries your account reference, so you never repeat a wallet number or the date of your last Nagad cash-in.

Contact form on this site

Use this when you cannot sign in. Give the mobile number on the account and the date you last logged in, and the team can locate you without a password.

Correction and closure requests

Ask for a copy of your details, a correction, or full account closure. We confirm from the registered number before anything is changed, removed or handed over.

SECURITY AND RETENTION

How We Handle Your Data

Most privacy trouble starts with account access, so we keep the unglamorous parts working. Your password is stored hashed, a handset we have not seen asks for an OTP sent to your registered number, and session cookies expire so a shared phone does not stay signed in. Cookie use stays narrow: session, language, fraud checks. Retention follows your account rather than a separate clock — transaction records stay while the account is open, and for the period the applicable rule requires afterwards, then they clear. Anything you want changed, you ask through the Help tab.

Password and OTP handling Passwords are stored hashed, never in plain text, and a login from a handset we have not seen triggers an OTP to your registered number before the session opens.
Cookie use stays narrow We set cookies for session handling, your language choice and fraud checks. Clearing them in your browser signs you out of the account; nothing else changes.
How long records stay Transaction records sit alongside your account while it is open, and for the period the applicable rule requires after closure. Then we clear them from the live system.
Change requests and replies Ask for a copy, a correction or closure from the Help tab. We verify from the registered mobile number first, then tell you what changed and when.

Privacy Questions We Get

These are the questions that come up most often at our support desk, answered the way we would answer them in chat. If yours is about a specific transfer rather than the policy itself, keep your transaction ID ready — it saves a round of messages.

Your mobile number, a hashed password, the wallet you cash in with, and session logs such as handset model, browser and IP address. That is the working set behind your account.

Yes. Request a copy from the Help tab and we send what we hold in a readable file, after confirming the request from your registered mobile number.

Only when a transfer needs tracing, and only the reference needed for that check. For a bKash, Nagad or Rocket cash-in that means the transaction ID and the amount.

We stop using it for anything beyond record keeping, hold the transaction history for the period the applicable rule requires, then clear it from the live system.

Login and session cookies are, because they keep you signed in. Language and fraud-check cookies help but your browser settings can clear them, and you will simply sign in again.

It can. What we may lawfully hold, and how long we keep it, depends on your local law and eligible regions. Where rules differ, the stricter one applies to your account.
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.