Why is encryption important?
Data reading remains hard to exploit; in 60BD, sensitive parts are protected along a separate path
How privacy works in the 60BD App
In many apps, rules are hard to understand; here the 60BD App's privacy policy is written in simple language, so you can grasp in 1 minute where data goes
This page also has UGC, moderation, public visibility, and deletion policies; since 2020, 60BD has maintained 99.7% uptime, and that mindset has been applied to data protection
What information is captured in UGC
On many platforms, comments and reports are not shown separately; here your posts, profile name, reported behavior, and support tickets—these four types of UGC are recorded separately
Users in Dhaka, Chattogram, and Sylhet follow the same rules in the 60BD App; user-generated content means not only text but screenshots, feedback, and report history also fall under it
Moderation and verification process
In many places, complaints take a day or more; here abnormal content is automatically filtered, and serious matters are reviewed hands-on within 24 hours
If someone violates the rules, that is also recorded; in an environment of 32,902 reviews and 3.1M+ active users, this verification system is essential, because a single line mistake can later create security risk
How to report abuse
There is no long form here; after logging in, you can send a report in 3 steps from the report button, and the initial response typically comes within a few hours
If you open your own account from 60BD Login, you will also see the report status in the same place; if needed, the support team will review notes related to bkash, Nagad, Rocket transactions
What information is visible to everyone
Not all information is open to everyone; only the profile basic section, name, and some selected settings are visible; sensitive information is hidden behind two levels of control
In the 60BD App, public visibility can be controlled separately; you can show less information if you want, and you can restrict feedback and activity history
Data deletion and retention
If not needed, data is not retained; when an account closure request is made, according to the retention policy, unnecessary logs are removed within 30 days
Some documents have limited time for security and compliance; however your requests, verification-related records, and 60BD APK usage history parts are kept separate so they can be traced later
Security, Compliance, and App Protection
Many sites have policies, but in practice compliance is lower here; account data is encrypted in channels, and on suspicious logins additional verification is required
In Bangladesh, users often work from mobile, so the security rules of the 60BD App and 60BD APK are kept the same; for Rocket, bkash, and Nagad users, transaction information is also separately secured
Main data protection aspects
Why is access limit needed?
Not all team members see everything; access is limited by role, so risk is reduced
Why are verification steps?
To prevent unauthorized logins, two-step verification is used; whether logging in from Dhaka or elsewhere, the controls remain the same
Why are documents kept separate?
Compliance-required documents are not kept with general activity; this speeds up review
Why retention limits?
Keeping unnecessary data is not right; after a specified period, old logs are deleted
If you have any questions, write to support
If you have questions about privacy, data protection, or account compliance, contact us directly; after 60BD Login, opening a support ticket makes your case quickly findable
For Bangladesh users, notes related to bkash, Nagad, and Rocket accounts are also visible; if verification is needed, for more details Help center privacy guidelines See, and learn about registration Registration page Read
Register Log in