Reference

jogjatoto Privacy Policy: Your Data Path

One clear account path shows what we collect, why we use it, and how you can ask us to change or remove eligible details.

Account clarityWallet dataCookie choicesRequest access
jogjatoto jogjatoto Privacy Policy: Your Data Path
REQUEST ROUTES

Where to Ask About Privacy

A direct support path helps you ask about the Privacy Policy without explaining your issue repeatedly.

Account request Use the signed-in account route to ask for access, correction or deletion of eligible…
Wallet query For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference, send the…
Access problem If you cannot reach the account route, use the support link presented on the…
HANDLING DETAILS

Inside jogjatoto Data Controls

We keep the Privacy Policy practical by tying each data category to an account action.

Account records

We use the details entered during account opening to create access, send account-related notices and match your requests to the correct record. Before account access, phone verification may be required; this step also helps prevent disclosure to the wrong person.

Payment references

DANA, OVO, GoPay and QRIS can return a status or reference that helps us reconcile a cashier event. Bank transfer and virtual account records are handled in the same operational way. We do not ask for your wallet PIN or banking password.

Cookies and devices

Our mobile and desktop pages may use cookies for session continuity, language selection and basic page operation. Device and browser signals can help detect an unusual login. You can manage browser cookie settings, although some account functions may then require another login.

Account protection

We limit account discussions until the required identity check is complete. If a phone verification event, login pattern or device change needs checking, we may request details already linked to your account rather than asking for a wallet credential.

Retention timing

We keep personal and transaction-related records for the period needed to operate the account, settle disputes, investigate misuse or meet a legal requirement. When a record no longer serves one of those purposes, we remove it or use a form that no longer identifies you.

Change requests

You can ask us to correct inaccurate account data, explain a processing purpose, provide eligible records or remove details where local law permits. Send the request through account support, and we will describe any verification or lawful retention reason that affects the response.

Privacy Policy Questions for jogjatoto

These answers address the Privacy Policy questions you may have before opening an account or using the account route on a phone. We focus on the data most likely to appear in an Indonesian account flow: phone verification, wallet status, cookies, device access and payment references. If your situation is different, contact us through the support path shown on the site and avoid sending passwords.

The jogjatoto Privacy Policy covers account details, phone verification, login and device signals, cookies, support conversations, and payment references from DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. It also explains purposes, retention, security steps and requests available where local law permits.

We may use your phone number to create the account record, complete the phone verification step before access and help match an account request to you. The number can also support account notices. We do not need your wallet PIN, banking password or private wallet login.

Yes. The Privacy Policy covers the payment status and reference details connected with DANA and QRIS, as well as OVO, GoPay, bank transfer and virtual account records. These details help us match a cashier event, investigate a mismatch and answer a receipt question without requesting secret credentials.

Use the signed-in account support route and ask for an access copy under the Privacy Policy. Include your account identifier, not a wallet password. We may verify your identity before responding, and the information we can provide depends on local law and any lawful retention requirement.

You can request correction of inaccurate details or removal of eligible data through account support. We first confirm the request belongs to you. Some records may remain for dispute handling, security checks or legal duties; we will explain that reason where local law permits.

Cookies can keep a mobile browser session active, remember a language choice and support basic page operation. If you block or clear them, you may need to log in again and some account steps may not work as expected. The Privacy Policy explains these uses and choices.

We keep payment and login records only for operational needs, account security, dispute handling or legal duties. The period varies by record type and applicable rules. When a record is no longer needed, we remove it or change it so it no longer identifies you.