Encryption in transit
Login, payment, and account information are encrypted in transit, meaning data is difficult to read in the middle of the network
- HTTPS secure connection
- Session token control
- Abnormal traffic monitoring
Average Rating
Feedback
Active user
Operating uptime
Login, payment, and account information are encrypted in transit, meaning data is difficult to read in the middle of the network
Not all staff can see all data; restricted access is maintained, and sensitive records are stored in separate layers
Server-level monitoring continues, so abnormal behavior is detected quickly; this routine has been strong since 2015
If any risk is detected, it is isolated first, then an investigation begins, and if necessary the user is instructed
During sign-up, basic identity information, device data, and usage logs are collected; these help detect issues with h31 Login, h31 Register, and h31 APK usage
Users logging in from Dhaka, Chattogram, and Sylhet have session behavior that isn't the same, so data is viewed separately to detect wrong logins or abnormal access quickly
Your provided information and browsing signals help the support team stay updated, keeping the h31 App experience clearer
Data is used to keep the account active, to detect problems, and to speed up page loading; the same security level is maintained for bKash, Nagad, and Rocket gateways
Also, repeated incorrect passwords are detected by the system, reducing unauthorized attempts, and making legitimate users' logins easier
The policy language is straightforward, as most users read on mobile, so extra digging isn't needed to understand the data flow of the h31 App
Cookies are small files, but they do important work: they maintain sessions, remember language preferences, and do not require you to change settings repeatedly
Some cookies are only for security; some cookies make usage easier—for example, session tokens are used if you do not want to log in repeatedly on the same phone
Only when necessary is limited data shared for payment processing, support, and legal requests
The minimum data principle is followed in all cases, meaning only as much as is needed
When the account is open, necessary records are kept; after the account is closed, unnecessary data is deleted or archived after a specified period
Operational logs may be kept a few days longer, because they are needed for security investigations; this helps maintain an uptime of about 99.1%
You can view, correct, and delete your data in some cases; if needed, contact support for the next steps
If someone from outside Bangladesh logs in via a VPN, the same rules apply; the rules do not change, only the verification becomes more strict
On the h31 Login page, password, session, and device verification run together, so attempts to login from the wrong place are detected quickly
If any problem, you can go to the h31 Contact page and send a message; at the same time, the h31 Help and h31 FAQ also have answers to common questions
In short: The h31 App privacy policy gives users control, and data security works in the background
Basic information about account, device, and usage is collected for security, sessions, and support needs.
It may be shared only when necessary and limited to payment, security, or legal reasons.
Using APK, device permissions and source verification are important; better not to install outside official channels.
Some features may not be remembered properly, but basic pages are usually accessible.
Submit a support request; after verification, relevant steps are taken.