Casino / App
33dm collects only what it needs to run your account and process transactions through rails like Nagad and Bank Transfer. This policy sets out exactly what we collect, why we hold it, and what choices you have — access and eligibility depend on your local law and the eligible regions we serve.
When you open an account with 33dm, we collect the registration details you submit — name, contact address and login credentials. When a transaction moves through Nagad or Bank Transfer, we record the reference data needed to match it to your wallet. We do not store your full Nagad PIN or Bank Transfer credentials; we receive only the confirmation references our payment processors pass back to us. Beyond transactions, we collect device identifiers and session data when you browse the lobby or navigate account settings on mobile. This session data helps us keep your authenticated state stable across page loads — it is not sold or shared with advertisers. We also retain records of account activity for the period required under the applicable rules of the eligible regions we operate in; if you are in Bangladesh, availability and data obligations both depend on local law. Any cookies placed by third-party game-content studios — PlayStar, CQ9, PG Soft or Habanero — are governed by each studio's own policies, though we only embed their content under contractual standards. If you have a question about a specific data point, the support route in the contact section of this page is the right starting point.
Transaction reference numbers from Nagad transfers are held against your account record for reconciliation. We do not store your mobile wallet PIN or full account credentials.
Bank Transfer confirmations are matched to your deposit record and retained for the period required under the rules of eligible regions, including Bangladesh where local law applies.
Mobile session tokens keep your account authenticated between page loads. These are not advertising identifiers and are not passed to third-party marketing networks.
Content from PlayStar, CQ9, PG Soft and Habanero may set their own session cookies. We embed their content under contractual data standards, but their individual policies apply.
Not every surface you interact with falls under this single policy document. Understanding the boundary helps you know where to look when a question arises. This policy covers your 33dm account directly — the data created when you register, log in and transact. It does not extend to every third-party service reachable from the site. Read the four boundary points below to see exactly what is and is not inside scope.
Everything generated when you open, authenticate and manage your 33dm account is inside scope. This includes registration fields, session tokens and the login history visible in your account settings.
Deposit and withdrawal records processed through Nagad or Bank Transfer are covered here. The data we hold is limited to the reference identifiers our payment processors return — not your full wallet credentials.
Pages you browse within 33dm, game lobby clicks and mobile navigation events are within scope. We use this data to maintain session continuity, not to profile you for external advertising.
External sites, game-studio portals linked from the lobby, and payment-provider dashboards operate under their own separate privacy terms. We do not control those policies and they are outside the scope of this document.
You are not a passive holder of an account here. This policy gives you concrete steps to review what we hold, correct anything that is wrong, and ask us a direct question if something is unclear. Start from the account settings page — the profile section shows the registration details we currently hold against your account. If a field is incorrect, you can update it directly from that screen; changed details take effect on your next login. For transaction records tied to Nagad or Bank Transfer, the history tab in your account wallet shows the reference entries we hold. If a record looks wrong, raise it with our support team before requesting a formal correction, because most discrepancies resolve at that step. Where local law in Bangladesh gives you a right to request deletion or restriction of your data, you can submit that request through the privacy contact route listed in the support section of this page. We will confirm receipt and respond according to the timeframe required in the eligible regions we serve. Access to any of these rights depends on your local law and your region's eligibility status.
Open account settings and check the profile tab. The fields shown there are the registration data we hold. You can read and compare them against what you originally submitted.
If a name, contact address or login detail is wrong, update it directly in account settings. The correction applies immediately to your active session.
Your wallet history tab shows Nagad and Bank Transfer reference records. If an entry looks incorrect, contact support with the reference number before escalating a formal correction request.
Where your local law in Bangladesh permits, submit a data review or restriction request through the privacy contact route in the support section below. We respond within the timeframe applicable to eligible regions.
If you have a question that goes beyond what this page covers — about a specific data record, a correction request or how a transaction reference is stored — use one of the contact routes below. These are the routes published on the 33dm site. Do not use a channel you cannot find on the published contact page, as messages sent elsewhere may not reach the right team. Availability of support depends on the eligible regions we serve; access is subject to your local law.
Open the chat icon visible on any signed-in page to reach the support team. State that your question is about the privacy policy and a representative will route it to the right person.
Use the email address published on the 33dm contact page to send a written privacy question or a formal data request. Include your account reference number so we can locate your record promptly.
The help section inside your signed-in account lists the current contact options and links to this privacy policy. Check there first — it reflects the most current published routes.
Every data-handling decision we make is designed to keep your account functional and your information contained. We do not sell account data, and we do not share transaction references from Nagad or Bank Transfer with advertising networks. Cookies placed by 33dm itself are session-functional; they expire when your session closes or when you log out. Retention periods follow the rules applicable to the eligible regions we serve — in Bangladesh, local law determines how long transaction and account records must be kept. If you want to know the retention period for a specific data category, contact us through the routes in the support section. Security measures covering your account are described in our terms, but the starting point for any concern is always the support contact route.
We do not sell your information or transaction references to third parties. Nagad and Bank Transfer reference data is used only for reconciliation inside your account wallet.
Cookies placed by 33dm are session-functional. They keep you authenticated while you navigate the lobby or account pages and expire when you log out or close your browser.
How long we keep your account and transaction data depends on the rules of the eligible regions we operate in. In Bangladesh, local law governs the required retention period for financial records.
To ask about data retention, request a correction or raise a security concern, use the email or live chat routes in the support section. We confirm receipt and respond within the applicable regional timeframe.
The questions below come from real account situations — registration, transactions through Nagad and Bank Transfer, cookie behaviour and how to reach us. If your question is not here, the support contact route in the section above is the right next step.
We collect your registration details — name, contact address and login credentials — and the session data generated when you navigate the lobby or account settings. We do not collect payment credentials directly; Nagad and Bank Transfer processors return only confirmation references to us.
No. Transaction references from Nagad or Bank Transfer are held inside your account record for reconciliation only. We do not pass these references to advertisers or data brokers. Game-studio content providers like PlayStar or PG Soft are subject to their own separate policies.
Retention periods follow the rules of the eligible regions we serve. In Bangladesh, local law determines how long financial and account records must be held. If you want the specific period for a data category, send a written request through the email route on our contact page.
Yes. Open account settings, go to the profile tab and update the incorrect field. The change applies on your next session. If the error is in a transaction record linked to a Nagad or Bank Transfer deposit, contact support with the reference number before raising a formal correction.
We place session-functional cookies that keep you authenticated while you move between the lobby, wallet and account pages. They expire when you log out or close the browser. Game-studio content — from studios like CQ9 or Habanero — may set their own session cookies under separate policies.
Send your request by email to the address on the 33dm contact page, or raise it through live chat on any signed-in page. Include your account reference number. We confirm receipt and respond within the timeframe required for your eligible region, subject to your local law in Bangladesh.