App / Live
bf1111 explains how we handle the details tied to your account — your login, your wallet activity on bKash, Nagad or Rocket, and the device you use to sign in. This page covers what we collect, why, and how you can check or ask about it.
This policy sits alongside our terms and covers the account data we hold once you register with bf1111 — your profile details, login activity, and the record of transactions you make through bKash, Nagad, Rocket or Bank Transfer where these are configured on your account. Availability of any payment route and the scope of this policy both depend on your local law and the region you access us from, so what's shown on your account page is the version that applies to you. We keep this record to support your wallet verification, resolve support queries, and maintain the account history you see when you check your transaction log. Where a game session is logged — slots, live casino tables or sportsbook markets, including Cricket Betsport rounds — the record ties to your account, not to a separate identity you'd need to manage. We don't share this data for purposes unrelated to running your account; we also don't promise a specific retention window beyond what's needed to keep your account functional and your support history traceable. If you move between devices — mobile browser one day, desktop the next — the same account record follows you, since the policy reads to account, not to device. Review the current version from the account or legal footer before you raise a question, since wording can change without a running list being sent to you directly.
We built this policy around four areas of your account life: how you sign in, how you move money, what you see in the lobby, and the outside services we sometimes connect to. Account access covers your login credentials and the mobile or desktop session you open from. Transactions cover the wallet record tied to bKash, Nagad, Rocket or Bank Transfer when configured for your account — not the processing itself, just the record you can check. Site content covers what the policy does not reach into: the game titles you open, like Baccarat Golden or Crash Burst, are logged only as session activity, not personal profiling. Third-party services, where we route a wallet confirmation or a support ticket outward, sit under their own handling terms, and we link to those where relevant. Where any of this differs by region, your local law and eligible region decide which version applies to your account.
Covers your login session, password reset activity, and the device or browser you use to reach your account. We log timestamps and access points so you can check recent sign-ins, but this scope stops short of the content of any message you send to support.
Covers the record of wallet activity tied to bKash, Nagad, Rocket or Bank Transfer on your account, where configured. This is the balance and transfer history you review on your account page — not the technical steps a payment route follows once it leaves your wallet.
Covers session logs for games you open, including Cricket Betsport, Football Bet Zone and Teen Patti LuckySpin. These are recorded as activity tied to your account — how long you played, which table or slot room — not a personal profile built from your choices.
Covers outward links such as a wallet confirmation step or a support escalation you raise through a published channel. These steps sit under their own handling terms once they leave our account system, and we reference that boundary here rather than restate separate rules.
You're not locked out of what we hold on your account. If you want to check what's logged against your profile — recent sign-ins, wallet activity tied to bKash, Nagad or Rocket, or a past support thread — you can ask us to walk you through it. Correcting a detail, say a mobile number tied to your account wallet, starts from your account settings page, where the editable fields are shown directly. If something looks off in your transaction record, raise it through a published support route rather than guessing at a fix. We treat each request on its own account, not as a blanket process, and what's available to you depends on your local law and the region your account is registered under. Keep your login details current; that's the fastest way to avoid a support back-and-forth later.
Open your account settings to see the activity tied to your profile — login history, wallet records linked to bKash, Nagad or Rocket, and past support threads — before you raise any follow-up question with our team.
Update a mobile number, email address or any other profile field from your account settings page. The editable fields sit right there, clearly labelled, and a saved change applies to your account record immediately — no separate request needed for routine edits like this.
Send your question through a published support route rather than guessing at an answer on your own; we handle each account individually, so include your account reference when you write in to help us find your record faster.
If a wallet entry or a session log looks wrong on your side, ask support to check it directly against your account record — this response stays specific to your profile and does not trigger any account-wide change.
Questions about this policy don't need a separate form hunt — the same support entry you already use for account help covers privacy questions too. Open the support option visible from your account page and mention that your question concerns data or privacy handling; our team routes it from there rather than asking you to search for a different desk. We don't run a separate privacy-only channel, so if you're asking about a wallet record tied to bKash, Nagad or Rocket, a login history entry, or a session log from a game you played, start from the same place you'd go for any other account query. Keep your account reference ready when you write in — it speeds up how fast we locate the right record once a support agent is looking into it for you, especially if the question touches more than one part of your account.
Reach our support team through the option shown inside your account dashboard on mobile or desktop; mention privacy or data handling in your message so it gets routed to the right person without extra back-and-forth or repeated explanations from you.
Check the help or FAQ area linked from your account for existing answers on data handling before you write in to support — many policy questions are already covered there, which can save you a wait for a direct reply.
Send a written request through the same support channel if you'd rather keep a record of your question; include your account reference so the response can be matched to your profile directly and nothing gets lost between messages or handed to the wrong agent.
Your account record sits behind the same login you use every time you come back to bf1111, whether that's checking a wallet balance, opening Baccarat Golden, or following a Cricket Betsport market. We don't treat privacy as a separate system bolted onto the platform — access to your data follows the same account security you already rely on to sign in. Cookies and similar session tools on our site mostly keep you logged in and remember basic preferences like language; they're not used to build a profile we sell elsewhere. Retention follows what your account actually needs: transaction history tied to bKash, Nagad, Rocket or Bank Transfer stays linked to your profile for as long as the account is active and for any period your local law requires afterward. If you want a change made — a correction, a question about a specific record — that request goes through the same support route as any other account matter, not a separate legal desk.
Your account data sits behind the same login protection as your wallet balance and game activity — we don't run privacy as a separate system apart from the account you already sign into daily on mobile or desktop.
Cookies on our site mainly keep your session active while you move between slots and the sportsbook, and remember basic settings like language; they support the account you're using rather than building a separate profile for outside use.
We keep transaction and session records for as long as your account stays active, plus whatever additional period your local law in your region requires afterward — this isn't an open-ended archive sitting apart from your actual account activity or wallet history.
Ask for a correction or raise a question about a specific record through the same support route you'd use for any other account matter; we match the request to your profile directly before anyone gets back to you with a response.
Here are the account and data questions we hear most from people checking this policy before or after they register with bf1111. If your question isn't answered below, the support route in the section above is the fastest way to get a direct answer tied to your own account record.
We keep a record of the wallet route you choose — bKash, Nagad, Rocket or Bank Transfer — tied to your account so you can review your own transaction history. We don't store full payment credentials separately from what your account page already shows you.
Yes — open your account settings to see login activity, wallet records and past support threads linked to your profile. If something isn't visible there, raise it through support with your account reference and we'll walk you through what's on file.
We use account data to run your login, wallet record and support history — not to pass it along for unrelated purposes. Any outward connection, like a wallet confirmation step, sits under its own handling terms, which we reference rather than hide from you.
Open your account settings page, where fields like mobile number and email are editable directly. Once you save a change, it updates your account record immediately — no separate privacy form is needed for routine detail corrections like these.
No — the policy follows your account, not the device. Whether you sign in from a mobile browser or desktop, the same record and the same rights apply, though what's available can still depend on your local law and eligible region.
Use the support option visible inside your account and mention that your question is about data or privacy; it gets routed from there. Keep your account reference handy so the response can be matched to your profile without delay.