Reference

Privacy Policy For Your Account

hokiraja88 Privacy Policy explains how we collect, use, store and protect the details connected with your account, including login records, device signals and wallet references for DANA, OVO…

Account dataWallet referencesCookie choicesAccess depends on local law
Explore Our Lobby Read FAQ
hokiraja88 Privacy Policy For Your Account
CONTACT PATHS

Ask About Your Privacy Policy

A direct support path helps you ask what data we hold, why a record appears, or how to request a correction.

Data access request Ask us for the personal data connected with your account and the purpose attached to each category. Include your registered contact detail so we can distinguish your request from a message about another account or an unrelated Baccarat session.
Correction request If your name, phone detail or contact record is inaccurate, tell us which field needs attention and what the correct value should be. We may ask for an account check before changing information used for login or payment-status matching.
Wallet status question For a DANA, OVO, GoPay or QRIS reference that looks unfamiliar, send the transaction date, amount reference and account contact detail through support. Never include your wallet PIN; we only need enough context to trace the record safely.
HANDLING DETAILS

How We Apply This Policy

Privacy is handled through account controls rather than vague promises. We limit internal access to records needed for account service, payment checks, security work or a response to you.

Account security

We use login events, device signals and account verification details to help detect access that does not look like your usual activity. If a sign-in needs checking, we may ask you to confirm the registered phone or email before discussing account data.

Payment references

Our records can contain a payment rail, reference number, status and time for DANA, OVO, GoPay, QRIS, virtual account or bank transfer activity. We use those details to reconcile your account, while sensitive wallet credentials stay with the payment provider.

Device behaviour

Opening the lobby on a mobile browser may create technical records such as browser type, device settings, session time and error events. These details help us keep the account path working when you move between login, wallet status and a game page.

Cookies and storage

Cookies or similar storage can remember a session choice, protect account access and help us understand a page error. You can manage browser storage through your device settings, although removing it may require another login or affect saved privacy choices.

Retention period

We retain account, support and payment-reference records only for as long as needed for the stated service, security checks, dispute handling or legal duties that apply. When a record is no longer needed, we remove it or separate it from direct account identifiers.

Policy changes

If we change how personal data is handled, we will place the revised Privacy Policy on this page and show the updated date or notice where practical. Please check this page before using a new account feature or submitting another privacy request.

Privacy Policy Questions From Indonesia

These Privacy Policy answers cover the account questions we expect you to ask before sharing contact details or linking a payment route. They explain how to reach us, what may appear in account records and what happens when you access hokiraja88 from a mobile device. For eligibility or regional access, the applicable position depends on local law.

It covers account details, verification records, device and session data, cookies, support messages and payment references. It also explains why we use those records for login security, account service, payment-status checks and legal duties. It does not replace rules that apply where local law permits access.

We may collect contact details supplied during account creation, verification information, login events, device signals, cookie choices, support correspondence and transaction references. A DANA or QRIS reference can identify a payment event, but we do not need your wallet PIN to check that event.

Use the support route shown in your account area and ask for a data access request. Include the phone or email attached to your profile, describe the records you want, and avoid sending passwords or wallet credentials. We may verify account ownership before releasing account-related details.

Yes, you can ask us to correct an inaccurate name, phone detail or contact record through support. State the field and the replacement value clearly. We may request an account check because changes to login or payment-status information can affect access and transaction matching.

A phone, tablet or desktop can create technical records such as browser type, session time, device settings and error events. We use them to protect sign-in activity, diagnose page problems and recognise unusual access. Clearing browser storage may require you to sign in again.

We keep account, support and payment-reference records for the period needed for service delivery, security checks, dispute handling or applicable legal duties. After that need ends, we remove the record or separate it from direct identifiers where practical.

Yes. The policy explains how we handle the reference, status, time and account connection for DANA, GoPay, OVO, QRIS, virtual account and bank transfer activity. Sensitive wallet credentials remain with the relevant payment service, and you should never send a wallet PIN to support.

Related Pages

hokiraja88 Indonesia bolaklik1 FAQ Baccarat gso777