Reference

autohoki Privacy Policy For Your Account

autohoki explains how we collect, use and protect the account details behind your lobby access, including phone verification and wallet status for DANA, OVO, GoPay and QRIS.

Account clarityWallet privacyCookie choicesLocal access
autohoki autohoki Privacy Policy For Your Account
PRIVACY HELP PATH

Where To Ask About Your Data

A clear contact route helps when you need to check a phone number, payment reference or stored account detail. Start from the support route linked to your autohoki account and describe the request in plain English. Include the account identifier and relevant wallet rail, but do not send a password or full payment credential.

Team online

Account request

Ask us to confirm the account data connected with your verified phone step. We may request enough account detail to distinguish your request from another person’s request.

Wallet question

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, include the date and reference shown in your receipt so we can trace the correct status.

Access concern

If sign-in or device access stalls, contact support through the account path and explain what appeared on screen. Never share your password, verification code or private wallet PIN.

OUR DATA PRACTICE

What We Do With Account Details

Your privacy choices work best when the handling steps are visible. We separate account operations, payment matching, security checks and cookie activity so you can understand why a detail may be used.

Account records

We use your submitted account details to create access, complete the clear phone verification step and connect the correct profile with account activity. Please keep your contact details current.

Payment matching

A DANA, OVO, GoPay or QRIS reference helps us identify a payment event. Bank transfer and virtual account records may also be checked against your account before status changes are shown.

Device signals

When you sign in from a phone or desktop browser, we may record session and security signals used to recognise unusual access. We do not need your wallet PIN for this process.

Cookie controls

Cookies and similar browser storage can keep a session active or remember a setting. You can clear them through your browser controls, though signing in again may then be required.

Retention approach

We retain account, payment and security records only for the period needed for the stated service purpose, account protection, dispute handling or applicable legal duties.

Changes and requests

You can ask about access, correction, deletion where applicable or a change to your details through support. We may verify account ownership before making a change.

Privacy Policy Answers For autohoki

These answers address the account and device questions you are most likely to have before using the privacy controls. They also explain what to include when you contact us about a payment record, phone verification step or sign-in session.

It covers account details, phone verification, device and session signals, cookies, support requests and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity.

We use the verification step to create and protect your account, connect requests to the correct profile and help investigate access concerns. We do not ask you to disclose a private wallet PIN.

Yes. The policy covers payment references and status details linked to DANA, QRIS, OVO, GoPay, bank transfer and virtual account steps when those records are connected with your account.

We may handle browser, mobile device, session and security signals needed for sign-in protection and service operation. These signals help us assess unusual access without requiring your wallet password or PIN.

Use the account support path and state whether you want access, correction, deletion where applicable or another change. Include your account identifier, but leave out passwords, codes and full payment credentials.

We keep each category only as long as needed for its stated purpose, account security, payment questions, dispute handling or applicable legal duties. You can ask support about a particular record.

Access or eligibility depends on local law. Check the rules that apply where you are before opening an account, and contact support if you need help understanding a policy-related access question.