Privacy First For Your Account
3d hoki keeps privacy controls close to your account flow: the policy explains what account data we collect, why we use it, and how you can reach us...
Our Indonesia Privacy Position
This Privacy Policy explains how we handle data connected to your 3d hoki account, device, session, cookie choices, and support contact. Where local law permits, we may process details needed to operate your account, protect access, confirm your requests, prevent misuse, and respond to privacy questions. In supported regions, transaction references linked to DANA, OVO, GoPay, or QRIS may appear in our
records only as needed for account administration, risk checks, and support follow-up. We do not write this policy as a one-time legal block. We keep it aligned with our account flow, privacy request paths, and the way you see notices on screen.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Contact Us About Privacy
If you need to ask about this Privacy Policy, start with the contact path that matches your request. We may ask you to confirm account ownership before we discuss data tied to your profile, device, wallet reference, or support history.
Account email
Send us a privacy request from your account email, and we will match it to your profile before discussing account data, device records, or consent choices with you.
Live help desk
Use the help desk when you are signed in and want a faster privacy check tied to your session, cookie setting, or current account access status.
Policy escalation
Ask for escalation if your privacy request needs a deeper look, such as correction, access, deletion, or a written response about how your data is handled.
How We Keep Policy Current
We keep this Privacy Policy practical, readable, and tied to what you see inside your account. Each update is checked against our support flow, account screens, cookie banners...
Plain wording
We avoid legal clutter where possible, so you can understand what data we collect, how we use it, and when...
Account flow match
We compare policy wording with the actual account journey, so privacy promises match the screens where you join, sign in...
Local wording
We use Indonesia-facing terms carefully, including supported regions and where local law permits, so the policy does not overstate access...
Cookie clarity
We explain cookie use in relation to sessions, device recognition, preferences, fraud control, and service stability, rather than hiding it...
Request handling
We keep internal steps for privacy requests, including identity checks, reply timing, correction paths, deletion review, and records needed to...
Change tracking
When this policy changes, we aim to make the update visible on the page, with wording that helps you see...
Consistent Policy Across Our Pages
Your privacy terms should not change from one legal page to another. We align this Privacy Policy with our terms, cookie wording, security notices, and contact pages so...
| Terms alignment | Our account terms and this Privacy Policy use matching language for identity checks, access control, support requests, and records kept for account administration or security checks. |
|---|---|
| Cookie alignment | Cookie wording matches our privacy section, so session tools, preference storage, device signals, and consent choices are described in the same way across pages. |
| Support alignment | Support pages reflect the same privacy contact paths shown here, including how we verify you before discussing account records, wallet references, or device details. |
| Security alignment | Security wording supports this policy by explaining why we may process device signals, login patterns, fraud flags, and access records to protect your account. |
| Wallet reference alignment | Where DANA, OVO, GoPay, or QRIS references appear, our privacy wording stays consistent: they are account records, not public data or marketing labels. |
| Retention alignment | Retention language stays consistent across legal pages, covering why some records are kept for support, audit, dispute handling, or account protection after a request. |
| Rights alignment | Your privacy request rights are described with the same limits and verification steps across pages, so correction, access, deletion, and objection paths stay clear. |
Policy Page Layout Highlights
This page is built so privacy details are easy to scan before you open or continue using your account. The layout separates policy posture, contact routes, consistency checks...