Direct identity removed
Emails, numbers, and account IDs stay separate; the report only includes aggregated data
How data is kept separate in the 5GBD App
The gist of this page is simple: personal data and aggregate data are not the same; in the 5GBD App, name, device, and usage type are viewed separately so that personal identity does not mix
Many apps accumulate raw data, which can't be used later; here collection is minimized first, then reports are made with anonymized data
Location is only general
Rough areas like Bangladesh or Dhaka are shown; exact addresses are not revealed
Cookie control is easy
Changing cookie preferences doesn't take long; the settings appear in 3 steps
What anonymization means at 5GBD
Many think privacy means only keeping passwords; actually the matter is bigger; the real work is to exclude parts that can identify a person
Here, data is not viewed as a whole but broken into small parts, and from those parts, identifiers of individuals are removed
Which parts stay, which don't
During use, device type, and general interactions are recorded; names, phones, and sensitive logs are kept under separate protection
How we combine data
Not all apps work the same; somewhere raw logs go directly to reports, and elsewhere they are first aggregated; the 5GBD App takes the second path
For example, 100 people's behavior can be shown in one line; there is no need to show separate users, so privacy is higher
What we see when combining
Only two or three common signals may be needed there to understand trends, but individuals cannot be distinguished
What aggregate data is used for
Which page is opened more, on which device the load is slow, and where help is needed; this is understood, so if there is a problem on the 5GBD Login or 5GBD Register page, it is quickly detected
This data can improve content, security, and loading, but personal habits are not looked at separately
Why it can't be reversed
Once data is anonymized, restoring it to its previous state is difficult; this is intentional, because if a reversal path is possible, security breaks
Sometimes someone may want more details, but we keep that limit; this is the real basis of privacy
One-way transformation
If identity markers are removed, they cannot be paired later, so analysis remains safe
Less data, more security
Nothing more than necessary is kept; this reduces risk
Regular review
Policy updates are reviewed; until 2026, if the method changes, the page will change
Your rights and choices
You can learn which data is kept; you can change cookie preferences if you wish, and you can also ask questions through account support
Documents related to bKash, Nagad, or Rocket transactions are also stored securely; requests coming from Dhaka or elsewhere in the country are treated the same
If you have any questions about any part, view the 5GBD Help page and you can submit a direct question on the 5GBD Contact page