Encrypted connection
All sensitive pages load over HTTPS, so data is hard to read in transit
Login, account, and session tokens are protected this way
Your data isn't kept in one place here; the 786jl App only keeps necessary data, and that too for a limited time
Bangladesh-based users typically want to know more about account security, login history, and cookie settings; from Dhaka, using bKash or Nagad-based usage, you can easily match the settings
All sensitive pages load over HTTPS, so data is hard to read in transit
Login, account, and session tokens are protected this way
Cookies remember only session, language, and preferences
You can delete cookies from the browser
If unusual login occurs, additional verification may be required
This reduces the risk of unauthorized access
If access from multiple devices at the same time is detected, the session restarts
Separate records are kept on mobile and desktop
System-level security rules are monitored 24 hours
This helps maintain 99.7% stability
Pages stay light on low-end phones, so loading is fast
Settings page opens easily on 3G networks
No unnecessary tracking is stored here; during setup you only see the necessary permissions
When you launch the 786jl APK, first the device, language, and session data are verified separately, then you can adjust browser cookies, notifications, and profile visibility if you want
Each request validates a token separately, so if you enter the same page twice, sessions won't get mixed
Only what is needed to run is kept; no unnecessary personal data is requested
Cookies remember language, preferences, and sign-in status; you can clear them from browser settings if you want
Your data is yours, so rights to copy, modify, restrict, and delete are explicit here
After logging in, most requests can be started from the profile section; once sent, a response usually arrives within 3 business days
You will know which information is stored, and why
You can change incorrect name, phone, or profile information
When the account is closed, unnecessary records are deleted after a limited time
Not all team members can see all data; access is role-based, and that is logged
Dhaka-based operations team only reviews the necessary parts for support; the Payment team has limited access to records related to bKash, Nagad, and Rocket
Each role has different permissions, so unnecessary access is prevented
Internal verification is required before sensitive tasks
Policy changes, requests, and responses are all documented
If suspicious activity is detected, an alert comes first, then the connection is temporarily restricted, and an investigation begins
In such reviews, logs, sessions, and device signals are usually checked; if urgent, control is also placed on the user's email or account status
If high risk is detected, the system team is notified; this reduces delays and limits damage
First determine where the incident originated, then changes are made only to the affected parts
In a serious incident, affected users are promptly informed what happened, which data was involved, and what to do
If you need help with bKash, Nagad, or Rocket, send a message from the Contact page; 786jl login issues are also checked there separately
For more details Terms Page And Support Page See payment records rules to understand Payment Guidelines Required
If you have privacy questions, write directly; all account information, cookies, or deletion requests are handled in one place.
If you wish, you can read the policy before registering for 786jl, or open the 786jl App and review the settings to ensure you have control over your data.
Register Login