Reference

Privacy Policy For Your jogjatoto Account

jogjatoto Privacy Policy explains how we collect, use and protect the details connected with your account, device and wallet status.

Clear data purposesWallet status checksMobile privacy controlsAccount contact path
jogjatoto Privacy Policy For Your jogjatoto Account
CONTACT YOUR WAY

Where To Ask About Privacy Policy

Questions about our Privacy Policy should reach us through the account support path so we can connect your request with the correct record.

Account privacy request Use the support contact linked from your jogjatoto account when you want to ask what personal details we hold, why they are used or whether a correction is possible. Include the account contact details you can verify so we can route the request safely.
Wallet record question For DANA, OVO, GoPay or QRIS questions, share the relevant transaction reference without sending your wallet password or private security code. We use the reference to locate status information, then reply through the account support path rather than exposing payment details publicly.
Device and login help If a mobile browser or desktop session shows unfamiliar activity, contact support and state the device type, approximate time and account contact. We can review the session context, help secure the account and explain which Privacy Policy process applies to the request.
DATA HANDLING DETAIL

Six Privacy Controls We Keep Visible

Privacy is managed through ordinary account steps rather than hidden settings. Phone verification helps us connect the right person to the right account, while device and login records help identify unusual access.

Collection

We collect the information needed for account creation, phone verification, login activity and payment status. A request to open an account does not require us to collect unrelated profile details. The fields shown in the account path indicate what we need for that step.

Purpose

We use account data to authenticate you, maintain sessions, answer support questions and connect DANA, OVO, GoPay, QRIS, bank transfer or virtual account records with the correct account. We also use relevant signals to investigate unusual login or payment activity.

Cookies

Cookies can keep a browser session working between account pages and help us understand whether a login step has completed. You can adjust cookie controls in your browser. Blocking required cookies may prevent parts of the account and Privacy Policy access path from working.

Account security

Phone verification and account ownership checks help limit disclosure to the person connected with the account. We do not ask you to publish passwords, wallet PINs or security codes in a support message. Keep those credentials private when requesting help.

Retention

We retain account, security and payment records for as long as needed for the purposes explained in this policy, including support, dispute checks and operational obligations. Retention can differ by record type, and removal requests may not erase records that must be kept.

Changes

To request a correction, ask about stored data or raise a concern about processing, contact us through the account support route. Tell us the specific record or purpose involved. We verify your identity first, then explain the available action and any reason a limit applies.

Privacy Policy Answers For jogjatoto

The questions below focus on the privacy decisions you are most likely to consider before opening or using an account. Our answers describe the account, device and payment records involved in the jogjatoto Privacy Policy, without turning the page into a general platform description. If your situation is unusual, contact support with a verified account detail and we can direct the request to the relevant privacy process.

It covers personal details submitted during account creation, phone verification data, login and device information, cookie use, support messages and payment status records. It also explains why we use those details, how long certain records may remain and how you can ask about correction or handling.

Phone verification helps us connect account access with the contact detail you provide and reduces the chance of private account data being disclosed to the wrong person. We may use the verified contact when handling an ownership request, login concern or change to account details.

Yes. The Privacy Policy covers payment status information connected with DANA, OVO, GoPay and QRIS, as well as bank transfer and virtual account references where used. We use those records to match a payment event with the correct account and answer status questions.

Cookies can maintain a login session and help us recognise whether an account step has been completed. You can manage them in your mobile or desktop browser. If you block required cookies, account pages may not retain the session needed to move between verification and account areas.

You can contact us through the account support route and identify the detail you believe is incorrect. We first verify account ownership, then assess the requested change. Some records may need to remain available for security, payment checks, support history or other applicable obligations.

Retention depends on the type of record and the reason it was collected. Account, security and payment records may remain while needed for account servicing, dispute checks and operational obligations. When you ask, we can explain the relevant retention reason and whether a deletion request can proceed.

Access and eligibility depends on local law. Our Privacy Policy does not change that condition, and we may use account or location-related signals where needed to apply local access rules. Check the current account path and contact support if you need clarification about your circumstances.