Slots / Sports
ca999 collects only the account and transaction data needed to run your wallet, verify your identity and keep your session secure. This policy tells you exactly what we hold, why we hold it, and the steps you can take to review or correct it — your access to that process depends on your local law and eligible regions.
When you open an account, we collect the registration details you provide — name, contact information and any identity document you submit during verification. When you fund your account or request a withdrawal using Nagad or Upay, we log the transaction reference, amount and wallet identifier attached to that payment. We do not store full mobile banking credentials; the payment is processed through the respective payment rail and we receive only the confirmation record your wallet generates. We also collect session data: device type, browser version, IP address range and the pages you navigate within the platform. This helps us detect unusual access patterns and keep your account safe. Cookies and local storage tokens are used to maintain your signed-in state and remember your language preference. You can clear these through your browser settings, though doing so will end your active session. Our data collection practices apply to the extent permitted by your local law and to accounts in eligible regions. We do not sell your personal data to third parties, and we do not share it with advertisers. Where a regulatory body with jurisdiction over your account requests disclosure under applicable law, we follow that process and, where permitted, notify you.
This policy covers data ca999 processes directly through the platform and its configured payment rails. It does not extend to third-party services you reach from our pages, and it applies only where your local law and the eligible region terms permit account access. Understanding the boundary between what we govern and what a third party governs helps you know where to direct a data question.
Any data you enter during registration, login or identity verification on the ca999 platform falls inside this policy. That includes your email address, contact number and any document image you upload to the account verification flow.
Payment records tied to Nagad and Upay deposits or withdrawals processed through the platform wallet are covered. We hold the confirmation reference and the amount; the mobile banking app on your device operates under its own privacy terms.
Browsing behaviour within the platform — which sections you visit, how long a session runs, device and connection data — is covered. This data is used for security monitoring and to improve navigation, not for external profiling.
Links to payment providers, game content studios or external support tools operate under their own data policies. ca999 does not control how those services handle data once you leave our platform environment, and this policy does not cover those interactions.
Your account area is the first place to check when you want to review or update what we hold. The profile section shows the contact details and verification status on record. If something there is incorrect — a misspelled name, an outdated mobile number, or an old wallet reference — you can submit a correction request directly from that page. We will process the request and confirm the change to your registered contact. Where a correction affects a payment record, such as an unmatched Nagad or Upay reference, the support team will cross-check against the transaction log before confirming the update. If you want to know exactly what data we hold on your account, you can raise a data access request through the support channel. We will respond with a structured summary of the personal data on file. Requests to close an account and delete associated personal data are also handled through support; retention rules set by applicable law may mean certain transaction records are kept for a defined period even after closure, and we will explain which records those are when you make the request.
Open the profile section of your signed-in account to see the contact details, wallet references and verification status currently on file. That is the fastest way to spot anything that needs correcting before raising a formal request.
Submit a correction through the account settings page. For changes that affect a Nagad or Upay payment reference, attach the transaction confirmation from your wallet so the support team can match it to our log quickly.
If you want a full summary of the personal data we hold, contact us through the published support route. We will prepare and send a structured account data summary to your registered contact address.
An account closure and deletion request goes through the same support channel. We will confirm which records must be retained under applicable law and explain the timeline for removing the rest.
If your question is not answered by the policy text above, or if you need to raise a formal data request, the routes below are the ones we actively monitor for privacy-related enquiries. All three connect to the same account support team; choose the route that suits how you work.
The live chat widget inside your signed-in account area connects you to account support. Start the conversation with your account reference and the nature of your data question so the agent can pull the right record without delay.
Send a written data or privacy request to the support email address published in the platform's help section. Include your registered contact detail and, where relevant, the Nagad or Upay transaction reference you are asking about.
The help centre, accessible from the account menu, contains step-by-step articles on data requests, correction forms and account closure. Reading the relevant article before contacting support often speeds up the process.
Data security on the platform covers four areas: storage, access control, retention and communication. Account records and payment references are stored on servers with access restricted to authorised operations staff. Your session is protected by an encrypted connection; when you sign in, the platform does not expose your full wallet identifier in any page view. We keep transaction records — including Nagad and Upay confirmation references — for as long as required by applicable rules in your region, and we review retention schedules periodically. When we need to contact you about your account or a data matter, we use only the registered contact on file. We will never ask for your mobile banking PIN or password through any channel.
We use session cookies to keep you signed in and remember your settings. You control these through your browser. Clearing them signs you out and resets preferences, but it does not delete the account data held on our servers.
Nagad and Upay transaction references are logged against your account but not displayed in full to other account holders or in shareable views. You can see your own transaction history in the wallet section of your account.
We hold account and payment data for the period required under applicable law in eligible regions. When that period ends, data is deleted or anonymised. You can ask us at any time which retention period applies to your account.
Only the verified account holder can request a correction or deletion. We confirm identity against the registered contact before processing any change. This step protects you from unauthorised alterations to your account record.
The questions below cover what we hear most often about data rights, account records and how to act on them. If your question is not here, the support routes in the section above will connect you to the account team directly.
We collect the registration details you submit — name, contact number and, where verification is required, a copy of your identity document. We also log device and session data for security purposes. We collect only what is needed to run and protect your account.
We store the transaction reference and amount that the payment rail sends us as confirmation. We do not store your full mobile banking credentials or PIN. The payment itself is processed by the Nagad or Upay system, and we receive only the resulting confirmation record.
Sign in and open the profile section to see what is on record. For a full structured summary of all personal data associated with your account, raise a data access request through live chat or the support email address listed in the help centre.
Yes. Submit a correction request from the account settings page or through support. Deletion requests are also handled through support. Some transaction records may be retained for the period required by applicable law in your region — we will explain which ones and for how long.
We do not sell your data to advertisers or share it for commercial profiling. Where a regulatory body with jurisdiction over your account requests disclosure under applicable law, we follow that process. Aside from that, your data is not passed to external parties.
This policy applies to accounts in eligible regions where access is permitted under local law. Whether your account falls within those eligible regions depends on your local law and the eligibility conditions confirmed at registration. Check the terms displayed during registration for the applicable regional conditions.