Reference

Privacy Policy for Your Wallet Path

Your kumutoto Privacy Policy explains how we handle the account details and wallet signals connected with DANA, OVO, GoPay and QRIS.

Account dataWallet statusDevice accessYour choices
kumutoto Privacy Policy for Your Wallet Path
HELP ROUTE

Get Privacy Help Beside Your Account

A clear support path helps when a Privacy Policy question touches login, payment status or an account record. Open the support link inside your account and describe the specific request, such as a wrong phone detail, an unfamiliar device entry or a DANA receipt that does not match the displayed status. We use the details you send to locate the relevant account record and keep the exchange focused.

Team online

Account support link

Use the support link after login for a Privacy Policy request. Include your account contact detail and the issue type, but do not send a password, wallet PIN or full payment credential in the message.

Wallet status check

If QRIS, OVO or GoPay status looks different from your receipt, tell us the reference, date and displayed result. We can compare the payment record without asking you to repeat sensitive wallet credentials.

Access concern

For an unfamiliar login or device, use the account help route promptly and describe when you noticed it. We may ask for an account verification step before discussing private records or changing contact details.

DATA PRACTICE

Data Choices Across Your kumutoto Account

Privacy is handled through practical account controls rather than broad promises. We separate login and verification details from payment references, limit internal access to records needed for a stated task and use…

Account details

We may hold the name, phone detail and verification result you provide when opening an account. These fields help us connect the correct person to the correct account path and respond to a data request.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account records may show a reference, amount status and time. We use those fields to reconcile a transaction, not to collect your wallet PIN.

Cookies and sessions

Browser storage can keep your login session and selected settings working between pages. You can clear or restrict cookies in your browser, though doing so may require another account verification step.

Device security

We may record device type, browser details, approximate access timing and security events. These signals help us spot an unusual sign-in before discussing account data or changing a phone detail.

Retention period

We keep account and payment records while they support security, account service or a lawful request. When the purpose ends, we remove them or separate them from direct account identifiers where practical.

Change request

Ask us to access, correct or clarify your stored details through the account support link. State the requested change clearly; we may verify account ownership before releasing or editing private data.

Privacy Policy Questions Indonesia Searchers Ask

These answers cover the account and payment questions we hear most often before someone opens an account. They focus on the Privacy Policy, including device records, wallet references, cookies, retention and the route for requesting a change. If your question concerns a particular login or receipt, use the support link after securing your account.

The kumutoto Privacy Policy covers account details, verification results, device and session signals, cookie settings, payment references and support messages. It also explains why we use each category, how long records may remain and how you can request access or correction.

No. Our Privacy Policy separates wallet credentials from the account record. We may receive a DANA or QRIS reference, status and time to match a transaction, but you should never send a wallet PIN or full secret credential through support.

Device type, browser details and login timing help us identify unusual account access. If you open the lobby on mobile and later use desktop, those security signals may appear in the account record without giving us access to unrelated files on either device.

Use the support link inside your account and state which detail is wrong, such as a phone number or verification record. We may ask you to complete an account check before changing private data, so the request reaches the correct account.

We keep payment references while they are needed for account security, transaction matching, service operation or a lawful request. After that purpose ends, we remove the record or separate it from direct account identifiers where practical.

You can clear or restrict cookies through your browser settings. Cookies may keep a session active or remember a preference, so changing them can lead to another login or verification step when you return to your account.

Open the account support link and ask for the specific data category you want to access, correct or clarify. Availability and eligibility depend on local law, and we may verify account ownership before discussing records connected with Indonesia access.