Reference

Privacy Policy for Your hoki678 Account

hoki678 Privacy Policy explains how we collect, use and protect details connected with your account, device and wallet activity.

Account dataWallet recordsCookie choicesAccess requests
hoki678 Privacy Policy for Your hoki678 Account
CONTACT ROUTES

Use Support When Privacy Questions Stall

A clear contact route helps you ask about the Privacy Policy without sending unnecessary account details. Tell us the email or phone identifier linked to your account, describe the request, and include only the payment reference needed for a status check. We may ask for an account step or verification detail before discussing private records. For an account opened from Makassar or another Indonesian location, the same privacy request path applies, with access depending on local law.

Team online

Account privacy request

Ask us to explain the personal details connected with your account, including phone verification and login records. We will use the account identifier you provide to locate the request and may ask you to confirm ownership before sharing account-specific material.

Wallet record question

If a DANA, OVO, GoPay or QRIS reference appears in your account history, send the date and reference shown to you. Do not send a wallet PIN. We can check the linked record and explain which details came from the payment route.

Access or correction help

When you cannot reach the account privacy settings, contact us with your verified phone or email identifier. We can explain the next account step, record a correction request or clarify why additional checks are needed before changing private data.

DATA PRACTICE

Explore How We Handle Private Details

We handle privacy as an account process rather than a broad promise. Your details are used for the purpose that brought you to us, such as account access, phone verification, wallet reconciliation…

Account details

We may hold your name or account identifier, verified phone or email, sign-in events and requested account changes. These details help us recognise your account and respond to a Privacy Policy request. Use accurate contact details so ownership checks do not fail.

Payment references

A wallet or bank record can contain a reference, amount, route and status needed to match an account action. DANA, OVO, GoPay, QRIS, BCA, BRI, Mandiri and BNI may appear in this context. We do not ask for your wallet PIN.

Cookies and devices

Cookies can remember a session, support security checks and show whether a page has loaded correctly. Your browser settings can remove or restrict them, although some account steps may then require another sign-in or device check.

Account security

Phone verification, sign-in records and device signals help us detect unusual account access. Keep your verification code private, sign out on a shared device and contact support if a login event does not match your activity.

Retention approach

We retain records only for as long as needed for the stated account, security, dispute or legal purpose, subject to applicable requirements. When a retention period ends, records are deleted, anonymised or isolated from routine account use.

Changes and questions

You can ask what data we hold, request a correction or ask how a record is used through the privacy contact route. We may need identity confirmation, and access to the service depends on local law and the result of required checks.

Browse Privacy Policy Answers

These Privacy Policy answers focus on the account questions Indonesian customers usually raise before opening access. We explain what to send, what we may verify and how payment or device records fit into the process. If your situation is not covered, use the contact route above and avoid including passwords, wallet PINs or full payment credentials.

The hoki678 Privacy Policy covers account details, phone verification, sign-in events, device signals, cookies, wallet references, security checks, retention and privacy requests. It applies when you create or access an account, contact us or use an account action where local law permits.

These payment routes can create account-linked references showing a requested action or status. We may use the reference to reconcile a record, but we do not need your wallet PIN. The payment provider may separately process information under its own privacy terms.

Yes. Send a correction request through the privacy contact route using the verified phone or email linked to your account. Explain which detail is wrong and what it should say. We may confirm ownership before changing it, especially after a phone verification step.

Ask us for the account data connected with your verified identifier and describe the records you need, such as login events or payment references. We may request an ownership check before responding. Some records may be limited where disclosure would affect security or legal duties.

Yes. Cookies and similar device signals can support session continuity, security checks and page loading on your phone or desktop. You can restrict them in browser settings, but doing so may require another login or device confirmation during account access.

We keep information for the period needed for the purpose collected, including account access, security, dispute handling or applicable legal requirements. After that period, we delete, anonymise or isolate it from routine use. A retention question can be sent through the privacy route.

Yes. Provide your verified account identifier, the privacy question and only the payment reference needed for context. Do not send a password, wallet PIN or full credential. We may ask for another ownership check before discussing private account records.