Mobile / Slots
lavish luck is clear about what data we collect, why we hold it, and what you can do about it — including how your bKash, Nagad, and Rocket transaction records are stored and who can access them. Access to this platform and the rights described here depend on your local law and eligible regions.
This policy covers every piece of information lavish luck collects when you register, log in, make a transaction, or contact support. That includes account identifiers such as your name and email address, device signals from your mobile browser session, and payment references linked to bKash, Nagad, or Rocket transactions you initiate. We hold payment references only long enough to reconcile your account wallet and meet any record-keeping obligations that apply in your jurisdiction — we do not store full wallet credentials on our servers beyond what processing requires. Cookie data from your browsing session is covered separately in the cookie section of this policy. Data we collect is used to operate your account, respond to your requests, detect irregular activity on your wallet, and where required, meet applicable legal or regulatory obligations. We do not sell your personal information to third parties. We share data with service partners only where they are directly involved in delivering a function you use — for example, a payment processor handling your Rocket transfer. The scope of sharing is limited to what that function requires. Your rights and our obligations under this policy depend on local law and the eligible regions from which access is permitted.
Not every data interaction you have while using this platform falls under this policy. Understanding what is and is not covered helps you know where to direct a question or request. The four areas below set out the boundaries clearly so you can navigate your rights with confidence.
Data collected during login, account creation, and session activity on lavish luck is fully covered by this policy. We control and are responsible for how that information is stored, retained, and used within your account profile.
When you use bKash, Nagad, or Rocket to fund or withdraw from your account wallet, transaction reference data passes through a payment processor. Our policy covers the reference record we hold; the processor's own privacy terms govern data on their side.
Browsing data collected while you navigate game lobbies, review your account balance, or read published terms is covered here. We use anonymised session analytics to understand how the site functions — no individually identifiable game history is sold or shared.
Links to external services, identity verification partners, or third-party tools operate under their own privacy terms. Once you leave lavish luck or interact with a third-party widget, this policy no longer applies to that data exchange.
Your account gives you direct access to several privacy-related actions without needing to contact support first. From the account settings area you can review the profile information we hold, update contact details, and check the payment methods currently linked to your wallet — including any bKash or Nagad references on record. If something looks incorrect, you can submit a correction request directly through the support channel described in the contact section of this policy. For requests that go beyond what the account interface allows — such as asking us to delete a record or clarifying how a specific piece of data has been used — our privacy contact route handles those in writing. We will acknowledge your request and follow the steps applicable under local law and the eligible region rules that govern your account. Response timelines depend on the nature of the request and applicable jurisdiction requirements; we do not state a fixed window we cannot verify. Every request is handled on its own facts.
Open account settings to see the profile data and payment references we hold. The information shown there reflects what is active on your account at that moment, including any linked mobile wallet identifiers.
If a name, contact detail, or payment reference is recorded incorrectly, use the edit fields in your account profile or send a written correction request through our support route. We update records once identity is confirmed.
Questions about how a specific piece of your data is used, retained, or shared can be sent to our privacy contact. Describe the data and the concern clearly; we follow up via the contact method on your account.
For deletion requests or questions about data export, contact us in writing through the support route. We handle each request according to the rules that apply in your jurisdiction and eligible region.
If you have a question about how your data is handled, want to submit a correction, or need to raise a concern about your account records, the routes below are the ones we actively maintain. We do not publish support hours we cannot verify — use the channel that works for your situation and we will respond through the same route.
Open the chat widget from any page on lavish luck to reach support directly. For privacy questions, describe the data concern clearly so it can be routed to the right team without delay.
Send written privacy requests, correction notices, or data questions to the support email address shown in your account area. Written requests create a reference record for both sides, which helps with follow-up.
The help section inside your signed-in account lists published policy routes and common account questions. Check there first for answers about data retention, cookie settings, and wallet record access before raising a new request.
We apply access controls to your account data so that only authorised processes can read or modify it. Mobile session tokens are handled the same way as desktop sessions — your bKash or Nagad wallet reference is not exposed in the browser interface beyond the masked display shown in your account. Cookie settings can be adjusted through your browser; session cookies that keep you logged in are separate from analytics cookies, and you can block the latter without affecting your account access.
Your account password and session token are stored using one-way hashing and time-limited session logic. We do not store plain-text credentials. Suspicious login patterns trigger a review before account access continues, visible in your account activity log.
We use session cookies to keep you logged in and analytics cookies to measure how the site performs. Session cookies expire when you close the browser. Analytics cookies can be blocked in your browser settings without affecting your account wallet or transaction history.
Account records are kept for as long as your account is active and for a further period required under applicable obligations in your jurisdiction. When an account is closed, personal data not required by law is removed from active systems on a scheduled basis.
When we update this privacy policy in a material way, we publish a notice in the account area before the change takes effect. You can review the current version at any time on this page. Continued account use after a posted notice means you have seen the update.
The questions below reflect what account holders commonly ask about their data rights, how records are kept, and what to do if something needs to change. If your question is not here, use the support contact route described earlier in this policy.
We collect the details you enter during registration — name, contact information, and account credentials. We also record device signals and session data when you browse or log in. Payment references from bKash, Nagad, or Rocket transactions are stored as part of your account wallet record, not as full wallet credentials.
We share data only with partners directly involved in delivering a service you use — for example, a payment processor handling a Nagad or Rocket withdrawal. We do not sell your personal data. Sharing is limited to what the specific function requires, and partners are expected to handle it under equivalent data-protection standards.
Open account settings while signed in to view the profile and payment references on record. The display shows active information at that moment. If you want a more detailed breakdown or a record of historical data, send a written request through email support and we will follow up via your registered contact.
Yes. Send a written deletion request through the email support route. We process deletion requests according to the rules in your jurisdiction and eligible region. Data we are required to retain under legal or regulatory obligations cannot be deleted ahead of that retention period, but we will explain what applies to your specific request.
This policy covers the transaction reference we hold on our side — the record that links a payment to your account wallet. The bKash or Nagad platform's own privacy terms cover data on their side. We do not store full mobile wallet credentials beyond what the transaction processing step requires.
When you close your account, personal data that is not required under applicable legal or record-keeping obligations is removed from active systems on a scheduled basis. Retention timelines depend on your jurisdiction. You can ask about the specific retention period for your account data via the email support route.