bd11 App Privacy Policy

Effective date: September 2026: bd11 App's data protection

Effective date: September 2026; many sites speak in vague terms, but the bd11 App clearly states which data is captured and why payment processors, cookies, and account security come together to provide the full picture in one place

There are no extra words here bd11 App or bd11 Download If you look into it, this page will show where data goes

Card tokenization and bd11 Login

The full card number is not stored; instead a token is used, so risk is reduced and the same card is not available on subsequent logins

Even after bd11 Login, sensitive information is not shown directly; many users in Dhaka operate accounts with bKash or Nagad, so a token-based flow is used instead of the card

Fast yet careful

Tokenization is set once, then the work is easy for you bd11 Platform From there you can view settings, and you can update later if needed

PCI scope and bd11 APK

PCI scope is kept small; that's the point, so use bd11 APK or mobile browser, the payment portion remains at a separate security level

In this method, the app's general part and the payment part do not mingle; during transactions with bKash, Nagad, and Rocket data limits remain strict, so only the necessary parts are shared

Less data, less hassle

Less access means fewer errors; this structure stays lightweight for users with older Android phones

Processor list and bd11 Register

bd11 Register: it's clear which processor data is taken; only as much as is needed to run the transaction, nothing more

Here, typical Bangladesh-based processing flow, verification steps, and session logging are used; Dhaka users see faster responses, as routing is kept lightweight

What data goes, and what doesn't

Your full profile is not sent to the processor unless needed Help page You can also review which data is shared

Chargeback data and bd11 App

In a chargeback, it is not forgotten data; evidence-based records are required; that record is stored separately in the bd11 App to reduce dispute time

Typically date, reference, and processor status are kept; for Nagad or card-related problems this data provides a clear trail, and users can understand the status

No fuss, paperwork

No need to guess from messages, if needed Contact Page From there you can talk with the team

Crypto wallet data, cookies, and user rights

If crypto wallet data is present, it is also kept limited; address, network, and transaction reference are not usually captured

Cookies are used to keep login, preferences, and sessions stable; you may control cookies from the browser, and you can also submit data protection requests

How your rights work

You can view, correct, or restrict data; delete requests are also possible if needed, but some records are retained due to legal retention

Policy is simple: as much as needed, not more; using bd11 Login, bd11 App, and bd11 APK, the same rule applies

Get help, and get a clear answer

If any clause is unclear, write to support from Dhaka or any other place in the country; questions about bKash, Nagad, Rocket, or account data will receive a specific answer from the team

One last thing: the bd11 App privacy policy is not paper rules; usable controls after bd11 Register let you monitor your own data

Register Log in