Casino / Sports
ban880 is direct about one thing: your account data belongs to you, and we handle it with a clear, documented process. This policy sets out exactly what we collect, why we collect it, and what choices you have — access and eligibility depend on your local law and eligible regions.
When you open an account on ban880, we collect the information needed to verify your identity, process transactions and keep your account secure. This includes the name and contact details you enter at registration, the device and browser information your session sends automatically, and the transaction records tied to your chosen payment method — whether that is Nagad, Upay or Bank Transfer. We do not collect payment credentials directly; those pass through the payment rail you select, and only a reference record lands in your account history. We also collect session logs to detect unusual access patterns and to keep your wallet activity tied to a verified device. Cookies and similar storage are used to maintain your logged-in state across pages, remember your language and layout preferences, and measure how pages load on your mobile connection. You can adjust cookie behaviour through your browser settings, though some functions depend on them. Data we hold is kept for the period required to maintain your account and meet our obligations under applicable law. If you close your account, retention periods depend on the jurisdiction and legal basis for holding each record. For any questions about what specific data we hold for your account, our support contact is published in the Support section of this policy.
This policy covers the data ban880 processes directly through your account. It does not extend to every service or link that may appear alongside your session. Understanding the boundary helps you know who to contact when a question arises. Each of the four areas below has a distinct scope so you can locate the right contact without going in circles.
Covers all data collected when you register, log in or reset credentials on ban880. This includes your email, phone number, and the device fingerprint recorded at each login. We process this directly and you can request a copy through our support channel.
Covers the reference data generated when you deposit or withdraw using Nagad, Upay or Bank Transfer. The payment rail itself operates under its own privacy terms; we hold only the transaction reference, amount and timestamp visible in your account wallet history.
Covers the session and preference data stored when you browse the lobby, load game pages or interact with navigation. This data is used to keep your session active and to measure page performance. It does not include the content of any game round.
Falls outside this policy. External links, payment processors and game content studios each operate under their own data terms. We do not control how those parties handle data once a request leaves our platform. Check their published policies for detail.
Your account data is not locked away from you. Once logged in, the account settings page shows the contact details and payment references we hold for your profile. If any detail is wrong — a misspelled name, an outdated phone number, or a Nagad reference that no longer matches your active wallet — you can update most fields directly from the settings screen. For records you cannot edit yourself, such as historical transaction logs or identity verification data, a written request to our support team starts the correction process. We aim to respond to correction requests within the timeframe set by applicable law, which varies by jurisdiction. If you want to understand what data we hold beyond what is visible in your account, a subject access request via our published email route is the right path. We do not require you to give a reason for asking. Closing your account does not automatically erase all records; some are kept for the period required by law or to resolve any open transaction queries.
Log into your account and open the settings page to see the contact details, wallet references and transaction history we currently hold for you. This is the fastest way to check what is on file.
Update your phone number, email or payment reference directly in account settings where the field is editable. For fields locked after verification, contact our support team with the correction and relevant account reference.
Send a subject access or data question to the support email published in the Support section below. State your registered account email and the specific record you are asking about. No reason required.
Account closure requests go through the same support route. We will confirm which data records are deleted immediately and which are retained for the period required under applicable local law and eligible-region obligations.
Questions about your data, correction requests and policy queries all go through our published support routes. We do not operate a walk-in service or a telephone line — all data-related contact is handled in writing so there is a record on both sides. Use the channel that suits your situation below.
Send data queries, correction requests and subject access requests to the support email address published in the Contact section of the ban880 site. Include your registered account email and a short description of the record in question.
For general account questions that touch on privacy — such as confirming which phone number is on file or checking a transaction reference — the live chat on the ban880 site connects you to the support team during published operating hours.
The help section inside your logged-in account lists the current contact routes and links to published policy documents. Check there first for the latest support email and any updated response guidance for your region.
We apply documented controls at each stage of data handling — from the moment you enter your details at registration through to the period after account closure. Here is how we approach the four main areas of concern.
We use cookies to keep your session active, store your display preferences and measure page load behaviour on mobile. You can disable non-essential cookies in your browser settings. Disabling session cookies will affect your ability to stay logged in across pages.
Account access is protected by your login credentials and, where enabled, a verification step on the registered mobile number. Unusual login patterns — such as a new device or location — may trigger an additional check before the session is confirmed.
We keep account data for as long as your account is active and for the legally required period after closure. Transaction references tied to Nagad, Upay or Bank Transfer are retained in line with applicable financial record obligations in your eligible region.
When this policy changes materially, we update the version date at the top of the page and notify you through the contact method on your account. Continued use of the account after the update date indicates you have read the revised terms.
These are the questions we hear most often from account holders about how their data is handled. If your question is not covered here, use the support routes listed in the Support section above.
We collect your name, contact details, and the device and browser information your session sends. When you use Nagad, Upay or Bank Transfer, we record a transaction reference and timestamp — not your full payment credentials, which stay within the payment rail you choose.
Yes. Log into your account and open the settings page to review what is on file. For records not visible in settings — such as identity verification data — send a subject access request to our support email with your registered account email address.
Most contact details and wallet references can be updated directly in your account settings. For locked fields such as verified identity records, contact our support team in writing with the correction you need and your account reference. We process corrections in line with applicable law.
Not immediately in all cases. Some records — particularly transaction references tied to Nagad, Upay or Bank Transfer — are retained for the period required by applicable financial and legal obligations in your eligible region. We will confirm what is deleted and what is retained when you submit a closure request.
Cookies keep your session active, store display preferences and help us measure how the site loads on your mobile connection. You can disable non-essential cookies in your browser settings. Note that disabling session cookies will affect login continuity across pages.
Send your complaint in writing to the support email published in the Contact section of the ban880 site. Include your registered account email and a clear description of the concern. All data-related contact is handled in writing so both sides have a record of the exchange.