Reference

Open Your tigerhoki Privacy Policy Path

Our Privacy Policy shows how tigerhoki handles the details you provide for account access, phone verification and wallet records.

Account clarityWallet recordsCookie choicesAccess requests
tigerhoki.xyz page image
REQUEST HELP DIRECTLY

Contact Us About Your Policy Rights

A clear contact path matters when you want to ask what we hold or correct an account detail. Start from the support route inside your account and include the phone number linked to your profile, the relevant date and the request you want handled. For a DANA or QRIS question, attach the receipt reference rather than your wallet password. We use those details to locate the right record without asking for unnecessary secrets.

Team online

Account data request

Ask for the account details connected to your phone verification record. We may check account ownership before responding, so keep your registered phone available and never send a password.

Wallet status check

For DANA, OVO, GoPay or QRIS records, share the transaction reference and date through the account support route. We can then match the payment status without requesting wallet credentials.

Correction request

If your contact detail or account record needs correction, state the exact field and preferred value. We review the request against phone verification before applying an account change.

HOW RECORDS ARE HANDLED

Explore tigerhoki Data Handling Steps

We keep this Privacy Policy practical by linking each data use to an account task you can recognise.

Account details

We use your account details to create access, connect phone verification and respond to requests made from your profile. Provide accurate contact details so a correction request can be matched to the right account.

Cookie controls

Cookies can retain session settings and help the account path load correctly on mobile or desktop. Clearing browser cookies may remove a session preference and require you to complete sign-in again.

Device signals

We may record device type, browser details and sign-in time to spot unusual access. Moving from an Android phone to a desktop can create a new security event without exposing your wallet password.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity can produce references used to match a cashier status. These references help resolve a receipt question without storing wallet login credentials.

Retention requests

We keep records only while needed for account operation, payment reconciliation, security checks or a legal request. You can ask us to explain a retained record and the reason it remains available.

Policy changes

If this Privacy Policy changes, we will present the revised wording on the policy page. Check the page before opening an account or changing payment details, especially when access depends on local law.

Find Privacy Policy Answers Before Access

These Privacy Policy questions focus on the account steps and local payment records you are most likely to ask about before opening access. Each answer points to a practical action, from checking cookies on your phone to sending a verified request through the account support route. If your location or eligibility is unclear, access depends on local law.

It covers account details, phone verification, sign-in events, cookies, device signals and payment references from DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity.

Phone verification helps connect an account request to the correct profile and supports account recovery or correction checks. We do not need your wallet password to confirm a payment reference.

No. Our policy distinguishes wallet credentials from transaction references. DANA and QRIS records may show a reference, date and status used for reconciliation, but your wallet password stays with the wallet provider.

Use the support route inside your account and identify the phone number linked to your profile. State that you want a data access request, then complete any ownership check we ask for.

Yes. Send the exact field that is wrong and the replacement value through the account support route. We compare the request with phone verification before changing a contact or profile record.

Cookies can remember session settings and help the policy page or account path load as expected. Clearing them may remove saved preferences and require a fresh sign-in on your mobile browser.

We retain payment references while they are needed for account operation, reconciliation, security checks or a legal request. You can ask why a particular DANA, QRIS or bank reference remains stored.