ja9 App Privacy Policy

Card Data Tokenization

If you top up from Dhaka using bKash or Nagad, we do not keep actual card or wallet details in plain text; sensitive data is sent as tokens, so numbers are not visible externally.

It may sound fancy, but tokenization reduces transaction risk and keeps account data protected at a separate layer.

• One-time token

  Card number is replaced with a token

• Session-based authorization

  Each transaction goes through separate verification

• Less visible data

  Support team also cannot view full payment data

PCI limits in the ja9 App

If you use the ja9 App, PCI-related rules apply directly, meaning sensitive payment fields move along a separate path and do not mix with other data inside the app

Many Bangladesh-based users run the app on low-latency networks, so lightweight processing is used to keep Rocket, bKash, or Nagad steps from becoming unnecessarily complex

• Limited access

  Only necessary systems touch payment data

• Separate storage

  User account data is kept separate

• Mobile-friendly rules

  Steps kept low for faster loading on Android phones

Processor list and transaction path

Knowing where data goes is necessary, so the roles of the payment processor, verification service, and server logs are clarified

In this framework, Bangladesh-based users' transactions using bKash, Nagad, and Rocket are tracked separately, reducing record errors and making issues easier to find

• bKash flow

  A small transaction ID is stored on top-up

• Nagad flow

  Success or failure goes to a separate log

• Rocket flow

  Reference numbers are matched across more than one step

How chargeback data is stored

If you raise any chargeback or payment questions, the full history is not disclosed; only necessary references, timestamps, and communication notes are kept

Many people from Dhaka first contact Support, then provide a receipt; in that case we do not retain logs older than 90 days unless needed for investigation

• Timestamp

  When the event occurred, it can be matched

• Limited notes

  Extra personal data is omitted

• No unnecessary retention

  Unnecessary data is deleted when the work is done

Crypto wallet data

Some users ask about alternative methods; if a wallet is connected, address and network data are kept very limited

The same principle here: the less data, the better; no unnecessary history is stored beyond local payments, and users can request deletion if desired

• Address shortening

  The full wallet address is not shown repeatedly

• Networks are separate

  Each network's record stays separate

• Account security

  Cannot be changed without authorization

Cookies, rights, and controls

If you want to disable cookies, you can, but some pages may load slower, and the login remember feature may be reduced

Your rights are clear: requests to view data, correct inaccuracies, and deletion requests after ja9 Login; talking to support makes the process easier

• Cookie Control

  Preferences can be changed from the browser settings

• Data correction

  Incorrect name or number can be corrected

• Delete request

  You can request deletion of data that is not required to be kept

Get direct assistance

If any part is unclear, send a message; after ja9 Register, the support team will guide you on any information-related questions

For new users this is especially important, particularly those in Bangladesh installing APK for the first time; understanding permissions and data settings may take some time

Quick Info