Reference

hore168 Privacy Policy for Your Account

hore168 Privacy Policy explains what we collect when you open an account, sign in on mobile, use DANA or QRIS, and contact our support desk.

Clear data purposesWallet record contextAccount access choices
hore168 hore168 Privacy Policy for Your Account
CONTACT PATHS

Privacy Help Beside Your Account Steps

A clear contact path helps when a privacy request meets an account or wallet question. Start from the support route connected to your hore168 account and include the phone number used for verification, the relevant payment reference and the request you want handled. If you are in Makassar, the same privacy process applies as for other supported Indonesian locations.

Team online

Account access request

Ask us to confirm the personal data connected with your account after phone verification. We may request account details to make sure the request comes from you, then explain the available access path.

Wallet record question

For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account query, include the payment reference and date. We use those details to locate the record without asking for your wallet PIN.

Correction or removal

Send a correction or removal request through our account-help route. Tell us which data is wrong or no longer needed, and we will check legal, security and transaction-record duties before replying.

DATA HANDLING

Six Practical Privacy Controls

Our privacy process follows the real steps you take: phone verification, mobile sign-in, wallet matching and support contact.

Account data collected

We may collect your phone number, account profile details, sign-in history, device type, browser signals and support messages. These records help us verify access and respond to a request about your account.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account records can contain a reference, amount status and time. We use this payment context for reconciliation, receipt checks and account support.

Cookies and sessions

Cookies and similar session tools help keep your sign-in active, remember basic preferences and detect unusual device changes. You can manage browser cookies, though some account steps may then need to be repeated.

Account security

Phone verification, sign-in records and device signals help us identify access that does not match your usual account pattern. Never send us a wallet PIN or password when asking for privacy help.

Retention period

We retain account, payment and support records only for the period needed for service security, dispute checks and legal duties. When a record is no longer required, our handling process addresses its removal.

Changing your data

You can ask us to correct contact details or question a data use through the support path. Include your verified phone number and a precise request so we can locate the right record.

Privacy Policy Questions for hore168

These Privacy Policy answers focus on the account actions Indonesian customers ask about most: verification, payment records, cookies, device access and requests to change stored data. If your question is not listed, use the account-help route with a clear description and the relevant reference.

The hore168 Privacy Policy covers account details, phone verification, device and browser signals, cookies, support messages, game or sports session records, and payment references linked to DANA, OVO, GoPay or QRIS.

Yes. Send an account access request through our support path using the phone number connected to your profile. We may verify your identity before explaining which records can be supplied under applicable requirements.

Phone verification helps connect an account request to the correct person and reduces unauthorised access. It can also help us investigate a sign-in or wallet-status question without requesting your private wallet PIN.

Yes. The Privacy Policy covers references and status details connected with QRIS, DANA, OVO, GoPay, bank transfer and virtual account activity when those records are needed for reconciliation or support.

Cookies support sign-in sessions, basic preferences and security checks when you open the lobby on a phone or desktop. Browser controls can remove them, but account verification or repeated sign-in may follow.

We keep different records for periods linked to account security, payment reconciliation, support handling and legal duties. When those purposes end, we assess the record for removal under our internal process.

Yes. Where local law permits, ask us to correct inaccurate account data through the support route. Include the affected field and verified contact detail; we check identity and any record-keeping duty before acting.