Sports / Mobile
aca35 collects only the account and transaction data needed to run your wallet, process payments through bKash, Rocket, and Upay, and keep your session records accessible to you. This policy explains what we hold, why we hold it, and the choices available to you — with access depending on your local law and eligible region.
When you open an account with us, we collect the information you provide during registration — your name, contact details and the payment credentials you use to fund your wallet. Every transaction processed through bKash, Rocket or Upay generates a record that stays attached to your account history. We use that data to verify your identity, process your deposits and withdrawals, and respond to any account queries you raise through our support route. We also collect technical data — your device type, browser session and IP address — to detect unusual access patterns and keep your account secure. This data is not sold or shared with third parties for marketing. Where we share data with payment processors, it is only to complete the transaction you initiated. Retention periods apply: we keep your records for as long as your account remains active and for any additional period required by applicable regulations in your jurisdiction. Availability of this service depends on your local law and eligible region. The chips below reflect the payment context in which your data is most commonly generated.
Not every part of your experience on aca35 falls under the same data rules. This section draws the boundary clearly so you know what this policy covers and what sits outside it.
Any login, session start or account-settings change is covered by this policy. We log the time, device and IP of each access event so you can query any unfamiliar entry through our support channel.
Every deposit and withdrawal processed via bKash, Rocket or Upay generates a record held in your account history. That record falls fully within this policy, including how long we retain it and who can view it.
General browsing of the lobby, game pages or odds listings does not create personally identifiable records tied to you unless you are signed in. Anonymous session data is aggregated and not linked back to your account.
Payment processors, game studios such as Pragmatic Play or PG Soft, and any external link you follow operate under their own privacy terms. We do not control those policies; check each provider's published terms directly.
You have concrete actions available to you at any point. Start by reviewing your transaction history: every deposit, withdrawal and session entry is listed in your signed-in account area, sorted by date, so you can cross-check any record against your bKash or Rocket statement. If something looks incorrect — a wrong name, an outdated contact number, a payment detail that no longer applies — you can request a correction by raising a ticket through the support route published on the site. We will confirm receipt and tell you what we can update and what must stay on record for compliance reasons. If you want to understand what specific data we hold against your account, you can submit a data inquiry through the same contact path; we will respond with a summary of the categories we hold. Closing your account does not immediately erase all records — retention rules apply based on applicable regulations in your jurisdiction. The steps below outline the four main actions and where to start each one.
Open your account area while signed in and check the transaction history tab. Every bKash, Rocket and Upay entry is timestamped and listed there for you to compare against your own wallet records.
If a name, contact number or payment detail in your profile is wrong, raise a correction request through the support channel. We will confirm what can be updated and note any fields that must remain unchanged for verification purposes.
Submit a data inquiry via our published contact route asking for a summary of the categories of information we hold on your account. We will respond with the categories held, not a raw data export by default.
Account closure requests go through the same support route. We will explain which records are removed immediately and which are retained under applicable regulations before processing the closure.
Privacy questions, data correction requests and account-closure inquiries all go through the contact routes we publish on the site. Use the channel that suits you; each one routes to the same team responsible for account and data matters.
Open the live chat widget from any page while you are signed in. Identify your query as a privacy or data matter so the agent routes it to the right team immediately.
Send your data inquiry or correction request to the email address listed in the Contact section of our site. Include your registered account identifier so we can locate your record without asking for sensitive details over email.
The Help section in your signed-in account area includes a form specifically for account and data queries. Submitting through this form attaches your account ID automatically, which speeds up the review process.
We use industry-standard encryption on all data transmitted between your device and our servers, including payment instructions sent through bKash, Rocket and Upay. Session cookies keep you signed in across pages; analytics cookies help us understand how account areas are used without recording your personal identity. You can manage cookie preferences through your browser settings at any time.
All data in transit between your device and our platform is encrypted. This includes login credentials, account details and payment instructions routed through bKash, Rocket or Upay. We do not transmit payment credentials in plain text.
We use session cookies to maintain your signed-in state and analytics cookies to understand how account areas are navigated. No cookie on this site is used to build an advertising profile. You can clear or block cookies via your browser settings.
We keep your account data and transaction records for as long as your account is active and for any additional period required by applicable regulations in your jurisdiction. When a retention period ends, we delete or anonymise the data.
When this policy changes in a material way, we post a notice in your account area before the change takes effect. Continuing to use your account after that notice means you have seen the updated terms. Check the policy page for the current version date.
These are the questions we hear most often about how aca35 handles account data, transaction records and your rights under this policy.
We collect the details you enter during registration — name, contact information and your chosen payment method details such as your bKash or Rocket number. We also log device type, IP address and session timestamps to protect your account from unauthorised access.
You can view your transaction history, session log and account details directly in your signed-in account area. For a broader summary of data categories we hold, submit a written inquiry through the support channel and we will respond with the relevant categories.
We share payment credentials only with the payment processor needed to complete your transaction — for example, bKash or Rocket — and only to the extent required to process it. We do not sell, rent or pass your payment details to advertisers or unrelated third parties.
Records are kept for as long as your account is active and for any additional period required by applicable regulations in your jurisdiction. When a retention period ends, data is deleted or anonymised. You can ask our support team about the specific period that applies to your account.
Raise a correction request through the support channel — live chat or the email address published on the site. Tell us which field is incorrect and what the right detail should be. We will confirm what can be updated and flag any field that must stay unchanged for verification compliance.
Closing your account does not erase all records immediately. We retain transaction history and identity records for the period required under applicable regulations in your jurisdiction. Our support team will explain exactly what is removed at closure and what is retained before processing your request.