Sports / Mobile
dk 33 is clear about what data we collect when you use our platform, why we collect it, and how you can review or correct it. Access to our services depends on your local law and eligible regions — this policy sets out exactly what that means for your account.
This policy applies to every interaction you have with dk 33 — from the moment you open an account through to each session you log in, every transaction you make, and every support message you send. We collect the information needed to operate your account: your registration details, login records, device identifiers and the transaction data associated with payments you process through Nagad or Bank Transfer. We do not collect more than what is operationally required, and we do not sell your personal data to third parties for their own marketing purposes. Where we share data with processors — for example, payment infrastructure that handles your Nagad transfer or Bank Transfer instruction — those processors are bound by data handling terms consistent with this policy. Your account activity, including deposit and withdrawal records, is retained for the period required under applicable rules and then deleted or anonymised. Because access to dk 33 depends on your local law and eligible region, the specific obligations and rights described in this policy apply to the extent permitted in your jurisdiction. If you have questions about how a particular data point is used, the support routes listed on this page are the right place to start.
Not every service or link connected to your dk 33 session falls under this policy. Understanding the boundary helps you know who to contact when a question arises.
Creating and managing your dk 33 account — including login credentials, personal details, session history and any communications you send through your account dashboard — falls fully inside the scope of this policy.
Payment instructions you submit through Nagad or Bank Transfer are processed using payment infrastructure that operates under its own data terms. We share only the data needed to complete your transaction; we do not retain full payment credentials on our servers.
Browsing behaviour on dk 33 pages — pages visited, game categories opened, session duration — is captured through standard analytics cookies. You can review our cookie behaviour in your browser settings, and we describe what each category does in the cookie section below.
Links or embedded content from studios such as Pragmatic Play, PG Soft, Habanero and Spadegaming operate their own environments. Once your device loads a game frame, the studio's own data terms apply to that session. dk 33 does not control or speak to those terms.
You have concrete actions available to you at any point in your account lifecycle. Reviewing the data we hold about you does not require a formal legal request — you can start by opening the account settings section while signed in, where your registered details, contact preferences and session history are displayed. If something looks wrong, the correction path is the same: update the fields shown or raise it through support if the field is not editable yourself. For questions about how a specific data point is used — or to ask that a particular record be removed where that is permitted under applicable rules — our support contact route handles those requests. Note that requests affecting your transaction history may be limited by retention requirements that apply regardless of your preference. Availability of any specific right depends on your local law and eligible region.
Open your signed-in account settings to see the personal details, contact information and session records we hold. The fields shown there reflect what is currently stored against your account.
If a registered detail is wrong — name spelling, contact number, preferred payment method — update it directly in account settings or contact support for fields that require verification before changes are applied.
Send your question through the published support route listed on this page. Describe the specific data point you are asking about so we can give you a direct answer rather than a general response.
Where removal is permitted under applicable rules, raise it through support. We will confirm what can be actioned and what must be retained under our operational requirements. Eligibility depends on local law and your account status.
If you have a question about how your data is handled, or if you want to take any of the actions described above, use the contact routes published on this site. We respond through the channels listed — do not use a channel we have not confirmed, as it may not reach the right team.
Open the chat widget from any page while signed in. Describe your data question clearly and include your account reference so the team can pull the relevant records without delay.
Send your privacy or data request to the support email address shown in your account area. Include your registered contact detail and the specific record or question you are raising.
The account help section covers common data and policy questions with step-by-step paths. Check there first — many correction and review actions can be completed without opening a support ticket.
We keep your account and data handling practices consistent across every session, whether you are on a mobile browser or a desktop connection. Here is what that looks like in practice.
We use session cookies to keep you signed in and analytics cookies to understand how pages are used. You can manage cookie categories in your browser settings. We do not use advertising cookies to track you across other sites.
Your login credentials are stored using standard encryption. If you notice unusual activity on your account — an unrecognised login or an unexpected change to your registered contact — raise it immediately through live chat or the support email shown in your account area.
We keep account and transaction records for the period required under applicable operational rules. After that period, records are deleted or anonymised. Nagad and Bank Transfer transaction logs follow the retention period tied to payment processing requirements.
When this policy changes in a material way, we will update the version date shown at the top of the page and, where the change affects your account directly, notify you through your registered contact method before the change takes effect.
These are the questions we see most often from people reviewing their account data rights or trying to understand how this policy applies to their situation.
We collect the details you enter at registration — name, contact information and payment method preference — along with login records and device identifiers generated during your sessions. We collect only what is needed to operate and secure your account. Nothing beyond that is gathered without a specific operational reason.
Your payment instructions are processed through infrastructure that handles Nagad and Bank Transfer separately from our main platform data. We share the minimum data needed to complete each transaction. Full payment credentials are not stored on dk 33 servers, and the payment processor operates under its own data terms.
Yes. Open your account settings while signed in to view your registered details and session history. For records not visible in settings — such as specific transaction logs — contact us through live chat or the support email shown in your account area and we will confirm what is available to share.
Most fields — contact number, email address, preferred payment method — can be updated directly in account settings. For fields locked behind verification, contact support through the published route and the team will walk you through the correction steps shown in your account.
When you load a game, your device connects to the studio's environment to run it. We do not pass your personal account data to studios. The data handled inside a game frame — session state, wager records — is governed by the studio's own terms, not by this policy.
This policy sets out dk 33's practices as we operate them. Your ability to access the platform and the specific rights available to you depend on your local law and eligible region. If you have a question about how a rule applies in your situation, contact us through the support routes on this page.