Data identification
System logs, device ID and session token are used to assess risk
If multiple devices log in, it is noticed and all sessions can be closed
LV666 App Data Protection Policy at a Glance
Encryption Level
Sensitive data is kept at 256-bit security level
Account Security
Login verification and session monitoring operate at a
Cookie Control
Browser cookies, preferences and session cookies are kept separate
User Rights
Data can be viewed, corrected and deleted upon request
How LV666 App works when data is breached
Here are the breach response steps; what happens at each step is central
1. Identification
Abnormal login, session break and unauthorized access are detected
2. Containment
Affected components are isolated to prevent it from spreading
3. Notification
Users are notified quickly if there is risk
4. Mitigation
Password reset, token revoke and log review occur
5. Audit
Finally, reports, timeline and remediation are documented
When is data viewed
Cookie Consent
Sessions do not run properly without essential cookies; analytics cookies may be disabled if you wish
Repeated logins with bKash or Nagad save preferred data
Rights Management
Request a copy of your data
If you wish, go to the contact page to raise data access questions
Session, login and user control
Session Management
If multiple devices log in, it is noticed and all sessions can be closed
Log Record
Login time, device and browser type are recorded
Preference Control
From the cookie banner, analytics, security and performance can be separated
LV666 Login and Data Protection Questions
What data is seen when you log in to LV666?
Typically device, IP, session time and security checks are seen; these help mitigate risk
Will LV666 App run if cookies are off?
Required cookies keep sign-in functioning, but some preferences and analytics features may be limited
What to do to delete data?
Go to the Help page to request; after verification, specific records can be deleted
Does bKash or Nagad share information?
Payment verification is not performed; additional financial information is not stored; transaction history is kept under separate rules
If breach occurs, when am I notified?
If risk is confirmed, a quick notification is issued and what to change next is also stated
Contact, Complaints and Data Officer
Questions about LV666 Register or LV666 Download? Please go to the Help page; for privacy, deletion and corrections, contact the team
Dhaka-based users may write with bKash, Nagad or Rocket transaction references to speed verification, and responses come in the right context
Register Log inHow user rights work
- Request a copy of your data
- Request correction of incorrect information
- Request deletion of unnecessary records
- Change cookie preferences
This page has one goal: to clarify what data LV666 App stores, and for questions about privacy, cookies and rights, please write on the Contact page