Slots / Sports
This page sets out what fbl77 collects when you open an account, move money through bKash or Bank Transfer, and browse the lobby on your phone. Access and eligibility depend on your local law and eligible regions, and the routes below show how to raise a question with us.
Privacy touches you at two points you actually feel: opening an account and moving money. When you register, we ask for what we need to create the account and keep it reachable — your name, a contact number, a password you control, and the wallet or bank reference you use for bKash or Bank Transfer. We do not collect details we cannot explain to you, and we do not hand your contact details to another company for marketing. Most of what we hold arrives from ordinary use. Session records show the device and browser you signed in from, which is how we notice a login that does not match yours. Lobby activity shows which rooms and titles load for you, so we can keep pages working on mobile data. Support conversations stay on file so a follow-up question does not start from scratch. Cookies do the smaller jobs: holding a sign-in session, remembering your language, and measuring which lobby pages are slow to open on a phone. How long we keep any of this depends on where you are. Personal data rules differ between jurisdictions, and some regions limit how wallet activity records may be stored or shared. We apply the rules that cover your location rather than one blanket setting for every user, and where a local rule conflicts with something written here, the local rule takes priority. Read this page whenever you like, signed in or not. If something here reads differently from what you were told at registration, send us a note through the support route and we will correct the record.
This policy covers the fbl77 website and the account you hold on it: the details you give at registration, the wallet activity tied to your account, the lobby pages you open, and the messages you send to support. Mobile and desktop both fall inside it, whether you arrive through a browser or a saved link. It does not cover what happens off our pages. When you approve a bKash or Bank Transfer inside a wallet app, or follow a link to a page run by another company, their own terms control that data. Game content is supplied by studios such as Pragmatic Play, Habanero and PG Soft, and anything their own tools collect is handled under their terms, not ours. One boundary worth knowing before you register: whether you may hold an account depends on the law where you live and on eligible regions, so check that first. If your location is not covered, we cannot open the account for you.
This covers the profile you sign in with — your name, contact number, password and the sessions started on your phone or desktop. Corrections you request here change the account itself, not just one page, so the update follows you across every device you use.
Deposits and withdrawals through bKash or Bank Transfer, plus the references shown against each entry in your account wallet. We keep these records so you can match a transfer to the lobby activity it paid for, and so a disputed entry can be traced back to its source.
What you open while signed in — game pages, studio titles, sportsbook categories and the lobby panels you scroll on mobile data. This is usage-level data that tells us which pages load slowly and which rooms you return to, and it stays tied to your account.
Links out to wallet apps, studio pages and anything we do not run ourselves. Once you leave our pages, the company behind that service decides what it stores and for how long, and their own policy — not this one — governs the request. Ask them directly about your data.
You are not stuck with whatever we hold. Sign in and open your account profile to see the details we store against your name, including your contact number and the wallet reference used for bKash or Bank Transfer. If a detail is wrong, correct it there rather than repeating it to support, because a fix in the profile is what updates the record everywhere else. Want to know what sits behind a ledger entry? Open the transaction list and match the reference you can see to the movement you made. If you want a copy of what we hold, or you want something removed where the law allows it, send the request through a published support route and tell us which account it concerns. We answer in writing so you keep a record of the reply. Where a local rule gives you a stronger right than this page describes, that rule wins.
Sign in and open your account profile to read what we hold against your name — contact number, wallet reference and the last sessions on your device. This is the same record our support team sees, so what you read there is what they work from.
Move to your transaction list and line up each bKash or Bank Transfer against the entry it created. The reference printed on the movement is what ties a deposit or withdrawal to your account, and it is the quickest way to settle a question about a payment you do not recognise.
If you want a copy of your account data, or you want it removed where local law allows, send the request in writing through a published support route. Name the account clearly so we can match it, and keep our reply for your own records.
Spotted a wrong spelling or an old number in the profile? Change it yourself in the account first. If a field will not accept the correction, raise it with support and explain what the correct value should be, so we can fix the record.
Questions about your data reach us fastest through the route published on the site. Send the message from the account you are asking about — a request that names the account and the detail in question is easier for us to trace than a general note from an address we cannot match. Tell us what you want to happen: read, correct, copy or remove. A short description of when the issue started helps too, especially for a wallet entry tied to bKash or Bank Transfer, because we can pull the matching record and check the reference with you. Write in English and we will reply in English; keep the thread on the published channel so both sides hold the same conversation. If you contact us about someone else's account, we will not discuss it with you, and if you are unsure whether your location is covered, ask that question first — eligibility depends on your local law and eligible regions.
Write to the contact address listed on our site, from the account you are asking about. Include the reference for any bKash or Bank Transfer in question, and state plainly what you want done with the data so we can route it to the team that handles it.
The help form inside your signed-in account travels with your profile, so we can see the details you are referring to without asking you to repeat them. Use it for corrections, copies and removal requests attached to a specific account.
Before you write, the help pages you reach after signing in set out the common points on account details, device sessions and wallet records. Many answers sit there already, and reading them first usually saves a round trip with support.
Data handling at fbl77 runs on a simple rule: hold what the account needs, and hold it no longer than the rules for your region allow. In practice that means account details sit behind your sign-in, sessions expire so a borrowed phone does not leave you open, and wallet references stay attached to the transaction that created them. Cookies do a narrow job — keeping you signed in, remembering your language, and showing us which pages stall on mobile data. We do not sell your details, and we do not pass your contact number to another company for marketing. Retention follows local law rather than a single fixed period, which is why we say a record's life depends on where you are and what the rule there requires. When something changes in this policy, the updated wording appears on this page, and the version you read here is the one we work to. Bring us a question at any point and we will answer it against your own account, not a general script.
Your sign-in guards the account record. Sessions end on their own so a shared or lost phone does not stay open indefinitely, and a login from a device we do not recognise is the kind of pattern we watch for. Keep your password to yourself and tell us if you think someone else has it.
Cookies on this site keep you signed in, remember your language and measure how lobby pages load on mobile data. They are not there to pass your details to other companies. You can clear or block them in your browser, though signing in may then need extra steps each time.
Retention runs on local law, so the life of a record depends on the rules that cover your location rather than one fixed period for everyone. Wallet records tied to bKash or Bank Transfer are kept while they are still needed for account reconciliation.
Want a correction, a copy or a removal where the law allows it? Raise it through a published support route and name the account. We reply in writing, so you hold a record of what was decided and when. If we cannot act, we say why.
Most privacy questions from Bangladesh players come down to four things: what we hold, why we hold it, who sees it and how to get it changed. The answers below stick to those. They cover the details you hand over at registration, the wallet records behind your bKash or Bank Transfer entries, device sessions on your phone, cookies that keep you signed in, and the routes for asking us to correct, copy or remove something. Nothing here replaces the policy above — if the two differ, the policy text is what we work to. Eligibility matters as well: whether you may hold an account at all depends on the law where you live and on eligible regions, so read that part before you register. If your question is about a specific entry on your account, send it through a published support route and name the account, and we will answer against your own record.
Your name, a contact number and a password you control, plus the wallet or bank reference used for bKash or Bank Transfer. We ask for what the account needs to work and stay reachable, and we explain each field rather than collecting details we cannot account for.
Yes. Sign in and open your account profile to read the details stored against your name, including your contact number and recent device sessions. Your transaction list shows wallet activity, and a written request through a published support route gets you a copy where local law allows it.
We do not sell your details or pass your contact number to another company for marketing. Wallet records stay tied to your account. When you leave our pages for a wallet app or another company's service, that company's own terms cover what happens next.
Change simple details yourself in the account profile first. For anything you cannot edit, write through a published support route, name the account and say what should change. Removal applies where local law gives you that right, and we reply in writing either way.
Cookies keep your sign-in active, remember your language and measure how lobby pages load on mobile data. They are not used to pass your details to other companies. You can block or clear them in your browser, though you may then sign in more often.
It depends on your local law and eligible regions. Personal data rules differ between jurisdictions, and some places restrict how wallet activity is stored or shared. We apply the rules that cover your location, and where a local rule is stronger than this page, that rule takes priority.