ck200 App Privacy Policy

This page clearly explains how data is captured, stored, and shared in the ck200 App, with topics explained separately for Dhaka, Bangladesh, using bKash, Nagad, and Rocket.

Register ck200 privacy policy document

How data protection works in ck200 App

When anyone uses the ck200 App, some data is automatically collected to run the system, which makes login, session security, and device matching easier.

The privacy aspect here is straightforward: nothing more than necessary is kept. Many Dhaka users want quick sign-ins, so a small and clean data flow is kept.

  • Limited information is kept for account security
  • Cookies help maintain sessions
  • References related to bKash, Nagad, Rocket are used only for transaction verification.
  • Unnecessary personal information is not requested.

Card data tokenization and ck200 Login

Card or sensitive payment information is not read directly; instead a token is used, so risk decreases after ck200 Login.

This is especially needed when the user returns later and does not have to type the same information again, and the real data is not shown on the screen.

ck200 tokenized payment screen

Why this helps users

A small code replaces the main data, so the payment flow is faster, and the chance of errors is reduced.

  • The actual card number is not shown
  • Re-login is easier
  • Risk of session attacks decreases

PCI scope and ck200 APK security

If someone uses the ck200 APK, the same security policy still applies, keeping payment data within PCI scope, so it does not spread outside.

Most importantly, only the necessary parts are processed; even after installing the Android APK, server-side security remains active.

ck200 PCI security checklist
  • Limited data access
  • Controlled processing path
  • Clear limits in retention policy
  • Secure login steps

Processor list and ck200 Register

The information required to register ck200 is used only to operate the account; the names of local methods such as bKash, Nagad, and Rocket are used only for checkout verification.

The full list is not long; a short list means less complexity, and less confusion for users.

Which information goes to whom

The processor sees only the necessary parts of the transaction; personal identification, passwords, and internal account settings remain separate.

  • Limited information for payment verification
  • Only necessary references for support
  • Local processing flow for Dhaka users

Chargeback data and ck200 Download

If someone views information from the ck200 Download page and later raises questions, it is kept in a separate document to facilitate review, and the same topic does not have to be asked repeatedly.

Chargeback notes usually include time, reference, and issue type; these help the support team to handle cases in 23 minutes.

ck200 chargeback note tracking
  • Case numbers are kept separate
  • Dispute history is limited
  • Resolution time decreases

Wallet data and Bangladeshi users' rights

Digital wallet-related information is used only for account matching; many in Bangladesh quickly complete tasks with bKash, Nagad, Rocket, so that information is kept separately.

If you want, you can view, correct, or delete information; this is a core part of user rights, and control remains in your hands.

What are your rights

  • You can view your data
  • You can correct incorrect
  • You can object to unnecessary retention
  • You can submit a data request to support

Cookies, sessions, and ck200 App experience

Some features won't work properly without cookies, such as staying logged in, remembering language, and returning to the previous screen.

These aren't broken; rather, small conveniences to save time for busy Dhaka users, especially when mobile network is slow.

For more information Privacy FAQ of the Help Center You can view

User rights, help, and resolution paths

If you have questions about any information, you can contact support; complaints, corrections, and data requests are all handled clearly.

If you see any incorrect information in the ck200 App, report it directly; usually a single clear ticket is enough.

  • Account information
  • Correct incorrect entry
  • Questions about retention policy

What to say in contact

If you do not understand something about privacy, ask support directly; if you keep the question short, the answer comes quickly

If desired ck200 contact page Get help from there, and if needed TermsAnd compare

Register

ck200 App keeps data protection, cookies, and user rights clear together

Log in Registration