cv222 App Privacy Policy
This page contains the cv222 App's device ID, cookies, and data security details, and users in Dhaka and across Bangladesh will understand in plain language
Three things to know
In this 2026 update we haven't beaten around the bush about what data we collect, why we collect it, and what control you will have; it's all written plainly
Before logging in or registering cv222, read this section once; it also clarifies how your data differs when using bKash, Nagad, or Rocket-based payments
- Device identification is limited
- You can control cookie settings yourself
- If you need help, there are separate contact
Which device IDs are captured in the cv222 App
We see four types of technical identifiers; these are used to verify login sessions, app status, and security checks
Many users in Dhaka switch between multiple Android phones, so secure sync on the same account is needed
What is typically logged
- Device model and Android version
- App session token and login time
- Crash reports and performance signals
How fingerprinting works
In short, security is verified by combining 68 small signals; this is not a dramatic mystery, just detecting unusual logins
To avoid false alerts on the same WiFi, old phones, and weak networks, we use limited scoring; it works well in Bangladesh on 3G or unstable connections
Which signals are checked
- Browser or APK basic information
- Screen size and language preference
- Small logs of security events
Control to disable cookies and tracking
Cookies do not mean constant surveillance; they are for keeping sessions, remembering language, and reducing repeated logins
If you want, you can block third-party cookies from the browser; this will open the cv222 App, but some personal settings will need to be chosen again
How to control
- Clear cookies from browser settings
- Limit the device's advertising identifier
- Submit a request on the cv222 Help page
Third-party SDK and data protection
Only three external SDKs may be needed; these are typically used for analytics, crash reporting, and push notifications
If any new tools are added we inform in advance; we do not like hidden tricks, because they’re always annoying
What these are used for
- Detect errors
- Identify causes of slow performance
- Understand which screens are opened most
How long data is kept
General logs are kept for 30 days; security events or legal notes may be kept for 90 days
When an account is closed, unnecessary identifiers are gradually deleted; some records are kept in a separate archive for audits, but your profile is not accessible there
Policy in brief
- Data is kept for a short time
- Only necessary parts are stored
- Deletion requests can be made
Your rights and complaint channels
You can view, correct, and request deletion; with cv222 Login enabled, many requests can be started from account settings
If you can't understand where certain data is, contact the Dhaka-based support team; even if there are notes related to bKash, Nagad, Rocket transactions, those are kept in a separate category
What you can request
- Copy of your data
- Request correction of incorrect data
- Requests for limited use
If you have questions, contact us directly
If you have questions about privacy, cookies, or device identification, write on the cv222 Contact page; typically a reply is sent within 1 business day
One last thing: The cv222 App keeps data protection, user rights, and transparent policy in the same place