Skip to content
dgb22 Slots / Live
YOUR DATA MATTERS

dgb22 Privacy Policy: What We Collect and Why

dgb22 handles your information, payment activity and device data with a clear purpose — to run your account, process transactions through Rocket, Upay or Bank Transfer, and keep your session secure. This policy sets out exactly what we collect, how we use it, and what choices you have. Access and eligibility depend on your local law and eligible regions.

  • Account data kept private
  • Rocket, Upay, Bank Transfer context
  • Your rights, clearly stated
  • Contact route published
POLICY DETAILS

How dgb22 Handles Your Information

When you create an account on dgb22, we collect the information you enter directly: your name, contact details, login credentials and any payment identifiers tied to Rocket, Upay or Bank Transfer transactions. We also collect device-level data — your browser type, operating system, session timestamps and IP address — so we can maintain continuity between your mobile and desktop sessions. This data is used to operate your account, process your deposits and withdrawals, respond to your support requests and monitor for unusual activity on your wallet. We do not sell your personal information to third parties. Data shared with payment processors — such as when you initiate a Rocket transfer or a Bank Transfer request — is limited to what those processors require to complete the transaction. We retain your account records for as long as your account is active and for a reasonable period afterward as required by our internal policies. You may request a summary of the data we hold at any time through our published support route. Availability of all services on dgb22 depends on local law and the eligible regions where we operate.

  • Rocket payment data

  • Upay transaction context

  • Bank Transfer records

  • Account session history

  • Device and browser logs

POLICY SCOPE

What This Policy Covers and What It Does Not

This policy applies to everything that happens inside your dgb22 account — from the moment you log in on your phone to the point where a Rocket or Bank Transfer transaction is confirmed. It covers account access, session data, payment records and the communications we send you. It does not extend to third-party sites linked from our pages, external payment processor privacy practices or any service operating outside the dgb22 domain. Understanding the boundary helps you know where to direct a data question.

  • Account Access

    Covers login activity, session tokens, device recognition and the data you submit when creating or updating your dgb22 account. Applies each time you authenticate on mobile or browser.

  • Transactions

    Covers payment identifiers and amounts linked to Rocket, Upay and Bank Transfer operations on your account wallet. We record what is needed to process and reconcile your requests.

  • Site Content and Behaviour

    Covers page visits, navigation clicks and session duration on dgb22. This data helps us understand how you move through the lobby and improves the experience for returning sessions.

  • Third-Party Services

    External processors, linked pages and any service outside dgb22 operate under their own policies. We are not responsible for how those parties handle data once a transaction or link leaves our domain.

YOUR ACCOUNT RIGHTS

Actions You Can Take Under This Policy

Your account data belongs to you, and this policy gives you several practical ways to manage it. You can request a copy of the personal information we hold on your account — this includes your registration details, login history and any payment identifiers associated with Rocket, Upay or Bank Transfer activity. If any detail is incorrect — a name, a contact address, a linked payment method — you can request a correction through the account settings page or directly via our support channel. You can also ask us to explain why we hold specific data, how long we keep it, and whether any of it has been shared with a third party. If you want to close your account and ask us to remove your data, you can submit that request in writing through our published support route; we will confirm receipt and tell you the steps that follow. All these rights are available subject to local law and the eligible regions where dgb22 operates.

  • Review Your Records

    Submit a data access request through our support channel. We will provide a summary of the personal information tied to your account, including login history and payment identifiers.

  • Correct Account Details

    Update your name, contact information or linked payment method in account settings, or ask our support team to make the correction if the field is not editable from your side.

  • Raise a Data Question

    If you are unsure why a particular piece of data is held or how it is used, send your question to our published support route and we will give you a clear, specific answer.

  • Request Account Removal

    Write to us through the published contact route to request account closure and data removal. We will confirm the steps, timeline and any obligations that apply before completing the request.

REACH OUR TEAM

How to Contact Us About This Policy

If you have a question about how we use your data, want to exercise a right described in this policy, or need to flag a concern about your account, use the contact routes published on dgb22. We respond through the channels listed below. Do not share your full payment credentials — Rocket PIN, Upay account number or Bank Transfer details — in any support message; describe the transaction type and we will verify the rest. Availability of support depends on the eligible regions where dgb22 operates.

  • Live Chat

    Open the chat window on dgb22 while logged in to your account. Describe your data or privacy question and our team will respond through the same session.

  • Email Support

    Send your privacy request or data correction question to the support address published on the contact page of dgb22. Include your registered account details so we can locate your record.

  • Account Help Centre

    The Help Centre on dgb22 lists published answers to common account and data questions. Check there first; if your question is not covered, use live chat or email to escalate.

DATA HANDLING APPROACH

How We Protect and Manage Your Data

Our approach to data handling on dgb22 is built around keeping your information accurate, accessible only to you and retained only as long as needed. Cookies on our site are used for session continuity — so your login state persists when you switch between mobile and desktop — and for basic analytics that help us understand navigation patterns. We do not use cookies to build advertising profiles or share browsing data with ad networks. Account security relies on the credentials you set at registration; we recommend keeping your login details separate from your Rocket, Upay or Bank Transfer account passwords. If we update this policy, we will post the revised version on dgb22 with the date of change noted. You can request a copy of the current policy or ask for an explanation of any clause through our published support route at any time.

  • Cookie Use

    Cookies on dgb22 maintain your session state and support basic navigation analytics. We do not use cookies to build advertising profiles or share your browsing data with external ad networks.

  • Account Security

    Your account is protected by the credentials you set. Keep your dgb22 login separate from your Rocket, Upay or Bank Transfer passwords. Report any unexpected login activity through the published support route immediately.

  • Data Retention

    We keep your account records while your account is active and for a reasonable period after closure as required by our internal policy. You can ask how long specific data is held at any time.

  • Policy Updates

    When this policy changes, we post the updated version on dgb22 with the revision date clearly shown. Continued use of your account after a change means you have reviewed the updated terms.

COMMON POLICY QUESTIONS

Privacy Policy Questions Answered

Below are the questions we hear most often about data, account privacy and your rights on dgb22. If your question is not here, use the live chat or email route on dgb22 to get a specific answer. Remember that access and all related rights depend on your local law and the eligible regions where we operate.

What personal data does dgb22 collect when I open an account?

We collect the details you enter at registration — name, contact information and login credentials — plus device and session data generated when you use dgb22. Payment identifiers linked to Rocket, Upay or Bank Transfer activity are also recorded as part of your account transaction history.

Does dgb22 share my data with third parties?

We do not sell your data. Information is shared only with payment processors — such as when you initiate a Rocket or Bank Transfer request — and only to the extent those processors need it to complete your transaction. We do not share browsing data with ad networks.

How do I get a copy of the data dgb22 holds on me?

Send a data access request through our published support route — live chat or the email address on the dgb22 contact page. Include your registered account details. We will provide a summary of the personal information tied to your account.

Can I correct incorrect information in my account?

Yes. Update editable fields directly in account settings. For fields that are locked after registration — such as your registered name — submit a correction request through live chat or email support, and our team will verify and update the record.

How are cookies used on dgb22?

Cookies keep your session active when you move between mobile and desktop, and support basic analytics that help us understand navigation patterns. We do not use cookies to build ad profiles. You can manage cookie preferences in your browser settings, though some session features may be affected.

What happens to my data if I close my dgb22 account?

We retain your records for a reasonable period after closure as required by our internal policy. You can request removal of specific data by writing to our published support route. We will confirm receipt, explain what can be removed and outline the steps involved. Eligibility depends on local law.