644JILI App Privacy Policy
This page clearly explains how data protection, cookies, and payment information are handled for Dhaka and Bangladesh users.
Download 644JILI APK View 644JILI App
Card data token and 644JILI Login
After logging in, if you add a payment, the token is more important; the actual card number is kept separate for security, so less information is shown
This helps Dhaka users easily understand which data is stored Security Policy And Terms Reading makes the image clearer
Where the token is used
The token works for recharge, verification, and session refresh, so during 644JILI Login you don't need to repeatedly enter sensitive information
- The token replaces the real number
- Access is reduced when the session ends
- Browser cookies can be controlled separately
PCI limits and 644JILI Download
Check security settings before running the file; after downloading 644JILI the app only asks for necessary permissions
Using bKash, Nagad, and Rocket, the payment processor handles most verifications, so less data is stored in the main app
Which parts are PCI compliant
Card verification, payment token, and transaction references are typically shown; actual secret data remains in a restricted part of the system
- Sensitive PAN data is not stored
- Verification logs have a limited duration
- You may change cookie preferences
Processor List and 644JILI Register
Learn which service uses your data during registration; when you register for 644JILI, a clear notice is shown during the verification step
For users from Bangladesh, local names like bKash, Nagad, and Rocket are more relevant; foreign payment names are not required here
Who data is shared with
Only necessary processors, hosting, and support teams see limited data, keeping the overall flow lean and reducing unnecessary sharing
- Payment Verification Processor
- Account Security Service
- Ticket-based Support System
Chargeback Data and 644JILI App
If there is an issue, don't stay silent; note it— for a chargeback case, transaction references, time, and verification history are needed
This document is usually restricted to speed up the investigation Customer Service If you submit a ticket from the page, the support team asks for the
What to include
Keep screenshots, transaction IDs, and timestamps as proof; within the 644JILI App these can be easily matched
- Note the transaction ID
- Send only one copy if disputed
- Exclude unnecessary personal information
Crypto wallet data and cookies
If using a wallet, only the public portion of the address is visible; private key is never shared, and that is the main rule
Cookies only retain session and language preferences, so on re-entry Dhaka or other Bangladeshi users quickly get the previous settings
What you control
You can delete cookies, restrict them, or keep only essential parts; this keeps browsing clearer
- Session cookies expire
- Preferred language can be kept separate
- Local device history is limited
Your rights and assistance
To view, correct, or limit data, send a request; 644JILI App users receive responses through the support process active since 2021
If needed, small policy updates arrive monthly; as of August 2026, the same rule applies: keep only what is necessary
If you have Privacy Contact Go to the page where you can submit data, cookie, or account-related requests
