Slots / Mobile
c6v6 collects only the account and transaction data needed to run your wallet, process payments through bKash, Rocket or Bank Transfer, and keep your session secure. Access to this platform and the scope of data handling depend on your local law and the eligible region you access from.
This policy sets out what personal information c6v6 collects when you open an account, make a deposit or withdrawal using bKash, Rocket or Bank Transfer, browse the game lobby, or contact our support team. We collect your name, contact details, wallet identifiers and session activity — enough to verify your account, process transactions and resolve disputes. We do not collect data beyond what your account journey requires, and we do not sell your personal information to advertisers or unrelated third parties. Retention periods vary by category: payment records are kept for as long as regulatory or dispute-resolution obligations require; session logs are held for a shorter operational window. If you access c6v6 from Bangladesh, whether and how local data-protection rules apply to you depends on your specific legal context and the region from which you connect. This policy is updated when our data practices change. We will flag material changes on the account notice board so you can review them before continuing to use the platform. Wallet identifiers such as your bKash or Rocket number are treated as sensitive payment data and are not shared outside the transaction flow.
Your bKash number is recorded only for the transaction it belongs to and is not stored in a shared marketing database or exposed to game studios.
Rocket transfer references are retained to match deposits and withdrawals to your account ledger, and for any dispute or reconciliation need that follows.
Bank account details submitted for a withdrawal are used solely to complete that transfer and are held according to our standard payment-record retention schedule.
Login timestamps, device type and browser session data help us detect unusual access and let you review your recent account activity from the security tab.
This policy covers information c6v6 holds directly — your account profile, wallet records, game session logs and support correspondence. It does not govern data handled by third-party payment processors, external websites you navigate to from a link on our pages, or any service outside the c6v6 platform. Understanding the boundary helps you know where to direct a privacy question and which organisation's policy applies in each case.
Login credentials, account profile fields and security settings fall inside this policy. We control how that data is stored and who on our team can access it.
Transaction records for deposits and withdrawals processed through our platform are covered here. The payment processor's own policy governs data on their side of the transfer.
Bet history, game session records and lobby navigation logs generated inside c6v6 are within scope. Game studios receive anonymised performance signals, not your personal account details.
Any external site, app or wallet provider you reach from a link on our pages operates under its own policy. c6v6 is not responsible for data practices outside our platform boundary.
You have specific actions available to you regarding the personal data c6v6 holds. You can request a summary of the information we have on file — including contact details, wallet references and transaction history — by reaching our support team through the contact route listed in the support section below. If any detail is wrong, such as an outdated phone number or an incorrect account name, you can ask us to correct it and we will action that after verifying your identity. Where data is held beyond an immediate operational need and no legal obligation requires us to keep it, you can ask about our retention position and what applies to your account specifically. For questions that go beyond a single correction — such as a broader data review or a question about how your bKash or Rocket records are stored — send a written request and we will respond through the same channel. All requests are handled subject to identity verification and, where relevant, to the legal framework that applies in your eligible region.
Ask for a summary of the personal data held against your account, including wallet identifiers and session history, by contacting support with your account details.
If your name, contact number or wallet reference is recorded incorrectly, raise a correction request and we will update it after confirming your identity.
For questions about retention periods, data categories or how a specific record is used, write to us directly and we will answer within the scope of what applies to your account.
If you cannot locate a record or need help understanding what data your account holds, our support team can walk you through the relevant section of your account view.
If you have a question about how your data is handled, want to correct a record or need to submit a formal data request, use the contact routes below. We respond through the channel you use to reach us. Availability depends on the support queue at the time of your request; we do not publish fixed response windows.
Open the support section inside your signed-in account to submit a privacy question or data request directly, with your account reference attached automatically.
Send a written privacy request to the email address listed in the contact section of your account dashboard. Include your registered account name and the specific data topic.
Use the live chat widget available on the c6v6 site to ask a privacy question or get directed to the right request form for your specific concern.
c6v6 applies access controls to personal data so that only the team members who need a record to carry out their role can retrieve it. Session cookies are used to keep your account signed in and to detect unusual login behaviour; you can manage cookie preferences through your browser settings. Data is not held indefinitely — account records inactive beyond a defined period are reviewed, and payment records are kept only as long as operational or dispute obligations require. If you believe your account has been accessed without your knowledge, report it through the support page immediately so we can review the session log tied to your account.
Personal account records and wallet references are accessible only to team members whose role requires them. We do not share your data across unrelated internal departments or external partners outside the transaction flow.
We use session cookies to maintain your logged-in state and to identify access anomalies. You can adjust cookie behaviour in your browser; some site functions depend on session cookies to work correctly.
Payment records linked to bKash, Rocket or Bank Transfer transactions are held according to operational and dispute timelines. Session logs are kept for a shorter window and reviewed periodically for necessity.
When this policy changes in a material way, we post a notice in the account area before the update takes effect so you can review what has changed before continuing to use the platform.
These are the questions we get most often about how c6v6 handles personal data, wallet records and account privacy. If your question is not answered here, use the support contact routes in the section above.
We collect your name, contact details, the wallet identifier you use for bKash, Rocket or Bank Transfer, and the activity logs generated by your account sessions. We collect what your account journey requires and nothing beyond that.
No. Your bKash or Rocket wallet details are used only to process the transaction they belong to. Game studios such as Pragmatic Play or CQ9 receive anonymised session signals for game performance purposes, not your payment identifiers.
Payment records are kept for as long as operational or dispute-resolution requirements apply. The exact period depends on the type of record and your account status. You can ask our support team for the retention position that applies to your account.
Yes. If a name, contact number or wallet reference is recorded incorrectly, contact our support team with your account details and the correction you need. We will verify your identity and update the record accordingly.
This policy covers data c6v6 holds regardless of where you connect from. Whether local Bangladesh data-protection rules apply to your specific situation depends on your legal context and the eligible region you access from — it is not something we can determine unilaterally.
Go to the support section inside your signed-in account and submit a report immediately. Our team can review the session log tied to your account and advise on the next steps for securing your access, including reviewing recent login timestamps.