Data stored in separate tokens
Card-related data is not stored directly; tokens are used, so the actual value stays in fewer places
Effective date: October 2026
jilibdt App privacy policy, data protection, cookies
This page explains what information is kept, why it is kept, and how it is safeguarded with separate protections for Bangladesh users; the jilibdt App rules are written clearly, concisely, and directly.
Why jilibdt App inspires trust
4.6
Average rating
83,770
Reviews
701K+
Active users
99.7%
Uptime
Users in Dhaka, Chattogram, and Khulna prefer quick access, so the jilibdt App keeps less data, more actions, and explanations clear
Card data tokenization
Sensitive data protection
Session, identity, and transaction sources are kept separate; data from one area does not appear in another
Restricted record access
Only the necessary team can view specific records; nothing opens without your permission
This is particularly useful for users who complete quick tasks with bKash or Nagad; tokenization keeps the card or wallet's core data from spreading
PCI scope and controls
Only essential parts work
Payment processing is limited in scope; data does not enter unnecessary systems
Regular audits
Controls, logs, and permissions are reviewed regularly; if errors are found, they are quickly corrected
Access control
Not all team members can view all records; role-based permissions are the main rule
If you log in on mobile, the system only takes session-related necessary information; it works reliably even on Dhaka's busy networks
Processor list and local payments
jilibdt App handles data in line with local channels; when working with bKash, Nagad, and Rocket in Bangladesh, verification moves faster
Processors operate under separate agreements, so who sees what is clearly stated in the policy
How chargeback data is used
Complaint documents
When problems arise, the relevant documents are retained to speed up investigations
Transaction history
Dates, references, and status summaries are kept; the full card number is not shown
Warning note
If an unusual request occurs, a small note is created to assist subsequent verification
During a chargeback, no extra information is kept; only the necessary parts remain, so records are tidy and clear
Crypto wallet data
Wallet address, network, and confirmation status may be stored in separate files; personal identity is kept at a separate level
This makes records easier to find and reduces the risk of leaks
Your rights, your control
Request a copy
You can request a summary of the information you have stored; typically it contains basic records
You can correct errors
If name, email, or contact information is incorrect, please request correction
Request to delete some data
Data no longer needed can be requested for removal; legal records may remain separate
Typically a two-step request: identity verification first, then the necessary steps
What you should know about
Session cookie
Keeps you logged in; you don't need to sign in again
Language preference
The language you see is remembered, so the next visit is faster.
Load speed
Keeping a small configuration makes the page load quickly and helps even on slow networks
Some Android users may allow the browser the first time; cookies work normally afterward, and it remembers settings.
For more information, see jilibdt Download and jilibdt APK
Also check the usage rules in line with the policy; on the jilibdt Download, jilibdt APK, and jilibdt App pages you will find device-related information
If you have questions about payment records or cookies, the support team is available from Dhaka or another district; the answer is provided clearly in the same way
Frequently Asked
How long is my data kept?
As long as an account or legal requirement exists, records may be kept
Can I disable cookies?
Yes, you can change the browser settings, but some benefits may be reduced
Is bKash or Nagad information shared?
No, only the necessary processing parts are used; they are not shared unnecessarily
If you still have questions after reading the policy, write on the contact page; transparency, control, and user rights are the main concerns