Slots / Sports
cv668 keeps its legal terms, account rules and policy positions on one page, so you can read what applies before you open an account or move through the lobby. Access to any part of the site depends on your local law and eligible regions, and we keep this wording short because a page you finish is a page you can act on.
Our legal page is a plain statement of how we run the site and what we expect from each other. Nothing on it is a promise we cannot evidence. Where a rule depends on where you live, we say so, because licensing, tax and payment rules differ from country to country and we cannot apply one set of terms everywhere. If your local law does not allow online casino or sportsbook access, the wording here does not override it, and we may be unable to open or keep an account for your region. You will find four main blocks: the terms that apply when you open an account, the rules that apply when you use the wallet, the terms attached to the game catalogue and the sportsbook, and the privacy and cookie text that explains what we record and why. When wording changes, the change appears on this page rather than in a message you might miss. Using bKash, Nagad, Rocket or Upay is context, not a separate contract. The payment names on this page describe the rails that appear in your account for Bangladesh, and the transaction rules beside them come from the provider as well as from us. If a provider changes how it handles a transfer, our wording changes with it. Come back to this page whenever a question about your account, wallet or data comes up.
This policy reaches the parts of the site we control directly, and it ends where another company takes over. Your account, the wallet balance recorded against it, the game catalogue and the cricket-led sportsbook we publish all sit inside the scope. That is why account access and transaction records appear in the same document as our content rules. What happens after money leaves us is a different matter. bKash, Nagad, Rocket and Upay each run their own terms, and your agreement with them sits outside this page. Device behaviour is the grey area worth naming. We can describe how the lobby responds on a phone, but the operating system, network and browser you choose are yours to manage. Third-party game content is the last piece. The studios whose titles appear in the lobby supply the games, and their own end-user terms can apply to a round you play. Where two sets of wording touch the same moment, we say which one governs, so you are not left guessing.
Signing in, the email registered to your account, device sessions and the controls you set for yourself sit inside this policy. If your region is not eligible under local law, that is covered here too: we can decline or close access, and we will explain the reason where we are able to.
Money moving through bKash, Nagad, Rocket or Upay is recorded against your account, and the part we control, meaning the record we keep, the status we show and the way you raise a query, is covered here. The rest of the journey follows the provider's own terms.
Our game catalogue, the studio titles shown in the lobby from Bigtime Gaming, Spadegaming, JDB, Habanero, Joker and Pragmatic Play, and the editorial wording on this site are ours to describe and ours to correct when something is wrong.
Your browser, your device maker, your network provider and any service you reach through a link on this site set their own conditions. We do not control those, and nothing on this page extends to them, so read their terms before you rely on anything they state.
You have practical options here, not just words. Start with your own account: the signed-in area shows the details we hold, and you can check them at any time without asking us for permission. If something is wrong, an old phone number, a mistyped name, a wallet reference that does not match, correct it in the same place or write through the published support route and we will look at it with you. Questions about the wording itself are welcome. If a clause reads as though it covers something it should not, or misses a case you have hit, tell us and we will explain how we apply it. Where a decision about your account rests on a rule here, you can ask us to point to that rule. You can also ask what we hold. Send the request from the email registered to your account so it can be matched to your profile, then follow the verification steps shown in your account.
Open your account area and read the profile, contact and wallet references stored against your name. Anything visible there is yours to question, and checking it early helps when a transfer reference or a contact detail needs matching later.
Update what the account area lets you change yourself. For anything locked, such as a name spelling or a wallet reference, use the published support route and follow the verification steps shown there before the change is applied, so the record stays accurate on both sides.
If wording on this page is unclear, or you want to know which rule was applied to a decision on your account, ask. We will point to the section that governs and explain how we read it in your case.
Send the request from the email registered to your account so it can be matched to your profile. We then tell you what is held and how to ask for a change, following the steps shown in your account rather than a public channel.
Policy questions travel the same route as any other account question. The support page linked from this site is the place to start, and the account help area inside your signed-in view covers the practical side: wallet records, transaction references and profile changes. Neither needs a guess about where to write. Write from the email registered to your account. That one step saves a round of back-and-forth, because the message can be matched to the right profile straight away. Say which section of the legal page your question is about, and include the account reference plus any transaction reference that belongs to the case. One question per message works best. A short, specific message gets a specific answer. This page does not carry an address, a hotline or a set of hours, and we will not invent one here. The routes above are the ones that exist on the site; use those, and if a route is not shown, it is not open.
The support page linked from this site is where a policy question starts. Choose the category closest to your case, describe it in your own words and send from the email registered to your account so the message can be matched to the right profile.
Inside your signed-in view, the account area shows wallet records, transaction references and the profile fields you can change yourself. For anything about a specific transfer or a detail we hold, it is usually the quicker place to look first.
If a question is not settled, reply on the same thread rather than starting a new one. Earlier messages stay attached, so the wording point you raised and the account context around it can be read together. Keep the reply specific.
What we record and why are part of this policy, not a separate subject. Account details, wallet activity and the device you sign in from are held so the account works and so a disputed transaction can be traced. Nothing is stored because it might be handy later. Cookies do the quiet work. Some keep you signed in, some remember a choice such as language, and some show how a page performed so we can fix it. You can clear or block them in your browser settings; the site still loads, though a few conveniences no longer work. Account safety is shared. We ask for the credentials on your profile, and you keep them to yourself: no sharing, no borrowed logins, no one else using your wallet. Anything unusual on the account is worth raising with us early. Retention follows the same logic. We keep what an account record needs and what the payment rails require, then remove it. If you want to know what is held on you, or want something corrected, write from the registered email and follow the steps shown in your account.
Your profile, wallet activity and sign-in records are stored so the account can work and a disputed transfer can be traced. We do not collect extra fields to fill a database; every item has a purpose you can ask about.
Cookies keep you signed in, remember a choice such as language and show how a page performed. You can clear or block them in your browser settings; the site still loads, though a few conveniences no longer work.
Your password and the controls on your profile are yours to keep. Do not share them, and do not let anyone else use your wallet. If you think someone has your details, use the published support route so the account can be looked at with you.
Account and transaction records stay while the account and the payment rails need them, then they are removed. To ask what is held on you, or to request a correction, write from the registered email and follow the steps in your account.
These are the policy questions we are asked most often, answered in the same plain wording as the rest of this page. Each answer points to where you can act rather than leaving you with a general statement. If your case is not here, a transfer that looks wrong, a detail you cannot change yourself, a clause you want explained, use the published support route and send it from the email registered to your account, so the message can be matched to your profile and answered against the rules that apply to it. This page sits alongside the account terms rather than replacing them, so read both where they touch the same subject. Nothing here changes your position where local law says otherwise, and nothing here overrides a provider's own terms for a transfer you send. Answers stay short on purpose.
It sets out the terms for opening and keeping an account, the rules around wallet activity through bKash, Nagad, Rocket and Upay, the conditions attached to the game catalogue and the sportsbook, and how we handle your details and cookies. Access depends on your local law and eligible regions.
Access depends on the law where you live. If online casino or sportsbook use is not permitted in your region, this wording does not change that, and we may be unable to open or keep an account for you. Where a region is eligible, the usual account steps apply.
Sign in and open the account area to read the profile, contact and wallet references stored against your name. For a copy of what we hold, send the request from the email registered to the account and follow the verification steps shown there.
The wallet records we keep, meaning the amount, the reference and the status, sit inside this policy. The transfer itself follows the provider's own terms, which sit alongside ours. Where a provider changes how it handles a payment, the wording here is updated to match.
Change what the account area lets you change yourself. For anything locked, such as a name spelling or a wallet reference, write through the published support route and follow the verification steps shown there before the correction is applied.
Use the support page linked from this site and send from the email registered to your account. Name the section you are asking about and the decision it affects. A short, specific message gets a specific answer.
Account, sign-in and transaction records stay for as long as the account and the payment rails need them, and no longer. When you ask about your own record, we tell you what is held and how to request a change where that applies.