644jili App Privacy Policy in Bangladesh

This page explains the data protection, cookies, and security of the 644jili App together; Dhaka-based users can easily see where data goes and why.

Open account

644jili App Privacy Summary

4.9 Average rating, 39,193Reviews, 7.3M+ Active users, and 99.9% The uptime figure shows the service running since 2018; in Bangladesh, people using bKash, Nagad, and Rocket prefer a quick setup.

Why this page is needed

Read the privacy policy; it shows what the app collects and doesn't, so view this section first, then 644jili App And 644jili Download Go to page

Card data tokenization

The real card number is kept separate in the system and a token is sent so that the actual data is not disclosed even in repeated transactions

PCI scope control

The payment part is kept small, reducing the review scope, and the security team can quickly detect risks

Cookie control

Cookies are used for session, language, and device preferences; if you want you can reduce tracking from browser settings

Local payment methods

In bKash, Nagad, and Rocket-based flows, only necessary information is shown; many users in Dhaka look for this first.

How data is handled in the 644jili APK

1. First step: required information

Name, device ID, and login session are taken; without these 644jili Login won't work properly, especially on older Android phones

2. Second step: security level

Data encryption and server-side verification work together, so even if the 644jili APK session is opened, no one else can easily log into the account

3. Third step: retention and expiry

Some logs are kept for up to 30 days, then automatically truncated; this helps detect errors, but does not allow extra data to accumulate

Cookies, tracking, and session control

Three types of cookies: essential, functional, and analytical; without essential cookies login won't work, and without functional cookies the language and preferences won't be remembered

You can disable third-party cookies from the browser if you want, but doing so may require re-entering information on some screens, especially on new phones

Session cookies keep you logged in
Local preferences remember Bengali language
Analytics data is viewed separately
Unnecessary tracking is limited

Processor list, chargeback, and wallet data

Only essential data goes to the payment processors; card, wallet, and chargeback notes are not mixed on the same document, so audits are faster

When using local flows such as bKash, Nagad, and Rocket, the reference number and timestamp are the most important; if a chargeback occurs, the support team uses these two items to match the case

What is kept separate

Wallet token, transaction ID, and device signals are not kept in a single file; this makes it easier to detect issues, and internal access is also restricted

Security checklist

Users in Dhaka, Chattogram, and Khulna typically look for the same three things: what is kept, how long it is kept, and how it is deleted; the list below covers that

Log into your account to view the device list
If an unknown session is detected, close it immediately
Limit analytics from cookie settings
Request data copy from support

If Help page Or Contact page Send a question from the support page; the support team usually responds within 1 business day

644jili Register and Login Security

Only the required fields are taken when opening a new account; after 644jili Register is completed, two-step verification in 644jili Login works more securely

If in doubt, change the password, then refresh the session; in the 644jili App, this can be done in under 2 minutes