Reference

aurhoki Privacy Policy In Plain English

The aurhoki Privacy Policy explains what we collect when you open an account, sign in from a mobile device, or use DANA, OVO, GoPay and QRIS.

Account dataWallet recordsDevice controlsYour contact rights
Explore our lobby Read FAQ
aurhoki aurhoki Privacy Policy In Plain English
CONTACT PATHS

Wallet Questions Need A Clear Route

A clear contact path helps when your account data or wallet record looks incorrect. Use the support contact shown on aurhoki to ask about a DANA receipt, an OVO or GoPay status, or a QRIS reference. Include your account identifier and the relevant transaction date, but never send a wallet PIN or full password. We use the details you provide only to locate and answer the policy request.

Team online

Account access

If phone verification does not match your account, contact support through the displayed account route. We can explain which details are required to check the login record without asking for your password.

Wallet record

For DANA, OVO, GoPay or QRIS questions, share the reference visible in your receipt. We compare that reference with the account record and explain what data was used for the status check.

Privacy request

Ask us to correct, export or clarify personal data through the listed support contact. We may ask for an account step or phone check before making changes to protect your account.

SECURITY DETAILS

Account Security From Login To Wallet

Privacy is practical at every account step, from the first phone check to a later wallet status request.

Account details

We use your submitted account details to create access, complete phone verification and answer support requests. The account path is kept separate from wallet credentials, so we do not ask for your DANA, OVO or GoPay passcode.

Payment references

A QRIS, bank transfer or virtual account reference helps us match a transaction to the correct account. We record the reference and status needed for reconciliation rather than collecting unnecessary wallet secrets.

Device signals

Browser type, device markers and sign-in time can help identify unusual access. If a phone or desktop path looks different, we may request another account check before discussing private records.

Cookie choices

Cookies support session continuity and selected account settings. You can manage browser cookie controls, although removing required cookies may interrupt sign-in or prevent a policy request from being linked to your account.

Retention period

We retain account, support and transaction records only for operational, security or legal needs described in the Privacy Policy. When a retention need ends, records are removed, restricted or de-identified where appropriate.

Change requests

You can ask us to correct account details, explain a data use or provide a copy of eligible records. We verify the requester first, then respond through the contact route connected to your account.

Privacy Policy Questions For Indonesia

These Privacy Policy answers cover the points you are most likely to check before opening an account. We keep the wording tied to real account actions, including phone verification, mobile sign-in and local wallet records. If your question is not listed, contact us through the support route shown on aurhoki and include only the details needed to locate your account.

The aurhoki Privacy Policy covers account details, phone verification, device signals, cookies, support messages and payment references from DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity.

Phone verification helps connect the right person to an account and reduces mistaken access. We may use the verification result when you sign in, request a data change or ask about a wallet record.

We do not need your DANA or GoPay wallet password for an account status check. We use the transaction reference and status supplied through the payment route to match activity with your account.

The Privacy Policy may cover browser type, device markers, session details and sign-in timing. These signals help us identify unusual account access and decide when another account check is needed.

Yes. Contact us through the displayed support route and request a copy, correction or explanation. We first verify the account connection, then handle the request using the data needed for that purpose.

We keep records for the operational, security or legal period described by the Privacy Policy. After that need ends, we remove, restrict or de-identify records where appropriate under applicable requirements.

Yes. Ask support to explain the cookies connected with session continuity or account settings. You can also adjust browser controls, though removing required cookies may interrupt sign-in or data-request handling.

Related Pages

aurhoki Indonesia FAQ The Dog House Megaways Access guide Baccarat