Live / Casino
cs9999 collects and uses your information only for the purposes described in this policy — nothing more. What we store, how long we keep it, and how you can review or correct it is all laid out here in plain terms.
This policy applies to every interaction your account has with cs9999 — from the moment you register through every session, transaction and support request. When you add a payment method such as Nagad, Rocket or Bank Transfer, we record only the transaction reference and wallet identifier necessary to process and reconcile that action. We do not store full payment credentials on our servers. The information we collect falls into three categories: account identity data you supply at registration, device and session data generated when you browse or log in on mobile or desktop, and transaction references tied to your wallet activity. We use this information to keep your account working, to identify unusual activity, and to respond when you contact support. We do not sell your personal data to third parties. Where we share data with service partners — for example, a payment processor handling a Rocket transfer — we require those partners to handle it under terms consistent with this policy. Availability of this service depends on your local law and the eligible regions we operate in. If local regulation changes what we can offer or how we hold data, we will update this policy and notify you through your registered account.
Not every data point touched during your time on cs9999 falls under the same rules. This section draws a clear line between what this policy covers directly and what sits outside its boundaries — so you know exactly where our obligations begin and end.
Data generated when you log in — device type, browser session, login timestamp — is covered fully by this policy. We use it only to authenticate your session and flag access from an unrecognised device.
Transaction references from Nagad, Rocket and Bank Transfer operations are recorded in your account history. This policy governs how long we retain those references and who can request them. Full payment credentials are never stored here.
Round histories and game interaction logs from titles in our lobby are part of your account record and fall within this policy. We retain them for account integrity and dispute resolution purposes.
Links to external services — including payment processors and any platform outside cs9999 — are outside this policy's scope. Those services have their own data terms, which we encourage you to read before sharing information with them.
Your account data is not a locked file. Several practical steps are available to you without needing to contact support first. Log in and open the account settings page to see the profile details we hold — name, registered mobile number, and linked wallet identifiers. If any detail is incorrect, the edit fields in account settings let you update most information directly. For changes to your registered number or wallet reference tied to Nagad or Rocket, submit a correction request through the support channel so the change is verified before it takes effect. If you want to know exactly what data we hold beyond what is visible in account settings, send a data enquiry via the support route. We will respond with a summary of stored fields. If you believe your data has been handled incorrectly, raise it with our support team — the contact paths are in the Support section below. We aim to acknowledge data-related requests and route them to the correct internal team promptly, though response times depend on verification steps we are required to complete first.
Open account settings after logging in to see the profile fields and wallet references we currently hold. Most information is visible there without any additional request.
Edit standard fields directly in account settings. For wallet identifiers linked to Nagad, Rocket or Bank Transfer, submit a support request so the update can be verified before it is applied.
Send a written enquiry through the published support channel if you want a full summary of stored data or have a question this policy does not clearly answer.
If you believe a data handling step was incorrect, contact support with the relevant account details. We will route the case to the appropriate team and follow up through your registered contact.
For any question about this policy — how your data is stored, what we hold or how to request a change — use the published contact routes below. We do not handle data requests through social media or any channel not listed here. All policy-related requests should include your registered account reference so we can locate and verify your record before responding.
Open the chat widget from any page on cs9999 while logged in. Identify your query as a privacy or data matter so the agent can route it correctly.
Send your data enquiry to the support email address shown in your account settings. Include your registered mobile number and a clear description of what you are requesting.
The help section inside your account dashboard lists current contact routes and any posted updates to this policy. Check there first if a contact detail has changed.
Keeping your account data accurate and protected is a practical commitment, not a marketing line. Here is how we handle the four areas that matter most to your account security and data rights on cs9999.
We keep account and transaction records for as long as your account is active and for a defined period after closure. Retention periods follow the requirements applicable to our operating regions. You can request a summary of what is held at any point through the support channel.
We use cookies to maintain your login session and remember device preferences between visits. No advertising cookies from third-party ad networks are set without a separate disclosure. You can clear session cookies from your browser or mobile settings at any time.
Login sessions are protected and flagged when access comes from an unrecognised device. If you notice a session you do not recognise in your account history, use the account settings page to end active sessions and then contact support.
When this policy changes in a material way, we post a notice in your account dashboard and update the effective date at the top of this page. Continuing to use your account after a posted update means you have seen the revised terms.
These are the questions we hear most often about how cs9999 handles account data. If your question is not answered here, use the support contact routes listed above.
At registration we collect the name, mobile number and any wallet identifier you provide. Device and session data is recorded automatically when you log in. We collect only what is needed to run your account and process transactions through Nagad, Rocket or Bank Transfer.
We share data only with service partners — such as payment processors handling a Rocket or Nagad transfer — and only to the extent needed to complete that service. We do not sell personal data. Partners are required to handle it under terms consistent with this policy.
Log in and open account settings to see your stored profile fields and wallet references. For a more detailed summary of all records we hold, send a data enquiry through the published support channel with your account reference and we will compile a response.
Most fields can be edited directly in account settings. For wallet identifiers linked to Nagad, Rocket or Bank Transfer, submit a correction request through support so the change is verified before being applied to your account record.
We retain account and transaction records for a defined period after closure, in line with the requirements applicable to our operating regions. The exact period may vary depending on local law and eligible regions. You can ask for a retention summary through support at any time.
We use cookies to keep you logged in and remember your device preferences. These are session and functional cookies, not advertising trackers from third-party networks. You can clear or block cookies through your mobile browser or device settings, though this may affect how your session behaves.