Reference

buahhoki Privacy Policy For Your Account

Our Privacy Policy explains what we collect when you open a buahhoki account, use the mobile lobby, or contact support about DANA, OVO, GoPay and QRIS status.

Clear data purposesCookie choicesAccount access controlsRequest a policy change
buahhoki buahhoki Privacy Policy For Your Account
HELP WITH PRIVACY

Get Help With Your Data Request

A clear support route helps you act on this Privacy Policy without guessing which team to contact.

Account corrections Ask us to amend a phone number, email detail or profile field through account…
Wallet status questions When a DANA, OVO, GoPay or QRIS status appears unclear, send the transaction reference…
Privacy requests For access, correction, deletion or processing questions, identify the account and state the action…
DATA HANDLING

What We Protect And Retain

Privacy controls work best when they follow the real account journey. We separate sign-in details from routine browsing signals, restrict account records to operational needs, and use verification before making a material…

Account data

Opening an account can involve a phone number, contact detail, verification result and sign-in history. We use those records to provide account access and identify an unusual attempt. Do not place passwords or private wallet credentials in a support message.

Device signals

A mobile or desktop connection may provide device type, browser details, language setting and technical logs. These signals help us maintain a session, diagnose a failed page and protect access. They are handled as service records, not as a public profile.

Cookies

Cookies can preserve your sign-in state and remember basic page preferences. Some are needed for the account path, while other measurement signals help us identify loading problems. You can manage cookies in your browser, although changing them may affect page access.

Payment records

A bank transfer, virtual account, DANA, OVO, GoPay or QRIS reference may be stored with status and timing details. We use this limited record to match a cashier event, investigate a missing update and respond to a payment question.

Security checks

Phone verification and sign-in records help us distinguish your account activity from an unfamiliar attempt. If access looks unusual, we may ask for an account step before changing details. This reduces the chance that another person can redirect account communication.

Retention requests

You can ask which personal records remain, request a correction, or ask whether deletion is available. We review the request against account, payment and legal needs, then explain the outcome. Access to the service depends on local law and applicable requirements.

Privacy Policy Answers For buahhoki

These Privacy Policy answers focus on the account actions you are most likely to search for before opening or using buahhoki. We keep the wording practical: what is collected, why a payment reference appears, how cookies affect a device, and where to send a request. If your situation is not listed, use the account support path and describe the specific record or action you want us to check.

The Privacy Policy covers data connected with your account, phone verification, sign-in activity, device access, cookies, payment status and support messages. It explains our purposes, retention approach, security steps and request path when you access the service from Indonesia.

We use your phone number for account identification and the verification step before account access or a material profile change. It helps us connect a support request to the correct account. We do not ask you to send a password in a message.

Yes. The Privacy Policy covers payment references and status details linked to DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. We use those records to trace an account event, check a receipt question and explain an unclear status.

Cookies can keep your account session active and remember basic page settings. Technical signals may also show whether the mobile or desktop page loaded correctly. You can manage cookies in your browser, but removing required cookies may interrupt sign-in or account navigation.

You can contact support through the account help path and request access to, or correction of, a personal record. State the account detail involved and the action requested. We may verify your identity before responding, and local requirements may affect the result.

We keep account, security, payment and support records for the period needed to operate the account, trace a transaction, investigate access or meet a legal requirement. Retention can differ by record type. You may ask us to explain why a specific record remains.

Use the account support route and label your request as a Privacy Policy question. Include the phone or contact detail associated with your account and avoid sending passwords or complete payment credentials. We will explain the next verification step and the available response.