igambel Privacy Policy: How We Handle Your Account Data
This policy explains exactly what data igambel collects when you access your account, make a transaction through DANA, LinkAja, or Bank Transfer, or reach our support team — and how we keep that data protected. Availability of our services depends on local law and is offered only where permitted in eligible regions.
Account data protection
DANA, LinkAja, Bank Transfer context
Your rights, clearly stated
Support contact paths included
POLICY POSTURE EXPLAINED
What This Privacy Policy Covers and Why It Matters
When you open an account or log back into the lobby, we collect the information needed to operate your session — your registered contact details, device type, session activity, and any transaction context tied to your chosen payment method such as DANA, LinkAja, or Bank Transfer. We do not collect payment credentials directly; those are handled by the respective payment service under their own terms. We retain account data for as long as your account remains active and for a period thereafter as required by applicable obligations in eligible regions. Data used for fraud prevention and account security may be held separately and for longer periods where local law requires it. We do not sell your personal data to third parties. We may share limited data with service partners who process transactions or provide platform infrastructure, and only to the extent needed for those services to function. Any such sharing is governed by contractual obligations that require those partners to protect your data in line with this policy. Your continued use of the platform constitutes acknowledgement of this policy. If you have questions about how a specific data type is handled — including records tied to your DANA or Bank Transfer transactions — the support routes in this document are the right place to start.
DANA
Transaction context from DANA payments is processed by the DANA service; we receive only the confirmation signal and the amount relevant to your account wallet.
LinkAja
LinkAja transaction records are treated identically — we store the outcome, not the credential, and that record is visible in your account transaction history after login.
Bank Transfer
Bank Transfer references linked to your account are stored in your transaction log and are accessible from your account dashboard at any time you are logged in.
SCOPE AND BOUNDARIES
Where This Policy Applies and What It Does Not Cover
This policy applies to data we process directly within the igambel platform — your account, your session, and the transaction records we hold. It does not extend to third-party services you reach through links on our pages. Understanding the boundaries helps you know whose policy applies at each step of your activity.
Account access and login data
Covered fully. Login activity, device type, and session records tied to your igambel account are governed entirely by this policy.
Transaction records (DANA, LinkAja, Bank Transfer)
Partially covered. We hold the transaction outcome in your account log; the payment processor holds credential and processing data under their own separate policy.
Site content and lobby activity
Covered. Game session data, lobby navigation, and feature interactions within the platform are recorded and handled under this policy.
Third-party links and external services
Not covered. Once you leave our platform via an external link, the data practices of that destination are governed by their own policy, not ours.
YOUR PRACTICAL RIGHTS
Actions You Can Take Regarding Your Data
You have practical options when it comes to the data we hold on your account. Reviewing your records is straightforward: log in, open the account dashboard, and your transaction history — including entries tied to DANA, LinkAja, and Bank Transfer — is displayed there without needing to contact support. If you notice a detail that looks incorrect, such as a registered contact entry or a name field, you can submit a correction request through the support channel. We review these requests and update records where the correction is substantiated. Requesting a summary of the data we hold on your account is also available — use the email contact path listed in the support section of this policy and include your registered account identifier. For requests to close your account or ask about data retention periods that apply after closure, the same email path applies. We aim to respond to data-related requests within the timeframe required by applicable obligations in regions where the service is available.
Review your records
Log in and open the account dashboard. Transaction history, session records, and registered details are all visible there without requiring a support request.
Correct account details
Submit a correction request via the support contact listed below. Include the specific field and the correct value; we review and update where the change is substantiated.
Request a data summary
Email us with your registered account identifier to request a summary of what we hold. We respond in line with applicable timeframes for eligible regions.
Ask about account closure and retention
Use the same email contact to ask about what happens to your data after account closure. We will explain the retention period that applies to your account.
CONTACT PATHS FOR PRIVACY
How to Reach Us About This Policy
Privacy questions deserve a direct path. If you have a question about how your data is held, want to raise a concern about a specific transaction record, or need to request a correction, use one of the contact routes below. Responses are handled by the same team that manages account support — there is no separate privacy desk to navigate.
Email support
Send your data-related question or correction request to our support email. Include your registered account identifier so we can locate your records quickly.
Live chat
The live chat option in your account dashboard connects you directly with the support team. Use it for straightforward clarifications about what data we hold or how a transaction record appears.
Account dashboard request
For record reviews and transaction history queries, your account dashboard is the first place to check — most answers are visible there after login without needing to contact us at all.
HOW WE PROTECT YOUR DATA
Data Handling, Cookies, Security and Retention at igambel
We apply account-level security measures to protect stored data from unauthorised access. Session cookies are used to maintain your logged-in state and to keep your lobby position between pages — you can manage cookie preferences through your browser settings, though disabling functional cookies may affect how the account session behaves. Data retention follows the applicable obligations for regions where our service is available; we do not hold data longer than necessary for the purpose it was collected. If you want to know the specific retention period for a data type on your account, the email contact route in this policy is the right path.
Cookies and session data
We use functional cookies to keep your account session active across pages. Preference and analytics cookies can be adjusted in your browser settings. Disabling functional cookies may interrupt your logged-in session.
Account security practices
Account data is stored with access controls that limit who can read or modify your records. We do not expose your full payment details internally; only transaction outcome data is accessible to account operations.
Data retention periods
We keep account data while your account is active and for a period after closure as required by applicable rules in eligible regions. Transaction records tied to DANA, LinkAja, or Bank Transfer follow the same schedule.
Requesting changes to held data
To request a correction, deletion, or summary of your data, use the email support path listed in this policy. Include your registered account identifier and the specific request so we can handle it accurately.
PRIVACY QUESTIONS ANSWERED
Frequently Asked Questions About This Privacy Policy
The questions below cover what we hear most often about how igambel handles account data, transaction records, and user rights under this policy. If your question is not listed here, the support contact paths in this document are the right place to ask.
What personal data does igambel collect when I open an account?
We collect the contact details you enter at registration, your device type, session activity, and transaction outcome records linked to your chosen payment method — DANA, LinkAja, or Bank Transfer. We do not collect payment credentials directly; those stay with the respective payment service.
Can I see all the data igambel holds on my account?
Yes. Log in and open your account dashboard — your transaction history and registered details are displayed there. For a full data summary beyond what the dashboard shows, email our support team with your registered account identifier and we will provide the details.
How do I correct an error in my registered account details?
Submit a correction request through live chat or email support. Include the field that needs changing and the correct value. We review each request and update the record where the correction is substantiated, then confirm the change to your registered contact.
Does igambel share my data with third parties?
Only to the limited extent needed for services to function — for example, transaction processing partners. We do not sell your data. Any partner we share data with is bound by contractual obligations to protect it in line with this policy's requirements.
What happens to my data if I close my account?
We retain account data for a period after closure as required by obligations applicable to eligible regions. Transaction records tied to DANA, LinkAja, or Bank Transfer follow the same schedule. Email support with your account identifier to ask about the specific retention period that applies to you.
How are cookies used on the igambel platform?
Functional cookies keep your account session active and maintain your position in the lobby between pages. You can manage other cookie types in your browser settings. Turning off functional cookies may interrupt your logged-in session, so we recommend reviewing the settings before making changes.