Data protection
Personal data kept to a minimum, and only necessary parts are stored
lv66 App Privacy Policy at a glance
This policy explains lv66 App's data-control rules since 2017, keeping language simple in light of 4.9M+ users' experience.
Here ISO 27001 and 27701-style security considerations mean that information, access, cookies, and incident management are viewed separately.
Cookie control
Limited cookies are used to remember sessions, preferences, and language
User rights
Requests to view, correct, and delete can be made
Data protection rules
Encryption
Encryption is used when sending sensitive information, so data stays secure even when logging in from Dhaka or another city
Secure connection maintained with 99.4% uptime
Secure login
lv66 Login detects account verification, device identification, and unusual access
If too many failed attempts occur, temporary alerts are issued
Minimal data
Only information necessary to operate is kept; fewer unnecessary fields reduce hassle
This keeps loading light, especially on 3G networks
Access and resource management
Who sees what information is controlled here; accounts, team tools, and back-office are separated
Various levels of permissions are used, so general support staff cannot access everything; work proceeds with restricted access
Role-based permissions
Permissions are set according to each team member's role
Device verification
Extra verification required on new phone or unknown browsers
Limited dashboard
Not everything is shown on the same screen, so risk is reduced
Cookies and data protection
Cookies are small auxiliary files that help retain login tokens, language, and sessions
If desired, cookies can be removed from the browser, but some parts of lv66 App may run slowly
Save preferences
Language and layout preferences are remembered
Usage analytics
Page slowdowns are identifiable
Deletion control
If desired, cookies can be removed from the browser
Cryptography and secure communications
lv66 App's internal connections travel on encrypted paths, making data in transit difficult to alter
For those who transact in Dhaka with bKash, Nagad, and Rocket, maintaining a secure session is also important, which is why strict connection-layer rules are followed
What measures
Encryption keys are handled separately
Secure path
Unnecessary open paths are not kept
Risk reduction
If unknown data is encountered, it is separately verified
Operational security
Monitoring is kept day and night to detect problems early; reviewing operational logs shows what has changed
Even with 785+ titles in the service here, the system remains stable; even under heavy workload, clear records are kept
Log records
Who changed what is tracked
Monitoring
System speed and errors are monitored regularly
Light mobile experience
lv66 APK is small, making it easy to use on slow phones
Incident management and reporting
In case of any security issue, rapid response is essential, so reporting, verification, and resolution steps are predefined
Users who register lv66 can request help via the same route; if needed, account verification is performed, then action is taken
Rapid identification
An alert is issued as soon as risk is
Remediation steps
Check first, then correct.
Contact
The user is informed of the results clearly.
User rights
You can view, correct, or limit your information; this is a core part of lv66's privacy policy.
If information is incorrect, submit update request; you may also disable specific cookies or profile options.
View information.
You can see what information is kept about you.
Edit.
Incorrect name or number can be corrected.
Limitations.
Requests to limit usage can also be made.
Small tips for safe use.
Many Bangladesh users log in on mobile first, then read the policy; lv66 App information is thus easily available.
