l89 App Privacy Policy

This page clearly states data protection, cookies, and user rights

Download l89 APK
l89 Privacy Policy Screen

3 data layers, 1 policy

Token-based security

Card data is not stored directly; tokens and masked references are used

PCI limit

Payment data stays within a limited scope and unnecessary logs are not kept

Clear rights

View, correct, request deletion, and objection is all possible

Session control

Many users in Dhaka complete work in short sessions

Cookie preferences

Language, login, and security preferences are remembered by cookies

Local consent

Only necessary information goes to bKash, Nagad, Rocket

Card data tokenization

1 card number, 0 raw storage

How the l89 token works

How the token works

Card numbers are replaced; tokens are used, reducing exposure of real data

This makes recurring payments easier and risk much lower

l89 Tokenized Card screen

Masked data

Last 4 digits are shown on Dhaka's phone; this provides quick verification

PCI limit and log control

99.6% uptime, 0 unnecessary logs

l89 Limited access

Limited access

Only authorized team members see the payment flow; all actions are recorded

l89 PCI limit board

Log trimming

Does not store card number, CVV, or sensitive parts; only necessary events remain

Processor list

4 main processors, 1 local flow

l89 bKash

bKash

In Dhaka and Chittagong, this is the most familiar flow; necessary references are shared

l89 Nagad

Nagad

Quick verification and easy sessions; less data shown on mobile screens

l89 Rocket

Rocket

On old phones, forms are small, easier and faster

l89 Processor list dashboard

Local match

Setup kept very simple for Bangladesh users

Chargeback data

Among 57,958 reviews, this notice is key

What does l89 keep

What is kept

Date, reference, and verification results kept; amount is protected separately

l89 Chargeback log screen

How long it stays

Legal needs end; limited records are kept, then they are reduced

Digital wallet information

This flow is active in 14 countries

l89 What data goes

What information

Wallet ID, success code, and reference number are not transmitted

Why is l89 different

Why separate

Wallet data kept under a separate policy, reducing exposure of sensitive parts

l89 Wallet data dashboard

Visible on the phone

Usually in 3 steps, the matter is clear; no extra complexity

Your rights and requests

Work starts with 1 message

Right of access

You can see what information you have and request a copy

Request deletion

What is not needed can be requested removed; legal records excepted

Help

Send a request from the l89 Login page; response is usually fast

For additional assistance Privacy contact page See

Login, app, and controls

Cookie settings 2 taps away in l89 App

Logging in with l89 activates session, language, and security preferences immediately, page remains light on older Android phones

Using the l89 APK for updates brings new policies quickly if desired App instructions And Help Center Take a look

Quick reference

Short summary

  • Tokenized card data
  • Limited processor access
  • Cookie preference controls

Practical tips

  • Keep phone notifications on
  • Check session after sign-in
  • Reset cookies if needed

If more is needed Terms And Responsible use Read

Log in Registration