Reference

gem188 Privacy Policy for Your Account

Our Privacy Policy explains what we collect when you open a gem188 account, use the mobile lobby, or check DANA, OVO, GoPay and QRIS status.

Clear data purposesWallet record handlingAccount access choicesCookie controls
gem188 gem188 Privacy Policy for Your Account
CONTACT PATHS

Get Privacy Policy Help Near Your Account

A clear contact path helps you act on this Privacy Policy without searching through unrelated pages. When you ask about personal data, include the phone number linked to your account and the relevant receipt or login date. Our support route can then locate the right record, explain the next step and direct you to the appropriate account process. You can reach that route from the account area, including when you are in Makassar or elsewhere in Indonesia.

Team online

Account data request

Use the support route shown in your account to ask what personal data is linked to your phone number. We may ask for an account step to confirm that the request comes from you.

Wallet record question

For a DANA, OVO, GoPay or QRIS record, include the receipt reference and approximate time. This lets us separate your payment details from another account before discussing the record.

Access concern

If a login or verification check appears unfamiliar, contact us through the account support path and pause further attempts. We use the account history and device record to assess the concern.

DATA PRACTICE

What We Do With Your Personal Data

We keep this policy practical: each data category has a purpose tied to account access, payment tracing or security.

Account creation

When you open an account, we collect the details needed to create your profile and complete phone verification. We use those details to connect later login activity with the correct account.

Wallet matching

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us match a payment event to your account. We do not treat an unmatched receipt as proof of ownership.

Cookie choices

Cookies can remember a session and help us understand whether a sign-in step has been completed. You can adjust cookie settings in your browser, though some account functions may then need another login.

Device security

We may record device type, browser details, approximate network data and login time to identify unusual access. If you change phones, a fresh verification step may be requested before account access.

Retention period

We keep account, payment and support records for the period needed to operate the service, resolve disputes and meet applicable obligations. When that need ends, records are deleted or separated from direct identifiers.

Change requests

To request correction, access or deletion of eligible personal data, contact us through the account support path. State the requested change clearly, and we will explain identity checks and any lawful limits.

Privacy Policy Answers for gem188

These Privacy Policy answers address the searches we hear most often before an account is opened. They explain account records, payment references, cookies, device checks and requests for access or correction, so you can decide what to share and how to contact us.

It covers account details, phone verification, wallet and bank references, device signals, cookies, login history and support messages. It also explains why we use, retain and protect those records.

We use your phone number to create and verify your account, connect sign-in activity to the correct profile and help prevent an unfamiliar person from discussing your records.

Yes. The policy covers payment references connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. We use those references to trace status and resolve mismatches.

Contact us through the support route shown in your account and ask for an account data request. Include your linked phone number; we may complete an identity check before responding.

Yes, where the request is legally available. Tell support which detail is incorrect and provide the relevant account step or record. We will explain verification and any retention requirement.

Cookies can keep your login session active and help identify completed verification steps. You can change browser cookie settings, but disabling them may require repeated login or affect account access.

We retain account, payment and support records while they are needed for service operation, dispute handling, security and applicable obligations. After that need ends, we delete or de-identify them.