r77 App Privacy Policy: Data protection in plain language
Dhaka users often read the policy first, then sign in; this page clearly explains the r77 App's privacy policy, cookies, and user rights
Download r77 APK r77 Login Guide
Trust in the r77 App at a glance
We saw these numbers earlier while reading the policy; they give a quick idea for Dhaka and users across Bangladesh
Average rating
Total reviews
Active users
Uptime
How card data tokenization works
When you do something with a card, the real number is not stored directly; a system token is used, so even if data is read, the real card data cannot be seen
bKash, Nagad, and Rocket: records remain separate under the same rule, making verification faster, and sensitive data is limited to a small controlled section
- The actual card number is not stored on the server
- A token, once created, is reused
- Transaction logs are stored separately
When a user logs in from the APK, the same security layer remains, so data is not exposed in one place even after registration or login
r77 Login PCI scope and controls
What security do I get when I log in? We have seen this question many times; the answer is simple: PCI-like controls with restricted access, log monitoring, and minimal data retention
Only the necessary parts are shown; many Dhaka users want to load quickly on mobile networks, so light sessions and small data flow are important here
- Access for authorized teams only
- Sensitive parts are governed by a separate
- Session timeouts are enabled regularly
Even if you use the r77 App, the same controls apply, so the post-login data flow is more restricted
Processer list: who sees what
Which information goes to whom is the most important point here; bKash, Nagad, and Rocket only view their own verification parts
User name, time, and reference number are checked against the full balance history; personal notes do not leak to anyone
- bKash: payment verification and status
- Nagad: cross-check and record confirmation
- Rocket: transaction tracing and support investigation
Information is shared less with registered accounts, so risk decreases; users generally understand this later when they see multiple methods together
Why cookies and session are
Without cookies, many tasks have to be repeated; we observed that remembering login information and language preferences makes the next visit much easier
There is an option to disable unnecessary tracking cookies; this is especially useful for users on limited data plans
Session cookies
Keeps login easy within a browsing session
Login remains active during the sessionPreference cookies
Remembers language and layout
The same settings remain on returnAnalytics cookie
Indicates which page is loading slowly
Usage may vary by deviceSecurity cookie
Helps prevent unusual logins
Faulty sessions are closed quicklyIdea cookies
Which part takes longer to load
Used for improvement planningConsent record
Cookie preferences are saved
Can be reset if changes are desired
Understanding data protection in four
This is actually very simple: data is collected, verified, kept in a limited space, then deleted or updated if needed
Step 1
Data is collected minimally
Step 2
Sensitive parts are tokenized
Step 3
The processor looks only at the necessary
Step 4
You can request rights
Invoice information and chargeback records
Sometimes questions arise about a transaction; then the record's time, reference, and channel are checked so the issue can be resolved in 1-2 steps
If a chargeback exists, only minimum information is used for investigation; private messages or unnecessary notes are not included here
- Transaction time, status, and reference are kept
- Support only looks at verification information.
- Separate log used for dispute resolution.
Some Dhaka users keep reference number screenshots; it helps, especially to match with bKash or Nagad.
What happens to crypto wallet data?
If a user tracks the wallet, it is viewed only in a limited way; address, time, and network ID are not shown, nothing else is kept.
We have seen that transparency in this section is very important, so users may request export or view history.
- Wallet address may be shown partially.
- Only for verification, blockchain records are used.
- Unwanted sharing is stopped.
This applies to the r77 App, r77 APK, and web versions; same security layer, device changes.
Your rights and request path.
What can I request? This question is very common; you may request a copy, correct mistakes, and delete within specified limits as well.
Requests actually begin after verification; there are usually two steps: identity confirmation, then viewing records separately and securely as needed.
- You have the right to obtain a data
- You can correct incorrect
- Requests can be made to delete some parts.
- Cookie preferences can be
If you want changes after r77 Login, just inform support; a clear request speeds the process up quickly.
Direct contact regarding privacy.
If questions are not visible on screen, go to the contact page and specify topics, such as data copy, cookie settings, or verification.
There you will find help for r77 Login, r77 Register, and r77 App; use the button below to go to APK.
Download r77 APK Open the contact page.