Reference

topan hoki Privacy Policy For Your Data

topan hoki Privacy Policy explains how we handle your account, phone verification, device activity and payment records before you enter the lobby.

Account dataWallet recordsDevice controlsPrivacy requests
topan hoki topan hoki Privacy Policy For Your Data
REQUEST SUPPORT

Get Help With Privacy Requests

You do not need to search through account screens to ask about your personal data.

Account help channel Use our account-help channel for access, correction or deletion questions.
Payment record check If a DANA, OVO, GoPay or QRIS reference concerns you, send the receipt reference…
Device access query For an unfamiliar mobile-browser session, tell us the device path and approximate sign-in time.
DATA PRACTICES

Your Device And Account Safeguards

We treat this policy as an operating process, not a page kept apart from account work.

Account data

We collect account details needed to create and maintain your access, including contact data and phone verification results. We use these records to match requests to the correct account.

Cookies and sessions

Cookies and session signals help remember a browser path, keep account pages working and detect unusual sign-ins. You can manage browser cookie settings, though some account functions may then need another check.

Wallet references

Payment records may show DANA, OVO, GoPay, QRIS, bank transfer or virtual account references. We use these entries to trace status without asking you for a wallet password.

Mobile protection

A mobile browser can create device and session signals when you sign in. We compare those signals with account activity to flag access that does not fit your usual account path.

Retention periods

We retain each data category only for the period needed for account service, dispute handling, security checks or legal duties. After that period, we remove or separate it where practical.

Change requests

To request access, correction or removal, contact support through the account-help channel. State the requested change clearly; ownership checks protect your account before any record is altered.

Privacy Policy Questions For Your Account

These answers cover the privacy questions you are most likely to ask before opening an account or using a mobile browser. They explain our data choices in plain English, with examples linked to phone verification, local wallets and account access where local law permits.

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

We use phone verification to confirm that an account request belongs to the person controlling the registered contact. It also helps us protect access when a new device or browser session appears.

No. We may retain a payment reference, method name and status for account records, but you should never send a DANA, OVO, GoPay or QRIS wallet password to support.

Contact our account-help channel with your account identifier and ask for a data access request. We first confirm ownership, then explain the available records and any lawful reason a category cannot be supplied.

Yes. Send the incorrect field, the replacement value and your account identifier through support. We may request phone verification or another ownership check before changing account, contact or payment-reference data.

Cookies and session signals help keep your account path active and identify unusual access. You can adjust browser settings, but disabling some cookies may require extra sign-ins or limit account-page functions.

Service access and some data rights depend on local law. We apply the relevant process where local law permits, and support can explain which request path applies to your account.