Effective date: July 2026
How your information is collected, stored, and used in the bd345 App is clearly stated here
The language has been kept simple for users in Dhaka and Bangladesh.
Average rating
Review
Active users
Uptime
| Vendor | Work | Shared data | Region |
|---|---|---|---|
| Google Analytics | Helps understand site usage | Device ID, page visits, and session data | International |
| Cloudflare | Security and bot protection | IP address, traffic signals | International |
| Meta Pixel | Helps measure relevant ads | Cookie ID, event data | International |
| Firebase | App status and notification support | Device tokens, log data | International |
| OneSignal | Helps send messages | Push tokens, browser data | International |
| Internal system | Account security and login verification | Email, device data, session token | Bangladesh |
What data is collected
Account, device, and browser information arrives at bd345 App
How cookies work
What happens when a vendor changes
Data protection
Security at transmission layer, limited access, and log monitoring
Some apps hide vendor lists; here they are open, so you can see who views the data.
In Dhaka, many users top up with bKash or Nagad, and payment processing data is kept separate there
Vendor verification in the bd345 App
Many sites show only the name, but not the work type; here each vendor's tasks, data, and region are listed separately.
Risk is considered before adding a new vendor, and unnecessary access is removed; in practice this means only the necessary signals go; nothing extra.
Security and usability balance
Data should not be kept in one place; sign-in, cookies, and analytics go through separate channels.
This keeps page loads fast, and basic features work on slow networks in Bangladesh.
Contracts, DPA, and data limits
Vendor data processing contracts with vendors specify use, retention, secure storage, deletion conditions, and responsibilities clearly
If any vendor requests extra data, it is not approved; without strict limits, tracking becomes difficult later.
What changes, what doesn't
When a vendor changes, the notice updates; how long old signals are kept is also documented.
The biggest limit is one: browsing data is not sold; what the user provides stays within the work.
What happens when a vendor
When old integrations are stopped, the new one is tested before launch; login, cookies, and session behavior do not break.
If any tool is no longer needed, its access is cut; leaving it behind increases risk.
Your rights and contact
You can view, correct, or delete data; cookie preferences can also be changed within specific limits.
For questions about bd345 Login, data updates, or account security, contact support; payment notes related to bKash, Nagad, and Rocket can also be checked.
For more details bd345 contact page More Terms See Payment policy Reading it will make top-up and verification clearer.
Download the bd345 APK