Reference

konohatoto Privacy Policy for Your Account

Our Privacy Policy explains what we collect when you open an account, sign in through a mobile browser, or check wallet status for DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesContact requests
konohatoto konohatoto Privacy Policy for Your Account
CONTACT PATHS

Privacy Questions Beside Your Account Help

A clear contact path helps when your Privacy Policy question concerns a phone check, wallet status or an unfamiliar sign-in. Use the support route displayed on our site and include the account detail needed to locate your request, without sending a full wallet password or one-time code. We use the same path for correction, deletion and access requests where local law permits.

Team online

Account access

Tell us if your phone verification or sign-in record looks wrong. We will ask for enough account detail to locate the matter, while keeping passwords and one-time codes out of the request.

Wallet records

For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account question, share the date and reference shown in your account. Do not send your wallet PIN or full payment credentials.

Privacy requests

Ask through our listed account support route to see, correct or remove eligible personal data. We may verify account ownership before making a change, so another person cannot alter your records.

DATA PRACTICES

What We Do With Your Account Data

We keep this policy practical by linking each data use to an account action: phone verification supports sign-in, device signals help identify unusual access, and payment references help reconcile wallet status.

Data we collect

We may receive your account details, phone verification result, sign-in time, device information and payment reference. We collect these details when they are needed to open access, protect an account or answer a support request.

Cookies and storage

Cookies and similar browser storage can keep a session open, remember a basic preference and help us understand whether a page loads correctly. You can manage browser settings, although some account steps may then need repeating.

Account security

We use phone verification before account access and may compare sign-in signals with earlier activity. If a device or location looks unusual, we may pause a step and ask you to confirm ownership.

Payment matching

A wallet or bank reference helps us match a deposit or status enquiry to your account. We do not need your wallet PIN for that check, and you should never place a one-time code in a support message.

Retention periods

We keep account, security and payment records for as long as operational or legal needs require. When a record is no longer needed, we remove it or separate it from direct account identifiers.

Changing your details

If your phone number, contact detail or another account field is inaccurate, contact us through the listed support route. We verify the request first, then correct eligible records and explain any required limit.

Privacy Policy Answers for Indonesia Accounts

These answers focus on the questions you may have before opening an account or checking a wallet record. Our Privacy Policy applies to account access across mobile and desktop, and the support route can help when a question concerns your personal data. Service eligibility depends on local law.

It covers account details, phone verification, sign-in activity, device signals, cookies, payment references and support messages connected with your use of our site. It also explains retention and requests to change eligible data.

Phone verification helps us connect account access with the right person and reduce unauthorised sign-ins. We may use the result during account opening or when a device shows an unusual access pattern.

Yes. The Privacy Policy covers references connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. These references help us match a wallet status or payment question to your account.

Use the account support route shown on our site and ask for a personal data access request. We may verify account ownership before responding, and the response scope can depend on local law.

You can ask us to correct an inaccurate phone number, contact detail or other eligible account field. Send the request through support, provide the relevant account context, and complete any ownership check we require.

We retain payment references, security records and account details only while operational or legal needs require them. After that period, we remove the data or separate it from direct account identifiers.

Yes. Contact support with the browser or device path you used, and we can explain the relevant cookie purpose. Browser settings can limit storage, but some sign-in or phone verification steps may repeat.