Reference

Privacy Policy for Your jackpotmaster Account

Our Privacy Policy explains how jackpotmaster handles your account data when you open the lobby, use DANA or QRIS, and contact support.

Clear data purposesWallet status contextAccount access choicesCookie controls
jackpotmaster Privacy Policy for Your jackpotmaster Account
PRIVACY CONTACT

Where To Ask About Your Account Data

A direct contact route helps when you need a copy, correction or explanation of data connected with your account. We keep privacy questions separate from ordinary lobby requests so the request can be matched to the right account record. Include the phone number linked to your account, the relevant date and the subject of your request, but do not send a password or wallet PIN. You can reach us through the support chat and the contact route shown near the account or cashier area.

Team online

Support chat

Use the support chat for a privacy question about sign-in records, cookie choices or a phone verification step. We may ask for account identifiers so we can locate the correct record, but we will not ask you to disclose your password, wallet PIN or one-time access code.

Account contact route

The contact path beside your account area is suited to requests for data access, correction or removal. Tell us which record concerns you, such as a DANA receipt reference or device sign-in, and we will assess the request under the rules that apply to your location.

Payment status help

When a privacy question involves QRIS, OVO or GoPay status, include the payment reference and approximate time rather than sending a full wallet screenshot. This lets us check the relevant record while limiting extra personal details in the support conversation.

DATA PRACTICES

What We Do With Policy-Related Data

We handle account data according to a practical access flow: your phone details support verification, device signals help identify unusual entry, and payment references help match a status request without exposing your…

Account records

We use your phone number and account identifiers to create access, send account-related messages and connect a privacy request to the correct record. Before changing or releasing account data, we may ask you to complete the same phone verification step used for account entry.

Device signals

Your browser and device can provide signals such as session details, operating system type and security events. We use these signals to detect unusual access and protect your account; they are not treated as a request to read unrelated files, photos or contacts on your device.

Cookies

Cookies and similar browser storage can keep a session active, remember selected settings and help us understand whether a page opened correctly. You can manage optional storage through your browser controls, although removing essential storage may require you to sign in again.

Payment references

A DANA, QRIS, OVO, GoPay, bank transfer or virtual account reference may be retained to match a payment status with the right account. We do not need your wallet PIN for that check, and support should never receive a one-time code from you.

Retention choices

We retain personal data only for the period connected with account operation, security checks, dispute handling or a legal requirement. When a record no longer serves one of those purposes, we work to delete it or separate it from direct account identifiers.

Your requests

You can ask us to access, correct or remove eligible personal data, or ask why a record is used. Send the request through support chat or the account contact path, identify the account phone number, and state the change you want us to assess.

Privacy Policy Answers for jackpotmaster

These Privacy Policy answers address the questions we expect when you are deciding whether to open an account or update your account details. They explain what we collect, how wallet references and device data are handled, and which route to use for a request. If your circumstances involve a different jurisdiction, access depends on local law and the applicable rules may affect the response.

It covers data handled through account access, mobile browser sessions, payment status screens, cookies and support conversations. That can include your phone number, account identifiers, device signals and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Yes, you can send an access request through support chat or the account contact route. State the phone number linked to your account and the records you want identified, such as sign-in activity or a QRIS status reference. We may verify your identity before responding.

Contact us through the account contact route with the detail that needs changing and the reason for the correction. For a phone number or identity-linked account field, we may require the normal phone verification step before we change the record or confirm the result.

You should never send a DANA or GoPay PIN to us, and our support route does not need it to check a payment reference. We may retain a transaction identifier, selected rail and status result so a wallet-related request can be matched to your account.

Device and browser signals help us identify unusual account entry, maintain a secure session and investigate a sign-in question. They can include session details, operating system type and security events. They do not give us permission to read unrelated files, photos or contacts.

Use your browser settings to remove or restrict optional cookies and similar storage. Essential session storage may still be needed for account access, so clearing it can sign you out or reset a preference. A support message can clarify which page setting concerns your request.

You can ask us to delete eligible personal data through support chat or the account contact route. We assess the request against account security, dispute handling and legal retention needs. Where local law permits, records no longer needed for those purposes are removed or separated from direct identifiers.