Data Protection Snapshot
Consent
On first visit, a cookie-consent notice appears; you can change your preferences in 2 steps.
Storage
Dhaka-based users' data is kept for a limited time, unnecessary information is kept separate
Protection
Security is active at the transmission layer; additional controls apply to sensitive parts.
Cookie
Session cookies and preference cookies — control from the browser if needed.
Collection: What CK200 App Collects
If someone wants to open a new account, CK200 App only takes the necessary information here, including name, contact details, basic device information, and usage preferences.
This follows the minimal-collection concept like Google's data-protection policy; that is, if additional information is requested, a clear reason is shown, and it does not activate without consent.
- Required information for account verification
- Login device and browser signals
- Cookie preferences and session
If you CK200 App Page There you will see more details about mobile usage; the main point of this page is that information is collected for a clear purpose, not hidden.
Storage: Where data is stored
When data is submitted, it goes to controlled storage inside or outside Dhaka, wherever you access from; the same principled framework applies.
Access is restricted by role; since 2021, user security and the audit trail have particular importance.
- Limited access
- Regular log monitoring
- Separate unnecessary records
If you Help Guide Read there; you will also find answers to storage-related questions; personal data does not stay dispersed for long.
Usage: What data is needed
Your data is primarily used to run the account: login, store preferences, and maintain session stability; these three tasks use it most.
For local users relying on bKash, Nagad or Rocket, support documents are kept separate, making it easier to understand common flows in Bangladesh, especially on mobile.
Usage Controls
- Re-authenticate if password is incorrect
- Cookie permissions can be changed
- Notification preferences are kept separate
Payment Information Policy Reading this provides a clearer understanding of local channels; at this usage level, transparency is the most important.
Sharing: With whom data may be shared
Sometimes data may be shared with service providers, compliance partners, or technical vendors, but only to run operations and within the necessary limits.
Many Dhaka-based users want to know what third parties' roles are; the simple answer is data is not sold commercially without consent, and if shared, the reason is shown.
- Limited sharing for service operation
- Legal Requests
- Partner Privacy Terms
If you want Terms Page Even so, you can review the scope of responsibilities; the policy language isn't hard; the goal is clear: clear boundaries.
Deletion: When data is removed
Upon request or when no longer needed, the data deletion process starts; some records may be retained for a legally specified period, but that too is limited.
If your account is deactivated, unnecessary personal data is reviewed; even if you withdraw consent, cookie settings can be changed quickly.
- Remove unnecessary profile sections
- Session data ends after expiry
- Cookie preferences are reconfigurable
Deleting does not mean everything disappears at once; controls remain, yet the policy is arranged so that data reduces as quickly as possible
Cookies and consent: small settings, big controls
When a user first lands, they see a cookie banner; it has two choices: essential cookies and optional analytics cookies
Here, consent is not just about ticking; it is recorded consent, so later you may change your settings, and that change is also counted
Most mobile users control these preferences from the browser; on some Android phones cookie blocking may be enabled by default, so site behavior may appear different