Reference

What We Collect From Your Account

Your bit111 account holds your name, mobile number and the wallet reference behind every deposit, and this page spells out what we do with it in plain English.

Plain-English policyWallet references onlyCookie choicesDeletion on request

Explore Lobby Read FAQ

REACH THE DESK

Where to Send a Data Request

Questions about your data land on the same desk that handles wallet problems. Open the chat panel inside your bit111 account, because it carries your account number and saves you explaining which one is yours. Email works too: mark the subject line as a data request so it reaches the right queue. Write in English and we answer in English, with a written confirmation once the change is done.

Team online

In-account chat

Open the chat panel while signed in and your account number travels with the message. Ask for a copy of your stored details, a spelling fix or a closure, and the desk sees your history.

Email route

Send from the email tied to your account and mark the subject line as a data request, so it reaches the right queue. Ownership gets checked before we reply, then we confirm in writing.

Code verification

Because sign-in runs on your mobile number, a one-time code confirms any data request. That step keeps someone else from reading or changing your bKash, Nagad and Rocket references.

HANDLING RULES

Open, Check or Close Your Data

Everything we hold sits behind one login: your mobile number. Change your password from account settings and every active session drops out. Players in Dhaka often share a handset or a browser, so that switch earns its keep, since the next person cannot pick up where you stopped. Cookies do quiet work: keeping the session alive, remembering your language, flagging odd logins. Clearing them is a browser setting away, and the only cost is signing in again with a fresh code. Close the account and we keep only what local rules require, then delete the rest.

Session control

Your sign-in pairs your mobile number with a one-time code. Changing the password ends every active session, so a handset you borrowed or a browser you left open cannot stay logged in.

Cookie behaviour

Session cookies keep you signed in; a small set remembers your language and screen size. Clear them from browser settings whenever you like, then you will just need a fresh code to get back in.

Retention window

Deposit and withdrawal references stay on file only as long as local rules ask, then they go. Keep your own record by saving the bKash, Nagad or Rocket confirmation message on your phone.

Request changes

Ask for a copy, a correction or a closure from the chat panel. We verify with a one-time code first, then confirm in writing what was removed and what we are obliged to keep.

Where Your Deposit Details Sit

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

We keep our data handling tied to one rule: collect what a working account needs, and nothing more. To run your bit111 account we store your mobile number, the name you gave us, the wallet or bank reference behind each deposit, and a log of session

1
times and the markets you opened, cricket included. When you deposit through bKash, Nagad, Rocket, Upay or a bank transfer, the provider returns a confirmation reference and we match it to your account so your balance moves. We never ask for your wallet PIN, and we
2
will never message you requesting it. Access and eligibility depend on your local law and the regions we can serve, so treat the wording below as applying where bit111 operates legally. If you are outside those regions, do not open an account. Where local rules require
3
it, we hold records for a set period after you close an account; where they do not, we delete what we no longer need. You can ask us to show what we hold, correct a misspelt name, or close the account outright. The same desk that
4
answers wallet questions answers these. Cookies keep you signed in and help us spot odd logins; clearing them in your browser is fine, you will simply sign in again with a fresh code.

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

Your Data Questions, Answered

These are the questions our desk fields most often about account data, answered the way we would answer them in chat. If yours is not here, send it through the panel and we will write back.

Your mobile number, your name, the wallet or bank reference behind each deposit, and your sign-in history. We do not store your bKash, Nagad or Rocket PIN, and we never ask for it.

Yes. Ask from the chat panel while signed in and we confirm ownership with a one-time code, then send what we hold. The scope of that request follows your local law and eligible regions.

Only what a transaction needs. When you deposit through bKash, Nagad, Rocket or Upay, we pass the reference and amount along so the transfer clears. Marketing lists are not part of that exchange.

As long as local rules require, and no longer. Once that window closes we delete the references. If you want your own record, save the wallet confirmation message from your phone.

Yes. Message the desk from inside your account and we close it after verifying with a code. Records that local law obliges us to hold stay on file; everything else goes.

Use the in-account chat or email with the subject marked as a data request. If you see a login you do not recognise, change your password at once, since that ends every active session.

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 Accountbit111 Login InfoBit111 Banking

What We Collect From Your Account

Where to Send a Data Request

In-account chat

Email route

Code verification

Open, Check or Close Your Data

Session control

Cookie behaviour

Retention window

Request changes

Your Data Questions, Answered

01 What data does bit111 hold about me?

02 Can I see a copy of my details?

03 Do you share my data with payment providers?

04 How long do you keep deposit records?

05 Can I close my account and have data removed?

06 Who do I contact if something looks wrong?

Privacy Policy

Related pages

Related pages