Reference

How We Handle Your Account Information

We collect what we need to run your 726 bd account and process deposits through bKash, Nagad and Rocket. This page explains what data we keep, why we use it, and how you can request changes or removal.

Account data protectionWallet transaction recordsCookie & session handlingSupport contact channelsUser rights & deletion
726 bd How We Handle Your Account Information
CONTACT US

Reach Us About Privacy Concerns

If you have questions about what data we collect, want to update your account information, or need to request data deletion, contact our support team through any of these channels. We handle privacy requests during business hours and aim to respond within two working days.

Live Chat Open the chat widget from any page while logged in. Our team can pull up your account details and walk you through data requests, correction steps or deletion procedures in real time.
Email Support Send your privacy question or data request to our support inbox. Include your registered phone number so we can verify your account and process your request securely without exposing your information.
Account Settings Log in and head to the profile section to update your phone number, email or password directly. For full account closure or data deletion, reach us via chat or email since those actions require manual verification.
DATA PRACTICES

How We Protect Your Information

We encrypt payment data when it travels between your device and our server. We store passwords in hashed form so even our own staff cannot read them. We log wallet transactions so you can verify every bKash, Nagad and Rocket payment from your history page, and we keep those records secure so unauthorized users cannot access your deposit details.

Encryption in Transit

Every page on 726 bd uses SSL, so your login credentials and wallet details are encrypted while they move from your phone to our server.

Secure Password Storage

We hash your password using industry-standard algorithms. That means we store a one-way fingerprint of it rather than the plain text, so even if someone accessed our database they could not retrieve your original password and use it elsewhere.

Transaction Logs

We keep a record of every deposit and withdrawal so you can audit your own payment history. Those logs include the timestamp, amount, wallet provider and status.

Cookie & Session Policy

We set a session cookie when you log in so you stay authenticated as you move between lobby pages. We also drop a language-preference cookie so the site opens in English on your next visit.

Privacy Policy Questions

We collect your phone number, email address and payment details. We need the phone number to send login codes, the email for password resets, and wallet information to process bKash, Nagad or Rocket deposits and withdrawals.

We share payment details only with the wallet provider handling your transaction. If you deposit via bKash, we send your phone number and amount to bKash so they can complete the transfer. We do not sell or rent your data to marketing companies.

We retain transaction records for a compliance period that depends on local regulation in eligible regions. Account credentials and personal profile details are deleted once that retention window closes, unless you reopen your account before then.

Yes. Contact our support team via live chat or email and ask for a data report. We will verify your identity and send you a summary of the personal information, transaction history and session logs we hold for your account.

Log in, open account settings, and edit your contact details directly. If you need to change the phone number linked to wallet deposits, reach our support team so we can verify the new number before updating your payment profile.

We use a session cookie to keep you logged in and a preference cookie to remember your language choice. You can clear or block cookies in your browser, but doing so will log you out and reset your language setting each visit.
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.