Browser signals
Session is verified by rendering and time zone
This reduces risk when signing in from a distant device
Effective date: July 2026
Crickex App Privacy Policy in Bangladesh
Crickex App shows how device IDs, cookies and security logs work; this explains which information Dhaka and Bangladesh users see, which is shared, and which you control yourself, all in plain language
Download Crickex APK Crickex Login Guide
What information is collected in Crickex App
4.5/5 rating
Users value security and control
6.5M+ active users
Multiple sessions are monitored on the account
13,464 reviews
Regular feedback on policy transparency
99.7% uptime
Access logs and session trails can be kept
App ID and device token
When you open Crickex App for the first time, a device token is created, making sign-in, session and security verification faster.
Dhaka's network pattern
A warning appears when a new phone signs into the same account; it makes detecting logins from unknown locations easier.
bKash, Nagad, Rocket references
Transaction references may be kept, but full financial information remains protected separately
Session and browser cookies
Cookies keep sessions, remember preferences, and you don't have to log in again
Device ID and session log
When you log in on a new phone, the system first checks the device, then verifies security by combining session token and browser information
This makes it easier to detect unfamiliar devices on the same account; in some cases Android 8+ devices and stable networks are verified quickly
- Device model and operating system
- IP address and approximate location
- Session ID and login time
- Device fingerprint after Crickex download
How fingerprinting works
Besides cookies, some browser signals are matched together in the Crickex App; screen size, language, time zone and rendering differences may be observed
These are not used to identify anyone by themselves, but help detect suspicious logins, multiple sessions or fake traffic.
Phone-based match
Mobile language and network pattern are observed
Behavior may differ when signing in from Dhaka or Chattogram
Risk detection
Repeated logins with the same pattern trigger a warning
Then Crickex Login screen may require additional verification
Session speed
Re-signing into a known device is faster
Sessions are easy to maintain even on weak 3G connections
Cookies and tracking controls
If you want to disable cookies, settings can be changed, but some preferences, saved language or session state may be lost
Still, basic browsing and help pages remain accessible; users signing in with Nagad or Rocket have the same controls
Required cookies
These are needed for login, language and security; turning them off may cause some parts not to work properly
Preferred cookies
Remembers your viewing preferences, theme or last visited page; these can be easily turned on or off
Analytics cookies
Which parts users spend more time on is observed; this helps keep the page fast and navigation smooth
Browser settings
Cookies from third parties can be disabled from Chrome or other browsers if needed; see Crickex App support page
Third-party SDKs and data sharing
Some analytics and security tool SDKs work to understand in-app usage, but keep the scope of personal data limited
References related to bKash, Nagad, Rocket follow separate paths; Dhaka users do not see payment and profile information getting mixed
- Security verification tool
- Error analysis service
- Session criteria report
- No unnecessary third-party sharing
How long data is kept
When no longer needed, data and unnecessary data are not kept; for support, security and legal records, it may be kept for a specified period
If an account is closed, some logs may be archived within 30 to 180 days; sensitive parts are kept under separate rules, then deleted
Security log
These logs are used to detect suspicious logins, device changes and failed logins
Support records
Once the issue is resolved, records are time-limited, and old tickets can be found again
Account information
Profile, contact and settings are required to run the account; if needed, you can request corrections
Deletion request
If you wish, you can request data review or deletion by writing to Crickex Contact
Your rights and control
You have the right to view your data; if there are mistakes you can request corrections, and you can also limit the use of some data
If you have privacy questions, write to Crickex Contact or the Help page; many users in Bangladesh first register with Crickex, then adjust the settings
- Data access request
- Request for correction
- Request to limit processing
- Request to delete account
Three steps to maintain privacy in the Crickex App
1. Download the APK
First, download the Crickex APK and install it; Android users, review permissions after downloading
2. Register with Crickex
When opening an account, provide only the necessary information; if you change the old phone, review the settings again
3. Review security settings
Enable two-step verification, cookie preferences and session notifications; this keeps control in your hands even when you are outside Dhaka or the district
Privacy contact
If you have any questions, write to the Crickex Contact page; your requests for account, cookies or data review will be handled separately
The Crickex App privacy policy is clearly stated for Bangladesh users; the bottom line is simple: what you share is under your control
Download Crickex APK Open Crickex Contact