BD10 App Privacy Policy: Information security and retention

This page shows how long your information is kept and why it is kept when using the BD10 App, and what is protected, which should be clarified up front

BD10 Privacy Policy Screen

How long is each data kept

Data storage in the BD10 App is always according to need; many Dhaka users operate accounts with bKash and Nagad, so transaction records are kept separate

The main rule here is one: as long as needed, only that much is kept; some data for 24 months, some for 5 years, and usage logs are kept for a very limited time

Data types

Registration, login, device, payment, cookies, support messages

How long kept

From 30 days to 5 years as needed

Why kept

To keep the account active, security, reconciliation, and support

Registration information

Kept until the account is active

Transaction data

Kept for up to 5 years for account and fraud controls

Cookie data

According to the browser settings, 30 days or less

Why account data kept

The name, phone number, and login records provided during registration keep the account secure; if a wrong device is detected during BD10 Login, the system quickly alerts

This information helps verify your identity; after BD10 registration, signing in from Dhaka or another city on a new device requires stricter verification

Name and number

Used for account verification and communication

Device records

Used to detect unusual logins

Session data

Active sessions kept for less than 30 days

How transaction data is secured

Notes related to your bKash, Nagad, and Rocket are used only for verification and reconciliation; in the BD10 APK these records are kept in a separate layer to keep accounts clear

Transaction history is not deleted in a day; if there is trouble, support reviews records within 48 hours to resolve, so older data must be kept for a while

bKash records

Used for questions about incorrect charges or reconciliation

Nagad records

Kept to reconcile account funding

Rocket data

Helps identify unusual activity

Cookies and usage data

Cookies remember your preferences in the BD10 App; these keep language, session, and fast-load settings correct

Such data is not kept long; usually browsing data 30 days, and security logs are reviewed within 90 days

Preferred cookies

Remembers language and viewing

Session cookie

Once logged in, hassles are reduced

Security log

Detects failed attempts and suspicious access

Pages can still be viewed when cookies are off, but some benefits, such as faster navigation, may be reduced

What happens when an account is closed

Even if the account is closed, not all data is deleted at once; for legal, security, and accounting reasons some records may be kept for up to 5 years

The main goal here is transparency; you may request old communications be deleted if it is not a mandatory record

Permanent records

Limited documents kept for account and fraud controls

Delete request

Requests can be made to delete data that is not required to be kept

Retention limit

Data is archived or deleted when no longer needed

Your rights and our contact

You can view, correct, and learn about usage limits in the BD10 App; if you need help Contact page See the full policy explanation Terms Read

The support team strives to respond within 24 hours for a clearer understanding. Help Center More Responsible gaming Page will be useful

Right to view information

You can find out what information is kept

Right to correction

Request to correct incorrect information

Right to limited use

Can request reduced usage when unnecessary

If you have any questions about BD10 Login or BD10 Register, write directly to Support. Our privacy and data protection rules for the BD10 App are the clearest.

More clear images to understand the policy

BD10 Data Protection Document

How documents are organized

Accounts and verification records are kept separate

BD10 Cookie Settings Page

Cookie Settings

Browser preferences and session control are here

BD10 Rights and Preferences

User Rights

The path to view, modify, and send requests remains clear

Log In Register