Reference

Privacy Policy for Your Account

Your privacy choices sit beside the same account steps you use to enter Sugar Rush, Andar Bahar and Aviator, so you can see what data we ask for…

DANA wallet contextOVO privacy checksGoPay account matchingQRIS payment records
mabar69slot Privacy Policy for Your Account
CONTACT PATHS

Privacy Help Through Real Channels

Privacy questions need a clear path, not a vague inbox. We keep account privacy requests inside support channels you already use, then route them to the team that can check wallet records, login events and profile fields. Include your registered phone or email, the payment rail involved and the approximate time of the action so we can locate the correct record without asking for extra personal data.

Team online

Live chat privacy queue

Use live chat from your logged-in account between 09:00 and 23:00 WIB for privacy questions tied to login, profile edits or wallet activity. We verify you inside the session before discussing account data.

Email request record

Email support when you need a written trail for access, correction or deletion requests. Add your registered email, DANA, OVO, GoPay or QRIS reference if relevant, and we will respond with the next account step.

Wallet privacy check

For payment-data questions, send the wallet method, transaction time and displayed status. We compare the record against our payment log without asking for your PIN, password or full wallet credentials.

DATA HANDLING

Account Privacy Behind the Lobby

Your account privacy is handled through the same operating checks that protect access to live casino tables, slots, sportsbook markets and fishing rooms.

Registration fields

When you open an account, we ask for practical details such as contact data, login credentials and wallet matching fields. These help us identify you during support checks and keep account changes traceable.

Device and session signals

We record browser type, device pattern, IP range and login time to spot account access that does not fit your normal use. This supports privacy protection without reading content outside our site.

Cookie use

Cookies keep your session active, remember basic preferences and help us detect repeated failed logins. If you clear them, you may need to sign in again and repeat normal account verification.

Payment references

For DANA, OVO, GoPay and QRIS, we keep reference numbers, timestamps, wallet status and account match results. We do not ask for your wallet PIN or store full access credentials.

Retention checks

We keep account, wallet and support records only for operational, security and legal needs. When a record is no longer needed, we remove it from active tools or restrict access to archived storage.

Correction requests

If your profile data is wrong, contact support with the field you want changed and proof that matches your account. We confirm the request before updating details that affect login or wallet access.

Answers About Your Privacy Choices

These answers focus on the privacy questions we receive most often from Indonesia account holders: what data is collected, how wallet records are handled, how long records stay with us and how to request changes. If your question involves a specific transaction, login or game session, send the time and account identifier so support can check the right privacy record.

We collect contact details, login credentials, account settings, device signals and wallet matching data. These fields help us create your profile, protect access and answer privacy questions without asking for unrelated documents.

We keep payment references, timestamps and status results so we can trace wallet questions and account matches. We do not ask for your wallet PIN, and we do not store full wallet login credentials.

Yes. Contact support with the field that needs correction and the account proof we request. We verify the request first because profile changes can affect login recovery, wallet matching and privacy records.

Cookies help keep your session active, remember basic site choices and detect repeated failed logins. You can clear cookies in your browser, then sign in again and complete normal account checks.

Only support staff with the right role can access chat records needed for your request. We use those records to answer account, wallet and privacy questions, then keep them under retention controls.

Send a deletion request through logged-in chat or email support. We review account status, wallet records and legal retention needs, then confirm what can be removed or restricted from active tools.

We may use IP range and device signals to assess access where local law permits. This helps us apply regional access rules and investigate unusual sign-ins without collecting precise location beyond operational need.