Reference

japritoto Privacy Policy for You

Our Privacy Policy explains how japritoto collects, uses and protects details connected with your account, including verification records and wallet activity through DANA, OVO, GoPay and QRIS.

Account clarityWallet recordsCookie choicesAccess requests
japritoto japritoto Privacy Policy for You
CONTACT ROUTES

Where To Ask About Privacy Policy

A clear contact path helps you correct a detail without exposing more data than needed. Use the account support route linked near the cashier area for questions about your Privacy Policy rights…

Account request Ask us to correct your name, phone number or account detail through the account support path. We may request a verification step before changing records tied to DANA, OVO, GoPay or QRIS activity.
Wallet enquiry For a privacy question about a deposit reference or status, share the date, rail and visible reference only. We use that limited detail to locate the record without asking for your wallet PIN.
Access concern If your sign-in or phone verification appears unusual, contact support from the account path and describe the device behaviour. We can review security events while keeping your password and payment credentials private.
DATA HANDLING

What Our Privacy Policy Covers

Your Privacy Policy rights work alongside practical account controls. We separate identity details from activity records where our systems allow, restrict internal access to staff who need it, and use security checks…

Account details

We collect details needed to create and maintain your account, including contact data and phone verification status. We use them to sign you in, send account messages and respond to Privacy Policy requests.

Wallet activity

DANA, OVO, GoPay and QRIS may create payment references visible in your account history. We use those references to reconcile status and investigate disputes, not to request your private wallet PIN.

Device signals

Your browser, phone type, session time and security signals can help us recognise unusual access. On mobile, these checks support the path from phone verification to the lobby without revealing your wallet secret.

Cookie controls

Cookies can retain sign-in preferences and help us understand which account pages load correctly. You can adjust browser cookie settings, although removing them may affect sign-in continuity and policy access.

Retention period

We keep account, support and transaction records only as long as needed for service, dispute handling, security checks or legal duties. The period can differ between a phone record and a payment reference.

Change requests

To request access, correction or removal, contact us through the account support route with the precise record involved. We verify ownership first and explain any restriction where local law permits.

Privacy Policy Answers For Your Account

These Privacy Policy answers cover the account steps Indonesian customers ask about most often. They explain what we collect, how wallet records are handled, how to request a change and what may happen when access depends on local law.

It covers account creation, phone verification, sign-in activity, cookies, support messages, device signals and wallet references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account routes.

We use phone verification to connect the correct person with an account, reduce unauthorised access and process sensitive changes. We do not need your wallet PIN to complete that account step.

Yes. The Privacy Policy explains how we use DANA and QRIS references, status details and timestamps for reconciliation, account support and security checks. A payment partner may also apply separate privacy terms.

Contact us through the account support path and state that you want an account-data access request. Include your account identifier, then complete the ownership check before we release or discuss the records.

Yes. Send a correction request through support, identify the inaccurate field and explain the needed change. We may verify your phone or account activity before editing details connected to wallet records.

Retention varies by record type. Account, security, support and transaction references may be kept for service, dispute handling or legal duties, with access depending on local law and the applicable request.

Use the account support route promptly, describe the device or sign-in event and avoid sending passwords or wallet PINs. We can review security signals and guide the next verification step where local law permits.