Sports / Mobile
ad880 publishes these terms so you know exactly what governs your account, your transactions and your use of this platform. Access to this site depends on your local law and eligible regions — read this page before you proceed.
Every time you open an ad880 account, deposit via Nagad, send a Bank Transfer or use Upay to top up your wallet, these terms apply. They set the boundary between what we manage and what sits with you. We do not make claims about local legal permissibility in any individual case — that is something you confirm on your side before registering. Our platform is built for supported regions, and where local law restricts access, it is your responsibility to verify eligibility. These terms cover the account relationship: how your data is held, how your transaction records are stored, and how disputes are raised. When you make a Nagad transfer or a Bank Transfer deposit, a dated entry is written to your account history. That record is the starting point for any question you bring to our support route. We do not alter completed transaction records; if an entry looks wrong, you raise it through the published contact path and we review the raw log. We update these terms when our platform or local regulatory context changes. The current version is always the one shown on this page. Continuing to use the account after a published update counts as acceptance. If a section does not apply in your eligible region, the remaining terms still hold.
Not every part of the ad880 experience is governed by the same rule. This section draws the line between what these terms cover and what sits outside them, so you can read each clause knowing exactly which part of your account it affects.
These terms apply to the login process, session management and account-level settings you control from your profile page. They do not extend to your device's own security settings or your mobile network's data policies — those sit with your carrier and handset.
All deposits and withdrawals processed through Nagad, Upay and Bank Transfer fall inside this policy. Each transaction writes a dated record to your account history. The terms define how long we retain those records and how you can request a review if something looks incorrect.
Game content supplied by studios in our lobby — including slots, live tables and sports markets — is covered for platform availability. We do not govern game rules set by individual providers; those are published at the game level and are the provider's own terms.
External links, wallet apps and bank portals you reach from ad880 operate under their own terms. Nagad's own app policies, your bank's transfer conditions and Upay's service rules are separate from ours. We are not liable for how those services handle your data once you leave this platform.
You hold practical rights over the information tied to your ad880 account. These are not abstract entitlements — each one maps to a specific step you can take from your account page or through our published support route. If you want to review what we hold, open the account history section: every Nagad deposit, Upay transfer and Bank Transfer entry is listed there with a date and reference. That record is your starting point. If a detail is wrong — a name field, a contact address or a transaction note — you can raise a correction request through the support channel. We check the raw log and update the field if the correction is valid. For broader questions about how we handle your data or how long we retain a record after an account is closed, send your query through the published contact path. We respond through that same route; we do not process data or correction requests sent to unofficial addresses. If at any point you want to stop using the account, the closure step is in your account settings.
Open your account history to see every dated transaction — Nagad deposits, Upay transfers and Bank Transfer entries are all listed there with references you can quote when contacting support.
Name fields, contact details and account notes can be corrected. Raise a request through the published support route with the correct information and we check against the original registration record.
If a clause in these terms is unclear or you want to know how a specific rule applies to your account, write to us through the support contact path. Quote the section you are asking about so we can respond precisely.
Account closure is handled from within your account settings. Once closed, we retain records only for the period set out in the retention section of this policy, then remove them in line with our data-handling procedure.
If a legal or policy question comes up — whether it is about your account records, a transaction entry or a data-handling query — use the routes we publish. We do not process policy requests through social comments or unofficial addresses.
Open the chat widget on any page of the site to reach the support team directly. For policy questions, state the relevant section or the specific account record you are asking about so the agent can pull the right log.
Send policy and data queries to the support email address shown on the Contact page. Include your account reference and a clear description of the question or record you want reviewed. We route it to the right team from there.
The Help section inside your account contains a category for policy and terms questions. Submit a ticket from there and your account details are attached automatically, which speeds up how we handle a correction or data request.
These are the specific ways we manage data, cookies, account security and record retention — each one a practical step, not a general promise.
We collect only the information needed to process your transactions and maintain your record. Nagad, Upay and Bank Transfer entries are logged with a date and reference. We do not sell account data or share it with third parties outside the scope set out in this policy.
We use session cookies to keep you logged in across your mobile browser and desktop. Preference cookies remember your lobby settings between visits. You can clear these from your browser at any time; doing so will log you out and reset saved preferences.
Your account is protected through the login and verification steps shown on the sign-in page. We do not store plain-text passwords. If you suspect unauthorised access, use the account-help route to flag it immediately — we can review the session log tied to your account.
Transaction records — including all wallet and bank transfer entries — are retained for the period required by the applicable policy framework. After that window, records are removed. You can ask about the retention period for a specific record type through the published support contact.
Real questions about how these terms work, how your data is handled and what steps to follow if something on your account needs attention.
Yes. Every transaction you make through Nagad, Upay or Bank Transfer falls inside the scope of this policy. Each deposit writes a dated entry to your account history, and that record is covered by the data-handling and retention rules set out here.
Open your account history and note the date and reference of the entry in question. Then raise a correction request through the published support route — live chat or the in-account help section both work. Quote the reference so we can pull the raw log and check it.
We retain records for the period set by the applicable policy framework. After that window closes, the records are removed following our standard data-handling procedure. Contact us through the support email if you want to know the retention period for a specific record type.
Access depends on your local law and the eligible regions we support. We do not confirm or deny eligibility for any individual. Review your local rules before registering, and check the region eligibility information shown on the sign-up page.
Send a correction request through the published support route — the in-account help ticket or the support email both go to the right team. Include your account reference and the corrected information. We check against the original registration record and update the field if the correction is valid.
When we update these terms, the new version is published on this page with a note of what changed. Continuing to use your account after the update is posted counts as acceptance. If a change affects how we handle a specific data type, we explain that in the update notice at the top of this page.