ck66 App Privacy Policy

This page clearly explains ck66 App's data security, encryption, and security rules; also see how data is handled for users in Dhaka and Bangladesh when using bKash, Nagad, or Rocket

Download ck66 APK
ck66 secure app dashboard

How Privacy Works

In the ck66 App, your account, device, and session data are kept separate; the main purpose is login, security and fast app use, but not to accumulate unnecessary data

This policy shows what information is collected, how long it is kept, and when it is deleted; the same rules apply if you use ck66 Login or ck66 Register

View ck66 Login Guidelines

ck66 App Technical Security

Encrypted connection

All traffic goes under TLS-based security, making login, session, and device tokens hard to read

Account lock system

Repeated failed attempts on the same IP lead to temporary blocks, reducing brute-force attacks

Device verification

When a new Android phone is added, a separate verification starts; the old Dhaka device setup remains fairly light

Quick checklist

  • 256-bit encryption is used
  • Unknown session ends in 30 minutes
  • APK installation limited to official files only

Organizational rules and data protection

Internal access is restricted to those who need it; only they can view specific data

Audit logs are kept for 12 months, so changes can be tracked; this is how information security and accountability go together

Role-Based Access

Each team has separate permissions; access to unnecessary data is blocked

Record retention

Mandatory records are not kept for more than 90 days, unless the law says otherwise

Support Note

For questions about bKash or Nagad, the support team only takes necessary information

Contact privacy questions

Data sharing and third parties

ck66 App does not sell user data; only limited sharing for payment verification or technical hosting

For Bangladesh users, processing related to bKash, Nagad, Rocket is limited to transaction verification only; no unnecessary data beyond name, phone number, and account reference is shared

  • Contractual controls with service providers
  • Analytics data is separated
  • Personal messages are not used for other purposes

Cookies and session data

Cookies store login state, language preference, and device token; this means you don't have to re-enter the password

If you want, you can clear cookies from the browser, but then re-verification may be required at ck66 Login

ck66 cookie settings screen

Session cookie

Keeps login active; expires when the browser is closed

ck66 device verification notification

Device token

Extra verification is added on new Android devices to identify unknown phones

What happens when an incident

  1. Alerts appear

    If abnormal login or session match, an alert is created; usually the team reviews within 5 minutes

  2. Reasons are

    Logs, IP, and device signals are checked; if necessary, the session is terminated

  3. Account Security

    Password reset and re-verification may be required, reducing repetition

Breach notification and user rights

If there is a real data incident risk, affected users are promptly notified what happened, which data was affected, and what to do; these are clearly stated

You can view, correct, or request deletion of your data; such requests typically take 7 to 14 days, depending on the circumstances

ck66 Download APK

Need help? Contact us

If you have privacy questions, go to the ck66 Contact page from Dhaka or any other city; you can send a request in the same way

Account security, ck66 Register, or ck66 APK; separate questions are also taken; the ultimate goal is to keep your data clear, limited, and secure

View Contact Page
Log in Register