Reference

Open arus hoki Privacy Policy controls

Your arus hoki account data, wallet records, game-session markers and device checks sit under one Privacy Policy, giving you a clear view of what we collect before you…

Account data scopeWallet record useCookie controlsDevice checks
arus hoki Open arus hoki Privacy Policy controls
CONTACT ROUTES

Check privacy contact routes

Privacy requests need a direct path, not a generic mailbox queue. We handle data access, correction and removal questions through in-account chat, the Contact page form…

In-account chat Use the chat button after login for questions about stored account data, cookie settings…
Contact form Send privacy requests through the Contact page when you cannot reach the lobby.
WhatsApp support WhatsApp is available during 09:00-01:00 WIB for identity checks linked to privacy requests.
ACCOUNT SAFETY

Switch security settings with clear data choices

Privacy protection is part of the account flow, not an afterthought. We separate wallet references from login passwords, restrict staff access by role and log changes made to your profile.

Data scope

We ask for your phone number, login name, password and wallet reference during account setup. Those fields connect your profile to support checks without asking for extra personal data on every visit.

Payment metadata

For DANA, OVO, GoPay and QRIS, we store wallet references, timestamps and status codes needed to match account activity. We do not need your app PIN or full wallet access.

Cookie choices

Session cookies keep you logged in, while preference cookies remember language and device choices. You can clear them in your browser, then log in again for a fresh session.

Device security

Account > Security > Devices shows recent sessions by device type and region. If you see a phone you do not recognise, ask us to end that session.

Game activity records

When you open Baccarat, Aviator or Mega Fishing, we log session time, device type and account ID so support can check dispute requests without exposing wallet data to game rooms.

Retention and edits

We keep account and wallet logs while needed for operations, support cases and security checks. If data is no longer needed, we restrict access or remove it where our process allows.

Browse Privacy Policy answers

These questions cover the privacy issues you are most likely to search before opening an account or changing devices. We answer in practical terms: what we collect, why we keep it, how wallet rails appear in records and how you can ask for changes. If your question involves eligibility or account access, the answer depends on local law.

We collect the details needed to create and protect your profile: login name, phone number, password, wallet reference, IP region, device type and session records. We use them for account access, wallet checks and support responses.

No. For DANA, OVO, GoPay and QRIS, we keep transaction references, status codes and timestamps linked to your account. We never ask for app PINs, wallet passwords or access to your payment app.

Cookies help us keep your session active, remember device preferences and detect unusual login behaviour. You can clear browser cookies at any time, but you may need to log in again afterward.

Open Account > Security > Devices after login. You can see recent device sessions by type and region. If something looks wrong, contact support and we can help end that session.

Yes. Send a request through chat, the Contact page form or WhatsApp. We will confirm your login name, phone number and recent wallet rail before changing or removing data tied to your account.

We keep records while they are needed for account operations, security checks, support cases and wallet matching. When data is no longer needed, we restrict access or remove it where our process allows.

We share only the technical data needed to run sessions, such as account ID, game round reference and device status. Providers do not receive your DANA, OVO, GoPay or QRIS app credentials from us.