Reference

Privacy clarity before you open an account

Your account data, device checks and DANA, OVO, GoPay or QRIS payment records are handled under this Privacy Policy before you reach Live Dealer Lobby, Mystical Spirits or…

Account data useCookie choicesDANA and QRIS recordsSupport contact paths

Browse the lobby Read FAQ

What this policy covers for you

golden189 Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Your privacy matters from the first account step, so this policy covers the data you give us when you create a golden189 account, verify access, contact support, use DANA, OVO, GoPay or QRIS, and move between mobile browser and larger-screen sessions. We collect only the account,

1
device, payment-reference and service records needed to run your wallet, protect access, answer your messages, and meet legal or payment processing duties that depend on local law. If you open the lobby from Denpasar, the same privacy controls apply as long as the account route is
2
available where local law permits. We do not sell your personal data. When we use partners for payment routing, fraud checks, analytics or support tools, we limit their role to the service task and keep internal access restricted by role.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

CONTACT ROUTES

Reach us about your privacy choices

Privacy requests should reach the team that can check your account record, not a general inbox with no context.

Live chat Use live chat in the account menu from 10:00 to 22:00 WIB for privacy questions that need quick routing. We will confirm your account handle before discussing cookies, payment references or device access.

Email request Send privacy requests from the email linked to your account when you need a written trail. Include your username, request type and payment rail used, such as DANA or GoPay, but never send your password.

Account centre Open the profile area, choose security, then check active sessions if you want to manage device access. That path helps you spot older mobile sessions before asking us to refresh stored access data.

ACCOUNT SAFETY

How we handle privacy day to day

Practical privacy work happens inside the account flow, not only on this page. We log payment references, support messages, cookie choices and device signals so we can operate the wallet and keep…

Account data

We collect the details you enter during account creation, such as username, contact channel and security answers. These records help us verify you when you ask to update contact data or recover access.

Payment records

DANA, OVO, GoPay and QRIS records are stored as transaction references, time stamps and account links. We use them to reconcile wallet activity and answer payment privacy questions without storing card-style secrets.

Cookies

Cookies help keep your session open, remember display choices and measure page errors. You can clear them through your browser settings, but doing so may require a fresh login on your next visit.

Device checks

We record device type, browser version, IP range and login time when you access the account. These signals help us flag unusual access and support your request to close stale sessions.

Retention

We keep account, payment and support records only for operational, dispute, security and legal needs. When a record is no longer needed, we remove it or detach it from account identity where practical.

Change requests

You can ask us to correct contact data, export account records or review stored session details. We verify the request first, then respond through the channel already linked to your account.

Your privacy questions answered

Use these answers when you want to know how privacy works before or after you open an account. They focus on account records, payment references, cookies, security checks and how to reach us. If your question involves local eligibility or access rules, our answer may depend on local law and may require extra account verification.

We collect the account details you enter, contact channel, login records, device signals and security-related activity. If you use DANA, OVO, GoPay or QRIS, we also keep payment references needed for wallet reconciliation.

We keep payment references so your wallet can be matched with the correct transaction, refund query or support case. The record normally includes timing, rail name, account link and status, not private app credentials.

Yes, you can request a copy through email or live chat after we verify your account. We may ask for your username, linked email and a masked recent payment reference before sending account records.

Cookies remember your session, display choices and page stability signals. You can clear them in your browser settings, but you may need to log in again and repeat security checks after clearing stored cookies.

We use outside service providers for payment routing, analytics, support tools and security checks. They receive only the data needed for that service task, and we do not sell your personal data.

Contact us from the current linked channel or through the account centre. We will verify your identity first, then update the contact detail so future privacy messages reach the right place.

We keep records for operational, security, dispute and legal needs, then remove or detach them when they are no longer required. Retention may vary by record type and depends on local law.

Privacy clarity before you open an account

Reach us about your privacy choices

How we handle privacy day to day

Account data

Payment records

Cookies

Device checks

Retention

Change requests

Your privacy questions answered

01 What personal data does golden189 collect when I open an account?

02 Why do you keep DANA, OVO, GoPay and QRIS records?

03 Can I ask for a copy of my account data?

04 How do cookies affect my privacy on mobile browser?

05 Do you share my data with outside service providers?

06 How do I correct the phone number or email on my account?

07 How long do you keep my account and support records?

Related Pages