App / Live
kkb33 collects and uses your information only to run your account, process wallet transactions through Rocket and Upay, and keep your session secure across phone and desktop. What we collect, why we collect it, and how you can manage it — that is what this policy covers. Access to our platform depends on your local law and eligible regions.
When you open an account with kkb33, we collect registration details such as your name, contact address and login credentials. When you make a deposit or withdrawal using Rocket or Upay, transaction reference data passes through our payment layer so we can match records on both sides. We also collect device identifiers and session tokens so your account stays signed in consistently when you move between your phone browser and desktop without re-authenticating. We do not sell your personal data to third parties. We share only what is strictly necessary with payment processors handling Rocket or Upay transactions and with technical partners who operate parts of our platform infrastructure. Cookies and local storage help us remember your account state, your preferred sports market view and the last section you visited — sports or casino — so the page loads in context when you return. Retention periods apply to each data category. Account records are kept while your account is active and for a period after closure as required by applicable rules in your region. You can ask us what we hold, request corrections and raise concerns at any time through the support routes listed on this page. Availability of this platform and the rights described here depend on your local law and eligible regions.
This policy applies to information kkb33 collects and controls directly. It does not extend to third-party sites linked from our pages, or to payment networks operating their own terms when you use Rocket or Upay outside our platform. Understanding the boundary helps you know which organisation to contact when a question arises.
Login credentials, session history and device identifiers collected when you sign in or stay signed in are covered fully by this policy. We control how those records are stored, accessed and deleted.
Deposit and withdrawal references processed through Rocket or Upay on our platform are within scope. The payment network's own data handling falls under that network's separate privacy terms, not ours.
Page-visit data, game-category clicks and sports-market views collected through our analytics layer are covered here. We use this only to improve navigation — not to profile you for third-party advertising.
External links, embedded content or any service with its own login sits outside our policy boundary. We are not responsible for how those services handle your data once you leave our platform.
Your account is the starting point for most privacy actions. You can review the personal details we hold by opening your account settings page, where your registered name, contact information and linked wallet labels are displayed. If something is wrong — a misspelled name or an outdated contact number — you can edit it directly in those fields and save. For records that are not editable through the account interface, such as historical transaction references tied to a Rocket or Upay deposit, you can submit a correction request through our support channel and we will update the record or explain why a correction is not possible in that instance. If you want to know precisely what data categories we hold against your account, you can send a data enquiry through live chat or email and we will respond with a plain summary. Requesting account closure is also an available action; note that some records are retained after closure under applicable rules, and we will explain which ones apply to your region when you make that request.
Open account settings to see your registered details and linked wallet labels. Transaction history for Rocket and Upay deposits is listed in the wallet section of your account.
Edit your name or contact number directly in the account settings fields. For transaction-level corrections, contact support with your reference number and we will investigate.
Send a data enquiry through live chat or our support email. We will respond with the specific data categories held against your account, without requiring you to fill in a separate form.
Closure requests are handled through support. We will confirm which records are retained under applicable regional rules and explain the timeline before finalising the closure.
If you have a question about how kkb33 handles your data, or you want to exercise a right described in this policy, use one of the contact routes below. We handle privacy enquiries through the same support channels as account and wallet questions — no separate form is needed. Availability depends on your local law and eligible regions.
Start a live chat from any page while signed in. Describe your privacy question and the agent will log it or escalate to the relevant team. This is the quickest route for account-level data queries.
Send your query to our published support email address, which is shown in the contact section of your account area. Include your registered contact detail so we can match the request to your account record.
The help centre inside your signed-in account lists published policy documents and common data questions. Start there if you want to understand a specific data category before raising a formal request.
Data handling at kkb33 follows a straightforward principle: collect what is needed to run your account, keep it only as long as required, and give you visible routes to review or correct it. Session tokens are rotated when you log in on a new device, so your phone session and desktop session each carry a fresh identifier without exposing one to the other. Cookie consent is surfaced at first visit and your preference is stored against your browser profile.
We use cookies to hold your account state, your last visited section and your language preference. You can clear these through your browser settings at any time. Clearing cookies will sign you out of the current session.
Login sessions are protected with encrypted tokens. If we detect an unfamiliar device accessing your account, the session requires re-authentication before proceeding. You can view active sessions in your account security settings.
Active account data is retained while your account is open. After closure, transaction records tied to Rocket or Upay activity are retained for the period required under applicable regional rules. We do not hold records beyond what those rules require.
When this policy changes materially, we publish a notice in your account notification area before the change takes effect. Continuing to use your account after that date means you have seen the notice. A copy of the current policy is always available at kkb33/privacy-policy/.
These are questions we hear most often from account holders about how their data is handled, what their rights are, and how to contact us. If your question is not here, live chat is the quickest route to a direct answer.
We collect your name, contact information and login credentials at registration. Once active, we also collect session identifiers, device type, page-navigation data and transaction references when you use Rocket or Upay. We do not collect data beyond what is needed to run and secure your account.
We share data only with payment processors handling your Rocket or Upay transactions and with technical partners who operate parts of our platform. We do not sell your data or pass it to advertisers. Each sharing arrangement is governed by a data processing agreement, not an open data transfer.
Send a data enquiry through live chat or the support email shown in your account area. Include the name and contact detail registered to your account so we can match the request. We will reply with a summary of the data categories held against your record.
Yes. Most fields — name, contact address — are editable directly in your account settings. For historical transaction references tied to a Rocket or Upay deposit that cannot be self-edited, contact support with the reference number and we will update or explain what is possible.
After closure, we retain transaction records for the period required under applicable regional rules, then delete them. We will confirm the specific retention period that applies to your account when you submit a closure request through our support channel.
This policy describes how kkb33 handles data for accounts on its platform. Whether you can access the platform at all depends on your local law and eligible regions. If access is available in your region, this policy applies in full to your account activity.