Reference

Privacy Policy for galaxi77 Account Access

Our Privacy Policy explains how galaxi77 handles the details you provide when opening an account, verifying your phone, entering the lobby and using DANA or QRIS.

Clear data purposesWallet record contextAccount request path
galaxi77 Privacy Policy for galaxi77 Account Access
HELP ROUTES

Get Policy Help Near Your Wallet

A clear support route helps when you want to ask about personal data rather than a game or account balance.

Account data request Ask our support team to confirm which account details we hold, including phone verification records and recent login references. We will use the account path to check your identity before discussing personal data.
Wallet record question For DANA, OVO, GoPay or QRIS questions, send the relevant receipt reference through the support route. We can trace the status record without asking you to reveal a wallet PIN or private wallet password.
Correction or removal If a detail is wrong, or you want to ask about retention, explain the requested change through account support. We will assess the request against account security, transaction records and local law before replying.
DATA PRACTICES

How galaxi77 Handles Account Data

We keep this policy practical: your data is connected to a defined account, payment or security purpose rather than collected without a reason.

Account details

We use your phone number and verification result to connect account access with the right record. Login events and device details help us investigate an unexpected sign-in without treating your wallet PIN as support data.

Cookies on web

Cookies can remember session settings and help the web path load correctly on your phone or desktop. You can clear browser cookies, although doing so may require another login and phone verification step.

Device signals

Our account checks may use device type, browser path and login timing to identify unusual access. These signals support account protection; they are not a request for files, contacts or your private wallet credentials.

Payment records

A DANA, QRIS, OVO, GoPay, bank transfer or virtual account reference can remain attached to the relevant account record. We use it to match receipts, answer status questions and investigate disputed activity.

Retention questions

You can ask our support route why a record remains stored and whether correction or removal is available. Some account, security or payment records may need to remain available when local law requires it.

Request identity

To protect your account, we may confirm your phone number or another account step before releasing personal data. Send requests through the signed-in support path, and avoid placing wallet PINs in the message.

Privacy Policy Answers Before Account Access

These Privacy Policy answers cover the points Indonesian account holders usually check first: what we collect, how wallet records are used, how cookies affect the web path and how to request a correction. They also explain why phone verification can appear before account access. If your question concerns a specific DANA, OVO, GoPay or QRIS reference, include that reference through support rather than posting private wallet credentials.

It covers account details, phone verification, login and device signals, cookies, support messages and payment references. It applies when you open or access an account and when you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account where local law permits.

We use phone verification to connect account access with the correct account holder and to investigate unusual sign-ins. The step may appear before entry to the lobby. If we cannot confirm the account details, access depends on local law and available security checks.

Yes. A DANA or QRIS reference, receipt detail and status event may be stored with the relevant account so we can match a payment question correctly. The same approach can apply to OVO, GoPay, bank transfer and virtual account records.

Cookies can keep a web session active, remember selected settings and help us identify an unexpected login. They may work on both phone and desktop browsers. Clearing them can sign you out or require phone verification when you return.

Yes. Send a correction request through the account support path and describe the field that is wrong. We may confirm your phone or another account step first, then check the request against security, payment records and local law.

Contact us through the signed-in support route and ask for an account data access request. Include the phone number linked to the account, but never include a wallet PIN. We will verify the request before explaining the records connected with you.

Retention depends on the type of record and its purpose. Phone verification, login, security and payment references may need to remain available for account protection, receipt matching or legal duties. Ask support for the retention reason linked to a specific record.