Slots / Sports
At cd 66, your information — including how you access the platform and the payment records tied to your wallet — is handled under a clear privacy framework. What we collect, why we keep it, and how you can act on it is set out in this policy. Access and eligibility depend on your local law and the regions where this service is available.
When you open an account on cd 66, we collect the information needed to run that account — your registration details, session activity, and transaction records tied to payment methods such as Nagad, Upay, and Bank Transfer. This data lets us process your requests, maintain your wallet history, and respond when you contact support. We do not sell your personal data to third parties for their own marketing. Data shared with service partners — payment processors, security verification systems — is limited to what those partners need to carry out the specific task. Each partner operates under a data-processing agreement with us. We keep account and transaction records for as long as your account remains active and for a retention period after closure, as required by the operational and regulatory standards that apply to the regions where this service runs. If you close your account, you can request a summary of what we hold before deletion is processed. This notice applies to the cd 66 website at cd 66 and any account-linked mobile sessions. It does not extend to third-party sites you may reach through links on our pages. Whether this service is accessible to you depends on your local law and the eligible regions we operate in — review those terms in your account area.
Payment records from Nagad transfers are logged against your account wallet. These records are retained for the operational period and are accessible from your account history. We do not share transaction values with unrelated third parties.
Upay deposit and withdrawal entries are stored in your account ledger. You can review each entry from the transaction history section. Queries about a specific entry can be raised through the support route published on the site.
Bank Transfer activity is recorded with reference numbers visible in your account. If a transfer is delayed or unclear, the reference number in your history is the detail our support team needs to locate the record.
Each login session generates an access log — device type, browser, and time. This is used for account security checks only. You can request a copy of your session history through the data-access route described in this policy.
This policy draws a clear line between what falls under our responsibility and what sits outside it. Understanding the scope helps you know which channel to use when you have a question about your data.
Anything generated when you log in — session tokens, device records, IP logs — falls fully within this policy. These are held by us and are subject to your access and correction rights described below.
Deposit and withdrawal records processed through Nagad, Upay, or Bank Transfer are covered here. The payment processor handles the transfer itself under its own terms; we hold the account-side record and that record is yours to review.
Pages you browse, games you open from studios such as Pragmatic Play or CQ9, and lobby navigation events are logged for service improvement. This data is held in aggregate form and linked to your account only where needed for account support.
Links to external sites, payment-provider portals, or identity-verification services operate under those providers' own privacy terms. Once you leave cd 66, this policy no longer applies. Check the third-party site's own notice before submitting data there.
You have a set of concrete actions available under this policy. You can request a copy of the personal data we hold on your account — this includes registration details, session logs, and transaction history from payment methods like Nagad and Upay. Submit the request through the support route published on the site, and we will confirm receipt and outline the next steps. If any account detail is incorrect — a name spelling, a contact address, a linked wallet number — you can raise a correction request through the same support channel. Our team will verify the change against the account record and update it. For questions about how a specific data category is used, or to ask that we stop using your data for a particular purpose, contact us through the published support path. We will respond with the relevant section of this policy and what options are available to you. Closing your account does not automatically erase all records immediately — some are retained for the operational period described above — but you can ask for a retention summary before you proceed.
Open the transaction history section in your account to see payment entries and session logs. For a full data export, submit a request through the support route on the site.
If a name, contact detail, or linked wallet entry is wrong, raise it via the published support channel with your account reference and the correct information.
For questions about a specific data category or how it is used, contact support directly. Reference the relevant section of this policy in your message so the team can respond to the right point.
Before closing your account, you can ask what data we hold and how long it will be retained. Submit this through the support channel before initiating closure so the information is available to you.
If you have a question about this privacy policy or want to act on one of the rights described above, use the contact routes published on the site. We do not publish response time commitments here — check the support section of your account for current availability details.
The live chat route on cd 66 connects you to our support team. Use this for account-level data questions, correction requests, or to raise a concern about how your information is handled.
A written privacy request submitted by email creates a record of your query and our response. The email address is listed in the contact section of the site. Include your account reference in the subject line.
Your account area includes a help and support section where data-related requests can be submitted directly. This route ties the request to your account record, which speeds up the verification step.
Our approach to data handling covers four areas: what we collect and why, how we protect it, how long we keep it, and how you request changes. Each area has a clear process rather than a general statement.
We use cookies to maintain your login session and to understand which parts of the site you use. You can review and adjust cookie preferences from the site settings. Essential session cookies cannot be turned off without ending your session, but analytics cookies can be declined.
Account access is protected by login credentials you control. Session logs record device type and access time so unusual activity can be flagged. If you notice a session you do not recognise, contact support through the published route immediately.
Active account data is held while your account is open. After closure, records tied to payment activity — Nagad, Upay, Bank Transfer entries — are retained for the operational period required by the service standards applying to eligible regions. A summary of what is held is available on request.
To correct, export, or ask about the deletion of your data, contact us through the support channel with your account reference. We will confirm the request in writing and follow the steps set out in this policy. Availability of all features depends on your local law and eligible regions.
Questions we hear most often about how cd 66 handles account and payment data — answered directly.
We collect the registration details you provide, your login session records, and transaction entries linked to your payment method — Nagad, Upay, or Bank Transfer, depending on which you use. We do not collect more than is needed to operate and support your account.
Yes. Your account history section shows each payment entry with a reference number and date. If an entry is unclear or appears incorrect, contact support through the published route with the reference number and we can locate the underlying record.
Data is shared only with partners who carry out a specific task on our behalf — payment processors, security verification systems. Each operates under a data-processing agreement. We do not sell personal data for third-party marketing. External sites you reach via links on our pages have their own privacy terms.
Some records, particularly those tied to payment activity, are retained for an operational period after closure. The length depends on the standards applying to the eligible regions where this service runs. Before closing, you can request a summary of what we hold through the support channel.
Submit the request through the support route on cd 66 — live chat, email, or the account help section all work. Include your account reference so the team can locate the right record. We will confirm receipt and outline the next steps in writing.
Yes. The policy covers all account-linked sessions, whether you access cd 66 on a mobile browser or a desktop. Session logs record device type, so mobile and desktop activity are both visible in your account history. Whether the service is available to you depends on your local law and eligible regions.