Sports / App
This page sets out how fv888 collects, uses and stores the details you give us when you open an account, sign in from your phone and move money through Rocket or Upay. It also explains what you can ask us to change on your own records, and where to send the question.
fv888 runs for Bangladesh users, and this page is written by us, for you. It sets out what happens to the details you hand over when you open an account — your name, contact number, email and the wallet reference used for Rocket or Upay — and how we treat the technical data your phone or browser sends while you are signed in. Whether you can open an account depends on your local law and eligible regions, and nothing here overrules the rules that apply where you live. We keep the wording short on purpose. Where a rule differs between markets, we apply the version required in your region, and the fields and verification instructions shown inside your account take priority over anything written on this page. If the policy changes, the updated text goes live on this same address, so the version you are reading is the one that applies. Send any question about a clause through the support route published on the site. If a point here conflicts with the law of your region, that law wins.
This policy follows your account, not the whole internet. Four areas sit inside it: the account you open with us, the transactions you run through your wallet, the pages and game screens we serve, and the outside services that handle a step on our behalf. Everything else — the messaging app you chat on, the extensions you install, the network you connect from — belongs to you and your providers. A game screen such as Cricket Betsport or Baccarat NightRush loads from our domain, so what happens on that page sits inside this policy. The moment a screen hands you to another company's product, that company's own policy takes over and we cannot answer for it. Check which one applies before you accept the step. Eligibility follows the same logic. Local law decides whether you can hold an account where you live, and where a region is not eligible, this page does not create a right to use the service.
Logging in, resetting a password and any detail you save to your profile sit inside this policy. When you sign in from a phone browser, the session data that keeps you logged in is covered too. Check the fields shown on your account page for the steps that apply to you.
Deposits and withdrawals you start through Rocket or Upay are covered here, including the wallet reference we store so you can match a transfer to your account. The payment provider keeps its own records and its own terms, which govern the part of the journey that happens on its side.
Game listings, category pages, lobby notices and the screens you scroll on your phone all fall inside this policy. So does the cookie data that remembers your language and layout choices between visits. What we do not cover is what you post or send outside our pages.
Some steps involve a company that is not us — a payment provider, an app store, a network operator. Their handling of your data follows their own policy. Read that policy before you accept their step, and treat anything it says as separate from this one.
You already hold the handles to your own account, and they sit inside the signed-in area. Open your profile to see the details on file — name, contact number, email and the wallet reference tied to Rocket or Upay. If something is out of date, change it there and save; the update reaches us the same way your other account actions do, so a spelling fix needs no message. Ask about anything you cannot see for yourself. A transaction you do not recognise, a cookie you want switched off, a copy of what we hold: raise it through the support route published on the site and quote the account and the time, so the record can be found. We answer what this policy allows and tell you plainly when a request falls under another set of rules. Closing your account uses the same route rather than an abandoned login. Closing it and erasing every trace are not the same thing, and we will say which parts stay.
Open your profile while signed in to see the name, contact number, email and wallet reference we hold for you. This is also the place you update them, so nothing about your account sits outside your control between one login and the next visit on the same phone.
Change an out-of-date phone number or email in the profile and save it. Keep the wallet reference for Rocket or Upay accurate, because that is the string we match against an incoming transfer when you report one through support.
Send a query about a record, a cookie or a clause on this page through the support route published on the site, quoting your account and the time of the action. If the request falls under another set of rules, we say so instead of leaving you guessing.
You can ask what we hold on your account and why we hold it. We point you to the record and explain the purpose behind it, or tell you clearly if local law in your region limits what can be handed over.
Every route you need for a policy question is already published on this site, and we would rather you used one of them than guessed an address. The support and contact links in the footer open the channel our team watches; the same links sit next to your account area once you are signed in, which saves a long scroll on a phone. Say what you need in plain words: which record, which date, which of our pages you were on. Quote the account email so the request lands with the right file. If your question touches a transfer through Rocket or Upay, add the reference the wallet gave you, because we match it against the record on our side instead of asking you to tell the whole story twice. We do not take policy requests through social media comments or a third party, and we will never ask you for your password.
The contact and support link in the site footer opens the channel our team watches for policy questions. Use it for anything about the details we hold, a cookie you want switched off, or a clause on this page you want explained in plain words.
The address published on our contact page reaches us for written requests, including a copy of the details tied to your account. Quote your account email, so the request can be matched without a round of follow-up questions.
Once you are logged in, the same support links sit beside your account area, which is quicker on a phone than scrolling a long page. Raising a question there keeps the account reference attached to it from the start.
Data handling here is short to describe because we keep it narrow. An account needs your name, contact number, email, the wallet reference tied to Rocket or Upay and a record of the transactions that follow. Alongside that sits the technical detail your browser sends, such as device type and the pages you open. We use it to run the account, match a transfer, answer your questions and meet the record-keeping rules that apply in your region. We do not sell your details. Cookies do two jobs. One keeps you signed in after you enter your password; the rest remember small choices, like the layout you last used on your phone. Clear or block them in browser settings whenever you like — some screens will ask you to log in again, which is expected behaviour, not a fault. Login safety is shared. We hold the account record; you hold the password and the device. Retention follows purpose: a payment trail stays as long as local rules require, while a cookie preference disappears when you clear it.
Name, contact number, email, the wallet reference tied to Rocket or Upay, and the transactions that follow on the account. Alongside that sits technical detail your browser sends, such as device type and the pages you open while signed in.
A session cookie keeps you logged in after you enter your password. Smaller preference cookies remember layout and language choices on your phone. Clear or block them in browser settings whenever you like; you will simply sign in again on the next visit.
Choose a password you do not reuse on other sites, keep a screen lock on your phone and sign out on shared devices. We never ask for your password in a message, and the login record on our side stays tied to your account alone.
Transaction records stay for the period local rules require, because a payment trail has to remain checkable. A cookie preference drops away as soon as you clear it. Ask through support if you want to know which category a particular record falls into.
The questions below are the ones we are asked most about this policy, answered in the same plain terms we use on the support route. If yours is not here, send it in with your account email and the page you were on, and it will reach the team that can read the record. Nothing on this page changes the rules that apply where you live, and access to the account depends on local law and eligible regions. Where a payment step happens on a wallet's own screens, that provider's terms sit alongside ours rather than inside them.
Your name, contact number, email and the wallet reference used for Rocket or Upay, plus the transactions that follow on the account. Your browser also sends device and page data while you are logged in. We use it to run the account and answer your questions.
Yes. Open your profile while signed in to see the details on file, and use the support route published on the site for anything not shown there — a transaction record, a cookie setting, or the reason a particular detail is held.
Change the field yourself in your profile and save it. Phone number, email and the wallet reference for Rocket or Upay are all editable there. For a record you cannot edit, send the account email and the date through support.
Only partly. We hold the transaction record and the reference stored on your account. The wallet's own screens, receipts and app fall under that provider's policy, so read theirs before you accept a step on their side of the transfer.
Closing the account stops the login. Transaction records still stay for the period local rules require, because the payment trail has to remain checkable. Ask support which parts are removed and which stay, and we will tell you plainly.
Use the support link in the site footer or the address shown on the contact page. Quote your account email and the page you were on. Requests sent through social media comments or a third party are not accepted.