What’s in scope
Accounts, devices, cookies and session IDs are viewed; many Dhaka users access this from mobile devices
Effective date and first notice
Effective date: October 2026. The information required when using bagh App, bagh Login and bagh Register is stated in this policy
The first thing is that some technical work is done by third-party vendors, and they view specific data
What is it used for
Login, security and preferences are remembered; cookies work when opening pages related to bKash or Nagad
Vendor list and data sharing
The chart below shows six common vendor types, indicating which data goes for which purpose
Vendor 1
Purpose: login verification data: email, session token; region: Bangladesh
Vendor 2
Purpose: cookie management data: preferences, language, device type; region: Dhaka
Vendor 3
Purpose: security monitoring data: IP, browser, unusual sign-in; region: Bangladesh
Vendor 4
Purpose: support ticket data: messages, order reference, device notes; region: South Asia
Vendor 5
Purpose: analytics data: visits, page views, click path; region: Bangladesh
Vendor 6
Purpose: payment verification data: bKash, Nagad, Rocket; region: Dhaka
This list may change from time to time; new vendors are added, the page is updated, and old ones are removed
How we view vendor selection
If anyone asks why this data is needed, the answer here is that each vendor goes through 3 steps
Why this verification is
First, security is checked by matching logs and behavior of the system since 2018
Even on slow networks in Dhaka, opening the policy page and reducing cookies quickly often stalls the session
What data is checked
IP, device model and browser fingerprint are checked; these help detect suspicious logins
If the same account is accessed from multiple locations, a warning appears; then bagh Login asks for further verification
Why is it different on mobile
In Bangladesh, most people use phones, so small screens, less data and faster loading are prioritized
When visiting Rocket or bKash pages, the same cookie policy applies; only the viewing page is different
Agreement and data processing
No vendor works alone; there is a data processing agreement with them, and the scope of work is also specified
Each contract includes four clear items: what data, how long, for what purpose, and who will see it; this reduces unnecessary sharing
Record limit
Only necessary information is shared; extra personal data does not go outside
Record Keeping
Requests are logged; this rule is seen in 51,470 review-type support notes
If any vendor goes outside 99.1% uptime, an alternative path is used so the service does not break
Cookies and device data
Cookies are small browser notes; they remember preferences, language and session, so you don't have to change settings repeatedly
Some cookies are essential; for analytics cookies you can control them from browser settings
Essential cookies
Used for login and page navigation; if disabled, the site won't function properly
Analytics cookies
Which pages are opened more often; this makes bagh App clearer
What happens when the vendor
When a new vendor arrives, the page language remains the same; only the backend provider changes, and notices are updated
When an old vendor is removed, its data retention period also decreases, giving Dhaka users slightly more control
New Notice
A small notice is shown before changes so you can understand in advance
Old data
Only what is needed is kept; unnecessary logs are deleted later.
The same policy applies to the bagh Download or bagh APK page.
More essential pages
In line with policy, view other pages too; these are concise and informative.
Contact
If you have any questions, message support; Dhaka, Chattogram or elsewhere, the same channel works
bagh Login, bagh Register, bagh App and bagh APK; even if you have questions, the support team replies