Live / Slots
This page sets out what cvb33 owes you and what we ask of you: account access, transaction records, wallet requests and the limits that come with local law. Read it before you raise a dispute or change your details, and come back to it whenever a support reply points you here.
Nothing on this page replaces the law that applies where you live, and we cannot promise that every feature we list is open to you. Access to cvb33 depends on your local law and eligible regions, so the rules here describe how we run the account side rather than a promise of availability. Where our terms and your local rules disagree, your local rules take priority. We keep the wording short on purpose. When you open an account or move money through a wallet rail such as Rocket, Upay or Bank Transfer, you accept the version of this policy that was live at that moment. If we change how we handle access, records or account closure, the updated text appears here and applies from the date shown on it. Continuing to use the account after that date means you accept the change. Older versions stay archived so you can check what applied when a particular transaction happened. If a clause is unclear, message our support desk before you act on it rather than after. We would rather explain a step than unwind a dispute. That is the whole posture: plain rules in one place, with nothing designed to hide a fee or a restriction from you.
Scope is the question we hear most after a support reply: what exactly does this policy govern? It covers the account you hold with us and the actions you take while signed in, including opening the account, keeping your details current, moving funds between your wallet and the account balance, and the records we keep of each of those steps. It also covers the rules you follow while using the lobby and the notices we publish here. It does not cover the wallet provider on the other end of a Rocket, Upay or Bank Transfer instruction. Their app, their limits and their dispute process belong to them, and we cannot override a decision they make. The four blocks below show the split, so you know which desk to approach first when something looks wrong. If you are still unsure whether a rule here applies to your case, ask us before you rely on it.
This policy governs how you open the account, how you keep your password and registered details correct, and what happens if we need to restrict or close access. It sets out what we tell you before that happens and how you can reply to us.
Every deposit you route through Rocket, Upay or Bank Transfer creates a line in your account history, and that history sits inside this policy. We keep it so you and we can both check what happened when a request looks wrong.
The pages you read here, the game listings and the notices we post in the lobby all fall under this policy. Titles such as Cricket Expert Bets and Slot QuickSpin are catalogue entries we publish, and this policy explains what we may change and how we announce it.
Rocket, Upay, Bank Transfer and other wallet rails run on their own systems and their own rules. When their limits, confirmation steps or dispute process decide an outcome, this policy does not override it. Raise a wallet-side issue with the wallet first, then with us.
Rights only matter if you can use them without hunting for them. So here is the practical side: you can read every transaction line tied to your account, ask us to correct a detail that is wrong, and raise a question about any clause before you act on it. None of that needs a special request form, and none of it costs you anything. Start in the account area. The record of a Rocket, Upay or Bank Transfer instruction sits in the same history list, in the order it happened, so you can match it against the wallet app on your phone. If a name, number or date on your profile is out of date, tell us and we will walk you through what we need to change it. If a clause reads badly, quote the line and ask, because we answer in plain words. And if a decision on your account feels wrong, reply through the support route on this site and we will look at it with you.
Open the account history while you are signed in and read the line for each deposit and withdrawal in the order it was recorded. If a line does not match your wallet app, take a screenshot and send it with the reference number shown beside it.
If your name, mobile number or registered email is wrong, tell support and we will explain what we need from you to update it. Keep the change request tied to the same account so your transaction history stays in one place.
Quote the exact sentence that is unclear and send it to us. We will explain what it means for your account, not what it means in general, and we will tell you if the answer depends on where you live today. If the wording itself should change, say so and we will pass it on.
If you disagree with a decision on your account, reply through the published support route with your account reference and the date it happened. We will look at it again and come back to you in writing so you have a record.
Two things make a policy question easy to answer: where you are writing from, and what the account shows. Send both. The support routes below are the ones we publish on this site. Anything outside them is not ours, so if someone contacts you offering to fix an account issue for a fee, that is not us and you should not share your sign-in details. Keep the message short. Tell us what you tried to do, when it happened and which wallet rail you used, then attach the reference number from your history list. If your question is about the legal wording on this page, quote the clause so we do not have to guess which part you mean. We answer in writing so you keep a record of what was said, and we may ask you to confirm a detail from your own account before we act. That check protects you as much as it protects us.
Use the support route shown inside your signed-in account for anything tied to your profile, a transaction line or a clause on this page. Include your account reference so we can find the right record without asking you twice. Keep the message short and in your own words.
The contact link published on this site is the other way in. It reaches the same desk, so pick whichever is easier on the device you are holding, and a phone on mobile data works as well as a laptop. We do not run any other contact point for this page.
We reply in writing so you can keep the answer beside your transaction history. If you need to follow up, reply on the same message rather than starting a new one, and the earlier detail stays with the case. Quote your account reference the first time and you will not need it again.
Handling is where a policy stops being words and starts being a decision. The details you give us at sign-up, such as your name, mobile number and the wallet reference you use, stay tied to your account, and we use them to run that account rather than to fill a mailing list. Your password stays yours. We will never ask you for it in a message, and no one from our side will ask you to move funds to a personal number. Cookies on this site do the ordinary work: keeping you signed in, remembering the language and region you picked, and showing us which pages people leave quickly. You can clear them in your browser at any time. Records attached to a transaction are kept while your account is open and for the period we need to answer a dispute after it closes. When you want a copy, ask. Both requests go through the same support route, and we tell you what we did with it.
At sign-up we collect your name, mobile number, email and the wallet reference tied to your deposits. We store these against your account so support can match a request to the right person, and we do not pass them to anyone outside the service.
Cookies keep the session alive between pages and remember the region you picked. Clear them in your browser and you will sign in again and may see the default region. Blocking cookies is your call, though some account pages may then behave less smoothly.
Keep your password off shared phones and never hand it to anyone who contacts you first. Sign out on a device you no longer use, and open your transaction history when something feels off. If you think someone else has your sign-in, tell support and we will help you lock it down.
Transaction records stay while your account is open and for the period needed to settle a later dispute. To ask for a copy, a correction or the closing of your account, send one request through the published support route and we will confirm what we changed.
These are the points members of our support desk answer most often about this policy page, written the way you would ask them. Read the answer that fits your case, and if your situation is not covered here, send us the clause you are unsure about through the route shown inside your account.
Access to cvb33 depends on your local law and eligible regions, so the rules on this page describe how we run the account rather than a promise of availability where you live. If you move, or your local rules change, read the current text here before you carry on using the account.
Open your signed-in account and read the history list, where each deposit and withdrawal appears in the order it was recorded with a reference number beside it. If you need a written copy, send one request through the published support route and we will confirm what we sent you.
Yes. Send the correction through the support route shown on this site and tell us which field is wrong. We will explain what we need from you before we change it, and we keep the update on the same account so your transaction history stays in one place.
We keep records tied to a transaction while your account is open and for the period we need to answer a dispute after it closes. Ask for the account to be closed and we will tell you what stays on file, why it is held, and for how long.
Quote the exact sentence and send it to the support desk inside your account. We will explain what it means for your account and say plainly if the answer depends on where you live. If the wording itself should change, tell us that too.
Raise it with the wallet first. Rocket, Upay and Bank Transfer instructions run on the wallet's own systems and their rules decide the outcome. If the wallet settles it and the record on your account still looks wrong, bring the reference number to our support desk and we will check it.