Reference

Privacy Policy Before Your First Login

Your account, wallet, and lobby activity sit under one Privacy Policy before you open an account with exa303.

DANA receipt handlingOVO wallet recordsGoPay request logsQRIS scan data
exa303 Privacy Policy Before Your First Login
CONTACT ROUTES

Three Routes for Privacy Requests

A privacy request should not disappear into a general queue. We route correction, access, deletion, cookie, and wallet-record questions through live chat, WhatsApp, and our privacy inbox, then link the request to your account ID. Have your username, registered phone number, and last DANA, OVO, GoPay, or QRIS reference ready so we can verify you without exposing the record to the wrong person.

Team online

Live chat privacy desk

Use live chat from 09:00-23:00 WIB when you need a quick account-data check. We ask for your username and registered phone number before discussing login sessions, wallet receipts, or cookie settings.

WhatsApp case check

Send a privacy request through WhatsApp only after you reach us from the account menu. We will never ask for your password, and we may mask DANA, OVO, GoPay, or QRIS references during verification.

Privacy inbox route

For correction or deletion requests that need documents, use the privacy inbox named in your account help panel. Attach only the files we ask for, then keep the ticket number for follow-up.

ACCOUNT CARE

Six Controls Around Your Data

Privacy work inside the wallet is handled by limiting access, checking requests against account records, and keeping an audit trail when staff view sensitive data.

Data minimisation

Account setup asks for the details needed to identify you, keep your wallet connected, and secure sign-in. If a field is not needed for those steps, we aim to avoid collecting it.

Payment record matching

DANA, OVO, GoPay, and QRIS references are used to match wallet requests with account activity. Support may see masked references, while full proof is limited to staff handling payment and privacy checks.

Cookie controls

Cookies keep your session active and remember basic display choices. If you clear them, we may ask you to sign in again or repeat a phone check before account data appears.

Device sessions

Use Account > Security > Active Sessions to see recent device access. If a phone or browser looks unfamiliar, close that session and contact us so we can help secure the account.

Retention triggers

We keep records while they are needed for account security, wallet disputes, privacy requests, and legal duties. When a record no longer has a valid purpose, we narrow access or remove it.

Change requests

You can ask us to correct spelling, phone, or document data connected to your account. We verify the request first, because changing the wrong record could expose your wallet history.

Seven Privacy Questions Before You Join

These answers focus on the privacy choices you make before and after you join. They cover the account fields we ask for, how payment references are handled, what cookies do, and how to reach us when you want access, correction, or deletion. Keep your account ID ready when you contact us. If a request touches eligibility, our answer will say where local law permits.

We collect the details needed to create and protect the account, such as username, registered phone number, password security data, device session, and wallet references. We use them for access, account safety, and privacy support.

Payment references are matched to your wallet activity so support can trace a request without exposing more than needed. Masked receipts may appear in tickets; full proof is limited to staff assigned to payment and privacy checks.

Yes. Send the request through live chat, WhatsApp, or the privacy inbox in your account help panel. We verify your identity first, then update the record or explain why a change cannot be made.

We keep records while they are needed for security, dispute handling, privacy requests, or legal duties. After that, we reduce access, archive only what is required, or remove the record from active tools.

Cookies may remember session state and basic lobby preferences, including whether you opened Live Casino or Sportsbook. They do not let support read your password, and you can clear them through your browser settings.

Access is limited to staff whose role requires the record, such as account verification, wallet checks, or privacy support. We use ticket trails so sensitive views can be traced and questioned if needed.

Start with live chat during 09:00-23:00 WIB, or use WhatsApp from the account menu. For document changes or deletion requests, use the privacy inbox shown in your help panel and keep the ticket number.