joya9 App Privacy Policy

Here it is clearly written what data is captured when using the joya9 App in Bangladesh, and how data related to Dhaka and other parts of the country stays secure with bKash, Nagad, Rocket

Effective Date and Start

Effective date: September 2026. This privacy policy for joya9 App, joya9 Login, and joya9 Register explains the core rules for protecting users' data

Payment processors and the support team are separate, so Nagad deposits, account verification, and cookie tracking do not merge in one place

joya9 Card Data Tokenization

1. Card number stays separate

The actual card number is not stored long-term; transactions are run with tokens, so the payment flow stays small and the hassle is reduced

2. Sensitive parts are redacted

CVV or full card details only go through authorized payment paths; Dhaka-based users see this as easily as bKash or Rocket transactions

Token-based transactions
Keep the real card number stored
Log data kept minimal

PCI scope and security limits

1. Less scope, less hassle

If card page tasks are kept limited, PCI scope is smaller, making audits and compliance much easier

2. Works fast on mobile

When opening the joya9 APK or joya9 App, data load is kept small so the page doesn't stall on weak networks

Many users from Khulna and Chittagong verify on mobile; this setup helps clearly show payment steps even on 3G connections

Start Registration

Processor List and Data Routes

1. bKash, Nagad, Rocket paths

In Bangladesh these three payment names are usually seen most; each processor operates under its own rules, and data is not shared beyond those limits

2. Logs are kept for a period

Transaction time, success, and failure reasons are kept succinct; this helps the support team to track issues, but does not spread unnecessary information

When you login from the joya9 App, the processor name and steps are visible at a glance, helping new users easily understand which path is going where

Chargeback data and complaints

1. Proof of complaint is kept separate

In a chargeback, only necessary records are used; transaction details, date, and support notes are organized in one place

2. The user side is also considered

If there are incorrect recharges, wrong accounts, or verification problems, information is viewed for both sides; it's best to raise this via Dhaka's official support channel

Crypto wallet data control

1. Store addresses in shortened form

Wallet address and transaction ID are stored in shortened form; the full history isn't visible to everyone, only the authorized system parts can view

2. Identity is matched

Crypto-related data goes through separate routes, but user rights remain the same; requests for export, correction, and review can be made

If you are looking for joya9 Download, first check privacy settings, then using joya9 Register or joya9 APK will be easier

Cookies, tracking, and preferences

Cookies remember session, language, and login status, so you don't have to set settings repeatedly, especially on mobile

Analytics cookies show which pages are opened more, but this cookie is not needed to obtain personal data

User rights and requests

You have the right to know how your data is used; if not, you can request corrections, and if needed, you can also request deletion

To send a request, use joya9 Contact or joya9 Help page; after verification the team typically responds in three steps: view, match, then update

View data
Correct data
Request data deletion