Reference

hoki 70 Privacy Policy for Your Account

Our Privacy Policy explains how we handle the account details, device signals and wallet records connected with hoki 70.

Account clarityWallet statusDevice controlsPolicy access
hoki 70 hoki 70 Privacy Policy for Your Account
DIRECT POLICY HELP

Privacy Policy Help for Account Questions

A clear contact path helps you act on this Privacy Policy instead of searching through account screens.

Account access Ask us to explain a phone-verification record or sign-in event. We may request account details to confirm that the Privacy Policy request comes from the person connected with the profile.
Wallet status If DANA, OVO, GoPay or QRIS shows an unexpected status, send the transaction reference through support. We check the account record without asking you to share a wallet PIN.
Policy requests Use support to ask about stored data, request a correction or ask how long a record is retained. We reply with the next account-verification step when one is needed.
SIX DATA PRACTICES

Six Practical Privacy Policy Commitments

We keep this policy practical by linking each data practice to an account action you can recognise.

Data we collect

We may collect your contact details, phone-verification result, sign-in timestamps, device information, security events and payment references needed to operate and protect your account.

Cookie choices

Session cookies help keep your account connected while you move from login to the lobby. Browser settings can restrict cookies, although some account functions may then need another sign-in.

Account security

We use phone verification, sign-in records and security checks to reduce unauthorised access. Never send us your password, wallet PIN or one-time code when requesting Privacy Policy help.

Payment matching

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference helps us match a receipt with your account and investigate a status question without storing unnecessary wallet credentials.

Retention periods

We retain account, security and transaction records only for the period needed for account support, fraud checks, dispute handling and legal duties, then apply deletion or access controls.

Your changes

You can ask us to correct inaccurate account details, explain stored records or address a data concern through support. We may verify your identity before changing or releasing information.

Privacy Policy Questions Before Account Access

These Privacy Policy answers focus on the questions you may have before creating an account on hoki 70. We cover phone verification, mobile browsing, wallet references, cookies, correction requests and deletion questions in plain terms. If your situation is different, contact support with the account detail needed to locate the record, and remember that access depends on local law.

It covers account details, phone verification, sign-in activity, device signals, cookies, support records and payment references connected with your use of the service where local law permits.

Phone verification helps us connect account access with the correct person, protect sign-ins and investigate unusual activity. We may retain the verification result as part of account security records.

Yes. The Privacy Policy covers transaction references and status details for DANA, OVO, GoPay and QRIS. We use them to match receipts and investigate payment questions, not to request your wallet PIN.

We may record browser or device details, sign-in time and security events when you use a mobile browser or desktop path. This supports session continuity, account protection and access checks.

Contact support with the account detail connected to the incorrect record and describe the change. We may confirm your identity first, then explain whether the correction can be made.

Yes. Ask support about a particular account, payment or security record. We explain the applicable retention reason and handle deletion or restriction requests where local law permits.

Use our account support path for questions about stored data, cookies, phone verification or wallet status. Include a transaction reference when relevant, while keeping passwords and one-time codes private.