Reference

How dcg33 Handles Your Personal Information

Your account data belongs to you, and we treat it that way. This policy sets out exactly what we collect when you use dcg33 — including wallet details from bKash, Nagad, and Rocket transactions — how we store it, and what rights you hold…

Account data protectionbKash, Nagad, Rocket wallet privacyYour rights to access and deletionClear retention periodsNo third-party selling of your data
dcg33 How dcg33 Handles Your Personal Information
PRIVACY CONTACT PATHS

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, our account support team is the right place to start. We keep a dedicated privacy contact path separate from general account help so your request is handled with the attention it deserves.

Team online

Email Support

Send your data request or privacy concern to our support email. Include your registered account ID so we can locate your records and respond without delay.

Live Chat

Open the live chat window from your account dashboard. Mention that your query is a privacy matter and the agent will route it to the right team quickly.

Account Settings

Some data preferences — including communication opt-outs and cookie choices — can be adjusted directly inside your account settings without contacting support at all.

HOW WE PROTECT IT

Data Handling, Cookies and Account Security

We apply technical and organisational measures to keep your account data safe. Wallet identifiers from bKash, Nagad, and Rocket are stored in encrypted form. Sessions are monitored for unusual access patterns, and your password is never stored in plain text. Here is what that looks like in practice across four key areas.

Cookies and Tracking

We use session cookies to keep you logged in and analytics cookies to understand page performance. You can block non-essential cookies via your browser without losing account access.

Data Retention

Account records are kept for as long as your account is active and for a period after closure as required by applicable law. You can request deletion of non-mandatory data at any time.

Account Security

Login sessions use OTP verification tied to your registered mobile number. Any change to your linked bKash, Nagad, or Rocket wallet triggers a re-verification step before it takes effect.

Requesting Changes

To update, correct, or request removal of personal data, contact support with your account ID. We aim to acknowledge your request and confirm the next step within a reasonable period.

Privacy Policy Questions We Hear Most

These are the questions we receive most often about data, account privacy, and your rights as an account holder on dcg33. If your question is not covered here, the support team can help directly.

We collect your name, contact details, device information, and payment records from bKash, Nagad, or Rocket transactions. Activity logs from your sessions are also kept to maintain account security.

We share data only with payment processors who need it to clear your wallet transfers, and where local law requires disclosure. We do not sell your personal information to any third party.

Contact our support team with your account ID and a deletion request. We will confirm which data can be removed and which must be retained under applicable legal obligations before proceeding.

Records are held while your account is active and for a further period after closure as required by law. The exact period depends on the type of data and the legal framework in your eligible region.

Yes. Submit a data access request via support with your registered account ID. We will compile the relevant records, including wallet transaction logs and session history, and share them with you.

Access to dcg33 and how your data is handled both depend on your local law and eligible regions. We recommend checking whether use of the platform is permitted under the rules that apply to you.
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.