Reference

39judi Privacy Policy Explained Clearly

39judi Privacy Policy explains how we collect, use, store and protect the details connected with your account, device and wallet activity.

Account dataWallet recordsCookie choicesPhone verification
Browse Our Lobby Read FAQ
39judi 39judi Privacy Policy Explained Clearly
CONTACT OPTIONS

Privacy Questions Reach Our Support Team

A clear contact route matters when you want to ask about your Privacy Policy rights or the data linked to an account.

Account contact Use the support contact shown in your account area for a Privacy Policy question. We first match your request to the account identifier and phone verification status, then explain which data can be viewed, corrected or restricted.
Wallet records For a DANA, OVO, GoPay or QRIS reference, send the transaction date, amount and visible reference only. We can check the record without asking you to share a wallet PIN, bank password or complete card details.
Request follow-up If your request needs additional checking, we keep the conversation in the same support thread and state what is still needed. A phone confirmation or account sign-in may be required before personal data is disclosed.
DATA PRACTICES

Six Practical Privacy Commitments

Privacy works best when each data use has a visible purpose, so we connect account records to the action that created them.

Collection purpose

We collect the account name, contact details and phone verification result needed to create and protect your account. Transaction references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account are used to reconcile the related wallet event.

Cookie controls

Cookies and similar device storage can keep a session active, remember a selected setting and help us detect suspicious sign-in patterns. You can manage browser cookie controls, although blocking required cookies may interrupt login or policy-page access.

Account security

We use sign-in records, phone verification and device signals to help protect your account. Never send us a password or wallet PIN. If an unfamiliar device appears, contact support from the account route and describe the sign-in event.

Retention approach

We keep personal and transaction records for as long as needed for the stated account purpose, security checks, dispute handling and applicable legal duties. When a record is no longer required, our handling follows the deletion or anonymisation process available to us.

Correction requests

You can ask us to correct inaccurate contact or account details through support. We may ask you to complete sign-in or phone verification before changing information, so another person cannot alter the record attached to your account.

Access decisions

Account and service eligibility depends on local law. If a request concerns data held by a payment provider or another service, we explain the relevant boundary and direct you to that provider when its own Privacy Policy controls the record.

Privacy Policy Questions About Your Account

These answers focus on the questions you may have before opening an account or when checking an existing data record. We keep the wording tied to real account actions: phone confirmation, device sessions, wallet references and support requests. If your situation is not covered, contact us through the support path shown on the site and avoid sending passwords, wallet PINs or complete banking credentials.

It explains that we use details such as your contact information, phone verification result, sign-in records and transaction references to provide account access, protect the account and resolve support requests. We use each record for a stated operational purpose and handle eligibility where local law permits.

You can contact support to ask which personal data is connected with your account and whether a copy can be provided. We may require sign-in or phone verification first. The response can exclude material that would expose another person, security controls or a legal restriction.

We may retain the reference, amount, date and status needed to match a DANA or QRIS transaction with your account. We do not need your wallet PIN. If the record is held by the payment provider, that provider's own policy also applies to its handling.

Cookies or similar storage may keep your session active, remember a setting and help identify unusual sign-in behaviour. Your browser controls can block or remove them, but required cookies may be necessary for login, phone verification and secure movement between account pages.

We retain records for the time needed to operate the account, investigate disputes, protect against misuse and meet applicable legal duties. The period can differ by record type. When continued retention is not needed, we follow the deletion or anonymisation process available to us.

Send a correction request through the support contact shown on the site and identify the account detail that needs changing. We may ask for a phone confirmation or account sign-in before making the update. Do not include your password, wallet PIN or banking password.

You can ask support whether a record can be removed, restricted or anonymised. We assess the request against account security, unresolved transaction questions and applicable legal duties. Account access depends on local law, and some records may need to remain for a defined purpose.

Related Pages

39judi Indonesia Access guide Football Handicap Guide Account information About Us