How 39judi Handles Your Account Data
This privacy policy explains what we collect when you open a 39judi account, why we hold it, and how long it stays on our systems. We wrote it...
Our Privacy Posture and Scope
We collect only what your account needs to function in supported regions. That covers your sign-up details, device fingerprints from each session, transaction references tied to DANA, OVO, GoPay or QRIS, and verification documents where local law permits. We store this data on access-controlled servers and share it only with payment partners, identity-check vendors and regulators that ask under legal process. You
can request a copy, ask us to correct an entry, or close the account and have residual records purged after the retention window expires. Marketing consent is separate from account consent — toggling one will not break the other, and you can withdraw either through your dashboard at any point.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Privacy Contact Paths
Reach our privacy desk directly through any of the channels below. We answer data requests within the window your jurisdiction sets.
Editorial Trust Signals for This Policy
Versioned Document
Every change to this privacy policy ships with a date stamp and a short note describing what moved. Older versions stay archived so you can compare wording from the day you opened your account.
Legal Review
Our in-house counsel reviews this text against Indonesian data rules and our payment partner contracts before publication. Nothing here is auto-generated marketing copy dressed up as a legal clause.
Named Owner
A single privacy lead signs off each revision. That person is reachable through the contact channels above and is accountable for how we respond to your data subject requests.
Minimal Collection
We only ask for fields the lobby genuinely needs — sign-up identity, payment routing for DANA, OVO, GoPay or QRIS, and session security signals. Optional fields stay optional and are clearly marked.
Third-Party List
Our processor register names every vendor that touches your data, from KYC checkers to email senders. You can request the current list at any time and we update it when partners change.
Audit Trail
Internal access to account records is logged per query. If a staff member opens your file, the system records who, when and why, and that log is retained for compliance review.
Consistency Across Our Policy Pages
| Privacy vs Terms | This privacy policy covers data handling only. Account conduct, wagering rules and dispute steps live in our Terms document and use the same definitions so nothing contradicts between the two pages. |
|---|---|
| Privacy vs Cookies | Cookie behaviour gets its own page with category toggles. This policy references it but does not repeat the table, keeping each document focused on a single reader question. |
| Privacy vs KYC | Identity verification mechanics sit in our KYC notice. Here we cover what happens to the documents afterwards — retention period, access controls and deletion triggers when your account closes. |
| Privacy vs AML | Anti-money-laundering checks may extend retention beyond the standard window. We flag that exception here and link to the AML notice rather than duplicating the legal grounds twice. |
| Privacy vs Marketing | Promotional consent is documented separately. Withdrawing marketing permission does not affect the lawful basis for processing your core account data, and both pages state this in matching language. |
| Privacy vs Payments | Payment references for DANA, OVO, GoPay and QRIS are processed under this policy; the Payments page handles operational detail like timing. Data scope wording is identical across both. |
| Privacy vs Complaints | If a privacy issue becomes a formal complaint, our Complaints page takes over the workflow. The escalation path is named here so you are never bounced between documents. |
What You Will See On This Policy
Plain-Language Sections
Each clause carries a short heading so you can jump to the part you need — collection, sharing, retention, your rights — without scrolling the full document on a phone screen.
Date-Stamped Updates
The header shows when the policy last changed. A change log at the bottom lists every revision in order so you can confirm what was different the day you signed up.
Rights Checklist
A boxed checklist summarises your access, correction, erasure, portability and objection rights. Each row links to the exact form or contact path you need to exercise it.
Retention Table
A compact table maps each data category to its retention window, from session logs measured in days to KYC files held for the period local law requires after closure.
Processor Reference
An anchor link opens our current list of named processors, with the role each one plays. The list refreshes whenever a partner is added, removed or replaced.
Contact Footer
Every page footer repeats the privacy inbox and postal address. You never have to hunt for the contact route, and the same details appear on the Terms and Cookies pages.