Contractual use
The information needed to run the account is kept on this basis; login, profile, and support requests fall under it
This policy is laid out as of October 2026; when you enter the basa8 App, certain account, device, and usage information is automatically collected.
These are kept to simplify sign-in, to detect mistakes, and to maintain security; when using bKash, Nagad, or Rocket, transaction references are also securely documented.
The information needed to run the account is kept on this basis; login, profile, and support requests fall under it
Security, fraud prevention, and performance require some logs; keeping them helps maintain 99.1% uptime
Some records must be kept for a specified period for financial reconciliation or in case of complaints
Here, policy means not just a document; it is about how users use the site, which is the basis for decisions
Permissions in the basa8 App are kept very limited; only what is needed is requested; no unnecessary camera or file access is requested
This aspect is preferred by many Dhaka users, because mobile data is cheaper and control is easier; the risk reduces further if you review permissions during Android APK installation
If there are questions about any information, the Data Protection Officer's team will handle complaints, requests for corrections, and account-security issues
For GDPR-like requests, identity is usually verified, and the first response arrives within 3 to 5 business days if documents are in order
Contact us directly via support channels, briefly state the issue; later, an account ID, login time, or permission screenshots may be requested
If you think data usage is not correct, first notify internal support; that's the fastest path
If not resolved, you may file a complaint with the appropriate supervisory authority; we generally handle data requests and corrections separately, so the response is clear
If someone sees incorrect information, they can request a correction; and if there are questions about device or login activity, it's better to report in a separate ticket
Reset, correction, or data-deletion requests require verification; thus write a clear message and indicate where the problem is
Correct wrong name, phone, or email
You can request a summary of your stored data
Requests to delete data within policy limits can be made
When logging in, if an unfamiliar device is detected, immediately change your password; or you can end the session quickly in the basa8 App, so control stays in your hands
Data remains private when using bKash, Nagad, Rocket or other local methods, but avoiding public WiFi reduces issues on Dhaka's busy networks
All data is not kept forever; kept only as long as needed
Support tickets, security logs, and legal documents may be kept for separate periods, so old device traces are not used for purposes outside their specific intent
When installing the APK, review permissions such as file, notifications, and network access
If any permission feels uncomfortable, you can proceed without it, but some access may be required for sign-in and security verification.
If any part of the policy is unclear, contact the same team that answers basa8 App, basa8 Register, basa8 APK, and basa8 Download.
In support messages, including the account ID and the type of issue will lead to quicker resolution if needed. Contact page More Help guide You can view
Sign up Log inAccount, device, session and security-related data is stored; nothing extra is submitted unless required.
Yes, many permissions can be turned off. However, some access may be required for login or security verification.
Write to support to request corrections; the team will update it if proof is provided.
Local payment references are kept securely; this speeds up coordination and support.
Notify internal support first. If needed, you can later file a complaint with the appropriate authorities.
These numbers show how users are using the basa8 App since service started in 2021, and access is available in 29 countries.
99.1% uptime and a clear support flow keep the experience steady; if you have questions about policy, data-security, or permissions, read this page again.