Mobile / Casino
vq988 handles your information, payment records and session data with a clear purpose — to keep your account working and your wallet activity accurate. This policy sets out exactly what we collect, how we use it, and what you can do about it, with access subject to your local law and eligible regions.
When you open an account with us, we collect the details you enter directly — your name, contact address, and the wallet identifiers you use when transacting through Nagad or Rocket. We also record session activity such as pages visited, games opened and device type, because these help us serve the account correctly across sessions. We do not sell your personal data to third parties, and we do not share wallet reference numbers with any party outside of what is strictly necessary to process your transaction. Cookies placed during your session are functional by default; analytics cookies are used only in aggregate form and do not identify you individually. If you connect through a mobile browser, the same data standards apply as on desktop — the collection path is the same regardless of device. Retention periods vary by data type: account registration details are kept for as long as your account remains active, while transaction logs may be retained for longer where local regulatory requirements apply. We review this policy periodically; the version published on this page is always the current one. Availability of this service depends on your local law and eligible regions.
This policy applies to all interactions with vq988 through our site and account system. The four areas below clarify what falls inside and outside its scope so you know exactly where your data is governed by our practices and where a third party's own terms apply.
Any data you submit during registration, login or account verification is covered by this policy. This includes your email, contact details and any identity steps shown in your account settings.
When you initiate a deposit or withdrawal using Nagad or Rocket, the reference data generated is handled under this policy. We do not store your full mobile wallet credentials — only the transaction reference.
Game session logs, page navigation and time-on-page signals are collected in aggregate. This data helps us understand which parts of the lobby are working and does not identify you individually in our analytics.
Payment processors, game studios and any external links have their own privacy terms. Once you leave our platform or interact with a third-party service, this policy no longer governs how that party handles your data.
Your account gives you direct access to several data-related actions without needing to contact us first. Open the account settings page to review the profile details we hold — your registered contact information, active session records and linked wallet references for Nagad or Rocket are visible there. If any detail is incorrect, you can edit it directly from the account page using the fields shown; changes take effect on your next login session. For data that is not editable through the account interface — such as historical transaction logs — you can submit a written request through our support route and we will confirm what records exist and what can be amended or removed within the limits allowed by applicable retention rules. You can also ask us to stop using your data for any analytics purpose that is not strictly necessary to operate your account; we will acknowledge that request and confirm the change. Availability of any data action depends on your local law and eligible regions.
Log into your account and open the profile section. Your registration details, active sessions and wallet reference history for Nagad and Rocket are listed there without needing to contact support.
Edit your name, contact number or email directly in the account settings fields. The updated information is applied immediately and reflects on your next authenticated session.
If a record looks wrong and cannot be changed from your account page, use our published support contact to flag it. We will review the request and respond with what we can confirm or correct.
For deletion or restriction requests on data beyond what the account page allows, submit a written request through support. We will confirm scope, applicable retention rules and the expected process.
If you have a question about how your data is handled, need to raise a correction or want to make a formal data request, use the contact routes published on the site. We do not publish operating hours or response-time commitments we cannot guarantee — follow the route that suits your query and we will respond through the same channel.
Open the chat widget from any page on the site. Describe your privacy question or data request and our team will handle it from there. This is the fastest route for account-level queries.
Send a written request to the support email address shown in the site footer. Include your registered contact detail so we can locate the correct account record and respond accurately.
The help section inside your authenticated account lists common data and privacy actions you can complete without contacting us. Check there first before raising a support request.
Our data handling approach is built around what your account actually needs to function — nothing more. We apply access controls to account records, use encrypted connections for data in transit, and limit internal access to account data to the roles that need it. Cookie settings, retention schedules and third-party data-sharing limits are all governed by this published policy.
Functional cookies keep your session active and your account preferences saved between visits. Analytics cookies operate only in aggregate; they do not link session data back to your individual account or wallet activity.
Connections to your account use encrypted transmission. We do not store plain-text wallet credentials — Nagad and Rocket references are held only as transaction identifiers, not as access credentials to your wallet.
Account registration data is held while your account is active. Transaction logs may be kept longer where local regulatory requirements apply. When retention is no longer necessary, data is deleted or anonymised.
To request a change to how your data is held or used, use the live chat or email route listed in the support section. We will confirm receipt and outline the steps that apply to your specific request.
These are the questions we hear most often about how vq988 handles account data, wallet records and your privacy rights. If your question is not covered here, use the support contact routes listed in the section above.
We collect the details you enter during registration — your name, contact number or email, and any wallet identifiers you use when transacting. We also log session activity like pages visited and device type to keep your account working correctly across visits.
We share wallet reference data only where it is strictly necessary to process your transaction. We do not sell your personal data and do not pass Nagad or Rocket identifiers to third parties for marketing or analytics purposes. Payment processors handling your transaction have their own separate privacy terms.
Log in and open the account settings page. Your profile details, active session records and wallet transaction references are shown there. For data that is not visible in the account interface, submit a request through our published support route.
Yes. Submit a written deletion request through the email support route shown in the site footer. We will confirm what data falls within scope, note any records subject to mandatory retention under applicable rules, and outline the process for removal of the rest.
Registration details are kept for as long as your account remains active. Transaction logs — including Nagad and Rocket deposit and withdrawal references — may be retained for longer where local regulatory requirements apply. We do not hold data beyond what is necessary or required.
Yes. The same data collection and handling standards apply regardless of whether you access the site on a desktop or mobile browser. Device type affects display, not the policy. Access to the service itself depends on your local law and eligible regions.