Reference

Open the hoki arena Privacy Policy

hoki arena Privacy Policy explains how we collect, use and protect the details connected with your account, including phone verification and wallet activity.

Account dataWallet recordsCookie choicesContact requests
hoki arena Open the hoki arena Privacy Policy
PRIVACY CONTACT

Ask for help with a policy request

A clear support route helps you act on the Privacy Policy instead of searching through account screens. Sign in first when you can, because the account path lets us match a request to the right record and avoid exposing details to the wrong person. If you cannot sign in, provide only the minimum details requested through the contact route shown on the site. We can then assess access, correction, deletion or wallet-record questions under the policy and local requirements.

Team online

Account access

If your phone verification or sign-in step blocks a Privacy Policy request, use the account support path shown on the site. We may ask for account details needed to confirm that the request comes from you before discussing stored records.

Wallet records

For a DANA, OVO, GoPay or QRIS privacy question, include the relevant transaction reference rather than sending a full wallet statement. This gives us a precise route to check the record while limiting the personal data shared in your message.

Policy changes

To request a correction or ask how long a record is kept, use the policy contact route connected to your account area. We will explain the next step, any identity check required and whether local law affects the request.

DATA PRACTICE

Browse the safeguards behind this policy

We handle privacy as an account operation, not as a paragraph hidden after checkout. Phone verification helps us separate your account from an attempted sign-in, while session controls help keep a mobile…

Phone verification

Before account access, we use the phone verification step to connect the sign-in attempt with your account details. This helps us investigate an access dispute without treating an unfamiliar device as automatically belonging to you.

Mobile sessions

When you move from login to a lobby on a phone, session data supports that path. Closing the browser or signing out can end the active session; avoid saving account details on a shared device where another person could reopen them.

Cookie controls

Cookies can remember the technical state needed for account pages and help us identify faults between login and the wallet screen. Your browser provides controls for removing or restricting cookies, although some account functions may then require another sign-in.

Wallet matching

A payment reference from DANA, OVO, GoPay, QRIS, bank transfer or a virtual account may be linked to your account record for status checks. We use the match to investigate the request, not to ask you for unrelated wallet credentials.

Retention checks

We keep account, support and payment records only for operational, security or legal reasons that apply to the service. When a retention reason ends, we assess whether the record can be removed, anonymised or kept in a restricted form.

Your requests

You may ask for access to personal data, correction of an inaccurate detail or clarification about deletion and retention. Send the request through the site support path, and we may verify your account before giving a record-specific response.

Find answers about Privacy Policy

These Privacy Policy answers cover the account and wallet questions you are most likely to have before opening an account. They explain the practical route for access, correction, cookies, payment references and contact requests, while recognising that some handling depends on local law. For a record-specific answer, use the support path connected to your account.

The hoki arena Privacy Policy covers account details, phone verification, sign-in sessions, cookies, support messages and payment references. It explains why we use those records, how we protect them, when retention may apply and how you can request access or correction.

When you use DANA or QRIS, we may retain a payment reference, status and related account details so a transaction question can be checked. We do not need your wallet password for that route. A record request can be made through account support.

Yes, you can ask for access to personal data linked with your account by using the support route shown on the site. We may first confirm your identity through the account or phone verification step, then explain the scope and response process.

Send a correction request through the policy contact path and identify the detail that is wrong. We may ask you to sign in or complete phone verification before changing an account record. Requests involving wallet records may need the relevant payment reference.

Yes, cookies or similar session data may support login, account navigation and error checks on a mobile browser. You can manage cookies in your browser settings, but restricting them may require repeated sign-ins or affect pages that depend on an active session.

Retention depends on the type of record and the operational, security or legal reason for keeping it. DANA, OVO, GoPay, QRIS, bank transfer and virtual account references may remain while a status or account matter needs review, subject to local requirements.

Use the support contact route connected to your account area and state whether you want access, correction, deletion clarification or retention details. If you cannot sign in, follow the contact option displayed on the site and share only the requested minimum information.