Slots / Live
lv666 keeps your account data under a clear, documented policy — what we collect, why we hold it, and how you can review or correct it. Access to this platform depends on your local law and eligible regions.
This policy sets out how lv666 collects, uses, stores and protects the personal information you provide when you open an account, make a transaction or contact support. We collect the minimum data required to run your account: registration details such as your name and contact address, transaction records tied to the payment rails you use — bKash, Upay or Bank Transfer — and device identifiers needed to maintain session continuity across mobile and desktop. We do not sell your personal data to third parties, and we do not share it with marketing networks outside the scope of running this platform. Data we hold for transaction purposes is kept for the retention period required by the applicable rules of the jurisdiction under which your account is operated, and no longer. Where we use third-party service providers — for example, payment processors that handle bKash or Upay instructions — those providers operate under contractual obligations that restrict how they may use your information. Your ability to access this platform, and the specific rights available to you under this policy, depend on your local law and the eligible regions recognised by lv666 at the time you register.
Not every part of your interaction with lv666 falls under this policy in the same way. The table below shows what is inside the scope of this document and what sits outside it, so you know exactly where to look for the rules that apply to each area of your account.
Covered fully. Data collected at registration, login and session management — including device identifiers and authentication signals — falls under this policy. You can request a record of what we hold by contacting us through the published support route.
Covered. Payment instructions you submit via bKash, Upay or Bank Transfer generate transaction logs that we retain under this policy. The processing of funds itself is handled by the payment provider; their own terms govern that step.
Partially covered. Browsing the game lobby, selecting a category or loading a table does not by itself generate personal data we store. Aggregated, anonymised usage signals used to improve catalog organisation are not personal data under this policy.
Outside scope. Links, embedded tools or payment processors operating under their own brand are governed by their own privacy terms. We cannot accept responsibility for how those third parties handle your data once you interact with their services directly.
You hold specific, actionable rights over the data lv666 holds about you — and this section explains how to use them, not just that they exist. Start in your signed-in account area: the profile and security sections show the core registration data we hold on file. If any detail is wrong — a contact address, a linked wallet identifier for bKash or Upay — you can correct it directly from those fields without needing to contact support. For data you cannot edit yourself, or if you want a full export of what we hold, raise a request through the support route published on this site. We will acknowledge your request and tell you the expected timeline based on the volume of data involved. Rights availability may vary depending on your local law and eligible regions.
Open the account settings page when signed in to see the profile data and linked payment identifiers we hold. This is the quickest way to confirm what is on file.
Edit your contact details directly in the profile section. For wallet-linked fields such as your registered bKash or Upay number, follow the verification steps shown in the account page.
If you have a question about specific data we hold, or want to request an export, contact us via the support route on this site. Include your registered account email so we can locate your record quickly.
Where local law and eligible region rules permit, you may request deletion of account data we no longer need to hold. We will confirm what can be removed and what we are required to retain for transaction record purposes.
If you have a question specifically about how this privacy policy applies to your account, or you want to act on one of the rights described above, use the contact routes published on this site. We do not invent timelines or operating hours here — follow the instructions shown in the contact section of your account for the most current information.
The support link inside your signed-in account is the direct route for data questions. Describe your request clearly and include your registered email address so your record can be located.
The contact page on lv666 lists the current methods for reaching the team. Use this route if you are not yet signed in or if your account access is the issue you are raising.
For formal data requests — an export, a correction you cannot make yourself, or a removal request — submit in writing via the contact route and reference this privacy policy. Written requests create a record we can track.
Holding your account data responsibly is not a one-time action — it is an ongoing part of how this platform operates. Here are the four areas where we apply consistent standards, so you know what to expect from us.
We use cookies to keep your session active across mobile and desktop and to remember display preferences. No advertising cookies are set without disclosure. You can review and adjust cookie settings through your browser at any time.
Access to your account data is restricted to authenticated sessions. We apply standard security controls to protect stored credentials and transaction records, including those linked to bKash, Upay and Bank Transfer.
We keep your data only as long as your account is active or as long as applicable rules require us to retain transaction records. When a retention period ends, data is deleted or anonymised according to our internal schedule.
When this policy changes in a material way, we will notify you via the contact address on your account before the change takes effect. Continued use of the platform after notification means you have acknowledged the updated terms.
These are the questions we receive most often about how lv666 handles account data. If your question is not answered here, use the support contact route on this site.
We collect the details you enter at registration — name, contact information and the payment identifiers you link, such as your bKash or Upay number. We also log device and session identifiers to maintain continuity across your mobile and desktop sessions.
We share data only with service providers who need it to run your account — for example, payment processors that handle bKash, Upay or Bank Transfer instructions. Those providers are bound by contractual restrictions on how they may use your information.
Transaction records are retained for the period required by the applicable rules of the jurisdiction under which your account operates. Once that period ends, records are deleted or anonymised. The specific retention period depends on your local law and eligible region.
Yes. Sign in and open the profile section to view and edit your registration details. For wallet-linked identifiers like a Upay or bKash number, follow the verification steps shown there. For data you cannot edit yourself, contact us via the published support route.
Send a written request through the contact route on lv666. Reference this privacy policy and include your registered email. We will confirm what can be removed and what we are required to keep for transaction record purposes under local rules.
Your rights under this policy and your access to this platform both depend on your local law and the eligible regions recognised by lv666. We cannot guarantee that every feature or right described here is available in all locations. Check current access conditions in your account.