Casino / App
a889 collects and uses your personal data only for what your account actually needs — login access, transaction records and support contact. What we collect, why we hold it and how you can act on it is set out clearly in the sections below.
When you open an account with us, we collect the information you provide directly: your name, contact details, and the credentials you set for login. When you make a deposit or withdrawal through Nagad, Upay or Bank Transfer, we record the transaction reference, amount and timestamp against your account wallet — not the full payment credentials held by your payment provider. We also collect device and session data automatically: your browser type, the pages you visit on a889, and how you navigate between sections. This helps us keep the site working correctly on mobile and on desktop without requiring you to contact support for routine errors. We do not sell your personal information to third parties. Data shared with payment processors is limited to what those processors need to complete the transaction you initiated. Retention periods depend on account status and applicable rules for the regions where access is permitted. If your account is closed, we hold only what is required to meet our record-keeping obligations, and no longer. Your use of a889 and any data we hold is subject to your local law and the eligible regions in which access is available.
This policy covers your interactions with a889 directly — your account, the lobby, support channels and payment routes we operate. It does not extend to external services you reach through links on our pages, nor to the data practices of payment providers like Nagad or your bank once a transaction leaves our platform. Understanding where our responsibility starts and ends helps you know who to contact if a question falls outside our scope.
Data collected during login, account creation and session activity falls fully within this policy. We control how that data is stored, who can view it and how long it is retained against your account record.
We record payment events on our side — reference numbers, amounts, method used (Nagad, Upay, Bank Transfer). The payment provider's own handling of your wallet credentials is governed by their separate policy, not ours.
Pages, game lobbies, promotional notices and support articles hosted on a889 are covered here. How you browse between sections and what device you use is logged for site performance, not for advertising profiling.
Game studios and external links are outside the scope of this policy. Once you follow a link away from a889 or interact with a third-party frame, their own data terms apply and we have no control over what they collect.
You have practical choices over the data we hold. The most direct route is your account settings page — open it after login and you will see the profile fields we store, including your contact details and linked payment method entries. If something is wrong or out of date, you can edit it there directly or send a correction request through our support channel. For a full record of what we hold against your account — transaction history, session logs, the contact information on file — you can submit a data access request through the support route published on this site. We will respond using the contact details on your account. If you believe data is being held incorrectly, or that your access to a889 should be reviewed given your local law and eligible region, raise it through the same support contact. We do not require a specific legal basis statement from you to begin a review; a clear description of what you want corrected or explained is enough to start the process.
Submit a data access request via our published support contact and we will compile the account data, transaction references and session records we hold under your account ID.
Edit contact details and profile fields directly in account settings after login. For fields that cannot be changed without verification, use the support channel and follow the steps shown there.
If any part of this policy is unclear — how we use your data, what we share with payment processors, or how long we retain records — contact support with a specific question and we will give you a direct answer.
When you close your account, tell us in your closure request if you want personal data removed beyond the minimum we are obliged to retain. We will confirm what can be deleted and what must stay under our record-keeping obligations.
For any question about how your data is handled, the fastest route is the support contact published on a889. Use the channel that matches your query — a live chat message for quick clarifications, email for formal requests that need a written trail, or the on-site contact form if you prefer not to use either. State your account-linked contact detail so we can locate your record without delay.
Open the chat widget on a889 and describe your privacy question. This is the fastest route for account-linked questions like checking what contact detail we have on file for your Nagad or Upay transactions.
Send a written request to the support email address shown on the contact page of this site. Include your account ID and a clear description of the data question or correction you need. Email is the recommended route for formal data access requests.
The contact form on a889 routes your message to the same support team without requiring you to open a separate email client. Select the privacy or account category from the dropdown so your query reaches the right person faster.
Account security, data retention and your ability to act on what we store are the practical parts of this policy that affect you most directly. Here is how each area works on a889.
We use cookies to keep your session active while you move between the lobby, your account wallet and the payment pages. You can manage cookie preferences through your browser settings. Clearing cookies will log you out; it does not delete stored account data.
Your login credentials are stored in hashed form — we do not hold your raw password. If you suspect your account has been accessed without your knowledge, use the password reset path shown on the login page and contact support immediately.
We retain account records and transaction references for as long as your account is active and for the period required by our record-keeping obligations after closure. The specific retention period depends on applicable rules for your eligible region.
All data change requests — corrections, access requests, closure and removal requests — go through the support routes on a889. We do not accept data requests sent through third-party channels or social media accounts claiming to represent us.
These are the questions we hear most from people reviewing this policy before or after opening an account with us. If yours is not here, contact support through the routes above.
We collect the name, contact details and login credentials you enter during account creation. We also record basic device and session data when you browse the site. We do not collect payment wallet passwords or full card numbers — those stay with your payment provider.
We pass only the transaction reference and amount needed to process a payment you initiate. Your full account profile is not shared with payment providers. Each provider then applies their own data policy to the information they receive from the transaction.
Submit a data access request through the support contact published on a889. Include your account ID and the specific records you want to review — transaction history, profile data or session logs. We respond to the contact detail registered on your account.
Some fields — display name, email address — can be edited directly in account settings after login. For fields tied to identity verification, contact support and follow the correction steps shown there. We do not require a formal legal statement to process a straightforward correction.
We retain the minimum records required by our obligations after closure — typically transaction references and the account identification details. Personal profile data beyond that is removed. The exact period depends on the applicable rules for your region and the eligible area in which your account was active.
Session cookies are required to keep you logged in while you navigate between the lobby and your account wallet. You can block non-essential cookies through your browser settings without losing access, but doing so may affect how some pages display on mobile.