Reference

valohoki Privacy Policy, Clearly Explained

The valohoki Privacy Policy explains what we collect when you open an account, sign in, use DANA or QRIS, and contact our support desk.

Account dataWallet recordsDevice accessCookie choices
valohoki valohoki Privacy Policy, Clearly Explained
CONTACT THE DESK

Get Privacy Help Beside Your Account

A clear contact path matters when a privacy question appears during sign-in or payment checking. Our support route sits close to the account and cashier areas, so you can explain a data concern without repeating the whole account journey. Include the phone or account reference linked to your request, but never send a password, wallet PIN, or one-time security code. We use the details you provide to locate the right record and answer the specific Privacy Policy question.

Team online

Account access request

Ask us to confirm which account details we hold by using the support path beside your account area. We may ask for phone verification or another account check before sharing personal records, so a request reaches the correct account.

Wallet data question

If a DANA, OVO, GoPay, QRIS, bank transfer, or virtual account reference looks unfamiliar, send the transaction date and account reference through support. Remove wallet PINs and security codes from screenshots before sending anything.

Correction or deletion

Use the same support route to request a correction or deletion of personal details. We assess the request against account security, open payment checks, and records that we may need to keep under applicable local requirements.

HOW WE HANDLE DATA

Privacy Controls From Login To Retention

We keep the Privacy Policy practical by linking each control to a point in your account journey.

Account security

Phone verification is used before account access so we can connect a sign-in with the correct account. We do not ask you to disclose a password or wallet PIN to our support team, and you should keep those credentials private.

Payment matching

For DANA, OVO, GoPay, QRIS, bank transfer, and virtual account activity, we use transaction references and status details to match funds with your account. This helps us investigate a receipt without requesting unnecessary wallet credentials.

Device signals

When you move from a mobile browser to desktop, we may record device, browser, session, and security signals linked to access. These details help identify unusual activity; they are not used to read unrelated files or messages on your device.

Cookies

Cookies can keep a sign-in session active, remember a language or display choice, and help us understand whether a page loads correctly. You can manage cookies through your browser, although disabling some may affect account access or saved preferences.

Retention periods

We retain account, security, support, and payment records only for as long as needed for the stated purpose, account protection, dispute handling, or legal duties. When a record is no longer needed, our process removes or de-identifies it.

Requesting changes

To request access, correction, or deletion, contact us through the account support path and describe the record involved. We may verify your phone or account details first, then explain any limit that applies to an open security or payment matter.

Answers About valohoki Privacy Policy

These Privacy Policy answers address the questions you may have before opening an account from Indonesia. We focus on the records created by account access, local payment checks, cookies, device use, and support requests. If your situation involves eligibility or access, that outcome depends on local law. For a record-specific answer, use the account support path and provide only the details needed to identify your request.

The valohoki Privacy Policy covers account details, phone verification, sign-in and device records, cookies, support messages, and payment references. It explains why we use each category, how we protect it, how long we may retain it, and how you can request access or correction.

We use phone verification to connect account access with the correct person and reduce the risk of an unauthorised sign-in. It can also help us confirm an access or data request. Never send your password, wallet PIN, or one-time security code to support.

Yes. The Privacy Policy covers transaction references and status details connected with DANA, OVO, GoPay, QRIS, bank transfer, and virtual account payments. We use those records to match activity with your account and investigate a receipt without requesting your wallet credentials.

Use the support path beside your account area and ask for an access request. Include the account phone reference and describe the records you need. We may complete a phone or account check before responding, because personal data must go to the correct account holder.

You can request a correction or deletion through the account support path. We assess the request against security checks, payment disputes, and retention duties. If a record must remain for one of those reasons, we will explain the applicable limit under the Privacy Policy.

Cookies can preserve a sign-in session, remember a display preference, and help us check page performance on your mobile browser. You can manage them in your browser settings. Turning off certain cookies may prevent account access or remove saved choices.

Yes. Account eligibility and access depends on local law. The Privacy Policy explains our data handling, but it does not change local requirements. If you are unsure whether access is available in your area, check the applicable local rules before opening an account.