Reference

Privacy Policy How We Handle Your Information

We collect account details, device information and payment records when you use bdok — this page explains what we gather, why we need it, and how you can request changes or deletion.

Account data handlingPayment record storageDevice access transparencyDeletion request pathCookie disclosure
bdok Privacy Policy How We Handle Your Information
PRIVACY CONTACT

How to Request Access, Changes or Deletion

If you want to see what data we hold, correct an error, or delete your account and associated records, reach us through any of these channels. Response time depends on request complexity.

Data Request Form Submit a privacy request through the account settings panel — select Data Access, Correction or Deletion, then confirm your identity with the phone number or email on file. We review each request and respond within a reasonable timeframe.
Email Privacy Team Send your request to our privacy contact address — include your registered phone number or account ID so we can verify ownership. Requests from unverified addresses take longer to process while we confirm identity.
Live Chat Escalation Open a live chat session from the support tab, state that your question is about privacy or data deletion, and the agent will escalate to the privacy team. Have your account details ready for verification.
DATA SECURITY

How We Protect & Store Your Information

We encrypt payment details in transit and at rest, restrict internal access to customer data, and log every query against your account record so you can audit who viewed what. Cookie policy, retention periods and third-party sharing are detailed in the full policy text.

Encryption Standards

Payment data moves over SSL connections and is stored in encrypted database fields. Session cookies are marked secure and httpOnly to prevent client-side script access. Your bKash, Nagad and Rocket wallet identifiers are never logged in plain text.

Access Logs

Every time a team member views your account record, the system logs their ID, timestamp and reason. You can request a copy of your access log to see who looked at your data and when.

Retention Policy

Active accounts retain all data. Closed accounts keep transaction history for dispute resolution, then anonymise personal identifiers after the retention period. You can request early deletion subject to legal and operational constraints.

Third-Party Sharing

We share payment details with bKash, Nagad or Rocket only to process your transaction. We do not sell data to advertisers. Legal requests in eligible jurisdictions may require disclosure of account records and transaction history.

Privacy Policy FAQ

We collect your phone number, email, date of birth and the bKash, Nagad or Rocket wallet details you provide for deposits and withdrawals. Device data includes IP address, browser type and login timestamps.

Transaction history is retained for dispute resolution and regulatory purposes, then personal identifiers are anonymised or deleted after the retention period. You can request early deletion subject to legal and operational constraints.

Yes. Submit a data access request through account settings or email the privacy team with your registered phone number. We will send a copy of your account record and transaction history within a reasonable timeframe.

No. We share payment details with your wallet provider to process transactions, and we may disclose records if required by legal process in jurisdictions where the service operates. We do not sell data to advertisers.

Submit a deletion request through account settings, email the privacy team, or escalate via live chat. Verify your identity with the phone number or email on file, and we will process the request subject to retention obligations.

We use session cookies for login state and language preference, plus analytics cookies to measure page performance. You can disable non-essential cookies in browser settings, though login and payment functions require session cookies to work.
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.