a4 App Privacy Policy

How data is handled in the a4 App

The core of this privacy policy is simple: personal data is kept only as necessary; during login, registration, and APK use the information received is reviewed separately

The average user typically finishes setup within 3 minutes, after which the data are not kept together but separated so that no one can be directly identified

1. Personal and technical data are kept separate

Names, phone numbers, and device information are not mixed in one place; many Dhaka users transact with bKash or Nagad, so transaction notes are kept separate

2. Remove unnecessary items

The information that isn't needed is not on the collection list, making a4 Login and a4 Register processes faster

How anonymization works in the a4 App

Anonymization means data are altered so that a user cannot be individually identified; here, record codes replace names, and area-based aggregates replace addresses

In this method, 625+ usage patterns are observed, but no individual's identity is revealed; thus reports contain numbers, not identities

3. Coded records are created

Each session has a separate code; it helps read reports inside the a4 App

• Names are not shown directly
• Phone numbers are partially redacted
• Location remains at city level only

How aggregated data is created in the a4 App

Aggregated data means looking at data from many users together, for example, among 8.2M+ active users how many log in at night, which is only in summary

This shows usage patterns for Dhaka, Chattogram, and Sylhet, but no individual login history is exposed

4. Make decisions from trends

If buffering is high on any day, it shows up in the average report, after which loading and server routing are fixed

5. Payment patterns kept separate

bKash, Nagad, and Rocket-based patterns are seen only in summary, allowing customer support to respond quickly

Why the a4 App data protection is strong

Data protection requires server uptime of about 99.3%; since starting in 2015, the policies have become clearer step by step

No data can be restored to its previous state, because the dashboard does not contain directly personal-level data, so reports can be read, but a person cannot be identified

6. Not reversible

There is no key inside anonymized records to extract a personal profile; this same policy applies to all places like a4 APK, a4 Download, and a4 Login

7. System rules are the same

The same standards apply to the app, web, and support tools, so the user experience is the same

Cookies, Rights, and Contact

Cookies remember sessions, and settings become easier; if the user clears the browser cookies themselves, they may have to log in again

If you have questions about your data, contact support; notes regarding bKash or Nagad for Bangladeshi users are also shown there if a support ticket has been opened previously

Understanding this page's rules makes using a4 Register and a4 App more transparent; the final word, what data is kept and why, is written openly here

Get a4 APK