What data is stored in the ban21 App?
Only necessary account information, usage patterns, and security logs are kept; personal identity is separated so you are not identifiable in research
Effective Date and Data Use
This policy takes effect from November 2026 and is used for data submitted to the ban21 App for research, security analysis, and experience improvement
By anonymizing, personal identity is hidden; only aggregated types and behavioral patterns are kept, and Nagad, bKash, and Rocket-related transactions are also viewed separately, not by name
First, if this core concept is clear, the rest becomes easier; then see below how anonymization works
Anonymization Method
Imagine a typical night-time user; you just want to log in quickly, and you don't want your data to roam unnecessarily
In ban21, name, phone number, and a unique identifier field are separated for research; those are tokenized, pseudonymized, and aggregated numbers are used, so individuals cannot be distinguished
ban21 APK and Secure Signals
Events from ban21 APK or ban21 App are read only as technical signals, such as which device, which session, and at what time problems occurred; that's what is examined
This part isn't very complex; the goal is one: understand work patterns without personal data, then improve security further
Scope of Research
Users from Dhaka to Chittagong open the app at different speeds, so session time, page load, and support-request types are recorded in research
From this data it shows where the app is slow, where login gets stuck, and which screen needs more help; this data helps improve the ban21 App experience
Differences in local networks are also captured here; sometimes there is a slight delay on 3G, sometimes everything runs smoothly on Wi-Fi, and we look at that separately
Sharing with Educators
Sometimes university-based analysts want to understand security patterns, then they do not get raw personal data; they only get cleaned, anonymized summaries
This does two things at once: research progresses, and user privacy remains intact
What is provided, and what is not provided
Training, reports, and statistics may be shared, but account passwords, real identities, and personal messages are never shared
This rule is not on paper; it is seen in practice, so security concerns decrease, and user trust increases
Opt-Out and Preferences
Not everyone wants to share the same data; if you wish, you can opt out of parts of research usage
For this, after logging in to ban21, check the settings; if needed, contact the support team, they will explain what options exist, in plain language
There is no extra drama here; you keep your preferences yourself, and the system honors that
2x2 Data-Security Summary
99.4%
Uptime is maintained, resulting in fewer mid-session cuts
50,146
Active users whose data is viewed in aggregate
65,049
Support and security improve from review analysis
552+
Safe browsing patterns are learned from topic-specific experiences
Quick Access and Support
Many people first, before viewing new ban21 App Go to the page; some go directly FAQ Read to save time on common questions
If Payment Information or Contact If needed, these are also on separate pages; Dhaka-based bKash users typically want quick responses, and that is kept in mind here
If you want to sign in Login Use if you want to create a new account Register Choose, then review the security policy once
FAQ
Is data from bKash, Nagad, Rocket viewed?
Transaction types are viewed, but not full personal data; this shows payment flow and makes risk identification easier
Can I opt-out after ban21 Login?
Yes, you can change preferences from settings; if needed the support team will guide you step by step
Does ban21 APK have separate security rules?
Yes, whether APK or app, the same data-security policy applies; event logs and behavioral data are stored under the same rules
How much is research data used after ban21 registration?
The information gathered after registration is what is used for improvement; that itself is a safe and effective method without personal data