Reference

What Our Privacy Policy Covers

Your privacy policy fits on a few screens: it names exactly what we store, why a bKash, Nagad or Rocket deposit needs it, and how you get it removed.

One policy, plain EnglishWallet data stays with usCookie controls in-browserDeletion on request

Enter Lobby Read FAQ

The Policy Behind Your Wallet

hbajee34 Service availability depends on eligible regions and local law. Users should check local rules before opening an account.

Everything you touch in the lobby sits on top of this privacy policy — your mobile number, your login, and the wallet details you attach for bKash, Nagad or Rocket. We ask for what an account genuinely needs and nothing more: a number to sign you

1
in, a name that matches your wallet, and the transaction reference our team checks when money moves in or out. What we do with it comes down to three jobs. We confirm a deposit came from a wallet in your own name, so a withdrawal can
2
return to the same place. We keep a record of your login and device so a strange session on a new handset gets flagged instead of ignored. And we read basic usage data — where the app drops you out, which pages crawl on mobile data
3
— to fix the flow on the next release. Bet records work the same way. A cricket bet on a BPL match, a Roulette Action round or a Teen Patti Blitz hand leaves a line in your history, and that line is held for as long
4
as the payment and gaming rules require it to stay. Law in Bangladesh sets the floor, and we work to it. We don't sell your details and we don't pass them to advertisers. Where a payment provider or a lawful request needs a specific record, we
5
share that record and not the rest. Whether you can hold an account at all depends on your local law and eligible regions, and so does the scope of what we may store — if you move, tell support and we'll confirm what applies.

Service availability depends on eligible regions and local law. Users should check local rules before opening an account.

HOW WE HANDLE IT

Data Handling, Cookies and Access

Three things sit under this policy: what we store, what sits on your device, and how you get it changed. Sign-in runs on a one-time code to your mobile number, so a new handset has to prove it's yours before the lobby opens — and that code is what we point to when you ask who entered your account. Cookies stay light: one keeps you logged in, one remembers your language. Payment records stay on file as long as a bKash, Nagad or Rocket transaction requires it; the rest you can ask us to correct or delete.

What we collect

A mobile number, your name, the wallet number you pay from, and a log of logins and device changes. We don't ask for documents unless a withdrawal or a legal check needs them.

Cookies on your phone

Two do most of the work — a session cookie that keeps you signed in and a preference cookie for language. Clear them from your browser settings and you'll simply sign in again.

Account security

Sign-in uses a one-time code to your mobile number, and a new device asks for it again. That's why we tell you never to forward the code, including to someone claiming to be support.

Records and change requests

Payment records stay while a bKash, Nagad or Rocket entry has to remain on file. Ask for a correction, a copy or a deletion from your registered number and we confirm in writing.

REACHING US

Ask Us About Your Data

Privacy questions tend to be narrow, so skip the long form and use a channel where a person answers. Every request lands as a ticket with your account number attached, which means we can see the same records you're asking about. Put your ask in the first line — delete my account, fix the name on my bKash record, tell me what you hold — and it goes to the desk that handles it rather than getting passed around.

Privacy Questions We Get Often

These are the asks that come up most from account holders, answered the way we'd answer them on chat. If yours isn't here, send it from your registered number and it gets picked up by the same desk.

Your account details, the wallet number you deposit from, login and device records, and the cookie settings on your browser. It covers the hbajee34 lobby and our support channels, not sites we link out to.

Only where a payment provider, a bank or a lawful request needs a specific record. We don't sell your data, and we don't hand your number to advertisers or notification brokers.

Yes. Write from the mobile number or email registered on your account and ask for a copy. We reply in writing with what we hold and explain anything that has to stay on file.

Send a deletion request from your registered number. We close the account and clear what isn't tied to a payment record; wallet transaction history stays while it has to remain on file.

It can. Data rules follow the law where you are, and account availability depends on your local law and eligible regions. Tell support your new location and we'll confirm what applies.

Login and device records stay for as long as we need them to catch a suspicious session on your account. After that they're removed, and you can ask what's still held at any time.

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.

InfoLegal InfoHbajee34 Banking Apphbajee34 App

What Our Privacy Policy Covers

Data Handling, Cookies and Access

What we collect

Cookies on your phone

Account security

Records and change requests

Ask Us About Your Data

Privacy Questions We Get Often

01 What does your privacy policy actually cover?

02 Do you share my details with anyone?

03 Can I ask for a copy of what you hold?

04 How do I get my account data deleted?

05 Does the policy change if I move country?

06 How long do you keep my login records?

Privacy Policy

Related pages

Related pages