Live / Sports
Your account data, payment records and session details sit under one published policy at cv71, written in plain English and kept on this same page. What we can offer you depends on your local law and eligible regions, so check what applies where you are before you open an account.
This policy explains what happens to the details we collect when you open an account, fund it through a local route and move around the lobby on your phone. It sits alongside the terms you accept when you start, and it covers the same ground: account records, transaction references, device and browser data, and the messages you send us. Two things decide how far the policy reaches in practice. The first is where you are. Rules about gambling, payments and data vary from place to place, so access to cv71 and the way we handle your records both depend on your local law and eligible regions. Where those rules differ from what we describe here, the stricter local requirement applies to your account. The second is which route you used. A wallet transfer, a Bank Transfer or any other named method leaves its own reference trail, and we keep that trail with your account so you can trace a payment later. The chips below show the payment contexts this page covers. If you want to know what we hold before you act, ask us first — we would rather answer a question than have you guess.
A policy is only useful if you can tell where it ends. Ours follows your cv71 account, not the whole internet around it, so the lines are worth spelling out before you raise a question. Everything you do inside the signed-in area is covered: the details on your profile, the payment references attached to your wallet or Bank Transfer activity, and the messages you send through the site's support route. The same applies when you browse the lobby on a phone browser, because session and device data is gathered there too. Outside our reach sit the services other people run. If you open your mobile wallet app to approve a transfer, that wallet's own policy governs that step, not this page. Your telecom operator, your bank and any site we link out to follow their own rules as well. We cannot change what they collect or how they store it, and we do not control it. If a third party's practice matters to you, read their policy alongside ours — the two sit side by side rather than replacing each other.
Everything you see once you sign in sits inside this policy: your profile details, your contact entries, your sign-in history and the preferences you save. If you change a detail there, the new value replaces the old one in our records, and you can ask us what we currently hold.
Payment references from a Rocket, Bank Transfer, bKash or Nagad step are stored against your account, so a transfer can be traced later if something looks off. The reference and the route you used stay linked to your profile.
Lobby pages, game listings and the copy you read while browsing, including the cricket, slots and live casino areas, are ours to change. What we publish here describes the policy at a point in time, and the version on the site is the one that applies to you.
Wallets, banks, telecom providers and any outside site you reach from a link keep their own rules. Approving a payment inside a wallet app is that provider's step, not ours. Read their policy if you want to know what they hold.
You do not need a reason to ask what we hold about you. Sign in, open your account area, and the details we store are shown there for you to read; if something is wrong, that same area is where you correct it. Ask us when a record looks incomplete and we will tell you what we can change directly and what needs a short written request from you. Raising a question is equally simple — use the support route published on the site and describe what you want to see, change or remove. We answer through the channel you wrote in on. If your concern is about a payment, quote the reference from your transaction list so we can match it without guesswork. When a request touches local rules that differ from ours, we explain what we can and cannot do under the law that applies where you are.
Open your account area while signed in and you can read the profile details, contact entries and transaction references linked to you. Nothing sits behind a special request — the record is visible to you first, and ours to answer for second.
Spotted a wrong number or an out-of-date address? Update it from the same account area so our records match what you actually use. If a field will not change there, ask us and we will explain what we can adjust.
If you want to know why we keep something or how long it stays, send the question through the published support route. Put your account reference in the message so we can pull the right record and reply to you properly.
Stuck halfway through a request? Message us with the step you reached and what you saw on screen. We will take you through the next part of the process rather than leaving you to work it out alone.
Policy questions reach us through the same support routes we publish on the site, and that is deliberate. You should not have to hunt for a separate contact address just because your question is about data rather than a payment. Sign in, open the help or support entry in your account menu, and describe what you need — the record you want to see, the detail you want changed, or the part of this policy that reads unclearly to you. That is the route we watch, and it keeps your request attached to your account. If you are writing about a specific step, include your account reference and, where a payment is involved, the reference from your transaction list. It saves a round trip and it means the first reply can be a real answer. Whatever route we list on the site is the one we answer, so start there rather than sending a request to an address you found elsewhere.
The help and support entry inside your signed-in account menu is the first place to raise a policy question. Describe what you want to see, change or remove, and we will reply through that same route.
Every support route we publish on the site is listed in plain view rather than buried in a menu. Use the one that fits your question; if you are unsure which, start with the help entry and we will point you on.
Quote your account reference when you write, and add the payment reference from your transaction list if the question touches a wallet or Bank Transfer step. It shortens the exchange and gets your question to the right record.
How we handle data is the practical part of this page, so here is the shape of it. We collect what an account needs to work — the details you enter, the references your payments generate, and the device and session data a phone browser leaves behind — and we use it to run your account, answer your questions and keep the service working. Cookies do a smaller job: they keep you signed in, remember basic preferences and tell us how a page performs on mobile. You stay in control of the account itself. Keep your sign-in details private, use the sign-out option on shared phones, and tell us at once if you think someone else has reached your account. When you ask us to remove something, we check what we can delete and what local rules require us to keep; where retention is set by law, we will say so rather than quietly holding on.
Account details you type in, references created when you fund the account through a wallet or Bank Transfer step, and the device and browser data a session leaves behind. We collect these to run your account, not to sell them to anyone.
Cookies keep you signed in between pages, remember small preferences and show us which lobby screens load slowly on a phone. You can clear or block them in your browser settings; some signed-in parts of the site may then behave differently.
Your sign-in details are yours to hold. Use the sign-out option on a shared device, avoid saving passwords on a phone others use, and contact us straight away if you notice activity on your account that you did not start.
We keep account and transaction records for as long as the account stays open and afterwards while local rules require it. Ask us and we will say what we still hold and whether any of it can be removed now.
These are the policy questions we see most often from members using the site on a phone. Each answer points to the route where you can check things for yourself rather than take our word for it. If your question is not here, the support entry in your account menu is where to send it, and access to cv71 itself still depends on your local law and eligible regions.
It covers what we collect when you open and use an account: your profile details, the references your payments leave behind, device and session data, and the messages you send to support. It also explains the choices you have over that data and how to ask us for changes.
We share only what a step needs to complete — for example, a payment reference handed to the wallet or bank involved in that transfer. We do not sell your account details to anyone. Anything else is shared only where local law requires it.
You can ask, and we will tell you what can be removed and what local rules require us to keep, such as transaction records tied to a payment you made. Send that request through the support route shown on the site so it reaches the right record.
Open your account area and change the field there while signed in. If it will not update, message support with the exact field and what it should say, and we will explain what we can adjust on our side of the record.
Partly. The cookie and device side applies from the moment you land on a page, because a session leaves basic browser data behind. The account sections apply once you create an account and sign in, including anything linked to Rocket, Bank Transfer, bKash or Nagad activity.
Use the support route published on the site — the help entry in your account menu is the simplest starting point. Include your account reference so we can find the right record and answer your policy question directly rather than sending you round the site.