Reference

What Our Privacy Policy Covers

A mobile number, your name and the wallet you pay from — that is all we need to open your account, and this page sets out exactly what happens to each detail after that.

Number and namePayment recordsCookiesCopy requestsDeletion requests
f111bet What Our Privacy Policy Covers
DATA HELP DESK

Where to Send a Data Request

Questions about your data go to one place, and we answer them in writing so you have something to keep. Write to our data team through the contact form in your account and tell us the mobile number on the account — that is how we find your record. If the request is about a specific bKash or Nagad deposit, add the wallet reference number and the date. You can raise the same thing in the support chat, but the written route is the one we track for requests to copy, correct or delete your details.

Written data request Send your request from the account contact form with the mobile number you registered. We reply in writing, so you keep a dated record of what was asked and what we changed.
Live chat routing Chat works for quick checks on how a payment shows on your wallet. If the question needs a record — a copy, a correction, a deletion — raise it there and we move it to the written queue.
Wallet reference checks Paste the bKash, Nagad or Rocket reference from your app when you write in. It lets us pull the exact deposit record instead of asking you for the same details twice.
HANDLING AND RETENTION

How Your Account Data Is Handled

Data handling here is deliberately plain. Your account record is read by the people who verify payments and the people who answer your messages, and by nobody else. Staff logins are checked rather than shared around the team. Cookies do two jobs: they hold your session so you are not signing in every few minutes, and they record your device and connection type so we can trace a page that stalls on a slow line. Payment details from bKash, Nagad, Rocket or Upay stay for the period our accounting and dispute rules require, then they are dropped.

What we hold

Name, mobile number, date of birth and the wallet you pay from. We also keep game history — a Football Quickstrike bet, a Roulette Spinnacle round — plus each deposit, so we can check a payment query.

Cookies and device data

A session cookie keeps you signed in. A device cookie records your browser, screen size and rough connection type, which is how we spot a page that loads badly on a mid-range Android.

Account security

A one-time code goes to your registered mobile at sign-in. We never ask for your bKash, Nagad or Rocket PIN in chat, on a call or by message, and no genuine message from us will.

Retention and deletion

Deposit and withdrawal records stay for the period our tax and dispute rules need them. Everything else — game history, device records, chat logs — you can ask us to remove, and we tell you what was deleted.

Privacy Questions From Bangladesh Accounts

These are the questions our inbox gets most often about data and this policy. Each answer is short, and if yours is not here, the written request route above reaches the same team.

A mobile number, your name, your date of birth and the wallet number you will pay from. Nothing else is needed to start, and you can see the full record by asking us for it.

No. We store the wallet number and the reference of each payment. Your PIN stays inside your own wallet app, and nobody from f111bet will ever ask you for it.

Yes. Send the request from your account contact form or through chat. We confirm in writing and send the copy to the mobile number on the account once we verify it is you.

Write in and say which details you want removed. We delete what our accounting and dispute rules no longer need, then reply with a list of what stayed and the reason it stayed.

When a rule or a payment process changes, we update this page and show a notice on your account at your next sign-in. The date stamped here tells you which version you are reading.

The team that verifies payments, the team that answers your messages, and the engineers who keep the site running when something breaks. Access is limited to what each role actually needs.
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.