Slots / Mobile
cd9999 collects only what we need to run your account, process transactions through bKash or Bank Transfer, and keep your session records accurate. This policy explains exactly what we hold, why we hold it, and the steps you can take to review or correct it — access and eligibility depend on your local law and the eligible regions we serve.
We collect information in three broad categories. First, account registration data: the name, contact details and credentials you provide when you open an account with us. Second, transaction data: every deposit and withdrawal you make — including records tied to bKash and Bank Transfer — is logged against your account wallet so you can review the full history from your dashboard. Third, session data: device type, browser session timestamps and in-session activity that help us keep your account functional and identify unusual access patterns. We do not sell your personal data to third parties. Where we share data with payment processors such as bKash or Bank Transfer partners, it is solely to complete the transaction you initiated. We retain records for as long as your account is active and for any period required under applicable financial or regulatory rules in the eligible regions we serve. If you close your account, we will retain only what we are required to keep under those rules, and no longer. All stored data sits behind access controls. Use of this platform depends on your local law and the eligible regions we support.
Every bKash deposit or withdrawal linked to your account is stored as a timestamped record. You can view these directly from your account wallet page without contacting support.
Bank Transfer transactions are logged with reference numbers and amounts. These records are available in your account history and are retained in line with applicable financial rules.
Login credentials are stored in encrypted form. We do not store plaintext passwords, and our access controls restrict which internal systems can read account authentication data.
Session timestamps and device identifiers are recorded each time you log in. You can review recent session activity from your account security settings to spot any access you did not initiate.
Not everything on your screen falls under this policy. We want to be clear about what we are responsible for and where our coverage stops — particularly when your session touches third-party payment processors or external services. The four areas below draw that line plainly so you know which entity to contact depending on the data question you have.
Your cd9999 account — registration data, login history, session records and wallet balance — falls fully within this policy. Any question about what we hold on you in these areas should come to us directly through the support route listed on the contact page.
We log your transaction references on our side. However, the payment processor — bKash or your bank — also holds its own records under its own privacy terms. For disputes about the processor's data handling, you will need to contact that provider directly.
Cookies and local storage used on cd9999 to maintain your session, remember preferences and measure page performance are covered here. We do not use third-party advertising cookies that track you across unrelated sites.
Game content is delivered by studios available in our lobby. Those studios operate their own software environments. We do not control their internal data practices, and their terms govern what happens within their game client — not this policy.
You have real, actionable options — not just abstract rights. Your account dashboard is the first place to start. From there you can pull up your full transaction history, including every bKash and Bank Transfer record attached to your wallet, and download or review it at any time. If you find an error in your registered details — a name spelling, a contact number, an email address — you can correct most fields directly inside account settings without waiting for a support response. For changes that require identity verification, the account page will show you the documents needed and the fields to fill in. If you want to know precisely what data we hold beyond what the dashboard shows, or if you want to request deletion of data we are not legally required to retain, you can raise that through our published support route. We aim to respond to data queries within the timeframe shown on our support page — we do not publish a fixed SLA here because it can vary by request type. Eligibility to exercise these rights may depend on your local law and the region from which you access the platform.
Open the account history section to see transaction logs, session timestamps and wallet activity. Everything tied to your bKash or Bank Transfer deposits is listed there with reference numbers and dates.
Most contact and profile fields are editable directly from account settings. For fields locked behind verification, the page will tell you which document to submit and where to upload it.
If you want a full account of the data we hold, or you believe something is inaccurate and you cannot fix it yourself, contact us through the support route on our published contact page with your registered account details.
You can ask us to delete data we are not required to keep. Submit the request through support with your account identifier. We will confirm what can be removed and what must be retained under applicable rules.
If this policy raises a question you cannot resolve from your account dashboard, the routes below are the right place to start. Use the channel that suits your query type — simple account questions move fastest through live chat, while formal data requests should come through email so there is a written record on both sides. We do not publish operating hours here because they are shown on the support page itself and may change; check there for the current schedule.
Open the chat widget from any page on cd9999. Use this for quick questions about what data appears in your account, session history or wallet records. The current availability window is shown inside the widget.
For formal data queries — access requests, correction requests or removal requests — email us at the address published on our contact page. Include your registered account identifier so we can locate your records without delay.
The help section inside your signed-in account area covers the most common questions about transaction records, session history and account data. Start there before raising a ticket — many queries are resolved without waiting for a reply.
We apply access controls and encryption to the data we store, and we limit internal access to account records on a need-to-know basis. Payment data linked to bKash and Bank Transfer is handled in transit using standard secure protocols; we do not store full payment credentials on our own servers beyond the reference identifiers needed to reconcile your wallet. Cookies that keep your session active are scoped to cd9999 and are not shared with advertising networks. We review our data handling practices when we make material changes to the platform, and we update this policy page when those changes affect how your information is used. The date of the most recent update appears at the bottom of this policy. If an update changes something that affects you, we will notify you through your registered contact details before the change takes effect.
Account credentials and personal details are stored in encrypted form. Plaintext passwords are never retained. Internal systems that need to verify identity do so through secure token exchange, not by reading raw credential fields.
We store only the transaction reference identifiers returned by bKash or Bank Transfer — not full account numbers or card details. You can view these references in your wallet history and use them to cross-check with your payment provider.
Session and preference cookies are set only on cd9999. You can clear them from your browser settings at any time. Clearing session cookies will log you out; preference cookies only affect display settings and do not hold personal account data.
When we make changes that affect how we use your data, we update this page and notify you through your registered contact method before the changes apply. Minor clarifications that do not change data use are updated silently with a revised date.
The questions below cover what we hear most often about account data, transaction records and your rights under this policy. If your question is not here, the support routes in the section above are the right next step.
We collect the registration details you enter — name, contact information and login credentials — plus the transaction records generated when you use bKash or Bank Transfer. Session data such as device type and login timestamps is also logged to support account security.
Yes. Every deposit and withdrawal, including bKash and Bank Transfer entries, appears in your account wallet history with dates and reference numbers. You do not need to contact support to access this view — it is available as soon as you log in.
We share data only where it is necessary to complete a service you initiated. Payment processors such as bKash receive the minimum data needed to process your transaction. We do not sell personal data and do not share it with advertising networks.
Most profile fields are editable in account settings. Fields that require identity verification will show you the documents needed and where to upload them. If you cannot locate the edit option, raise a query through email support with your account identifier.
After account closure, we retain only what applicable financial or regulatory rules in the eligible regions we serve require us to keep. Data that falls outside those requirements is removed. The specific retention period depends on the category of data and local rules.
Go to the security section of your account settings, where recent session timestamps and device identifiers are listed. If you see an entry you do not recognise, change your password immediately and contact us through live chat or email so we can flag the activity on our side.