Sports / Slots
cba77 collects only the information needed to run your account, process wallet transactions through Rocket and Upay, and keep your session secure. This policy tells you exactly what we hold, why we hold it, and what choices you have — with access subject to your local law and eligible regions.
When you open an account with us, we collect the details you enter during registration — name, contact address, and the wallet identifiers linked to payment methods such as Rocket or Upay. We also record transaction references so your deposit and withdrawal history stays accurate inside your account wallet. Device data — browser type, screen resolution and session token — is captured automatically to keep the login flow stable across mobile access. We do not collect data beyond what is necessary for account operation, transaction verification and security monitoring. Payment data is handled through the payment processor's own environment; we store only the reference needed to match a transaction to your account record. Where you use a local payment method, the wallet provider's own privacy terms also apply alongside ours. If you access our platform from a jurisdiction where online account services face restrictions, your eligibility and our obligations both depend on the law applicable in that region. We review this data collection scope periodically, and any material changes will be reflected in an updated version of this page.
When you transact via Rocket, we store the transaction reference number only — not your full wallet credentials. This lets us match deposits and withdrawals to your account record without holding sensitive payment identifiers on our side.
Upay transactions follow the same reference-only approach. The full payment detail stays within Upay's own secure environment. We log the reference, amount and timestamp so your account wallet history stays accurate.
Each login from a mobile browser generates a session token tied to your account. We use this to keep you authenticated without re-entering credentials on every page, and we expire idle sessions after a set inactivity period.
Your registered contact information is used to send account notifications, respond to support requests and verify your identity if you raise a data query. We do not share this with third parties for marketing without your explicit agreement.
This privacy policy covers data processed directly by cba77 in connection with your account. It does not extend to external services you reach through links on our platform, nor to the internal data practices of payment providers like Rocket or Upay. Understanding the boundary helps you know which questions to direct to us and which to raise with a third party. Access to our platform and the applicability of this policy both depend on your local law and the eligible regions we serve.
Login credentials, session tokens and account activity logs fall entirely within this policy. We control these records, and you can request a summary through the account support route described in the Rights section below.
Deposit and withdrawal references linked to your account wallet are covered here. The underlying payment processing — including what Rocket or Upay stores on their side — is governed by their own respective privacy terms, not ours.
We collect aggregated, anonymised usage data to understand which sections of the platform are most visited. This data is not linked back to your individual account unless a security review requires it.
Game content delivered by studios such as PlayStar, Spadegaming or CQ9, and any external links on the platform, are outside the scope of this policy. Those providers operate under their own data terms, which we do not control.
You have practical options for managing the personal data held against your account. First, you can review the information we hold by opening a support request and asking for a summary — our team will respond through the channel you used to contact us. Second, if any account detail is incorrect — your registered contact address, for example — you can update it directly in your account settings page or ask support to correct it on your behalf. Third, if you want to raise a question about how a specific piece of data is used, send it through the email support route and we will address the specific point rather than sending a generic response. Fourth, if you wish to request deletion of non-essential data, note that transaction references linked to completed Rocket or Upay payments may be retained for the period required by applicable financial record rules. What you can have removed and what must be kept will be explained clearly when you raise the request. Eligibility for these actions may vary depending on your region and applicable local law.
Open a support request and ask for a data summary. We will outline what categories of information we hold against your account, including session history and wallet references.
Log into your account and navigate to the profile or settings section to update contact details. For fields you cannot edit directly, raise the correction through live chat or email support.
Send your question through email support with your account identifier. We address specific data questions rather than issuing blanket replies, so include the exact detail you are asking about.
You can request removal of non-essential data. Transaction records tied to Rocket or Upay activity may need to be retained for financial compliance periods; we will tell you exactly what applies when you submit the request.
If your privacy question is not answered on this page, use one of the contact routes below. Each route reaches the same account support team — choose whichever works on your device right now. For written records of a data request, email is the most reliable channel because it creates a thread you can refer back to. All queries about Rocket or Upay transaction data, account deletion or data correction should include your account identifier so we can locate the right record without delay.
Open the chat widget from any page inside your logged-in account. Use this for quick clarifications about what data we hold or how a specific account field works.
Send a written request to the email address shown on the Contact page of the platform. Email creates a written record of your data query and our response, which is useful for correction or removal requests.
The Help section inside your account lists the most common data and privacy questions with direct answers. Check there first — many account-data questions are resolved without needing to contact support at all.
We take a few clear steps to keep your account data handled consistently. Cookies are used for session management and basic analytics — you can adjust non-essential cookies through the cookie preference panel accessible from the footer. Account security relies on session tokens that expire after inactivity, and we do not store payment credentials beyond the transaction reference needed for wallet reconciliation. Data retention follows a defined schedule: active account data is held while your account is open; transaction references linked to Rocket or Upay activity are kept for the period required by applicable financial rules; and data you have not actively used is reviewed on a rolling basis. Changes to this policy are published on this page, and the revision date at the bottom of the page tells you when it was last updated. If a change materially affects how we use your data, we will notify you through your registered contact detail before the change takes effect.
Session cookies are necessary for your logged-in experience. Non-essential analytics cookies can be adjusted or declined through the cookie panel in the site footer. Your preference is stored against your browser session.
Session tokens expire after inactivity to reduce exposure on shared devices. We do not store full payment credentials — only the reference numbers needed to match Rocket or Upay transactions to your account wallet.
Active account records are held while your account remains open. Transaction references may be kept beyond account closure where financial compliance rules require it. We will tell you the applicable period when you ask.
Material changes to this policy are communicated to your registered contact detail before they take effect. The revision date at the foot of this page confirms when the current version was published.
These are the questions we hear most often about how your account data is handled. If yours is not here, use the email support route or live chat to get a specific answer.
We hold your registration details, contact address, session history and transaction references linked to wallet activity such as Rocket or Upay payments. We do not hold full payment credentials. Open a support request if you want a written summary of the specific categories held against your account.
Yes, you can request deletion of non-essential data. Transaction references tied to completed Rocket or Upay payments may need to be retained for the period required by applicable financial rules. When you submit the request, we will explain clearly which data can be removed and which must be kept.
We cover only the transaction reference we receive from the payment process. The full payment credential and wallet data remain within Rocket or Upay's own environment and are governed by their respective privacy terms. For questions about what those providers hold, contact them directly.
Log into your account and check the profile or settings section first — many fields can be updated directly. For fields that are locked, raise a correction request through email support or live chat, including your account identifier so the team can locate the right record quickly.
We do not sell your data or share it with third parties for marketing without your agreement. Game studios such as PlayStar, Spadegaming, CQ9 and others deliver content through our platform but do not receive your personal account data from us. Payment processors receive only what is needed to complete a transaction.
Your eligibility to use the platform and how this policy applies both depend on your local law and the eligible regions we serve. If access is restricted in your jurisdiction, data we may have collected prior to that restriction is still handled under this policy. Contact support for region-specific questions.