Reference

Privacy Policy for Your wahoki Account

wahoki Privacy Policy explains how we handle the details connected with your account, device, cookies and payment status.

Account dataWallet statusCookie choicesPolicy requests
wahoki Privacy Policy for Your wahoki Account
HELP WITH YOUR DATA

Get Policy Help Before Account Access

A clear support route helps you ask about Privacy Policy matters without guessing which account step to use. We can direct questions about a phone verification record, a wallet status entry or a cookie choice to the relevant account path. If a payment receipt from QRIS or DANA needs checking, keep the receipt reference and the account detail used for the transaction. Contact us through the support path shown on wahoki, and describe the request clearly so we can locate the correct record.

Team online

Account questions

If you want to know why we request a phone verification step, contact support from the account path shown on wahoki. Include the account identifier you use and the page where the question appeared. We will explain the relevant Privacy Policy purpose without asking you to share an account password.

Wallet records

For a DANA, OVO, GoPay or QRIS status question, send the payment reference and approximate transaction date through our support path. We use those details to locate the related record. Do not send a wallet PIN or password. Our reply can clarify what payment data is linked to your account.

Policy requests

You can ask us to explain, correct or remove eligible personal data through the contact route displayed on wahoki. State whether your request concerns cookies, account access, device data or a payment record. We may ask for account verification before making a change, so the request reaches the right account.

HOW WE HANDLE RECORDS

Your Privacy Choices Across Devices

Privacy Policy choices should remain understandable whether you open wahoki on a phone, tablet or desktop.

Account security

We use account details and phone verification to help confirm an access request belongs to you. Keep your login details private and avoid saving them on a shared phone. If access looks unfamiliar, contact support through the account route and describe the device or sign-in concern without sending your password.

Cookie controls

Cookies can remember settings and help us understand which page needs to load after you move from account access to the lobby. Your browser provides controls for clearing or blocking cookies. Some policy-related account functions may respond differently after those settings change, so check the page again before sending a request.

Device signals

When you use a mobile browser, we may receive technical signals such as browser type, device details and connection events. These signals help us investigate failed access or a wallet status mismatch. They do not replace the account details needed for a phone verification request or a data correction.

Payment records

A payment record can include the selected rail, amount reference, account link and status needed to reconcile a receipt. For QRIS, DANA, OVO or GoPay questions, we use the transaction reference to find the relevant event. Bank transfer and virtual account records may follow a separate matching step.

Retention periods

We retain account, support and payment records only for the period needed for the stated purpose, account security, dispute handling or a legal requirement. The exact period can depend on the record and local rules. Ask support which retention question applies, and we will explain the available process.

Change requests

You can request a correction to eligible account or contact details, ask how a record is used, or request removal where applicable. Send the request through the policy contact route and identify the affected account step. We may verify ownership first, then explain any limit created by local law.

Privacy Policy Answers for wahoki

These Privacy Policy answers focus on the account, device and payment questions you may search before using wahoki. We keep the wording practical: what we collect, why a phone step appears, how cookies affect a mobile browser, and how to ask about a record. If your situation involves access or eligibility, it depends on local law, so the policy contact route remains the right place for a case-specific response.

The wahoki Privacy Policy covers account details, phone verification, device and browser signals, cookies, support messages and payment status records. It explains why we use each category, how those records support account access, and how you can ask about correction, removal or the handling of an eligible record.

We may use phone verification to confirm that an account access request belongs to you and to reduce mistaken account changes. The step can appear before account access or a policy request. If you need clarification, contact support through the account path and do not send your password.

Yes. The Privacy Policy covers payment status and references connected with DANA, OVO, GoPay and QRIS when those details are used to match an account transaction. Bank transfer and virtual account records can follow the same policy purpose, with a separate matching step.

Cookies can remember browser settings and help a page continue from account access to a requested lobby or policy screen. You can clear or block them in your browser. After changing cookie settings, some account functions may behave differently, so check the page before submitting a request.

You can ask us to explain, correct or provide eligible account data through the policy contact route shown on wahoki. Identify the account and the record involved, such as a phone detail, cookie matter or payment reference. We may verify ownership before responding or changing the record.

We keep records for the time needed for their stated purpose, account security, payment reconciliation, dispute handling or a legal requirement. The period can differ between account, support and payment records. Ask support about the category involved, and we will explain the applicable retention process where local law permits.

Use the support or policy contact route displayed on wahoki and describe your question in clear terms. Include the account identifier or payment reference only when relevant, and never include a password or wallet PIN. We can route questions about access, cookies, device signals and payment records.