Reference

How OKBazz Handles Your Account Data

This page sets out how OKBazz collects, stores and protects the details tied to your account and your bKash, Nagad, Rocket transactions.

Account DataPayment RecordsCookie ControlsSupport Access
OKBazz How OKBazz Handles Your Account Data
SECURITY AND RETENTION

How We Protect Account Records

Your account password and wallet details sit behind standard encryption in transit, and we restrict who on our team can view a raw transaction log. Session cookies keep you logged in on mobile and desktop without asking for your PIN every time you switch screens. We keep transaction and account records for as long as our verification and support processes need them, then they're scheduled for removal. If you want a record changed, deleted, or explained, contact support with your account reference and we'll action it directly.

Encrypted Transmission

We encrypt the connection between your device and our servers when you log in or send a bKash, Nagad, Rocket confirmation, so wallet details stay unreadable in transit.

Login Session Controls

Session cookies remember your login across our website and app so you don't re-enter credentials every visit, though we time them out after periods of inactivity for safety.

Retention Windows

We hold your account and transaction records only as long as verification, support and fraud-check needs require, after which older entries are scheduled for removal from our systems.

Request A Correction

Write to our support desk with your account reference if you want a data entry corrected, deleted, or explained; we handle these requests directly rather than through automated forms.

REACH OUR DESK

Contact Us About Your Data

If you want to know what OKBazz holds on your account, or you want a record corrected, the fastest route is our support desk rather than digging through a settings page. Tell them your registered account details and the wallet you used, bKash, Nagad, or Rocket, so they can pull up the right transaction thread. We reply through the same channel you contact us on, and we log every data request against your account so nothing gets lost between shifts.

Live Chat Message our support desk from inside your account for any question about the data we hold or how a bKash, Nagad, Rocket transaction was logged.
Email Support Send a written request if you want a copy of your account data or want us to correct a wallet reference tied to a Rocket or Nagad deposit.
Account Help Desk Ask us directly about cookie settings or device sessions linked to your account; we can walk you through what's stored without technical back and forth.

Common Questions About Our Privacy Policy

These are the questions we hear most often about how OKBazz handles your account data, your bKash, Nagad, Rocket transaction history, and your control over what's stored. If your question isn't covered here, our support desk can walk you through it directly using your account reference.

We collect your registration details, device details, and the wallet reference tied to your bKash, Nagad, or Rocket transactions so we can verify deposits and withdrawals on your account.

We only share wallet or transaction details with parties needed to process a payment or resolve a support query; we don't sell your data to outside advertisers.

Yes, contact our support desk with your account reference and we'll check what can be removed, keeping in mind some transaction records may need to stay for verification purposes.

Yes, we use cookies to keep you logged in and remember your language choice; you can adjust cookie settings through your browser, though some features may not work the same way.

We log the reference details tied to each Bank Transfer or Upay deposit and restrict access to that log to our verification team, so your wallet details aren't exposed elsewhere.

Reach our support desk directly with your account reference; they handle privacy questions themselves rather than forwarding you to a separate team, and availability depends on your local region.
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.