Reference

How beg33 Handles Your Personal Information

This Privacy Policy sets out exactly what data beg33 collects when you open an account, make a deposit via bKash, Nagad or Rocket, and use the platform — and how we protect it.

Account data protectedbKash, Nagad, Rocket payment privacyYour right to access your dataClear data retention rules
beg33 How beg33 Handles Your Personal Information
PRIVACY CONTACT PATHS

How to Reach Us About Your Data

If you want to request a copy of your data, ask us to correct something or raise a concern about how your information is handled, reach out through any of the channels below. We aim to respond to privacy-related account requests within a reasonable timeframe. Availability of our support channels depends on local law and eligible regions.

Email Support Send your data request or privacy question to our support email. Include your registered account email and the wallet number linked to your account for faster matching.
Live Chat Open the live chat window from any page on beg33. For privacy queries, select the account topic so it reaches the right team without delay.
Account Help Centre Log in to your beg33 account and navigate to the Help section. You can raise a data access or correction request directly from your account dashboard there.
DATA HANDLING PRACTICES

How We Protect and Manage Your Information

We apply SSL encryption across all account pages and payment flows, so data you send — including bKash or Nagad transaction references — travels encrypted. Internally, access to account data is restricted to staff roles that need it to operate or support your account. We keep your data for as long as your account is active and for the period required by applicable law in eligible regions; after that, we delete or anonymise it. You can request a full copy of your data or ask us to correct inaccurate details at any time through our support channels.

SSL Encryption

Every account session and payment submission on beg33 runs over SSL. Your bKash, Nagad and Rocket transaction data is encrypted end-to-end during transfer.

Cookie Use

We use session and functional cookies to keep you logged in and remember your preferences. You can manage cookie settings through your browser without losing account access.

Data Retention

Account records are kept for the duration your account is active plus any period required by law. We do not hold data longer than necessary and remove it on account closure.

Correction and Access Rights

You have the right to see what data we hold, correct anything inaccurate and ask us to delete data where law permits. Contact our team via live chat or email to start that process.

Your Privacy Policy Questions

These are the questions we hear most often about how beg33 handles account and payment data. If your question is not here, reach out via live chat or the Help section of your account.

We collect your name, email, phone number and login credentials at registration. Once you make a deposit, we also record the transaction reference and wallet number for bKash, Nagad or Rocket payments.

No. Your mobile wallet PIN is never sent to or stored on our servers. PIN entry happens inside your bKash, Nagad or Rocket app, and only the completed transaction reference reaches us.

Yes. Log in to your account, go to the Help section, and raise a data access request. Alternatively, contact us via email or live chat with your registered email and linked wallet number.

We keep records for the period required by applicable law in eligible regions after account closure, then delete or anonymise them. The exact duration depends on local legal requirements.

We share data only with payment processors like bKash or Nagad gateways and identity verification services, strictly to complete transactions or confirm your identity. We do not sell your data.

Send a correction or deletion request through live chat or email. Include your account email and specify what needs to change. We will confirm once the update is made on our end.
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.