Data Protection
Personal data travels through encrypted channels with limited access and audit logs kept, so only the necessary team sees it
Effective date: July 2026; This page clearly explains how information is collected, stored, and shared in the jeli App, and that it is done in accordance with Dhaka regulations regarding payment processors, cookies, and user rights
Personal data travels through encrypted channels with limited access and audit logs kept, so only the necessary team sees it
Cookies are used to maintain session, language and login status; you can largely control this from the browser settings
Card numbers are not stored directly; tokenization separates the sensitive parts, reducing reuse risk
This method aligns with PCI concepts; even if the user's payment history is viewed, full card details are not visible
In flows based on bKash, Nagad and Rocket, tokens are used; many users in Dhaka and Chattogram call this method fast
There is a small confirmation step before the transaction, reducing input errors, and logging is easier
Many sites keep everything in one place; payment processing sits in a separate boundary at jeli, so less sensitive data reaches the main system
Here, login, session, and device ID are viewed together; if abnormal behavior is detected at jeli Login, additional verification occurs, and it ends in a few seconds
Data passes through processors such as bKash, Nagad, and Rocket; each flow uses a separate identifier, so risk does not spread
The name and contact information provided when registering with jeli are used only for verification and are later kept within the retention policy
Processor logs are usually archived after a specified period; if not legally required, they are kept for a limited time
Users in Bangladesh may view a copy of the policy to see what is stored; it is clearly stated
In case of a chargeback, usually the transaction reference, time and processor notes are required; jeli keeps these documents separate to facilitate dispute resolution
The full message history is not shown here; only the parts needed for investigation are kept, and it is opened after two-factor verification
If you want to review documents, the jeli Download help page has details; send a request there and the support team will arrange
Wallet address and transfer references are visible, but unnecessary personal data is not stored; this is a simple example of data minimization
Transparency is needed in crypto transactions, so logs are kept small, while security policies remain strong
You may request a copy of your data, request corrections, and in specific cases deletion; this is easily done via a written request in the jeli App
Cookie consent, notifications, and device permissions can be controlled separately, giving users control
Many users in Dhaka want quick problem resolution, so reading policy and help together saves time, especially if you have questions about bKash, Nagad or Rocket
Cookies disabled; many core pages will still work, but the ability to remember login state and language preference may be reduced
Write on the contact page; provide your account or data reference and the team will locate the correct documents
Some preferences may not be remembered; the session may be shorter, but the core information and support will still be available
Send a request with required identification; data that must be retained legally will be kept, the rest will be reviewed
If you understand the jeli App privacy policy, data protection, and user rights together, decision-making becomes easier; if you have questions, contact us directly, and if needed review jeli Register or jeli Download first