Reference

kputoto Privacy Policy for Indonesia Accounts

DANA, OVO, GoPay and QRIS details stay tied to the account steps you choose, and our Privacy Policy explains what we collect, why we use it and how…

Account data clarityWallet record controlsIndonesia access terms
kputoto kputoto Privacy Policy for Indonesia Accounts
HELP ROUTES

Where To Ask About Privacy

A clear contact path matters when an account record looks unfamiliar or a wallet reference needs checking.

Account data request Ask us to locate the account data connected with your phone verification, login email or account step. We may request matching details before discussing private records.
Wallet record check For DANA, OVO, GoPay or QRIS questions, share the transaction reference and date shown in your receipt. We use those details to trace status without requesting your wallet password.
Policy contact route Use the support contact displayed inside your account when you want to ask about cookies, retention, correction or deletion. Keep the message limited to the Privacy Policy request.
SIX DATA CONTROLS

Six Controls Behind Your Account Data

We keep this policy practical by linking each data type to an account action you recognise. Phone verification, wallet matching and device signals serve different purposes, while cookies help remember selected settings.

Account creation

We use the contact details and phone verification step you submit to create and protect your account. If a detail changes, contact us through the signed-in support route for a correction request.

Payment matching

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference helps us match a transaction to your account. We do not need your wallet password to check that reference.

Cookie choices

Cookies can remember account settings and help us understand whether a page request belongs to an active session. Your browser controls can remove stored cookies, though some account steps may need repeating.

Device signals

We may record limited device and session signals to identify unusual login patterns and protect account access. These signals are handled for account safety rather than used to request private wallet credentials.

Retention period

We keep account, payment and support records only for the period needed for the stated purpose, account administration or legal duties. The applicable period can vary with the record type and local law.

Change requests

You can ask about inaccurate account data, request an explanation of a record or ask whether deletion is available. We verify the request before making a change to protect your account.

Privacy Policy Answers For Your Account

These Privacy Policy answers cover the questions we expect you to ask before opening an account or linking a local wallet. If your situation is not listed, use the account support route and refer to the specific record, device or payment reference involved.

It covers account details, phone verification, device signals, cookies, support messages and payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Phone verification helps connect your account to the contact detail you submitted and supports account protection. We may use the verification status when checking an access or correction request.

Yes. We may retain transaction references, dates and status details needed to reconcile DANA, QRIS and other supported routes. We do not need your wallet password for a status check.

You can contact us through the signed-in support route to ask about account data or request a correction. We first verify your identity and may limit a request where local law permits.

Cookies may remember session settings and help connect a page request with your active account. You can manage them in your browser, but removing them may require you to repeat account steps.

Retention depends on the type of record, account administration needs and applicable legal duties. The Privacy Policy explains that periods can differ for payment references, support messages and account details.

Use the support contact shown inside your account and describe the data, cookie or payment reference involved. Do not include passwords or complete wallet credentials in your message.