App / Slots
a880 keeps this policy clear so you know exactly what data we collect when you use your account, how we store it, and what choices you have. Access to our platform depends on your local law and eligible regions.
When you open an account with us, we collect the details you provide at registration — your name, contact information and any identity verification material we request. We also record transaction activity linked to your account wallet, including payment method references such as bKash, Nagad or Rocket mobile numbers used during a deposit or withdrawal process. We do not store full wallet credentials; we record only the reference data needed to process and verify your transaction history. Session data — device type, browser, IP address and page navigation — is logged automatically each time you access the platform. We use this to keep your session secure across devices and to detect unusual account activity. Cookie data helps us remember your preferences between visits so you do not have to re-enter settings each time. We do not sell your personal data to third parties. We share it only where required to complete a payment, verify identity, or comply with a lawful request. The specific data we share and the parties involved are set out in the scope section below. This policy applies to all account holders regardless of which device or payment channel they use, and eligibility for our platform depends on your local law and the eligible regions we serve.
Mobile wallet reference data noted for transaction records; full credentials are never stored on our side.
Nagad account references appear in your transaction history only; we do not retain your Nagad PIN or password.
Rocket payment references are logged against your account wallet for verification purposes only.
This policy covers data generated when you interact with your a880 account directly — from the moment you land on the site through every session action you take. Some areas fall clearly inside this policy; others sit with third-party providers who maintain their own separate terms. Understanding the boundary helps you know who to contact when a data question arises.
All data collected during login, session activity and account settings changes is covered by this policy. This includes device records, session tokens and any identity verification steps completed inside your account area.
Payment references linked to bKash, Nagad or Rocket are covered here. We hold only the reference data necessary for record-keeping; the payment processor or mobile wallet operator handles the actual fund movement under their own policy.
Game interaction data — which categories you open, how long a session runs — is collected and covered by this policy. We use it for account security and to keep your preferences consistent across devices.
External links, game studio platforms and any third-party service you reach from our site operate under their own privacy terms. We do not control or take responsibility for data handling outside our own platform boundary.
You have practical steps available to you at any time. Start by reviewing the data held against your account — log in and open the account profile section where your registered details and linked payment references are visible. If any information is incorrect, you can update standard fields directly in the profile area; for identity documents or verification records, submit a correction request through our support route and we will process it from our side. Raising a question about how your data is used is straightforward. Use the support contact listed in the section below and describe the specific record or data category you are asking about. We do not require a formal legal notice to act on a reasonable data question from an account holder. If you want to close your account and request that we delete your personal records, you can make that request through the same support channel. We will confirm receipt and outline the steps involved, noting that some records may be retained where required by applicable law or for the purposes of resolving a payment dispute.
Open your account profile after logging in to see your registered details and any payment references on file.
Update contact fields directly in the profile section; for identity documents, contact support with the specific correction needed.
Write to us through the published support route naming the specific record or category you are asking about.
Submit a closure and deletion request via support; we will confirm receipt and explain what is retained under applicable law.
If this policy raises a question you cannot resolve by reviewing your account directly, these are the routes we publish. Use the channel that fits your situation; describe the specific data or account record involved so we can respond accurately.
Open the chat widget from any page while logged in. State that your query relates to a privacy or data matter so the team can route it correctly.
Send your data question to the support email address shown in your account settings. Include your account reference and the specific record you are asking about.
The Help Centre contains published articles on account data, session controls and how to submit a correction or deletion request without waiting for a live agent.
We keep data handling practices visible so you can verify what applies to your account. Session cookies, retention periods and security controls are outlined here so there are no surprises when you review your account settings.
We use session cookies to keep you logged in across page loads and to remember your display preferences. You can clear cookies through your browser settings at any time; doing so will end your active session and reset preferences.
Account and transaction records are kept for as long as your account remains active and for a period afterward as required by applicable law. When you request deletion, we confirm what can be removed and what must be retained.
Access to your personal data on our side is restricted to staff who need it to process support requests or verify transactions. We do not expose account records to general operational teams.
When we update this policy, the revised version is published on this page. Continuing to use the account after a change is posted means you have seen the updated terms; check this page periodically to stay current.
These are the questions we receive most often about account data, cookie use and your rights under this policy. If your question is not here, contact us through the support routes listed above.
We collect the registration details you enter — name, contact information and any verification material requested. We also log session data like device type and IP address automatically. Payment references such as a bKash or Nagad number are recorded against your transaction history.
We share data only where necessary: to process a payment through your chosen method, to verify your identity, or to respond to a lawful request. We do not sell your personal data. Third-party services you reach from our site manage their own data under their own policies.
Log in and open the account profile section. Your registered contact details and linked payment references are visible there. For identity documents submitted during verification, contact support and request a summary of the records held.
Yes. Submit a deletion request through our support contact channel. We will confirm receipt and explain which records can be removed immediately and which must be retained under applicable law, for example records tied to a payment dispute or a legal obligation.
We use session cookies to maintain your login state and remember display preferences between visits. You can disable or clear cookies in your browser settings at any time. Doing so will log you out of your current session and reset any saved preferences on the site.
Mobile wallet numbers like bKash, Nagad or Rocket are stored as payment references in your transaction history only. We do not store your wallet PIN or password. These references help us verify deposit and withdrawal records when you raise a support question.