Casino / Mobile
This page sets out the legal framework that governs your use of v366. Access to our platform and the rights described here depend on your local law and whether you are in an eligible region — read this before you proceed.
v366 operates under a framework that places your account rights and data handling at the centre of every policy decision. Whether you reach us via bKash, Nagad or Rocket for a transaction query, or through our support route for an account matter, the same policy standards apply. We do not treat payment-channel queries differently from account or content queries — the policy covers all of them. Access to v366 and the protections described on this page are conditional on your local law and the eligible regions we serve. If local law in your area restricts or prohibits online wagering platforms, the eligibility conditions stated in our terms apply and we ask you to confirm your eligibility before continuing. We cannot verify local legal status on your behalf. Where this policy refers to data or records, we mean the account and transaction history held in your registered profile. We retain this to fulfil our operational obligations and to allow you to review your own activity. Retention periods are defined in our full terms, accessible from your account area. Any conflict between this summary and the full terms document is resolved in favour of the full terms. We update this page when the policy changes, and the current version is always the one in effect.
Transaction records linked to bKash deposits or withdrawals are part of your account history and are subject to the same retention and review policy as all other account data.
Nagad-linked account activity is logged under your registered profile. You can review these entries in your account history section and raise a correction request through the support route.
Rocket payment references stored against your account fall within the scope of this policy. They are accessible for your review and can be included in any data query you submit to us.
Not every part of your interaction with v366 falls under the same policy clause. This section distinguishes what we govern directly from what sits outside our direct control — so you know where to direct a concern.
Login credentials, session activity and account-level permissions are governed by this policy. Any access dispute or lock-out query should be directed to our published support route, not to a payment provider.
Deposits and withdrawals processed through bKash, Nagad or Rocket are subject to both this policy and the individual payment provider's terms. Disputes involving the payment network itself are handled by that provider.
Game content supplied by studios such as Pragmatic Play or Spadegaming is governed by those studios' own content licences. Our policy covers how we present and restrict that content, not its underlying intellectual property.
External links, third-party verification tools and any service not hosted directly by v366 operate under that third party's own terms. We are not responsible for the policy practices of services we do not control.
Your rights under this policy are practical, not abstract. You can review the transaction and activity records held in your account at any time by opening the account history section after logging in. If you spot an entry that appears incorrect — a payment reference, a session record or a personal detail — you can request a correction by contacting us through the support route listed on this page. We will confirm receipt of your request and work through it in the order it was received. If you want to understand what data we hold against your account, you can submit a written query to the contact route below. We do not require a formal legal process for a straightforward account query; the support channel handles it. For account closures or requests to limit what we retain, the process is documented in the full terms accessible from your logged-in account page. Acting on your rights starts in your account — open it, check the relevant section, and use the support route if the answer is not there.
Log in and open the account history section to see your activity and transaction entries. This is the fastest path to checking what we hold.
If a name, contact detail or payment reference is wrong, raise a correction request via our support route. Include the specific field and the correct value.
For questions about what data we retain or how it is used, send a written query through the published contact route. We respond in the order queries arrive.
Closure or retention-limit requests are documented in the full terms. Open the terms from your account page and follow the steps described there before contacting support.
Policy questions, data queries and account-rights requests all reach the same support team. Use the route that works for your device — every channel goes to the same team and receives the same response process.
Open the chat icon from any page on v366. State your account query or policy question clearly. The team will confirm receipt and let you know the next step.
Send your written query to the email address published in the Contact section of your logged-in account area. Include your registered account reference so we can locate your records promptly.
For self-service policy navigation, open the Help section inside your account. It links to the full terms, the correction-request form and the contact routes in one place.
Handling your account data carefully is not optional for us — it is part of how we operate. Below are the four areas that define our approach.
We keep account and transaction records for as long as our operational obligations require. The retention period is defined in the full terms. You can request a summary of what we hold at any time through the support route.
We use session cookies to keep your account state between pages and to record activity for security purposes. You can review the cookie policy from the footer of any v366 page. Browser settings can limit non-essential cookies.
Your account is protected by the credentials you set at registration. If you believe your account has been accessed without your consent, contact support immediately using the live chat route — do not wait for an email response.
If this policy changes in a way that affects your rights, we update this page and note the revision date at the bottom. Check this page after any notification you receive about policy updates.
These are the questions we receive most often about the v366 legal framework, account rights and data handling. If your question is not here, use the support route above.
Access and the rights described here depend on your local law and whether Bangladesh falls within our eligible regions at the time you use the platform. We recommend reviewing the eligibility conditions in the full terms before creating or using an account.
Log into your account and open the account history section for a full view of your activity and transaction records. For a broader data summary, submit a written query through the email support route published in your account's Contact section.
Yes. If you see an incorrect entry in your account history — whether it involves a bKash, Nagad or Rocket reference — raise a correction request through live chat or email support. Include the transaction date and the specific detail you want corrected.
We retain certain records after account closure to meet our operational obligations. The specific retention period and what is kept are described in the full terms, accessible from your logged-in account page before you submit a closure request.
Start with our support team via live chat or email — most account and policy disputes are resolved at that stage. If the matter is unresolved, the escalation path is outlined in the full terms document under the dispute resolution section.
We update this page whenever the policy changes and note the revision date at the bottom of the page. If an update materially affects your rights, we will also send a notification to your registered contact detail. Check this page after any such notification.