Reference

galaxyslot Privacy Policy for Your Account

Our Privacy Policy explains what galaxyslot collects when you open an account, sign in from a mobile device, browse Baccarat or Slots, and use DANA, OVO, GoPay or…

Account dataWallet recordsCookie choicesSecurity checks
galaxyslot galaxyslot Privacy Policy for Your Account
HELP WITH REQUESTS

Ask About Your Privacy Policy Rights

A clear support route helps you act on this Privacy Policy without searching through account screens. Use the support link beside the cashier path when a wallet reference, login record or profile detail needs checking. Tell us the account email or phone reference you use, and we will direct the request to the right policy process.

Team online

Access request

Ask us what account, device and wallet-reference data is associated with your galaxyslot profile. Include the contact detail used at account creation so we can verify the request.

Correction path

If your phone detail or account record is outdated, contact support from the account area. We may ask for a verification step before changing personal data tied to wallet activity.

Receipt question

For a DANA, OVO, GoPay or QRIS receipt question, send the transaction reference rather than a wallet password. We use that reference to check status while limiting unnecessary exposure.

HANDLING YOUR DATA

How We Apply This Privacy Policy

We keep this policy practical: you should know why a record exists, how we protect it and which route can change it.

Data collection

We collect account details you submit, device and sign-in signals, page actions needed to load requested lobby areas, and payment references used to reconcile DANA, OVO, GoPay, QRIS or bank activity.

Cookie controls

Cookies can remember a session, language choice or security state on your phone or desktop browser. You can adjust browser controls, although restricted cookies may interrupt sign-in or policy-request steps.

Account security

We use sign-in checks and phone verification before account access or sensitive changes. Never send a password or wallet PIN through support; provide only the reference needed for the request.

Retention period

We retain records only for operational, security, dispute or legal needs described in this Privacy Policy. When a record is no longer needed, our process removes it or separates it from direct account identification.

Change request

You may request correction, access or deletion of eligible personal details. We first confirm that the request comes from the account holder, then explain any record that must remain for a stated reason.

Policy contact

Send a Privacy Policy question through the support link beside the cashier path. Include your account contact detail and a short description, while leaving wallet passwords and full payment credentials out.

Privacy Policy Questions From Indonesia

These answers address the Privacy Policy searches we hear most often before an account is opened or a wallet is connected. If your situation is not covered, use the support path with the smallest amount of personal detail needed to identify your request.

It covers details you submit during account creation, sign-in and phone verification, together with device signals and records needed to secure your profile, answer support requests and meet applicable legal needs.

Yes. We may keep payment references and status details for DANA, OVO, GoPay and QRIS, plus bank transfer or virtual account references, so a receipt can be matched without requesting your wallet password.

Use the support link beside the cashier path and state that you want an account-data request. Provide the account email or phone reference used at creation so we can verify ownership before responding.

You can ask us to correct eligible profile details, such as an outdated phone reference. We may require phone verification or another account check before changing data connected to wallet records.

Cookies may keep your session, language choice and security state available on a mobile browser. Browser controls can restrict them, but sign-in, policy requests or account screens may then need extra steps.

We retain records for operational, security, dispute or legal needs described in the Privacy Policy. When those needs end, we remove the record or separate it from direct account identification.

You can request deletion of eligible data through support. We verify the account holder first and explain if a payment, security or legal record must remain for a defined purpose.