Reference

Privacy Policy for Your huntertoto Account

Your DANA, OVO, GoPay and QRIS details stay connected to the account steps that need them, while our Privacy Policy explains what we collect, why we use it…

Account dataWallet detailsCookie choicesPhone checks
huntertoto Privacy Policy for Your huntertoto Account
CONTACT PATHS

Three Ways To Ask About Privacy

A clear contact path matters when you want to understand a Privacy Policy request.

Account request Open the support route from your account area and tell us whether you need…
Wallet reference For DANA, OVO, GoPay or QRIS questions, include the payment reference and date rather…
Device detail If a cookie or phone check looks unfamiliar, tell us the device path, browser…
DATA PRACTICES

Six Controls Behind Data Care

We keep this policy practical by linking each data use to an account action, a device event or a payment status check.

Account records

We use phone verification before account access to connect the right person with the right profile, and we use account…

Payment matching

A DANA, OVO, GoPay or QRIS reference helps us match a wallet event with your account status without asking you…

Cookie controls

Cookies can support sign-in continuity and page settings on your browser.

Device signals

Browser type, device path and connection details may help us spot an unusual account access pattern or investigate why a…

Retention choices

We keep records only for the operational, security or legal purpose connected to them.

Change requests

You can request access, correction or removal of eligible personal data by using the account support route and confirming enough…

Privacy Policy Questions, Answered

These Privacy Policy answers address the account, wallet and device questions you may search before opening access. We keep each response tied to a real huntertoto step, from phone verification to a DANA reference or a browser cookie choice, so you know what to prepare before contacting us.

It covers account details, phone verification, device and browser signals, cookies, payment references and requests to access, correct or remove eligible personal data where local law permits.

Yes. The Privacy Policy explains how DANA and QRIS references can help match a wallet event with your account status. Never send a wallet PIN or full security credential in a request.

Phone verification helps connect account access with the correct profile and can help us investigate an unfamiliar sign-in. The Privacy Policy describes this use as part of account protection.

Use the support route inside your account, state that your request concerns the Privacy Policy, and provide the phone number or account detail needed to locate your record.

You can request a correction through account support. Include the inaccurate field and the correct detail; we may ask for an account check before changing a phone or wallet-related record.

Cookies may support sign-in continuity, saved page settings and technical checks. You can change cookie choices through your browser settings, although some account steps may then behave differently.

Yes. It applies when you reach the account and lobby from a phone or tablet, including browser, device and verification records created during that mobile access path.