bajee App privacy policy
This page explains what information is stored, why cookies are needed, and what you can control for bajee App users from Dhaka and all of Bangladesh, with the language kept straightforward
Download bajee APK bajee Login Guide
Effective date: July 2026; this policy applies to bajee App, bajee Download, and bajee Register users
Cookies, device information, and session data make sign-in faster; security verification is easier for bKash, Nagad, and Rocket-based users
Data types
Account name, email, device ID, and log records may be kept to troubleshoot issues, ensure security, and keep the session running
How cookies work
Cookies remember preferences, preserve language, and keep the browser session alive; page loads stay stable on slow networks in Dhaka or Chittagong
Data protection
Standard encryption is used in data transmission; unnecessary data is not kept for long, and access is restricted
Your rights
You can view, correct, and delete your data; after verification, the team typically responds within 1 to 3 business days
bajee App browser controls
Many sites run all cookies together; here from browser settings you can control third-party cookies, cache, and tracking
In Chrome, Firefox, and Android WebView, these controls are shown separately; if some features are disabled, the bajee Login screen may prompt for a new session
What to change
Block cookies, clear site data, and limit auto-fill; this will prevent forms from auto-filling quickly, but increase personal control
bajee App internal controls
In-app notifications, language, and security options are shown separately; after starting the bajee APK, these preferences can be easily changed in the profile section
Extra verification on first sign-in on a new device is normal, especially if you sign in on a phone outside Dhaka
Session and
Remove unfamiliar devices from the active session list; if notification permissions are requested you can disable them at any time later
Third-party cookies
Analytics tools, embedded videos, and security services may have separate cookies; these do not directly control your account, but help with usage analytics
If you sign in quickly with bKash or Nagad, some verification cookies may be temporarily active; even if there are Rocket-related references, they only identify the session outside of transactions
Control limits
If some third-party components are blocked, media or reports may not load; the core account features usually remain active
Cookies duration
Session cookies usually end when the browser closes; persistent cookies last for a specified period to remember preferences and language settings
When they expire they are automatically deleted; this is part of data minimization, and no unnecessary old data accumulates
If you have questions, write to the bajee Contact page; for verified requests about accounts, cookies, and data protection, clear answers are provided, and if needed bajee Register or bajee App settings are shown