Effective Date: August 2026
EK999 App Privacy Policy and Data Security
This page clearly states EK999 App privacy, cookies, and rights, and shows how users in Dhaka and across Bangladesh control their information in language
How data identification works in the EK999 App
We detect risk signals in 3 steps
Login, device, and session pattern are used to detect suspicious behavior; extra verification may be required when EK999 Login from a new device
This keeps account inner information separate; documents related to bKash, Nagad, and Rocket transactions are used only for verification
- Unusual login attempts are detected within 1 minute
- Security checks are activated when the device changes
- Session tracking remains stable on Dhaka's network
Data security and restricted access
All sensitive information is protected by layered security
Account data, device ID, and contact information can be read with separate permissions; only those who need to work can view specific parts
We keep minimum data in the EK999 App; even with separate permissions when installing the APK for Android users, personal data does not go to other apps
- Access logs are monitored with 99.7% uptime
- The same security policy has been updated since 2017
- Rules are tightened by looking at usage patterns of 29 countries
Cookies and tracking settings
Cookies come in 4 types, functions
Necessary cookies keep the session active, remember language preferences and display, and analyze cookies to see which pages have issues
You can limit cookies from the browser, which may reduce some features, but basic pages will remain accessible
Rights, complaints, and data requests
You have 5 explicit rights
You can see what information is stored about you; if you see erroneous data, you can request corrections; if needed, you can request deletion of specific data
You have control over the information provided when registering EK999; many Dhaka users operate accounts with bKash, so payment-related records are viewable on request
- Access requests are reviewed within 48 hours
- Identity verification is required for
- Marketing messages can be turned off if needed
Reduce incidents, minimize damage
When a breach is detected, three actions start
First restrict access, then block the source of risk, finally secure the affected part's data separately
These steps, when fast, keep users safe; EK999 App security alerts work from outside Dhaka as well, so suspicious logins are detected quickly
Audits, documents, and our communications
Reviewed once per quarter
Audits show why information is kept, who viewed it, and where rules need to be clearer, so old records do not accumulate unnecessarily
If you have privacy questions, write to the DPO team via EK999 Help and EK999 Support page for a reply
We are here for any data-security questions about EK999 App, EK999 APK, and EK999 Login
Quick info
2.6M+ users
A larger user base makes security monitoring stricter
4.5/5 rating
Users prefer stability and clear rules
23,207 reviews
Feedback helps determine policy updates
868+ titles
Data management is important to keep account usage fast
Q&A
What information is stored in the EK999 App?
Account, device, and security logs are kept; additional information is not stored unless needed
What happens if cookies are
Basic pages will work, but keeping preferences or session persistence may be reduced
What should I do to view my own information?
Write on Support page; after identity verification, a data summary is sent
What happens when EK999 Login on a new device?
Additional verification may be required; this is kept for security
Is there something special for Bangladesh users?
Rules are based on bKash, Nagad, and Rocket-based usage patterns
Send help and complaints
Write directly about privacy, cookies, or data security
The EK999 Support, EK999 Help, and EK999 About pages share the same information; whether from Dhaka or another city, the response remains in same flow