Policy summary
Key rules in brief
Effective date: June 2026
Many Dhaka users open the crickex App first and see this page; it explains what information is kept, where it goes, and what you can control
When viewing the account at 11 PM, people often ask where data is stored and who sees it; this privacy policy answers right there, making crickex App usage clear
We discuss personal data, device data, and usage patterns; for those who use bKash, Nagad, and Rocket in Bangladesh, the matter is even more important
Key rules in brief
Account and device logs are kept separate
There is a setup to load quickly on Dhaka networks
Sometimes data is not in one place; account data, security logs, and session records may go to separate servers, making it easier to identify problems
This practice of keeping them separate in the crickex App reduces user harm, so login history and device identifiers do not merge into a single file
Experience is the same when accessing from Dhaka or Chattogram; on slower networks, only essential data loads first
Some data may go outside the country for security testing; it's not hidden, and the reasons are clear, usually system validation, server reliance, or backups
If you want, you can understand that foreign servers do not necessarily mean risk; the real question is what security exists when data moves, and how clear the rules are
Without transparency there is no trust, so in this section we state directly what types of data may go and which do not
Privacy is not just a one-liner; in the crickex App, access restrictions, encryption, and internal permissions are implemented separately, reducing unnecessary handling
Many people in Bangladesh use bKash or Nagad for quick transactions, so account verification is handled carefully; the same policy applies to Rocket users
Login attempts, device changes, and unusual activity are monitored; if issues arise, the support team will take the next step
You can see what you have in your data, correct any mistakes, and request to delete some parts
Not all requests end with one click, but you have the right to a clear response, and that matters here
First verify your account information, then by writing on the contact page the next steps are given
If you ever feel a usage type is becoming excessive, you can file an objection, especially regarding marketing messages and analytics-based tracking
After crickex login, review the settings if needed Contact page Use, or Terms Read
If you write directly, the matter moves quickly; provide the address, username, and a brief description of the problem
Better to ask as a user, not as a customer; the following answers are written in that tone
Account, device, and basic usage-related information may be stored; nothing extra is kept beyond security
Yes, some system information may go; it's for security, backups, or service
The fundamental privacy policy does not change; only local transaction steps may differ
This page clearly presents privacy, data protection, and user rights together when using the crickex App, so users in Bangladesh from Dhaka or elsewhere can make clear decisions