App / Mobile
dkk666 collects only the account and transaction data needed to run your wallet, process Rocket, Upay and Bank Transfer records, and keep your session secure. This policy tells you exactly what we hold, why we hold it, and what you can do about it — with access and eligibility subject to your local law and the eligible regions we serve.
When you open an account, we collect the details you enter during registration — name, contact address and the payment identifiers tied to your chosen method, whether that is Rocket, Upay or Bank Transfer. We also log session activity: the pages you open, the games you launch and the device type your browser reports. This operational data helps us keep your account working correctly and lets us trace any transaction question you raise with our support team. We do not sell your personal data to third parties. Data shared with payment processors — such as the Rocket or Upay rails that handle your wallet movements — is limited strictly to what those processors need to complete or verify a transaction. Bank Transfer confirmations that appear on your Bangladesh bank statement are generated by your bank, not by us; we hold only the reference number on our side. Retention periods follow our internal schedule and any applicable requirements for the regions we serve. If you close your account, we retain only the minimum records required by those obligations, then delete the rest. All of this is subject to local law and the eligible regions where dkk666 operates.
Transaction identifiers for Rocket wallet movements are shared only with the Rocket payment processor to complete or verify your deposit or withdrawal request.
Upay payment data follows the same limited-disclosure rule — only the reference details needed to match your Upay transaction are passed to the processor.
For Bank Transfer, we hold the reference number on our side. The confirmation on your Bangladesh bank statement is your bank's record, not ours.
Our privacy policy covers the dkk666 platform directly — your account, the games lobby, wallet actions and the data our systems process. It does not extend to third-party services you reach through our pages, including external payment processors or studio software running inside game windows. Understanding the boundary helps you know which entity to contact when a question arises outside our direct scope.
Every login, session token and account-settings change falls inside this policy. We log these events to protect your account and to answer any access dispute you raise with support.
Rocket, Upay and Bank Transfer actions initiated from your wallet page are covered. The moment funds enter the processor's network, that processor's own policy applies alongside ours.
Game lobby pages, promotional notices and published terms pages are part of the dkk666 platform and sit inside this policy's scope for analytics and session data.
Game software from studios available in the lobby, and external payment network infrastructure, operate under their own data terms. This policy does not override or extend to those services.
You have several concrete options available through your account and through our support route. Start by signing into your account and opening the account-settings page — that is where your profile details, linked payment methods and communication preferences are shown. If something looks wrong, you can edit it directly from that screen. For transaction records tied to Rocket, Upay or Bank Transfer, the history tab in your wallet section shows the reference entries we hold. Anything you cannot update yourself — such as a data query that goes beyond a standard profile edit — can be directed to our support team using the published contact route. We aim to respond to data-related questions through the same channel, following the process described in the support section below. Account closure requests are also handled through support. When you close an account, we process the deletion of non-essential data as set out in the retention terms above, and we confirm completion through the same contact channel.
Open the account-settings and wallet-history pages after signing in. Transaction references for Rocket, Upay and Bank Transfer are listed there for you to check.
Edit your profile information directly from the account-settings screen. If a field is locked and needs changing, contact support with the detail you want corrected.
Use the published support contact route for any question about what data we hold, how it is used, or how long we keep it. Include your account reference so we can locate the right record.
Submit a closure request through support. We will process deletion of non-essential data and confirm completion via the same channel once the retention obligations are met.
If you have a question specifically about how your data is handled — or you want to make a request described in the rights section above — use the contact routes published on the dkk666 site. We do not invent channel names or response windows here; use only the routes you can see on the published support page. Each route carries the same reference: include your account ID and describe the data matter clearly so the right team can handle it.
Open the live-chat widget from any page while signed in. Describe your data question and include your account reference. The agent will route it to the correct team.
Send your query to the support email address published on the contact page. Include your account ID, the nature of the data request and which payment method — Rocket, Upay or Bank Transfer — is involved if relevant.
The help section inside your signed-in account lists current contact options and explains how to submit a formal data request. Check that page first for the most current route.
We approach data handling as an operational responsibility, not a formality. Session cookies keep your account authenticated while you browse the lobby and your wallet stays linked to the correct payment method — Rocket, Upay or Bank Transfer. You can manage cookie preferences through your browser settings; blocking functional cookies may affect how your signed-in session behaves. For account security, access to your data inside our systems is restricted to staff with a direct operational need. We do not store full payment credentials on our servers; only the transaction reference identifiers required to match your wallet records are retained. Retention schedules are reviewed internally and aligned with the requirements of the regions we serve. If those requirements change, we update this policy and note the revision date at the top of the page.
We use session and functional cookies to keep your account signed in and your wallet method remembered. Manage preferences in your browser; restricting cookies may affect account page behaviour.
Inside our systems, your account data is accessible only to staff with a clear operational reason. We do not share or sell data outside the limited payment-processor disclosure described in this policy.
We hold account and transaction data for as long as needed to meet our obligations for the eligible regions we serve, then delete non-essential records. Closure requests are processed through the published support route.
When this policy changes, we update the revision date at the top of the page. Continued use of the account after a revision means you have had the opportunity to review the updated terms.
These are the questions about data handling and account privacy that come up most often. If your question is not here, use the published support contact route and include your account reference.
We collect the registration details you enter — name and contact information — along with the payment identifiers for Rocket, Upay or Bank Transfer that you add to your wallet. Session and device data is also logged to keep your account secure and functional.
We share only the minimum identifiers needed to process a transaction with the relevant payment processor — Rocket, Upay or Bank Transfer. We do not sell your personal data. Game studio software in the lobby runs under its own data terms, which are separate from ours.
Sign in and open the wallet-history tab. Rocket, Upay and Bank Transfer reference entries are listed there. If a record looks incorrect, contact support with your account reference and the transaction detail in question.
Yes. Submit a closure or deletion request through the published support route. We process deletion of non-essential data once our retention obligations for the eligible regions we serve are satisfied, then confirm completion through the same contact channel.
Session cookies keep your account authenticated as you move between the lobby, wallet and account-settings pages. You can manage or restrict cookies in your browser settings, but blocking functional cookies may affect how your signed-in session behaves on the site.
Use the support contact routes published on the dkk666 site — live chat or the support email address shown on the contact page. Include your account ID and describe the data matter clearly so it reaches the correct team without delay.