Reference

How bd1k Handles Your Personal Information

This page sets out exactly what data we collect when you open an account, make a deposit via bKash, Nagad or Rocket, and use our lobby — and how we keep that data secure.

Account data protectionbKash, Nagad, Rocket payment privacyCookie and device data disclosureYour right to request changesContact path for data queries
bd1k How bd1k Handles Your Personal Information
DATA HANDLING PRACTICES

How We Protect and Manage Your Information

We apply encryption to data in transit and at rest. Account passwords are hashed, not stored in plain text, and access to your account is protected by an OTP sent to your registered mobile number each time you log in from an unrecognised device. We review data retention regularly and remove account data that is no longer required for operational or legal purposes. You can request a copy of your stored data or ask for corrections at any time through our support channels.

Payment Data Security

Your bKash, Nagad and Rocket transaction references are stored only as needed to reconcile deposits and withdrawals. We do not retain your wallet PIN or full payment credentials.

Cookie Usage

We use session cookies to keep you logged in and analytics cookies to understand which lobby sections are used most. You can manage cookie preferences through your browser settings.

Account Access Logs

Every login attempt — successful or failed — is logged against your account. If you notice unfamiliar access, contact support immediately via live chat or email.

Data Retention Policy

We keep your account data for as long as your account is active or as required by applicable rules. When retention is no longer necessary, we delete or anonymise the records.

DATA CONTACT PATHS

Reach Us About Your Privacy

If you want to request access to your stored data, ask us to correct something, or raise a concern about how we handle your information, use any of the channels below. We aim to respond to all data-related queries within a reasonable time. For payment-specific queries — such as a bKash or Nagad transaction record — include your account number and the date of the transaction so we can locate it quickly.

Live Chat Open the chat widget from any page in the lobby. State your account details and your data request clearly so the team can route it to the right person.
Email Support Send your privacy query to our support address listed in your account dashboard. Include your registered mobile number for faster identification.
Account Help Centre Log into your account and navigate to the Help section. You can submit a formal data request form there, which creates a reference number for your query.

Common Questions About Your Privacy on bd1k

Below are the questions we hear most often about data, cookies, account security and your rights. If your question is not covered here, reach us through live chat or the Help section inside your account.

Yes, we store the wallet number you use to deposit or withdraw so we can match transactions to your account. We do not store your wallet PIN or app login credentials.

Yes. Submit a data access request through the Help section in your account or email support with your registered mobile number. We will respond within a reasonable time.

Contact us via live chat or the account Help section. State what needs correcting or deleting. We will review the request and confirm the outcome to you directly.

We use session cookies for login continuity and analytics cookies to see lobby usage patterns. You can block or delete cookies through your browser settings, though some features may not work fully.

Access to your data is limited to staff with a specific operational need — account verification, payment reconciliation or support queries. We do not sell or share your data with third parties for advertising.

Your rights and our obligations depend on your local law and the eligible regions we serve. We encourage you to check whether access to bd1k is permitted under the rules that apply to your location.
Reference

Privacy Policy

Service availability depends on eligible regions and local law. Users should check local rules before opening an account.

Access may be available only where local law permits.